At 2001-06-05 11:32:58, Justin Schoeman <justin@xxxxxxxxxxxxxxxxxxxx> wrote: > After many comments/complaints about my existing capture engines, I > finally sat down and wrote a new one. After two evenings of furious > coding, I have a very alpha program just waiting for a few suckers to > test. There are a number of problems documented in KNOWN_BUGS (and > probably quite a number that aren't too!). > > The capture core features perfect A-V synchronisation, irrespective of > frame drops/video loss, etc. It also has dynamic time warping of the > audio stream to ensure that EXACTLY the right amount of audio data is > written for the number of video frames (at least averaged over a couple > of frames). This removes the problem of synch drift over long > recordings (without any clicks/pops). Hi Justin, Your code is the first I have used under Linux that will synch audio and video properly during capture! That's great, but I do have one problem using it. After a few minutes of capture, I get the following error from DIVXrec: VQ: 29.476 Offset: 0.005 Slipage: 0.003 Warp: -7 Drop: 0 v4l2 core next - new frame out of sequence - ignoring-7 Drop: 0 NVrec: error getting more video data. Trying to continue. v4l2 core next - new frame out of sequence - ignoring-7 Drop: 0 NVrec: error getting more video data. Trying to continue. v4l2 core next - new frame out of sequence - ignoring-7 Drop: 0 NVrec: error getting more video data. Trying to continue. v4l2 core next - new frame out of sequence - ignoring-7 Drop: 0 NVrec: error getting more video data. Trying to continue. v4l2 core next - new frame out of sequence - ignoring-4 Drop: 0 NVrec: error getting more video data. Trying to continue. [...loops a million times until I hit Control-C...] At this point it stops capturing video but keeps on capturing audio. The resulting DivX AVI file is valid, but the video freezes at this point. My load never goes above 0.5 on this P3-833 768Mb RAM. The capture file is on a separate (fast) disk, and I can't really find any system bottleneck that might be interfering with a successful capture. If I do create large load on this box, the DIVXrec program drops a few frames and continues OK (until the above error). I'm running kernel 2.4.5 with v4l2. I have a $50 bt878 hooked up to cable TV box. My dmesg follows: Video for Linux One (2.2.16). Major device: 81 Video for Linux Two (V0.20). Major device: 81 i2c-core.o: driver i2c TV tuner driver registered. bttv: driver version 0.7.53 loaded bttv: Bt8xx card found (0). PCI: Found IRQ 10 for device 00:0a.0 PCI: The same IRQ used for device 00:0a.1 bttv0: Bt878 (rev 17) at 00:0a.0, irq: 10, latency: 32, memory: 0xe3020000 bttv0: subsystem: 0070:13eb => Hauppauge WinTV => card=10 bttv0: model: BT878(Hauppauge new (bt878)) [insmod option] bttv0: Hauppauge msp34xx: reset line init i2c-dev.o: Registered 'bttv0: i2c adapter' as minor 1 tuner: chip found @ 0x61 bttv0: i2c attach [Philips NTSC] i2c-core.o: client [Philips NTSC] registered to adapter [bttv0: i2c adapter](pos . 0). i2c-core.o: adapter bttv0: i2c adapter registered as adapter 1. bttv0: Hauppauge eeprom: model=44001, tuner=Philips FI1236 MK2 (2) bttv0: i2c: checking for MSP34xx @ 0x80... not found bttv0: i2c: checking for TDA9875 @ 0xb0... not found bttv0: i2c: checking for TDA7432 @ 0x8a... not found V4L2: Registered "BT878(Hauppauge new (bt878))" as char device 81, 0 V4L2: Registered "Bttv2 VBI device 0" as char device 81, 224 Any ideas why this happens after ~5 minutes of capture? I would love to be able to make this work. :-) More details: I am using NVrec version 20010612 from your web site. My insmod options are: /sbin/insmod /lib/.../videodevX.o /sbin/insmod /lib/.../tuner.o type=2 /sbin/insmod /lib/.../bttv2.o card=10 tuner=2 bttv_norm=1 \ bttv_maxmem=16 -Nathan Bradshaw nb@xxxxxxxxxxx
