Same Error in 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779680
Title:
Firewire broken
To manage notifications about this bug go to:
I think this is still an issue in Trusty!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779680
Title:
Firewire broken
To manage notifications about this bug go to:
I'm not clear if this is the same bug that I am experiencing, but I am
having a similar problem that just began last weekend after I ran an
Ubuntu update on Ubuntu 12.04 64-bit. Previously, I was able to capture
from my Canon HDV Vixia HV30, than one day, the message in the command
window said:
There clearly is some kind of permissions problem.
I ran as root and I can capture video (after linking /dev/raw1394 to
/dev/fw0 )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779680
Title:
see if doing this helps
in a terminal
LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so dvgrab
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779680
Title:
Firewire broken
To manage notifications about
Thank you, but it didn't work, the command
LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so dvgrab returns:
Found AV/C device with GUID 0x008088030730d524
Waiting for DV...
And nothing happens, when killing the process it outputs:
0.00 MiB 0 frames
Capture Stopped
Error: no DV
dmesg upon executing the
I have the same problem. It seems it's a kernel problem because (as I
understand) dvgrab should work with the new firewire stack too. But that
new stack seems to be broken at least for some people. You can find
several forums post in the net about it.
dmesg shows this:
[ 430.890270]
** Changed in: dvgrab (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779680
Title:
Firewire broken
To manage notifications about this bug go to:
Confirming this issue still exists and there is no supported work around
at the moment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779680
Title:
Firewire broken
To manage notifications about
Same problem!
The vloopback module doesn't compile:
vloopback-source 1.3-2
with
linux-headers-2.6.38-8-generic 2.6.38-8.42
(ubuntu natty)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779680
Title:
I still haven't found a working solution, but there seems to be an
alternative.
sudo aptitude install v4l2loopback-source module-assistant
sudo module-assistant auto-install v4l2loopback-source
sudo modprobe -r ohci1394
sudo modprobe firewire-ohci
sudo modprobe v4l2loopback
sudo gst-launch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779680
Title:
Firewire broken
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Regarding kino and dvgrab, it seems like they are looking for the device at the
wrong place. So sudo ln /dev/fw0 /dev/raw1394 solves the problem for them.
But dv4l still isn't working because the vloopback module cannot be compiled:
sudo apt-get install vloopback-source
cd /usr/src/
sudo bunzip2
13 matches
Mail list logo
