hi all

i would lije to use a unibrain firewire camera for tracking in debian.
my problem is that i can see the picture in coriander, but mot in
pd/gem/pidip.

any ideas?

please help markus brandt

yess...and thank you

device 1 says dev/dv1394/0: no such device or directory

which is no wonder, caouse there is only a video1394 directory

also coriander complains about not finding /dev/videoO and .... it seems v4l is not running....and i do not know how to start
that module (just started again with debian....got lost in the
winworld the last years)

Zitat von Jack jack@rybn.org:

Can you tell us the return in the console when you create [pix_video]. Have you try to send the message [device 1( to [pix_video] ? ++

Jack

Le mardi 30 novembre 2010 à 17:14 +0100, brandt@subnet.at a écrit :

...

hi all

i would lije to use a unibrain firewire camera for tracking in debian. my problem is that i can see the picture in coriander, but mot in pd/gem/pidip.

any ideas?

please help markus brandt

---

Pd-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list

thank you

i allready downloaded it, but stick around with all the linux hacks.
(exwindise-user and starter in linux)

markus

Zitat von "Husk 00" husk00@gmail.com:

On Tue, Nov 30, 2010 at 5:14 PM, brandt@subnet.at wrote:

...

hi all

i would lije to use a unibrain firewire camera for tracking in debian. my problem is that i can see the picture in coriander, but mot in pd/gem/pidip.

any ideas?

Hi, you need to use vloopback module to forward the video signal from coriander to PD as a standard v4l device.

suerte husk

-- when Art become pratical we call it technology.

When Technology become useless we call it Art

www.estereotips.net

On 2010-11-30 17:14, brandt@subnet.at wrote:

hi all

i would lije to use a unibrain firewire camera for tracking in debian. my problem is that i can see the picture in coriander, but mot in pd/gem/pidip.

any ideas?

#1 (Gem only) upgrade to the latest and greatest Gem (svn!), where you can read iidc cameras directly

#2 older versions of Gem and pdp don't have iidc support; so you need to somehow make your camera's images show up in v4l(2) devices

#2a v4l1-loopback: coriander already comes with v4l1-loopback support; in order to use it you have to, install the the v4loopback kernel module: # module-assistant auto-install vloopback # modprobe vloopback this will give you 2 new devices e.g. /dev/video1 (being the "pipe" where coriander can write to) and /dev/video2 (being the "pipe" that pix_video/pdp_v4l can read)

#2b v4l2-loopback (which i favour as it is more modern and i have my fingers in it) if you are on debian/sid you can simply do: # modula-assistant auto-install v4l2loopback # modprobe v4l2loopback this will give you 1 new device e.g. /dev/video1 which can be written to by e.g. gstreamer and read by pix_video/pdp_v4l2 $ gstreamer dc1394src ! ffmpegcolorspace ! v4l2sink

if you are not on debian/sid, you might want to get v4l2loopback from http://github.com/umlaeute/v4l2loopback/ and simply run $ make $ sudo insmod ./v4l2loopback.ko

gmsdr IOhannes

Zitat von brandt@subnet.at:

i have inserted the modules vloopback, videodev....coriander is
neither complaining anymore about misseng etc/video0 nor avout
missing v2l anymore.

and its running V4L output device /etc/video0

sofarsonice

by the way...i use GEM: ver: 0.91.3 'tigital' and PiDiP : additional
video processing objects for PD version 0.12.23

if i try pdp_v4l2 console says pdp_v4l2: opening /dev/video0 pdp_v4l2: error: open /dev/video0: Device or resource busy

pdp_v4l2: opening /dev/video1 pdp_v4l2: error: open /dev/video1: Invalid argument get capabilities: Inappropriate ioctl for device

/dev/video0: No such file or directory /dev/video3: Device or resource busy /dev/video2: No such file or directory get capabilities: Inappropriate ioctl for device (when i do video1) /dev/video0: No such file or directory

Gem pix_video

video driver 0: video4linux video driver 1: ieee1394 for linux

pd bash error: failed opening device: '/dev/video0' console says /dev/video0: Device or resource busy

if i try video driver 1 gem is telling me /dev/dv1394/0: No such file or directory console detto...wich is not a wonder, since i just have
/dev/video1394 and no /dev/dv1394

any ideas?

markus

---

Pd-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list

hi husk 00

vloopback is using as input 0 and its output 1

if i try to do pdp_v4l and set to dev 1 i get the following error get capabilities: Inappropriate ioctl for device

cheers markus

Zitat von "Husk 00" husk00@gmail.com:

Hi, If I'm not worng vloopback module create a third (or a forth...) video device. So try to open /dev/video2 or /dev/video3

husk

On Wed, Dec 1, 2010 at 11:10 AM, brandt@subnet.at wrote:

...

i have inserted the modules vloopback, videodev....coriander is neither complaining anymore about misseng etc/video0 nor avout missing v2l anymore.

and its running V4L output device /etc/video0

sofarsonice

by the way...i use GEM: ver: 0.91.3 'tigital' and PiDiP : additional video processing objects for PD version 0.12.23

if i try pdp_v4l2 console says pdp_v4l2: opening /dev/video0 pdp_v4l2: error: open /dev/video0: Device or resource busy

pdp_v4l2: opening /dev/video1 pdp_v4l2: error: open /dev/video1: Invalid argument get capabilities: Inappropriate ioctl for device

Gem pix_video

video driver 0: video4linux video driver 1: ieee1394 for linux

pd bash error: failed opening device: '/dev/video0' console says /dev/video0: Device or resource busy

if i try video driver 1 gem is telling me /dev/dv1394/0: No such file or directory console detto...wich is not a wonder, since i just have /dev/video1394 and no /dev/dv1394

any ideas?

markus

---

Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

-- when Art become pratical we call it technology.

When Technology become useless we call it Art

www.estereotips.net

Thank you..all and yes iohannes...[pdp_v4l] does the job

its working now...like it should.....wonderfull

thank you so much markus

Zitat von "IOhannes m zmoelnig" zmoelnig@iem.at:

On 2010-12-01 11:10, brandt@subnet.at wrote:

...

i have inserted the modules vloopback, videodev....coriander is neither complaining anymore about misseng etc/video0 nor avout missing v2l anymore.

and its running V4L output device /etc/video0

sofarsonice

by the way...i use GEM: ver: 0.91.3 'tigital' and PiDiP : additional video processing objects for PD version 0.12.23

if i try pdp_v4l2 console says pdp_v4l2: opening /dev/video0 pdp_v4l2: error: open /dev/video0: Device or resource busy

well, i thought i was quite clear that vloopback would make the first device the input (sink) device, and the 2nd device the output (src) device, so try /dev/video1

...

pdp_v4l2: opening /dev/video1 pdp_v4l2: error: open /dev/video1: Invalid argument get capabilities: Inappropriate ioctl for device

well, i thought i was quite clear that this solution involves v4l1(!), thus pdp_v4l2 will bail out, as it needs a v4l2 device. try [pdp_v4l]

...

Gem pix_video

video driver 0: video4linux video driver 1: ieee1394 for linux

pd bash error: failed opening device: '/dev/video0' console says /dev/video0: Device or resource busy

again, /dev/video0 is the sink, you need /dev/video1

...

if i try video driver 1 gem is telling me /dev/dv1394/0: No such file or directory console detto...wich is not a wonder, since i just have /dev/video1394 and no /dev/dv1394

well "driver 1" changes the driver to the dv4l (ieee1394). you don't want to change the driver (the default is video4linux, which is just what you need), you want to change the device. use "device /dev/video1"

if you still cannot open the device with neither application, you might want to switch to one of my other suggestions (which were both favoured over the one you chose....)

ghmst IOhannes