Sorry, Mark. I have the configuration working on my Linux box and have not touched it in over a year. I am not aware of recent kernel or driver changes.
Well, the chroot lenny install was not able to access the firewire hardware. I tried a vm player version of lenny, and vmware is not able to access firewire. So, I am back to my amd64 machine trying to get the video off my camera.
I see that raw1394 have been replaced in newer kernals. Some posts say it should not matter, and others disagree. Do you know of ither ways to grab DV from a camera? Google has not helped much in that regard.
Thanks,
MarkOn Sun, Dec 5, 2010 at 8:01 PM, Mark Phillips <mark@phillipsmarketing.biz> wrote:
On Sun, Dec 5, 2010 at 5:28 PM, Alan Dayley <adayley@gmail.com> wrote:I have always used Kino and the interface to dvgrab and other tools in my acquisition of video from my camera. I have not seen driver problems like you are describing. And yes, that does look like a driver problem to me.I was always on 32-bit Linux. It appears you are using 64-bit. Are there any problems with this difference?
I just installed from the Debian repositories so I am not aware of any issues. I have a chroot lenny 32 bit installed, so perhaps I could try that. Just the command line dvgrab, and then move the files over to 64 bit land.
Sorry, but at the moment I am out of ideas for you.
So am I! ;-)AlanOn Sun, Dec 5, 2010 at 9:15 AM, Mark Phillips <mark@phillipsmarketing.biz> wrote:
---------------------------------------------------I have been trying to get dvgrab to work with my setup and I can't seem to get it to grab the video from my camera over firewire. It starts the camera says it is grabbing video, but never writes a file with the video to my hard disk. Running dvgrab as a normal user occaisionally gives me a segmentation fault. Even running it as root does not create an output file.
A typical run:
orca:/home/mark/Movies/Savage/clips# dvgrab -f dv2 foo-
Found AV/C device with GUID 0x0800460102561c47
Waiting for DV...
"": damaged frame near: timecode ??:??:??.?? date ????.??.?? ??:??:??
This means that there were missing or invalid FireWire packets.
......quite a few of these as the camera starts and comes up to speed. Once the camera is up to speed, they stop. I assume (perhaps incorrectly?) that these are just due to the camera motor coming up to speed. After running for a minute and no error messages I hit ctrl-C and get this:
^C"": 0.00 MiB 0 frames timecode 00:00:00.00 date 2010.12.05 09:10:52
Capture Stopped
Warning: 151 damaged frames.
I am running Debian testing amd64.
Google gave me this tip: http://mylinuxramblings.wordpress.com/2010/01/02/grabbing-dv-from-a-video-camera-using-dvgrab-kdenlive/ and followed those simple instructions. Still noo ouput file. Is the addition of the file raw1394.rules with the contents (KERNEL==”raw1394″, GROUP=”video”) to /etc/udev/rules.d necessary?
I am trying to use Lives to edit the videos, but I can't even get past the command line usage of dvgrab!
Thanks!
Mark
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss