Stan Brown wrote:
On Tue Dec 4 09:08:38 2001 Justin Schoeman wrote...
Stan Brown wrote:
The DivX library is not initialising properly. Try "locate
libdivxencore", and see if there are multiple versions lying around.
Try to delete them, and re-install the latest version.
OK, I purged all copies of this library, re configured NVrec, rebuilt it
and now it sarts. However, Im shure getting lot's of error message:
Script started on Tue Dec 4 18:21:26 2001
stan@yogi:~$ DIVX4rec -dq 3 -o test.avi
Starting NVrec.c, version 20011204 (NVrec-20011204).
Error opening "/etc/NVrec.conf"
Error opening "/home/stan/.NVrec.conf"
v4l1 core init - Size: 384x288 from /dev/video
v4l1 core init - could not get enough buffers - using copy mode
v4l1 core init - got 2 buffers
v4l1 core init - emulating 60 buffers
v4l1 core init - trying video format YUV420
oss core init - 44100 bps, 16 bits, mono, from /dev/dsp
oss core init - 3528 bytes per frame (128,9)
oss core init - 826 buffer frags required of 512 bytes
divx4file core init - file: test.avi (384x288)
file core init - frame rate is 25.000000
Got DivX bitrate: 910000
oss core thread - starting!
nvrec core - not using any sync() method
NVrec: initial sync - audio: 1007508088920514143 video 1007508088917399000 (delta 0.003115)
v4l1 core next - new frame out of sequence - ignoring
NVrec: error getting more video data. Trying to continue.
Frame | CPU/estimated | time/estimated | play/CPU | ETA
VQ: 0.107 Offset: 0.002 Slipage: 0.012 Warp: -12 Drop: 0 VQ: 3.424 Offset: 0.004 Slipage: 0.012 Warp: -12 Drop: 0 VQ: 5.173 Offset: 0.005 Slipage: 0.012 Warp: -12 Drop: 0 VQ: 7.258 Offset: 0.001 Slipage: 0.012 Warp: -12 Drop: 0 v4l1 core next - new frame out of sequence - ignoring
> ...
NVrec: error getting more video data. Trying to continue.
VQ: 7.028 Offset: 0.004 Slipage: 0.008 Warp: -7 Drop: 0 VQ: 10.365 Offset: 0.005 Slipage: 0.008 Warp: -7 Drop: 0 VQ: 11.497 Offset: 0.005 Slipage: 0.008 Warp: -7 Drop: 0 VQ: 11.716 Offset: 0.000 Slipage: 0.008 Warp: -7 Drop: 0 VQ: 11.579 Offset: 0.002 S
Also how do I control the lenght of the capture?
Thanks for all the help on this.
Oh, BTW even droping the quality to 1 doesn't make all the errors go away,
althogh it does reduce the qty. This is on an Athalon 750mHZ with 256MB of
memory, a WinTV card, and an IDE drive, if thta helps.
The "errors" are due to the difference between the system clock, and the
source video clock. Unfortunatley, low-end capture cards do not
generate a clock from the input stream, so we have to use the system
clock. The slight drift between the two will result in occasional
(although hopefully rare) frame drops/dups.
V4L2 is a little better, as the frame is timestamped on the VSYNC pulse,
which improves the accuracy quite a bit.
You can control the length of capture with the "-F x" switch, where x is
the number of frames to capture, or the "timer" app in the tools directory.
-justin
