Re: [transcode-devel] A/V sync problem transcoding from .nuv to .mpeg

[Steve Hosgood]

Andrew Church wrote: This looks like a side effect of other changes, and certainly isn't obvious to a random punter. Might I suggest that someone renames --enable-lzo to --enable-nuv This would be wrong, because LZO by itself is a valid import/export module. However, I could see the use of an extra --enable-nuv option, which would generate errors if --enable-lzo was not also given. Fair enough - I hadn't spotted the possible use of LZO as an output module. However, it isn't totally true to say that NuppelVideo depends on LZO. Remember that patch that I contributed to get import_nuv.c to compile in the absense of LZO? Well, though I couldn't try it on 1.1.x, I "ported" it to 1.0.2 and it worked without LZO (albeit rather strangely). I suspect that LZO compression of .nuv streams is an option, not a requirement. Of course, compiled without LZO would mean that the .nuv import module wounldn't be able to decode *all* .nuv streams, but it would be OK for "vanilla" .nuv streams, and I suspect that that covers most .nuv streams generated as a result of live analog video capture. I can't seem to get "-y ffmpeg -F mpeg2video" to work, nor anything involving "-y mpeg2enc". Actually, the former generates status lines indicating that it is working, but mplayer complains there's no video in the resulting file..... I guess the first question would be, does it work with anything besides NuppelVideo? (I'd be surprised if it did.) ISTR that mpeg2video produces a raw .m2v stream rather than an AVI file, for the purposes of later multiplexing. That would make sense, but if it did, I couldn't find it. The latter just barfs complaining about a missing shared library. Again, it would have been nice if ./.configure had noticed that there was something amiss with the shared library. What's the exact error? I'll have to recompile on my home machine to be sure, and that's not going to happen tonight! I'll back to you with an error report ASAP. Steve.