Re: dvgrab

Is there some command to capture dv and split files on date when is video was made, not when new recording starts,

?
DVGRAB works perfect when capture from DVcamcorder, but when capture from VHS 

through
DV issue still exist, but this time makes about 20gb of video and then crash.

Sorry for my english
Best regards from Croatia


________________________________
From: jole jole <[email protected]>
To: [email protected]
Sent: Thursday, April 2, 2009 9:37:22 AM
Subject: re: dvgrab


> 3) > 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   
>
>
> I have to admit I read about this bug, but can i get some simpler
> explanation, because I'm a bigginer at this. I can't find solution .

I understand. The bug is still open. There was some progress, but it
required building dvgrab in a special way (without libdv) to be most
reliable. Well, that lets you capture the DV, but the DV might still
contain some invalid data that will cause applications to crash. It
does not appear that Linux, Firewire, or dvgrab is to blame for this
invalid DV data - it very much seems to be from the device.

A good test for you to do next is to see if the problem only happens
when you use the analog input with your VCR. Capture some footage that
you made using the camera lens.
 
I make another capture of my VHS with dv  cassette in dv camera but I run capture with command : dvgrab -noavc -s 0 -showstatus -d 02:10:00  
and the wrong data ("dvgrab-001.avi": buffer underrunnear: timecode45:85:85.45 date 2009.03.29) disappear, and was replaced with this correct data "dvgrab-001.avi": buffer underrunnear: timecode 00:27:31.45 date 2009.03.29.
With that configuration I make almost 20 gb capture, and then dvgrab was crash (Segmentation fault (core dumped) , before I only make 3 or 4 gb of capture. 
I see in https://sourceforge.net/tracker/?func=detail&aid=2153747&group_id=14103&atid=114103 that everybody have same problem with that wrong data?-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2009/3/31 jole jole <[email protected]>:
> Here is some answers:
>
> 1) send the output of 'ls /sys/bus' so we can see if you are using the
> old ieee1394 or new firewire drivers?
>
> komir@komir-laptop:~$ ls /sys/bus
> acpi  i2c       MCA       pci          platform  sdio   ssb
> eisa  ieee1394  mdio_bus  pci_express  pnp       serio  usb
> hid   isa       mmc       pcmcia       scsi      spi    usb-serial
> komir@komir-laptop:~$

ieee1394 - OK

> 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?
>
> as I say my  English is not very good, but if I understood the question no
> 2:
> Storage: HDD 500.0 GB, SEAGATE Momentus, SATA, 8MB c., 5400
> o./min,Filesystem: NTFS and ext3 (ubuntu studio 9.04 and 8.10)
> I use this disk in windows and capuring works good

looks good unless you are trying to capture to the NTFS partition - I
do not have any experience with that to know if there is a throughput
problem

> 3) > 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 
>
>
> I have to admit I read about this bug, but can i get some simpler
> explanation, because I'm a bigginer at this. I can't find solution .

I understand. The bug is still open. There was some progress, but it
required building dvgrab in a special way (without libdv) to be most
reliable. Well, that lets you capture the DV, but the DV might still
contain some invalid data that will cause applications to crash. It
does not appear that Linux, Firewire, or dvgrab is to blame for this
invalid DV data - it very much seems to be from the device.

A good test for you to do next is to see if the problem only happens
when you use the analog input with your VCR. Capture some footage that
you made using the camera lens.

-- 
+-DRD-+

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p

_______________________________________________
Kino-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kino-dev