[mythtv-users] nuvexport causes mythtranscode memory leak, swap file gone in secs

[Chris Petersen]

On Mon, 2003-09-29 at 18:27, Chris Germano wrote:
> What's going on? Is it mythtranscode, 
> nuvexport or the encoders???

If mythtranscode is "leaking" memory, that's most likely due to its a/v
buffer misalignment corrections.  Most likely, for some reason ffmpeg
(which should be what's being used for divx export) is losing it's
"grip" on either the audio or video fifo, and mythranscode is buffering
that stream until it gets read from the fifo.

Unfortunately, the --fifosync option isn't supposed to be used with
ffmpeg, since it has a tendency to create an infinite wait if ffmpeg
wants to read from audio/video, and mythtranscode is expecting it to
read from the other (eg. it won't send more audio until its related
block of video is read).

> The other issue is that my audio is still way off -- about 6 seconds before 
> my video:
> 2003-09-29 18:20:27 Audio is 154ms ahead of video at # 3530
> 2003-09-29 18:20:45 Audio is 120ms ahead of video at # 3532bits/s
> 2003-09-29 18:20:50 Audio is 86ms ahead of video at # 3534kbits/s

How is that 6 seconds?  154ms is .154 seconds.   Or are you talking
about in the final output?

> I'm using btaudio to capture at 32000hz, but it sounds right, just not a/v 
> synced, but one thing at a time lol. I also notice nuvexport likes to do 
> things in PAL, um is that hardcoded into it since i'm NTSC?

No it doesn't.  I've added preliminary PAL support, but the only way it
would be executing as PAL is if it detected your streams as PAL streams
from the nuv header (by the framerate).

-Chris