Hey,
with gridflow which webcam drivers are supported? i found that pwc and qc-usb are. i wanted to know whether uvc driver would be supported by gridflow.?
Sisil.
sisil mehta wrote:
Hey,
hi.
since this is really a non-dev issue, i excluded pd-dev for now...
with gridflow which webcam drivers are supported? i found that pwc and qc-usb are. i wanted to know whether uvc driver would be supported by gridflow.?
as matju has stated several times (in this thread), all drivers that speak v4l (aka: v4l1) are supported by gridflow. all drivers that only speak v4l2 are not natively supported by gf. however (as said before) you can use libv4l to add v4l2 support to v4l1 applications at runtime.
other than that, it is hard to make any anwers (as matju has pointed out): gf (and any other video-application) does not directly communicate with a driver (pwc, qc-usb,...) but with a middleware (the v4l*-protocol).
fgmansdr IOhannes
Hey, As you had mentioned i did use libv4l, and finally my cam -- logitech quickcam e2500 started working with camorama. However it still doesnt work with PD???? PD always crashes when i'm using the #camera-help.pd while selecting the cameraa input device. More detials posted in this thread: http://www.mail-archive.com/pd-list@iem.at/msg27734.html
Could there be an issue with the OS (ubuntu 9.04) or while configuring ?? I'm totally lost.
sisil On Thu, Aug 6, 2009 at 12:32 PM, IOhannes m zmoelnig zmoelnig@iem.atwrote:
sisil mehta wrote:
Hey,
hi.
since this is really a non-dev issue, i excluded pd-dev for now...
with gridflow which webcam drivers are supported? i found that pwc and qc-usb are. i wanted to know whether uvc driver would be supported by gridflow.?
as matju has stated several times (in this thread), all drivers that speak v4l (aka: v4l1) are supported by gridflow. all drivers that only speak v4l2 are not natively supported by gf. however (as said before) you can use libv4l to add v4l2 support to v4l1 applications at runtime.
other than that, it is hard to make any anwers (as matju has pointed out): gf (and any other video-application) does not directly communicate with a driver (pwc, qc-usb,...) but with a middleware (the v4l*-protocol).
fgmansdr IOhannes
Quoting "sisil mehta" sisilmet2000@gmail.com:
Hey, As you had mentioned i did use libv4l, and finally my cam -- logitech quickcam e2500 started working with camorama. However it still doesnt work
we're getting closer.
with PD???? PD always crashes when i'm using the #camera-help.pd while
please not that "GridFlow" is not "PD", nor is it the only way to
access a camera in Pd.
does the camera work with Gem or pdp?
if it works with Gem, you could use the Gem2GF bridge (which you have
turned off in your configuration process, btw)
Could there be an issue with the OS (ubuntu 9.04) or while configuring ?? I'm totally lost.
i don't think so.
just a wild guess: make sure that you don't use pwc-specific options
when using libv4l (read: have you turned off the "pwc" configuration
when compiling GF?)
This message was sent using IMP, the Internet Messaging Program.
Hey, I tired to run GEM examples using pd but pd always crashed irrespective of the examplle used. The error seen in the terminal was Segmentation fault. and running dmesg i saw : [18025.621428] pd[29961]: segfault at 2f0 ip b76ede26 sp bff87abc error 4 in libGL.so.1.2[b76ec000+5000] [18066.999632] pd[29993]: segfault at 2f0 ip b797ae26 sp bf822d7c error 4 in libGL.so.1.2[b7979000+5000] [18098.126229] pd[30026]: segfault at 2f0 ip b7683e26 sp bf81db4c error 4 in libGL.so.1.2[b7682000+5000] [18919.339953] pd[31217]: segfault at 2f0 ip b76f0e26 sp bfb886bc error 4 in libGL.so.1.2[b76ef000+5000]
So how do i fix this?
Sisil.
2009/8/7 zmoelnig@iem.at
Quoting "sisil mehta" sisilmet2000@gmail.com:
Hey,
As you had mentioned i did use libv4l, and finally my cam -- logitech quickcam e2500 started working with camorama. However it still doesnt work
we're getting closer.
with PD???? PD always crashes when i'm using the #camera-help.pd while
please not that "GridFlow" is not "PD", nor is it the only way to access a camera in Pd. does the camera work with Gem or pdp? if it works with Gem, you could use the Gem2GF bridge (which you have turned off in your configuration process, btw)
Could there be an issue with the OS (ubuntu 9.04) or while configuring ?? I'm totally lost.
i don't think so.
just a wild guess: make sure that you don't use pwc-specific options when using libv4l (read: have you turned off the "pwc" configuration when compiling GF?)
This message was sent using IMP, the Internet Messaging Program.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Quoting "sisil mehta" sisilmet2000@gmail.com:
Hey, I tired to run GEM examples using pd but pd always crashed irrespective of the examplle used. The error seen in the terminal was Segmentation fault. and running dmesg i saw : [18025.621428] pd[29961]: segfault at 2f0 ip b76ede26 sp bff87abc error 4 in libGL.so.1.2[b76ec000+5000] [18066.999632] pd[29993]: segfault at 2f0 ip b797ae26 sp bf822d7c error 4 in libGL.so.1.2[b7979000+5000] [18098.126229] pd[30026]: segfault at 2f0 ip b7683e26 sp bf81db4c error 4 in libGL.so.1.2[b7682000+5000] [18919.339953] pd[31217]: segfault at 2f0 ip b76f0e26 sp bfb886bc error 4 in libGL.so.1.2[b76ef000+5000]
the crash occurs in libGL, the openGL implementation installed on your system.
now Gem uses openGL to do pretty much everything (actually [pix_video]
could do without openGL, but you still need it to make Gem do
_anything_ for you)
in order to give you better advise, we need to know: which gfx-card do you use? which drivers? which Gem version?
mfgr. IOhannes
This message was sent using IMP, the Internet Messaging Program.
Hey, i'mm using ATI Radeon mobility 4570. I checked in the harddware drivers section and this is what i found:
No proprietary are in use on this system.
ATI/AMD proprietary FGLRX graphics driver (description....)
this driver is not activated.
after this i hit the activate button and downloaded the driver...it installed. and the driver now shows active.
PD still crahes when running any of gem's applications requiring a video. this is the error when i use dmesg::
pd[4519]: segfault at 4 ip b787c5dc sp bfaee8e0 error 6 in libstdc++.so.6.0.10[b77c3000+e4000] pd[4691]: segfault at b7b58824 ip b7f2bb64 sp bfa81bf4 error 7 in libpthread-2.9.so[b7f25000+15000]
Now?
Sisil.
2009/8/8 zmoelnig@iem.at
Quoting "sisil mehta" sisilmet2000@gmail.com:
Hey,
I tired to run GEM examples using pd but pd always crashed irrespective of the examplle used. The error seen in the terminal was Segmentation fault. and running dmesg i saw : [18025.621428] pd[29961]: segfault at 2f0 ip b76ede26 sp bff87abc error 4 in libGL.so.1.2[b76ec000+5000] [18066.999632] pd[29993]: segfault at 2f0 ip b797ae26 sp bf822d7c error 4 in libGL.so.1.2[b7979000+5000] [18098.126229] pd[30026]: segfault at 2f0 ip b7683e26 sp bf81db4c error 4 in libGL.so.1.2[b7682000+5000] [18919.339953] pd[31217]: segfault at 2f0 ip b76f0e26 sp bfb886bc error 4 in libGL.so.1.2[b76ef000+5000]
the crash occurs in libGL, the openGL implementation installed on your system. now Gem uses openGL to do pretty much everything (actually [pix_video] could do without openGL, but you still need it to make Gem do _anything_ for you)
in order to give you better advise, we need to know: which gfx-card do you use? which drivers? which Gem version?
mfgr. IOhannes
This message was sent using IMP, the Internet Messaging Program.
On Sat, 15 Aug 2009, sisil mehta wrote:
i'mm using ATI Radeon mobility 4570. I checked in the harddware drivers section and this is what i found: No proprietary are in use on this system. ATI/AMD proprietary FGLRX graphics driver (description....) this driver is not activated.
What does it mean "this driver is not activated" ? Because it looks a lot like one of the top two "bugs" of GridFlow, which is a strange interaction between GridFlow, C++, and an ATI driver (the OpenGL part thereof). Claude found the solution:
http://lists.artengine.ca/pipermail/gridflow-dev/2008-October/000455.html
But I would very much like to know how to fix this permanently, because you can't make people have to jump through hoops that much to get something running.
(The other top two "bug" of GridFlow is that it uses a lot of stack for speed, yet the default maximum stack size is dangerously low).
pd[4519]: segfault at 4 ip b787c5dc sp bfaee8e0 error 6 in libstdc++.so.6.0.10[b77c3000+e4000] pd[4691]: segfault at b7b58824 ip b7f2bb64 sp bfa81bf4 error 7 in libpthread-2.9.so[b7f25000+15000] Now?
With gdb you can get a better (more detailed) backtrace. I never used dmesg for those things.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
sisil mehta wrote:
Hey, i'mm using ATI Radeon mobility 4570. I checked in the harddware drivers section and this is what i found:
No proprietary are in use on this system.
ATI/AMD proprietary FGLRX graphics driver (description....)
this driver is not activated.
after this i hit the activate button and downloaded the driver...it installed. and the driver now shows active.
PD still crahes when running any of gem's applications requiring a video. this is the error when i use dmesg::
hmm, i'm not sure whether i understand this.
- does it mean, that Pd/Gem _always_ crashes (when opening a window, or
closing a window, or...) OR
- does it mean that Pd/Gem crashes as soon as you use anything which
involves pixes (coming from e.g. [pix_image], [pix_film] and/or [pix_video]) OR
- does it mean that Pd/Gem crashes as soon as you use [pix_video]?
in the first case, try running "glxgears" from the cmd-line and see what it tells you (it is part of the mesa-utils patckage)
pd[4519]: segfault at 4 ip b787c5dc sp bfaee8e0 error 6 in libstdc++.so.6.0.10[b77c3000+e4000] pd[4691]: segfault at b7b58824 ip b7f2bb64 sp bfa81bf4 error 7 in libpthread-2.9.so http://libpthread-2.9.so[b7f25000+15000]
in the last case, try running Pd/Gem from the cmdline and see what it tells you before crashing. try adding "-stderr" to also catch the messages to the Pd-console try adding "-verbose" to get additional messages.
fgmasdr IOhannes
On Fri, 7 Aug 2009, zmoelnig@iem.at wrote:
please not that "GridFlow" is not "PD", nor is it the only way to access a camera in Pd. does the camera work with Gem or pdp? if it works with Gem, you could use the Gem2GF bridge (which you have turned off in your configuration process, btw)
What's really weird is that it's not just about trying with this or that video-library, it's also about which video-libraries are loaded. I had to remove -lib Gem sometimes. I don't know what to do about the ATI driver bug/conflict. Do you have any idea how this could be solved permanently? I think it's something like the definition of the C++ keyword «throw» is partially contained in the C++ standard library, of which 2 different versions are loaded at once, and the «throw» of one of them clashes with the «try»/«catch» implementation... I suppose the latter is compiled inline while part of «throw» is not.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
Personally, i use the bridge between GEM and Gridflow for camera because [#camera] crash Pd when i select device #0. (Ubuntu 9.04 with GF 0.9.5 compiled on Aug 3 2009). And it works fine ! However (and i don't know why) the examples 'frequency_mask', 'nervous_video' and 'videodev_effects' in GF example crash Pd too when i open them. Do you know why ? ++
Jack
Le samedi 15 août 2009 à 12:34 -0400, Mathieu Bouchard a écrit :
On Fri, 7 Aug 2009, zmoelnig@iem.at wrote:
please not that "GridFlow" is not "PD", nor is it the only way to access a camera in Pd. does the camera work with Gem or pdp? if it works with Gem, you could use the Gem2GF bridge (which you have turned off in your configuration process, btw)
What's really weird is that it's not just about trying with this or that video-library, it's also about which video-libraries are loaded. I had to remove -lib Gem sometimes. I don't know what to do about the ATI driver bug/conflict. Do you have any idea how this could be solved permanently? I think it's something like the definition of the C++ keyword «throw» is partially contained in the C++ standard library, of which 2 different versions are loaded at once, and the «throw» of one of them clashes with the «try»/«catch» implementation... I suppose the latter is compiled inline while part of «throw» is not.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Le samedi 15 août 2009 à 19:10 +0200, Jack a écrit :
Personally, i use the bridge between GEM and Gridflow for camera because [#camera] crash Pd when i select device #0. (Ubuntu 9.04 with GF 0.9.5 compiled on Aug 3 2009). And it works fine ! However (and i don't know why) the examples 'frequency_mask', 'nervous_video' and 'videodev_effects' in GF example crash Pd too when i open them. Do you know why ?
For information, here the error in the terminal : error: ioctl VIDIOCSPICT: Invalid argument this driver is unsupported: it wants palette 8 instead of 15 warning: no channel #0 pd_gui: pd process exited Erreur de segmentation ++
Jack
++
Jack
Le samedi 15 août 2009 à 12:34 -0400, Mathieu Bouchard a écrit :
On Fri, 7 Aug 2009, zmoelnig@iem.at wrote:
please not that "GridFlow" is not "PD", nor is it the only way to access a camera in Pd. does the camera work with Gem or pdp? if it works with Gem, you could use the Gem2GF bridge (which you have turned off in your configuration process, btw)
What's really weird is that it's not just about trying with this or that video-library, it's also about which video-libraries are loaded. I had to remove -lib Gem sometimes. I don't know what to do about the ATI driver bug/conflict. Do you have any idea how this could be solved permanently? I think it's something like the definition of the C++ keyword «throw» is partially contained in the C++ standard library, of which 2 different versions are loaded at once, and the «throw» of one of them clashes with the «try»/«catch» implementation... I suppose the latter is compiled inline while part of «throw» is not.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Sat, 15 Aug 2009, Jack wrote:
However (and i don't know why) the examples 'frequency_mask', 'nervous_video' and 'videodev_effects' in GF example crash Pd too when i open them. Do you know why ?
For information, here the error in the terminal : error: ioctl VIDIOCSPICT: Invalid argument this driver is unsupported: it wants palette 8 instead of 15 warning: no channel #0 pd_gui: pd process exited Erreur de segmentation
I don't know what the segmentation fault is about, but palette #8 is YUYV, one of the YUV encodings of V4L1, and I don't have any camera that has this, so I wouldn't be able to test it directly.
I would like to have a backtrace for the segmentation fault, using GDB or equivalent.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
On Sat, Aug 15, 2009 at 11:34 PM, Mathieu Bouchard matju@artengine.cawrote:
On Sat, 15 Aug 2009, Jack wrote:
However (and i don't know why) the examples 'frequency_mask',
'nervous_video' and 'videodev_effects' in GF example crash Pd too when i open them. Do you know why ?
i got the same error:
For information, here the error in the terminal :
error: ioctl VIDIOCSPICT: Invalid argument this driver is unsupported: it wants palette 8 instead of 15 warning: no channel #0 pd_gui: pd process exited Erreur de segmentation
I don't know what the segmentation fault is about, but palette #8 is YUYV, one of the YUV encodings of V4L1, and I don't have any camera that has this, so I wouldn't be able to test it directly.
I would like to have a backtrace for the segmentation fault, using GDB or equivalent.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Sat, 15 Aug 2009, Jack wrote:
Personally, i use the bridge between GEM and Gridflow for camera because [#camera] crash Pd when i select device #0. (Ubuntu 9.04 with GF 0.9.5 compiled on Aug 3 2009). And it works fine ! However (and i don't know why) the examples 'frequency_mask', 'nervous_video' and 'videodev_effects' in GF example crash Pd too when i open them. Do you know why ?
try this in the shell just before starting pd from the shell:
ulimit -s 66666
does it make a difference ? this is _the_ other big problem with GF these days. GF uses more stack than it used to, and the OS is pretty opinionated about how much stack an app ought to use... (fortunately, it's but a default value). And when too much stack is used, it only looks like any other crash (praise Linux's error messages!)
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
Hey, @Mathieu :which linux flavour do u use?? Maybe if that os doesnt give these problems, i could switch over to it. Sisil.
On Sat, Aug 15, 2009 at 11:29 PM, Mathieu Bouchard matju@artengine.cawrote:
On Sat, 15 Aug 2009, Jack wrote:
Personally, i use the bridge between GEM and Gridflow for camera because
[#camera] crash Pd when i select device #0. (Ubuntu 9.04 with GF 0.9.5 compiled on Aug 3 2009). And it works fine ! However (and i don't know why) the examples 'frequency_mask', 'nervous_video' and 'videodev_effects' in GF example crash Pd too when i open them. Do you know why ?
try this in the shell just before starting pd from the shell:
ulimit -s 66666
does it make a difference ? this is _the_ other big problem with GF these days. GF uses more stack than it used to, and the OS is pretty opinionated about how much stack an app ought to use... (fortunately, it's but a default value). And when too much stack is used, it only looks like any other crash (praise Linux's error messages!)
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hey, running with gdb, the terminal showed: Waiting for connection request... ... connected OSS: requested audio buffer size 8820 limited to 8192 OSS: issuing first ADC 'read' ... ...done. [New Thread 0xb7e5c8d0 (LWP 9989)]
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb7e5c8d0 (LWP 9989)] 0xb7bbd2eb in handle_braces (ac=1, av=0xbfea9b98) at gridflow.c.fcs:766 766 const char *s = av[i].a_symbol->s_name; Current language: auto; currently c++ (gdb) Quit
Sisil..
On Sat, Aug 15, 2009 at 11:54 PM, sisil mehta sisilmet2000@gmail.comwrote:
Hey, @Mathieu :which linux flavour do u use?? Maybe if that os doesnt give these problems, i could switch over to it. Sisil.
On Sat, Aug 15, 2009 at 11:29 PM, Mathieu Bouchard matju@artengine.cawrote:
On Sat, 15 Aug 2009, Jack wrote:
Personally, i use the bridge between GEM and Gridflow for camera because
[#camera] crash Pd when i select device #0. (Ubuntu 9.04 with GF 0.9.5 compiled on Aug 3 2009). And it works fine ! However (and i don't know why) the examples 'frequency_mask', 'nervous_video' and 'videodev_effects' in GF example crash Pd too when i open them. Do you know why ?
try this in the shell just before starting pd from the shell:
ulimit -s 66666
does it make a difference ? this is _the_ other big problem with GF these days. GF uses more stack than it used to, and the OS is pretty opinionated about how much stack an app ought to use... (fortunately, it's but a default value). And when too much stack is used, it only looks like any other crash (praise Linux's error messages!)
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Sun, 16 Aug 2009, sisil mehta wrote:
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb7e5c8d0 (LWP 9989)] 0xb7bbd2eb in handle_braces (ac=1, av=0xbfea9b98) at gridflow.c.fcs:766 766 const char *s = av[i].a_symbol->s_name; Current language: auto; currently c++ (gdb) Quit
You have to use the «where» command to actually get the backtrace. for example, this line's error is probably caused because an invalid message was being processed, but it doesn't show where the invalid message came from, so I can't tell why it could be invalid. The «where» command usually is able to tell the caller of this function, and the caller of the caller, and so on.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
hi, ok, so i used the where command and also the backtrace full command. I've attached 2 files , one for each command.
Sisil. On Sun, Aug 16, 2009 at 12:30 AM, Mathieu Bouchard matju@artengine.cawrote:
On Sun, 16 Aug 2009, sisil mehta wrote:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7e5c8d0 (LWP 9989)] 0xb7bbd2eb in handle_braces (ac=1, av=0xbfea9b98) at gridflow.c.fcs:766 766 const char *s = av[i].a_symbol->s_name; Current language: auto; currently c++ (gdb) Quit
You have to use the «where» command to actually get the backtrace. for example, this line's error is probably caused because an invalid message was being processed, but it doesn't show where the invalid message came from, so I can't tell why it could be invalid. The «where» command usually is able to tell the caller of this function, and the caller of the caller, and so on.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
On Sun, 16 Aug 2009, sisil mehta wrote:
ok, so i used the where command and also the backtrace full command. I've attached 2 files , one for each command.
It has to be that the attribute "name" or the attribute "colorspace" gets replaced by garbage that isn't a valid symbol, and when trying to send that symbol, the first object that tries to do something with that broken-symbol will die.
It would be nice to know which attribute causes the problem... but I can't find anything relevant related to either attribute.
I did just find a buffer overflow that could possibly cause the same problem, but it's incredibly unlikely that this is it. I fixed it. You can do "svn update; make" if you want to confirm that this is not the bugfix we're after.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
On Sat, 15 Aug 2009, sisil mehta wrote:
@Mathieu :which linux flavour do u use?? Maybe if that os doesnt give these problems, i could switch over to it.
I'm also on Ubuntu 9.04, but I don't think anyone should change distros for that, unless there is a known technical reason to do so.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
Le samedi 15 août 2009 à 13:59 -0400, Mathieu Bouchard a écrit :
On Sat, 15 Aug 2009, Jack wrote:
Personally, i use the bridge between GEM and Gridflow for camera because [#camera] crash Pd when i select device #0. (Ubuntu 9.04 with GF 0.9.5 compiled on Aug 3 2009). And it works fine ! However (and i don't know why) the examples 'frequency_mask', 'nervous_video' and 'videodev_effects' in GF example crash Pd too when i open them. Do you know why ?
try this in the shell just before starting pd from the shell:
ulimit -s 66666
does it make a difference ?
Yes, only for 'nervous video'. The others still crash Pd. ++
Jack
this is _the_ other big problem with GF these days. GF uses more stack than it used to, and the OS is pretty opinionated about how much stack an app ought to use... (fortunately, it's but a default value). And when too much stack is used, it only looks like any other crash (praise Linux's error messages!)
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
hey, so i updated gridflow using svn, and the #camera still causes pd to crash, I've attached the new where and backtrace full results. (this time also i compiled GF using ./configure --no-gem09 --no-gem08 , cause before i had problems running gem also) Sisil.
On Sun, Aug 16, 2009 at 6:07 AM, Jack jack@rybn.org wrote:
Le samedi 15 août 2009 à 13:59 -0400, Mathieu Bouchard a écrit :
On Sat, 15 Aug 2009, Jack wrote:
Personally, i use the bridge between GEM and Gridflow for camera
because
[#camera] crash Pd when i select device #0. (Ubuntu 9.04 with GF 0.9.5 compiled on Aug 3 2009). And it works fine ! However (and i don't know why) the examples 'frequency_mask', 'nervous_video' and 'videodev_effects' in GF example crash Pd too when
i
open them. Do you know why ?
try this in the shell just before starting pd from the shell:
ulimit -s 66666
does it make a difference ?
Yes, only for 'nervous video'. The others still crash Pd. ++
Jack
this is _the_ other big problem with GF these days. GF uses more stack than it used to, and the OS is pretty
opinionated
about how much stack an app ought to use... (fortunately, it's but a default value). And when too much stack is used, it only looks like any other crash (praise Linux's error messages!)
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Fri, 7 Aug 2009, zmoelnig@iem.at wrote:
Could there be an issue with the OS (ubuntu 9.04) or while configuring ?? I'm totally lost.
i don't think so. just a wild guess: make sure that you don't use pwc-specific options when using libv4l (read: have you turned off the "pwc" configuration when compiling GF?)
With the newer GF, the PWC options are always compiled in, but are enabled at runtime using a message that you have to send after the "open". This is reflected in the structure of [#camera], which also greys-out any sliders you can't use, etc.
Some older versions of GF used PWC options supposing they wouldn't conflict with other camera drivers, which wasn't completely true, and so there was a tiny compile-time hack that had to be done, but this has been over for a while.
Just don't use GridFlow from CVS, though, as it is probably that much old (maybe not). GridFlow switched to SVN a while ago, but I haven't removed the CVS yet.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
hey, ok so i didnt load the Gem library. and ran gridflow patch called: #camera-help.pd as always in the #camera when i select the device number PD crashes . i used gdb and this came up:
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb7dbc6c0 (LWP 4888)] 0xb7b1d2eb in handle_braces (ac=1, av=0xbfd91af8) at gridflow.c.fcs:766 766 const char *s = av[i].a_symbol->s_name; Current language: auto; currently c++ (gdb) Quit (gdb) quit
So will i ever be able to run a camera on gridflow??? The camera is a e2500 logitech quickcam, it works on camorama,cheese cause i used the libv4l library.
Sisil.
On Sat, Aug 15, 2009 at 10:09 PM, Mathieu Bouchard matju@artengine.cawrote:
On Fri, 7 Aug 2009, zmoelnig@iem.at wrote:
Could there be an issue with the OS (ubuntu 9.04) or while configuring ??
I'm totally lost.
i don't think so. just a wild guess: make sure that you don't use pwc-specific options when using libv4l (read: have you turned off the "pwc" configuration when compiling GF?)
With the newer GF, the PWC options are always compiled in, but are enabled at runtime using a message that you have to send after the "open". This is reflected in the structure of [#camera], which also greys-out any sliders you can't use, etc.
Some older versions of GF used PWC options supposing they wouldn't conflict with other camera drivers, which wasn't completely true, and so there was a tiny compile-time hack that had to be done, but this has been over for a while.
Just don't use GridFlow from CVS, though, as it is probably that much old (maybe not). GridFlow switched to SVN a while ago, but I haven't removed the CVS yet.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Thu, 6 Aug 2009, IOhannes m zmoelnig wrote:
as matju has stated several times (in this thread), all drivers that speak v4l (aka: v4l1) are supported by gridflow.
Unfortunately, this is not true, in the end. Only some of the most common image formats are supported: YUV420P, RGB32, RGB24, RGB565. I don't have any camera that is supported by a driver that outputs YUYV (some kind of "422"). Unfortunately, no format is supported by all cams, and the kernel dudes removed all format conversion code. This leads directly to the use of a user-space conversion library that didn't exist when I last rewrote gridflow/format/videodev.c (libv4l 0.1 was over a year after that, iirc).
all drivers that only speak v4l2 are not natively supported by gf. however (as said before) you can use libv4l to add v4l2 support to v4l1 applications at runtime.
Supporting libv4l instead of v4l1 (and hypothetically v4l2), I will be able to support all formats (colour models + other variations) without any fuss... plus all v4l2 cameras. So, what's coming next with cams in GF is not v4l2 support, it is libv4l support.
other than that, it is hard to make any anwers (as matju has pointed out): gf (and any other video-application) does not directly communicate with a driver (pwc, qc-usb,...) but with a middleware (the v4l*-protocol).
I'd say that gf and other video-applications directly communicate with a driver, because the protocol is not middleware. However if you have a protocol conversion library such libv4l, ... that is what middleware is. AFAIK, *.h don't count as middleware, *.c does. (unless you put a real lot of stuff in the *.h... but you get my point).
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
On Thu, 6 Aug 2009, sisil mehta wrote:
with gridflow which webcam drivers are supported? i found that pwc and qc-usb are. i wanted to know whether uvc driver would be supported by gridflow.?
[#in videodev] supports the V4L1 camera drivers that use one of the following formats: YUV420P, RGB32, RGB24, RGB565, and... that's all for now.
[#in dc1394] supports black-and-white only. (I had a colour cam for a day but couldn't find how to make it work)
[#in quicktimecamera] supports the Apple QuickTime driver interface.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
-
IOhannes m zmoelnig -
IOhannes m zmölnig
-
Jack -
Mathieu Bouchard -
sisil mehta -
zmoelnig＠iem.at