I just checked into CVS a major rework of the Kino Firewire interface. It uses libiec61883 exclusively, if available, for the DV data I/O. Of course, libavc1394 is still used for device discovery and control. Also, one does not need to specify which raw1394 interface card/port to use. The AV/C device selection implies what to use. Finally, I removed all of the advanced settings that one very rarely needs. I am not a simplfication overlord. The advanced settings were put in much earlier to allow experimentation and tweaking of new features that were not proven. With maturity comes some confidence that the defaults work for 99% of the people for whom it works at all. As a result, the Preferences panel looks much less intimidating. :-)

Due to security implications of exposing the raw1394 device file for read/write to any user by default, the next Kino version continues to support the dv1394 device. dv1394 exposes much less funciotnality so its device files can be given more permissions by default. However, it exposes multiple files, at least one per interface card/port, which is a usability problem. This can probably be resolved by using the /sys/bus/ieee1394 tree for device discovery instead of librom1394. For now, when using dv1394, Kino exposes an additional field for the entry of the device file name because another usability problem is lack of a defacto standard name for the device file.