raw1394 wrong group for kino/dv camera capture

[Paul Precious]

Binary package hint: udev

Most video camera´s use raw1394 for capture. Kino is the program used to capture and edit video.
However, in dapper the raw device is marked as Group=¨DISK¨. This means that users must manually edit the permissions file to change to ¨video¨ in order to get kino working.

Recommend the following by default

$ sudo gedit /etc/udev/rules.d/40-permissions.rules
2) search for the line
KERNEL=="raw1394", GROUP="disk"

and change it to
KERNEL=="raw1394", GROUP="video"

[Scott James Remnant (Canonical) (canonical-scott)]

No.

NO.

 _ _ ___
| \ | |/ _ \
| \| | | | |
| |\ | |_| |
|_| \_|\___/

[Paul Precious (preciousp)]

I'll take that as a no then :-)

I guess its a feature not a bug?

Thanks for the prompt reply

On 5/24/06, Scott James Remnant <email address hidden> wrote:
>
> No.
>
> NO.
>
> _ _ ___
> | \ | |/ _ \
> | \| | | | |
> | |\ | |_| |
> |_| \_|\___/
>
>
> ** Changed in: udev (Ubuntu)
> Status: Unconfirmed => Rejected
>
> --
> raw1394 wrong group for kino/dv camera capture
> https://launchpad.net/bugs/46393
>

[Scott James Remnant (Canonical) (canonical-scott)]

Use the video1394 device? :)

[Paul Precious (preciousp)]

you are right. Default in kino is wrong.
you need to select dv1394 as the driver then /dev/dv1394-0 as the device
many thanks and different to the forums

On 5/24/06, Scott James Remnant <email address hidden> wrote:
>
> Use the video1394 device? :)
>
> --
> raw1394 wrong group for kino/dv camera capture
> https://launchpad.net/bugs/46393
>

[Paul Precious (preciousp)]

Looks like I spoke too soon.
I changed the permissions back so raw1394 is back as a disk
now kino won´t let me control the video camera. it says on the preferences
that you must have read/wrtie access to raw1394.
I guess this may be a kino problem. I assume if these dev´s changed the
device to have read/write access to /dev/dv1394-0 then then camera control
would be enabled.

Should I post something on the kino site?

I´m thinking that if the ubuntu forums suggest changing the udev permission
on raw1394 to video - and that this is a no no. Then if we are to aviod
people doing this we must get kino changed?

On 5/25/06, Paul Precious <email address hidden> wrote:
>
> you are right. Default in kino is wrong.
> you need to select dv1394 as the driver then /dev/dv1394-0 as the device
> many thanks and different to the forums
>
>
> On 5/24/06, Scott James Remnant <email address hidden> wrote:
> >
> > Use the video1394 device? :)
> >
> > --
> > raw1394 wrong group for kino/dv camera capture
> > https://launchpad.net/bugs/46393
> >
>
>

[Paul Precious (preciousp)]

Found this bug reference Bug #6290
looks like its already reported

On 5/25/06, Paul Precious <email address hidden> wrote:
>
> Looks like I spoke too soon.
> I changed the permissions back so raw1394 is back as a disk
> now kino won´t let me control the video camera. it says on the preferences
> that you must have read/wrtie access to raw1394.
> I guess this may be a kino problem. I assume if these dev´s changed the
> device to have read/write access to /dev/dv1394-0 then then camera control
> would be enabled.
>
> Should I post something on the kino site?
>
> I´m thinking that if the ubuntu forums suggest changing the udev
> permission on raw1394 to video - and that this is a no no. Then if we are to
> aviod people doing this we must get kino changed?
>
>
> On 5/25/06, Paul Precious <email address hidden> wrote:
> >
> > you are right. Default in kino is wrong.
> > you need to select dv1394 as the driver then /dev/dv1394-0 as the device
> > many thanks and different to the forums
> >
> >
> > On 5/24/06, Scott James Remnant <email address hidden> wrote:
> > >
> > > Use the video1394 device? :)
> > >
> > > --
> > > raw1394 wrong group for kino/dv camera capture
> > > https://launchpad.net/bugs/46393
> > >
> >
> >
>

[Dan Dennedy (dan-dennedy)]

dv1394 does not implement the camera control protocol. libavc1394, which uses raw1394 does. Why? Well, it is a matter of these being different protocol from differing standards bodies and the history of their implementations. It is still possible to capture and export when all you have access to is dv1394 by manually controlling the device. However, usage of dv1394 is not as friendly when you have more than one 1394 interface on the system.

Still, having access to raw1394 is much nicer, and most users will prefer it. Has it not occurred to anyone else but me that you can create a _new_ grouped named "raw1394" ?!

Finally, in the other bug, I suggested Ubuntu follow the dv1394 naming convention as established on linux1394.org FAQ topic on udev. This also affords some backwards compatibility with Debian kernel 2.4 and it did not use devfs and setup dv1394 as /dev/dv1394/%n.