<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.14.3">
</HEAD>
<BODY>
Le mardi 14 août 2007 à 22:19 +0200, Tim Boykett a écrit :
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Hi Kids!</FONT>
<FONT COLOR="#000000"> Time for a new adventure. I would like to have a working</FONT>
<FONT COLOR="#000000">firewire camera input for manipulation in Gem on a linux</FONT>
<FONT COLOR="#000000">box that is sitting here purring at me. The cam works</FONT>
<FONT COLOR="#000000">fine with Kino and dvgrab, so the linux-firewire connection</FONT>
<FONT COLOR="#000000">is all well.</FONT>
<FONT COLOR="#000000">But I am having no luck with pix_video or pdp_v4l. The main problem</FONT>
<FONT COLOR="#000000">seems to be that (apparently) recently the naming conventions</FONT>
<FONT COLOR="#000000">in debian and possibly linux in general were changed. So there is</FONT>
<FONT COLOR="#000000">no more /dev/video0 for the v4l mode, and for pix_video trying to</FONT>
<FONT COLOR="#000000">work directly with ieee1394, I get complaints that /dev/ieee1394/dv/ </FONT>
<FONT COLOR="#000000">host/PAL/in</FONT>
<FONT COLOR="#000000">"Is a directory".</FONT>
<FONT COLOR="#000000">Has anyone had more luck? Do I need to going from stable to testing in</FONT>
<FONT COLOR="#000000">some parts of debian? Do I need to use some special somethings?</FONT>
</PRE>
</BLOCKQUOTE>
Hi<BR>
apparently this is a problem related to the new behavior of udev under Debian. I wouldn't recommand to downgrad udev though. I read the following on videolan's website: <BR>
<BR>
if you have a distribution that uses udev, then you must add/change the following line to the file 50-udev.rules in your /etc/udev/rules.d directory. <BR>
<BR>
%vi /etc/udev/rules.d/50-udev.rules <BR>
# IEEE1394 (firewire) devices (must be before raw devices below) <BR>
KERNEL=="raw1394", NAME="%k" KERNEL=="dv1394", NAME="dv1394/%k" KERNEL=="video1394*", NAME="video1394/%n" <BR>
<BR>
I havent tested it yet, since i havent any DV cam before hand at the moment.<BR>
<BR>
The workaround i used at the time is the following:<BR>
<BR>
first check that you belong to the right groups : disk and video by issuing the command groups <BR>
<BR>
If not, then <BR>
<BR>
$ sudo adduser username disk<BR>
$ sudo adduser username video<BR>
<BR>
<BR>
then run the attached bash script as a superuser after each restart:<BR>
<BR>
$ sudo bash ./dv.sh<BR>
<BR>
you might have to chmod +x the shell script <BR>
<BR>
Start Pd/Gem, pix_video should work as expected if feeded with the pathname given in the shell script <BR>
(I cant remember well this part, i'm sorry i'm only sending a translation of my blog notes, i dont have access to the original machine and Pd program this week (public holiday).) <BR>
<BR>
The shell was adapted from an article about Ubuntu Edgy and DV cams <BR>
<BR>
<A HREF="http://tonywhitmore.co.uk/blog/2006/11/08/ubuntu-edgy-and-dv-cameras/">http://tonywhitmore.co.uk/blog/2006/11/08/ubuntu-edgy-and-dv-cameras/</A><BR>
<BR>
O.
</BODY>
</HTML>