hello
just built gridflow on maverick. ./configure tells me: libv4l1 ---> found libv4l2 ---> found etc (everything except osx related is found), it builds fine, but if try the examples, opening [#camera], selecting libv4l2 and then my video device (video0) gives me this error:
error: [#io.v4l2 in /dev/video0 1]: this [#io.v4l2] wasn't compiled with libv4l2 support #io.v4l2 in /dev/video0 1 ... couldn't create print: symbol v4l2 error: [gf/not_open]: not open
if I choose ...v4l2 I get:
error: ioctl VIDIOC_G_FREQUENCY: Invalid argument
I get the same errors with both pd-extended 0.42.5 and latest pd from git.
thanks for your help, _y
Hi, a similar thing happened to me, was related to the dimensions as said Mathieu ... check it anyway
Best
José
2010/12/22 Yvan Volochine yvan.pd@gmail.com:
hello
just built gridflow on maverick. ./configure tells me: libv4l1 ---> found libv4l2 ---> found etc (everything except osx related is found), it builds fine, but if try the examples, opening [#camera], selecting libv4l2 and then my video device (video0) gives me this error:
error: [#io.v4l2 in /dev/video0 1]: this [#io.v4l2] wasn't compiled with libv4l2 support #io.v4l2 in /dev/video0 1 ... couldn't create print: symbol v4l2 error: [gf/not_open]: not open
if I choose ...v4l2 I get:
error: ioctl VIDIOC_G_FREQUENCY: Invalid argument
I get the same errors with both pd-extended 0.42.5 and latest pd from git.
thanks for your help, _y
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Wed, 22 Dec 2010, Yvan Volochine wrote:
etc (everything except osx related is found), it builds fine, but if try the examples, opening [#camera], selecting libv4l2 and then my video device (video0) gives me this error:
[#io.v4l2] does not work in any way, therefore I didn't bother enabling libv4l2 at all. To use v4l2, you go through libv4l1 instead, which does v4l1/v4l2 conversion.
I added [#io.v4l2] in [#camera] because I was going to work on it, but when I decided not to, I didn't remove it before the release(s), which is misleading.
I get the same errors with both pd-extended 0.42.5 and latest pd from git.
It does not make a difference.
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
On 12/22/10, Mathieu Bouchard matju@artengine.ca wrote:
[#io.v4l2] does not work in any way, therefore I didn't bother enabling libv4l2 at all. To use v4l2, you go through libv4l1 instead, which does v4l1/v4l2 conversion.
I added [#io.v4l2] in [#camera] because I was going to work on it, but when I decided not to, I didn't remove it before the release(s), which is misleading.
ah yes, v4l1 works fine. thanks for your amazing work !
_y
On Wed, 22 Dec 2010, Yvan Volochine wrote:
On 12/22/10, Mathieu Bouchard matju@artengine.ca wrote:
[#io.v4l2] does not work in any way, therefore I didn't bother enabling libv4l2 at all. To use v4l2, you go through libv4l1 instead, which does v4l1/v4l2 conversion.
I added [#io.v4l2] in [#camera] because I was going to work on it, but when I decided not to, I didn't remove it before the release(s), which is misleading.
ah yes, v4l1 works fine.
BTW, if you use the one called just "v4l1" in [#camera], it doesn't do the v4l1/v4l2 conversion, so it will work only with v4l1 drivers. That's why there is the "libv4l1" option (well, it's also because it does all the color conversions that we don't want to bother supporting...)
thanks for your amazing work !
:)
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
On Wed, Dec 22, 2010 at 11:36 PM, Mathieu Bouchard matju@artengine.cawrote:
BTW, if you use the one called just "v4l1" in [#camera], it doesn't do the v4l1/v4l2 conversion, so it will work only with v4l1 drivers. That's why there is the "libv4l1" option (well, it's also because it does all the color conversions that we don't want to bother supporting...)
mmh, I updated to maverick (2.6.25-24-generic) and it looks like it was a bad idea.. any gridflow patch just freezes my os now :/ I don't have any special verbose output (it seems), just after opening any patch from the examples I loose the mouse/keys and have to force reboot.
any hints much appreciated
(thinkpad w500 - core 2 duo)
_y
On Thu, 23 Dec 2010, Yvan Volochine wrote:
On Wed, Dec 22, 2010 at 11:36 PM, Mathieu Bouchard matju@artengine.ca wrote: mmh, I updated to maverick (2.6.25-24-generic) and it looks like it was a bad idea.. any gridflow patch just freezes my os now :/
Any, or just when you try to get a frame from [#camera] ?
I do get a lot of freezes from [#camera], but that's because of the pwc.ko driver (for the Philips protocol). As far as I can tell, the Linux kernel has been shipping with a bad version of pwc for a while. But it doesn't freeze the OS, it just means I have to unload and reload the driver quite often, and kill Pd (Ctrl+c in the terminal works, but Ctrl+q in the pd-gui doesn't). I should reinstall a non-bundled version of pwc.ko like I used to have (I think I recall it made a difference).
What's your situation ? (camera driver, if that's an issue...)
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
On Thu, Dec 23, 2010 at 2:55 AM, Mathieu Bouchard matju@artengine.cawrote:
On Thu, 23 Dec 2010, Yvan Volochine wrote:
On Wed, Dec 22, 2010 at 11:36 PM, Mathieu Bouchard matju@artengine.ca wrote: mmh, I updated to maverick (2.6.25-24-generic) and it looks like it was a bad idea.. any gridflow patch just freezes my os now :/
Any, or just when you try to get a frame from [#camera] ?
any patch (just by opening them) then I can't kill pd because my keyboard is also lost..
I do get a lot of freezes from [#camera], but that's because of the pwc.ko driver (for the Philips protocol). As far as I can tell, the Linux kernel has been shipping with a bad version of pwc for a while. But it doesn't freeze the OS, it just means I have to unload and reload the driver quite often, and kill Pd (Ctrl+c in the terminal works, but Ctrl+q in the pd-gui doesn't). I should reinstall a non-bundled version of pwc.ko like I used to have (I think I recall it made a difference).
What's your situation ? (camera driver, if that's an issue...)
sorry but how do I find out my camera driver ? I use a Sony Eye usb cam (from ps3).
cheers, _y
On Thu, 23 Dec 2010, Yvan Volochine wrote:
any patch (just by opening them)
even hello-world.pd ?
What if you create a new patch and put some GridFlow objects in it ?
sorry but how do I find out my camera driver ? I use a Sony Eye usb cam (from ps3).
If your freeze is not related to [#camera], in the end, it does not matter.
BTW, several other people reported that the PS3eye didn't work with GridFlow. Did it really work for you ?
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
On Thu, Dec 23, 2010 at 3:17 AM, Mathieu Bouchard matju@artengine.cawrote:
On Thu, 23 Dec 2010, Yvan Volochine wrote:
any patch (just by opening them)
even hello-world.pd ?
yep (but this one crashes after a couple of secs)
What if you create a new patch and put some GridFlow objects in it ?
for some it works (like #window #rotate) but it seems inconsistent it's not on my machine so I have to go back and forth to make further tests and I can't make as much as I'd like..
I use a Sony Eye usb cam (from ps3).
If your freeze is not related to [#camera], in the end, it does not matter.
BTW, several other people reported that the PS3eye didn't work with GridFlow. Did it really work for you ?
yes, we also have an old asus here, PS3 eye works fine with gridflow on it
BTW the same kernel on the old machine works fine it seems related to the FireGL, which is a pity if it's the case... unfortunately I don't have much ideas to try...
thanks again, _y
On Thu, 23 Dec 2010, Yvan Volochine wrote:
On Thu, Dec 23, 2010 at 3:17 AM, Mathieu Bouchard matju@artengine.ca wrote:
even hello-world.pd ?
yep (but this one crashes after a couple of secs)
Hey, that one only produces one frame, and does so at [loadbang] time. So, it's especially weird.
You could try patches that don't use any window at all... lots of help-patches are like that.
for some it works (like #window
What do you mean "it works"... is anything being sent to [#window] ? Inside of [#window] there's a [#out window], inside of which there's a [#io.x11] (or other), isn't it ? So it should be the same as a plain [#out window].
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
On Thu, Dec 23, 2010 at 4:20 PM, Mathieu Bouchard matju@artengine.cawrote:
Hey, that one only produces one frame, and does so at [loadbang] time. So, it's especially weird.
You could try patches that don't use any window at all... lots of help-patches are like that.
for some it works (like #window
What do you mean "it works"... is anything being sent to [#window] ? Inside of [#window] there's a [#out window], inside of which there's a [#io.x11] (or other), isn't it ? So it should be the same as a plain [#out window].
sorry but this kernel and fglrx version are not usable unfortunately. now Gem also crashes badly (deb and src). I'm trying another distro and I'll report back here.
I forgot ATI cards were such a PITA in linux...
geez, finally all seem to be fine. this time on lucid 2.6.32-27-generic, gridflow is running (and ps3-eye as well =)
cheers ! _y
On Wed, 2010-12-22 at 21:17 -0500, Mathieu Bouchard wrote:
On Thu, 23 Dec 2010, Yvan Volochine wrote:
any patch (just by opening them)
even hello-world.pd ?
What if you create a new patch and put some GridFlow objects in it ?
sorry but how do I find out my camera driver ? I use a Sony Eye usb cam (from ps3).
If your freeze is not related to [#camera], in the end, it does not matter.
BTW, several other people reported that the PS3eye didn't work with GridFlow. Did it really work for you ?
This camera works for me on Ubuntu 9.10 and 10.04 (haven't tested on other releases, but it might work as well). It uses the gspca driver (gspca_ov534, to be exact).
The driver shipped with Ubuntu doesn't have an interface to adjust the camera settings, so it works with a fixed size of 640x480 and a fixed rate of 30 fps. However, with the kaswy [1] patch applied, all settings are exposed.
[1] http://kaswy.free.fr/?q=node/38#ps3
Roman
On Thu, 23 Dec 2010, Roman Haefeli wrote:
On Wed, 2010-12-22 at 21:17 -0500, Mathieu Bouchard wrote:
BTW, several other people reported that the PS3eye didn't work with GridFlow. Did it really work for you ?
This camera works for me on Ubuntu 9.10 and 10.04 (haven't tested on other releases, but it might work as well). It uses the gspca driver (gspca_ov534, to be exact).
You did report a problem with this in http://lists.artengine.ca/pipermail/gridflow-dev/2010-May/000582.html
Did you change something since, or am I misunderstanding something ?
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
On Thu, 2010-12-23 at 02:17 +0100, Yvan Volochine wrote:
On Wed, Dec 22, 2010 at 11:36 PM, Mathieu Bouchard matju@artengine.ca wrote: BTW, if you use the one called just "v4l1" in [#camera], it doesn't do the v4l1/v4l2 conversion, so it will work only with v4l1 drivers. That's why there is the "libv4l1" option (well, it's also because it does all the color conversions that we don't want to bother supporting...)
mmh, I updated to maverick (2.6.25-24-generic) and it looks like it
Hm.. How is this version string '2.6.25-24-generic' related to (Ubuntu) maverick? I'm using Ubuntu Lucid and it ships with a 2.6.32-26-generic linux kernel.
Roman
On Thu, Dec 23, 2010 at 8:49 AM, Roman Haefeli reduzent@gmail.com wrote:
mmh, I updated to maverick (2.6.25-24-generic) and it looks like it
Hm.. How is this version string '2.6.25-24-generic' related to (Ubuntu) maverick? I'm using Ubuntu Lucid and it ships with a 2.6.32-26-generic linux kernel.
sorry typo (was late). it's 2.6.35-24
_y
-
Jose Luis Santorcuato -
Mathieu Bouchard -
Roman Haefeli -
Yvan Volochine