On Wed, 16 Nov 2005 20:49, Steve O'Hara-Smith wrote: > I had a quick look at what has happened to the capture code in > mplayer since I last saw it (and felt a bit ill). It seems that it pretty > much depends on the frame sync signals from the bktr device with a fallback > one second alarm. I know that missing frame sync signals are not uncommon > from instrumenting my capture code in ffmpeg which is kept sane by using > a tightly timed usleep to capture a frame close ot the right time when the > signal is missed.
Hmm I see.. > I'm guessing that enabling the audio capture is causing signals > to be missed. Strange.. I wouldn't expect to miss signals.. Missing frames I can believe - the picture quality sucks due to a long cable. Time to dig into the code myself I guess :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
pgpMnlmevE6cD.pgp
Description: PGP signature
