Dan (the Kino man) has a video on the kino site.
It shows what to do to check loaded modules, groups, and permissions.
It will recognize the camera type.
--
[gutsy/hardy] Kino can't capture video
https://bugs.launchpad.net/bugs/152392
You received this bug notification because you are a member
dv1394 is going away in the kernel :-(
--
[gutsy/hardy] Kino can't capture video
https://bugs.launchpad.net/bugs/152392
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
@teledyn
Have you tried 'dvgrab', which is the command line wrapper around the
kino capture facility. That way you can easily use 'sudo dvgrab' and it
will use the raw iee1394 device - including starting the playback
automatically on the DV device.
If this doesn't work then the problem is
Neil -- thanks for that strategy advice, I will try that. I had thought
dvgrab and kino were the same code, which is why I raised the issue
here first (since there were already issues overlaying the kino
capture that seemed to preclude any success.
I'm also going to try and obtain a second
** Changed in: kino (Ubuntu)
Assignee: (unassigned) = Neil Wilson (neil-aldur)
--
[gutsy/hardy] Kino can't capture video
https://bugs.launchpad.net/bugs/152392
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Attached is the debdiff which activates the dv1394 facility.
kino (1.1.1-1ubuntu3) hardy; urgency=low
* debian/rules: change without-dv1394 to with-dv1394 (closes
#LP152392)
--
[gutsy/hardy] Kino can't capture video
https://bugs.launchpad.net/bugs/152392
You received this bug notification
** Attachment added: kino_1.1.1-1ubuntu3.debdiff
http://launchpadlibrarian.net/14892581/kino_1.1.1-1ubuntu3.debdiff
** Changed in: kino (Ubuntu)
Assignee: Neil Wilson (neil-aldur) = (unassigned)
--
[gutsy/hardy] Kino can't capture video
https://bugs.launchpad.net/bugs/152392
You
this patch gives me the option to set the device to /dev/dv1394/0 but
with the camera playback rolling, there is still no capture, even when
run as root.
Using dv1394 capture
Leaving Capture
Constructing File Capture tracker
Starting Capture
Using dv1394 capture
AV/C Enabled
Kino Common
on mine, I see /dev/raw1394, it is root.video and I am in the video
group, yet in Kino the dialog for setting the ieee1394 device is an
empty pull-down list; I get the same behaviour when I run kino under
sudo. lsmod shows the raw1394 module is loaded, and the syslog shows
ieee1394: raw1394:
I'm unsure why you've opened a udev task for this bug? I have marked it
as Invalid.
** Changed in: udev (Ubuntu)
Status: New = Invalid
--
[gutsy/hardy] Kino can't capture video
https://bugs.launchpad.net/bugs/152392
You received this bug notification because you are a member of Ubuntu
For the record, the simple fact is that the kernel firewire subsystem is
entirely inadequate for your needs.
In past bugs, people have compared the expected functionality with the
USB subsystem, but now compare the implementation.
For USB, we have, for each single device, a multitude of sysfs
I marked this as a udev bug because something has been changed in the
permissions system between Feisty and later versions.
In Feisty dv1394 was accessible to Kino (dvgrab) with no user
interaction. I assume that this was some kind of 'read only' connection,
I think that's part of the point of
@James: 'The file at '/dev/dv1394/0' should be the solution to this
problem' /dev/dv1394/0' gives access to capture dv over firewire without
the security risks. But Kino has to be compiled with a certain flag or
it won't look for the '/dev/dv1394' file, I understand this is because
of some
@Duncan
Except that /dev/dv1394 doesn't provide full functionality, as the user can't
operate the playback controls (unless something has changed from last time I
looked into this). IMO, I think that some sort of controlled privilege
elevation is the right way to go.
--
[gutsy/hardy] Kino
@James: I agree totally - I just haven't heard anyone suggest a way of
doing this that the dev team thinks is acceptable.
--
[gutsy/hardy] Kino can't capture video
https://bugs.launchpad.net/bugs/152392
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Since raw1394 access can't really be given to users, we have to find
some sort of workaround that makes itself obvious.
How about the possibility of policykit integration (I know that can't be
done for hardy)?
We could have a better error message with instructions when /dev/raw1394
exists, but
** Description changed:
Ubuntu Gutsy, installed from Tribe 5 CD. Updated October 13th. This
camera and this system works fine capturing with Kino on Feisty.
We're right back to the old message:
'Edit Preferences IEEE1394'
-
The IEEE 1394 Subsystem is not
** Summary changed:
- [gutsy] Kino can't capture video
+ [gutsy/hardy] Kino can't capture video
** Description changed:
Ubuntu Gutsy, installed from Tribe 5 CD. Updated October 13th. This
camera and this system works fine capturing with Kino on Feisty.
We're right back to the old
** Description changed:
Ubuntu Gutsy, installed from Tribe 5 CD. Updated October 13th. This
camera and this system works fine capturing with Kino on Feisty.
We're right back to the old message:
'Edit Preferences IEEE1394'
-
The IEEE 1394 Subsystem is not
19 matches
Mail list logo
