>Just a couple of surprises.
>It seems that you have to give the --enable-lzo option to './configure'
>just to get support for the .nuv import filter.
This is mentioned in the manpage, but probably ought to be in INSTALL
as well--good point.
>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.
>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.
>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?
>Judging by other posts, there's been some syntax changes to the -y
>option in the 1.1.0 branch, maybe I just need to learn a bit more about
>that.
Those changes are only for the new module system (NMS), which is
still at an experimental stage. For ordinary usage, -y works the same as
it always has.
>Do I also see signs that as yet, 'transcode' can't produce an mpeg
>multiplex? I presume that (for now) transcode could produce mpeg2 video
>and mp2 sound as elementary streams, and I could run 'mplex' by hand to
>create a program stream. That's what I apparently has to do in 1.0.2 anyway.
Yes, that's correct. Native MPEG multiplexing is under development
as well, but won't be available for a while.
--Andrew Church
[EMAIL PROTECTED]
http://achurch.org/
