Re: DVGRAB
Dan Dennedy <[email protected]>
| Newsgroups | gmane.comp.video.kino.devel |
|---|---|
| Message-ID | <[email protected]> |
2009/3/30 jole jole <[email protected]>: > For the first time I use dvgrab ( before windows user, now I "try" ubuntu), > and now I discover another problem, after some time of capture I had error : > > # > komir@komir-laptop:/media/disk/Stari$ sudo dvgrab -noavc -s 0 -showstatus -d > 03:10:00 -f dv2 -nostop > Found AV/C device with GUID 0x08004601021fda7e > Turning on OpenDML to support large file size. > Capture Started > > 03:57:30 > "dvgrab-001.avi": buffer underrun near: timecode 45:85:85.45 date 2009.03.29 This timecode value is strange because there are only 60 seconds in a minute and 60 minutes in a hour. This timecode is in the DV stream received from the device - dvgrab and dependencies merely extracts the timecode and displays it. > 03:57:30 > This error means that the frames could not be written fast enough. In dvgrab 3.2 and earlier versions, this message would be produced under two different conditions - one for the reason reported. Another reason would be due to some DV data corruption - missing or invalid packets that had been dropped. dvgrab uses a firewire library libiec61883, and in version 1.2.0, I increased the validation testing on DV packets, which can increase the amount of these errors. The invalid DV packets was causing some DV parsers and decoders to crash. dvgrab v3.4 now separates these two error conditions to make the source of the problem more clear. For now, there are 2 things for you to investigate and provide more information: 1) send the output of 'ls /sys/bus' so we can see if you are using the old ieee1394 or new firewire drivers. 2) What kind of storage and filesystem are you writing to? Is it fast enough to support the file writing for the somewhat high datarate of DV? > 2009.03.29 04:06:42Segmentation fault (core dumped) > # We have an open bug for some invalid DV data creating a crash in libdv, which dvgrab uses. Currently, this is what I suspect due to seeing invalid timecode in the messages. Here is that bug report: https://sourceforge.net/tracker/?func=detail&aid=2153747&group_id=14103&atid=114103 > komir@komir-laptop:~$ cat /etc/lsb-release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=9.04 > DISTRIB_CODENAME=jaunty > DISTRIB_DESCRIPTION="Ubuntu jaunty (development branch)" > > same problem appears on ubuntu 8.10 > > > komir@komir-laptop:~$ aptitude show dvgrab > Package: dvgrab > State: installed > Automatically installed: no > Version: 3.2-2 > Priority: extra > Section: universe/graphics > Maintainer: Ubuntu MOTU Developers <[email protected]> > Uncompressed Size: 369k > Depends: libavc1394-0 (>= 0.5.3), libc6 (>= 2.4), libdv4, libgcc1 (>= > 1:4.1.1), > libiec61883-0 (>= 1.1.0), libjpeg62, libquicktime1 (>= > 2:1.0.3+debian), > libraw1394-8, libstdc++6 (>= 4.2.1), zlib1g (>= 1:1.1.4) -- +-DRD-+ ------------------------------------------------------------------------------