On 26 Nov 2003, Florin Andrei wrote:

> So, since we're at "look at the preview release and say what you don't
> like" anyway :-) here's another documentation feature request:

        Just a bit late for this one - the next release candidate is
        RSN (Real Soon Now). Ronald's probably working it right now .

        Maybe next one ;)

        If you can't wait you can do a 'cvs update' - no more changes are 
        anticipated aside from coredumping show stoppers.

> mpeg2enc. Would it be too hard to document:

        Well, yes, at least a little bit ;)    There's the problem of implied 
        knowledge - after a certain point the mjpegtools documentation would
        end up being a treatise on video compression and there are tons of
        excellent books on that topic.

> - what are those steps (essentially, what happens in each one of them)

        You mean it's not intuitively obvious that single coefficient
        elimination would be done between the quantization and encoding? :-)

        Oh - you can safely use "-N x.x" with "-H"  now, that was something
        I fixed.  Previously the last one used would override the first.
        And you can use "-N" with "-K" to further customize/tailor the 
        tables if desired.

> > You can, if you wish, create your own custom matrices and use them
> > with "-K file=path_to_your_file".   Thus you can take the intra (I
> 
> You'da man! I was looking for precisely the same thing: something to

        (thankful) shrug - just doing my small part in the collective effort.

        *WARNING*

        The parser for the '-K file=' option is simplistic in the extreme -
        don't put extra whitespace, extra commas, hard (DOS) newlines, and
        so on in the file.

        As a diagnostic/debug aid you can spell 'file=' as "FILE=" and 
        mpeg2enc will log to stderr the tables it read in so that you can
        verify the correctness of the parsing.

> boost the quality of the full frames, while keeping the delta frames
> "good enough". But not so painfully pedantic as a full-blown hi-res
> (which, BTW, is a bandwidth pig).

        Na, you want a bandwidth pig try "-g 1 -G 1" and generate only
        I frames :)  Encoding is very fast but the files end up being
        60% larger than a GOP size of 15 using P frames.

        But I thought you weren't on a bit budget... ;)

        Cheers,
        Steven Schultz



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users

Reply via email to