On 12/29/2009 11:25 AM, cyrille henry wrote:
hello,

/dev/video2 look to be a V4L device, and not V4L2.
so you have to configure pix_video to use V4L driver.
a message [driver v4l< should do it (or driver 1, or whatever number pix_video use for V4L)
then [open /dev/video2<

cyrille


Bart Koppe a écrit :
Thanks, I now tried, funny to mention that pdp_v4l can read /dev/video2 (virtual video device) and pdp_v4l2 cannot! But I was not clear in my message i think, I just wanted to do the same in GEM. Now I yesterday finally found out how to correctly use pdp2gem, i can just use pdpv4l and use the output wherever i can.
Baically i'm a newb in doing a bit of video/images mixing in PD.. ;)
Cheers,
Bart




On 12/28/2009 06:56 PM, Pagano, Patrick wrote:
did you try pdpv4l2?


________________________________________
From: [email protected] [[email protected]] On Behalf Of Bart Koppe [[email protected]]
Sent: Sunday, December 27, 2009 6:05 PM
To: PD list
Subject: [PD] How to use /dev/video2 virtual video device in GEM

Hi,

I use /dev/video2 to get a mjpeg live stream into PD.
With pix_video I can open my webcam, but when I open the virtual video
device (/dev/video2) i get an error, i guess todo with the fact that
it's not a real webcam:

error: Cannot open '/dev/video2': 25, Inappropriate ioctl for device
GL: invalid enumerant--

Is there other ways to get it fixed in GEM?

With pdp_v4l i can open the virtual device, but I want to try it in GEM,
mostly because GEM is better documented, I need to add several jpeg/png
pictures on both sides of that stream.


Thanks..

Bart


#N canvas 527 149 328 354 12;
#X obj 55 78 gemhead;
#X obj 55 222 rectangle 4 3;
#X obj 55 188 pix_texture;
#X obj 55 152 pix_video;
#N canvas 340 107 682 322 gemwin 0;
#X obj 102 122 tgl 15 0 \$0-gemstart \$0-gemstart empty 17 7 0 10 -262144
-1 -1 0 1;
#X obj 102 161 r \$0-gemstart;
#X obj 102 182 select 1 0;
#X msg 102 214 create \, 1;
#X msg 177 215 destroy;
#X obj 102 239 t a;
#X obj 318 54 inlet;
#X obj 318 255 gemwin;
#X obj 318 100 t a a;
#X obj 318 287 outlet;
#X obj 350 128 route create destroy;
#X obj 350 150 t b;
#X msg 350 172 1;
#X obj 390 150 t b;
#X msg 390 172 0;
#X obj 350 195 t f;
#X msg 350 219 set \$1;
#X text 118 122 rendering;
#X connect 1 0 2 0;
#X connect 2 0 3 0;
#X connect 2 1 4 0;
#X connect 3 0 5 0;
#X connect 4 0 5 0;
#X connect 5 0 8 0;
#X connect 6 0 8 0;
#X connect 7 0 9 0;
#X connect 8 0 7 0;
#X connect 8 1 10 0;
#X connect 10 0 11 0;
#X connect 10 1 13 0;
#X connect 11 0 12 0;
#X connect 12 0 15 0;
#X connect 13 0 14 0;
#X connect 14 0 15 0;
#X connect 15 0 16 0;
#X connect 16 0 0 0;
#X coords 0 -1 1 1 85 40 1 100 100;
#X restore 56 254 pd gemwin;
#X msg 139 114 device 2;
#X msg 69 114 device 0;
#X connect 0 0 3 0;
#X connect 2 0 1 0;
#X connect 3 0 2 0;
#X connect 5 0 3 0;
#X connect 6 0 3 0;


-----/\/\/\/\/\/\-----
Bart Koppe
bk at a-bort dot org
http://a-bort.org
-----\/\/\/\/\/\/-----


_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list




--
-----/\/\/\/\/\/\-----  
Bart Koppe              
bk at a-bort dot org            
http://a-bort.org
-----\/\/\/\/\/\/-----


_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Reply via email to