Hallo gem-devs!
As I use udev now I cannot use the dv input in Gem anymore. The problem is the following (i think): with devfs the device was /dev/dv1394 (on my computer) now (udev) the device is on my computer /dev/dv1394/0
The problem is, that /dev/dv1394 is hardcoded in videoDV4L.cpp, so changing line 194:
if ((fd=open("/dev/dv1394", O_RDWR)) < 0) {
to:
if ((fd=open("/dev/dv1394/0", O_RDWR)) < 0) {
fixes the problem !
So we would need an additional message, to set the proper device - don't know which one... (pix_video is already very confusing) anyway, I don't have the time to make a clean implementation now - have to make a video till friday ... :)
LG Georg
Georg Holzmann wrote:
Hallo gem-devs!
As I use udev now I cannot use the dv input in Gem anymore. The problem is the following (i think): with devfs the device was /dev/dv1394 (on my computer) now (udev) the device is on my computer /dev/dv1394/0
The problem is, that /dev/dv1394 is hardcoded in videoDV4L.cpp, so changing line 194:
if ((fd=open("/dev/dv1394", O_RDWR)) < 0) {to:
if ((fd=open("/dev/dv1394/0", O_RDWR)) < 0) {fixes the problem !
the CVS-version of Gem *should* support symbolic devices: so you could send it a [device /dev/dv1394/0( message. this is extremely untested, so it would be nice if you could give it a try. (btw, if i remember correctly, it even attempts to figure out which driver to use (but i may be wrong)
of course, exchanging the hardcoded device-name (as you proposed) is a no-no.
mfg.asdr. IOhannes
-
Georg Holzmann -
IOhannes m zmoelnig