[PD] Gem and ieee1394 firewire cam on linux debian

Tim Boykett tim at timesup.org
Thu Aug 16 07:54:22 CEST 2007

Hi Georg,

  Thanks for your reply. When you say "quite some time ago" when was
that approximately? I see that in Dec 06 Ico Bukvic was having
the same problem, but the thread stops on the PD list.

Anyway, I tried your suggestion.

When I try this I get "Bad argument for message 'driver' to object  

Seeing as when I send |driver 1( to pix_video I receive the error
message that refers to /dev/ieee1394/dv/host0/PAL/in, or host1 if I
have send |device 1( message, then I would guess that the external
is trying to do the right thing.

I must mention that /dev/ieee1394 does not even exist in my hierarchy.
Perhaps something has not been created for this.

However, Kino and dvgrab work "out of the box" so the basics are all
working fine. Only PD is trying to do the wrong thing.

Hmmm, any further ideas?



On 15/08/2007, at 8:07 AM, Georg Holzmann wrote:

> Hallo!
>> But I am having no luck with pix_video or pdp_v4l. The main problem
>> seems to be that (apparently) recently the naming conventions
>> in debian and possibly linux in general were changed. So there is
>> no more /dev/video0 for the v4l mode, and for pix_video trying to
>> work directly with ieee1394, I get complaints that /dev/ieee1394/ 
>> dv/ host/PAL/in
>> "Is a directory".
> Yes we had this discussion quite some time ago: I think you can  
> open the device with sending the message [driver /dev/ieee1394/dv/ 
> host/PAL/in( (fill in your device) to [pix_video]. If not let me  
> know, then the fix was not added ...
> LG
> Georg

More information about the Pd-list mailing list