Aarrgh... I just had one of those moments: after 10 hours of
frustration, you are about to give up and then have that last-second
"this may seem stupid, but let's try it anyhow" idea--and it works! DOH!<br>
<br>
When I looked at the gem code, it seems that Gem also looks for the
/dev/dv1394 node as a fallback option. Well, on my computer, even
though the dv1394 driver is loaded, the /dev/dv1394 node is missing.
Apparently the node type depends on the format being captured
(something like 171,32 for NTSC and 171,34 doe PAL), so Ubuntu never
created one (I am not even sure if it should have generated it in the
first place). So, I go and first start messing with /dev/MAKEDEV dv1394
and computer tells me it does not know how to make it... Then I try the
brute-force way of simply doing: <br>
<br>
mknod /dev/dv1394 c 171 32<br>
chown root:video /dev/dv1394<br>
chmod 660 /dev/dv1394<br>
<br>
And... What Happen? We got signal! Main screen turn on!... (sorry, it's 4am and I feel a bit geeky :-)<br>
<br>
Now, if I could only figure out my other problem... BTW, does anyone
know who/what is responsible for generating the dv1394 node? This may
be a useful piece of info to the Ubuntu maintainers... Oh well, off to
bed...<br>
<br>
Thanks to all Pd/Gem/externals devs for the wonderful software!<br>
<br>
Best wishes,<br>
<br>
Ico<br>
<br>
<br><br><div><span class="gmail_quote">On 3/17/06, <b class="gmail_sendername">Ivica Ico Bukvic</b> <<a href="mailto:ico.bukvic@gmail.com">ico.bukvic@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="direction: ltr;">Greetings all,<br>
<br>
I have just started messing with the video in on my Linux laptop and have encountered some problems with Gem:<br>
<br>
*The OS is Ubuntu Hoary, Pd 0.38, and Gem 0.90.<br>
<br>
*I am using ADVC-100 ieee1394 interface which allows me to connect any
S-Video device to my laptop. The device works fine with Kino (dvgrab).<br>
<br>
*My /dev folder includes /dev/raw1394 and /dev/video1394/0<br>
<br>
*All of the stuff is installed TTBOMK properly.<br>
<br>
*When using Gem, I cannot get the video to work as I do not have v4l
devices available (/dev/video0) with this device, and the ieee1394
devices Gem looks for under /dev/ieee1394/dv/host<x>/<y>/in
which obviously fails on my system. The exact error in the terminal is:<br>
/dev/ieee1394/dv/host0/PAL/in: No such file or directory<br>
<br>
*I tried linking /dev/raw1394 to /dev/video0 (I am not sure as to what
is the difference between the two, so this may have been
stupid--nonetheless I tried it just to cover all possibilities) and
then using ../gem/examples/04.video/00.SimpleVideo.pd tutorial
generates one complaint: get capabilities: Invalid argument and I get
no video. All permissions should be properly set on the devices/links
(root:video 660).<br>
<br>
*I tried using latest vloopback driver (0.97) and when I modprobe it, I
get /dev/video0 and /dev/video1 devices (81,0). However, connecting to
them yields following in PD:<br>
<br>
video4linux<br>
ieee1394 for linux<br>
Direct Rendering enabled!<br>
GEM: Start rendering<br>
pix_videoNEW: starting transfer<br>
cap: name Video loopback 0 input type 0 channels 1 maxw 0 maxh 0 minw 20 minh 20<br>
picture: brightness 32768 depth 32768 palette 0<br>
channel 0 name Composite1 type 2 flags 0<br>
setting to channel 0<br>
buffer size -1397530602, frames 2, offset 0 -698765301<br>
wanted format is 0x1908<br>
setting cmcapture to 0x0 5<br>
now trying standard palette 0<br>
closing video<br>
pix_texture: not using client storage<br>
<br>
In addition, the terminal also spits out: VIDIOCMCAPTURE: Invalid argument<br>
<br>
*I tried using dc1394_vloopback with various settings including:<br>
dc1394_vloopback --video1394=/dev/video1394/0 --vloopback=/dev/video0<br>
but that simply tells me "no cameras found :(" no matter what settings
I try (I also made sure that the vloopback driver was unloaded).<br>
<br>
I am not aware of any other way to bridge ieee1394 feed and v4l, nor am
I sure as to how to force pix_video to use different ieee1394 source
(not sure whether this even works with the advc-100).<br>
<br>
*I tried accessing Gem CVS to see if there were any changes since the 0.90, but the CVS seems to be inaccessible:<br>
cvs -z3 -d:pserver:anonymous@cvs.gem.iem.at:/cvsroot/pd-gem login<br>
Logging in to :<a href="http://pserver:anonymous@cvs.gem.iem.at:2401/cvsroot/pd-gem" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">pserver:anonymous@cvs.gem.iem.at:2401/cvsroot/pd-gem</a><br>
CVS password:<br>
cvs [login aborted]: unrecognized auth response from <a href="http://cvs.gem.iem.at" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">cvs.gem.iem.at</a>: M -!- Project map lookup failed ()<br>
<br>
So, I have pretty much run out of ideas and I was hoping that someone might be able to help me out with this one, namely:<br>
<br>
1) Is there a way to use my ADVC-100 to stream video to PD/Gem?<br>
2) If there is no native way to do that is there a way to use vloopback
or some similar method to channel its feed into the v4l format?<br>
3) any other ideas/suggestion (other than spending money and buying myself a new <whatever> :-)<br>
<br>
I would greatly appreciate assistance in this matter!<br>
<br>
Best wishes,<br></div><div style="direction: ltr;"><span class="sg">
<br>
Ico<br>
</span></div></blockquote></div><br>