>> > > > Ok, so I just discovered that yuvmedianfilter has a -I switch for >> > > > interlaced inputs (it switches to separate field filtering). >> > >> > Shouldn't this be something that yuvmedianfilter should set >> > automatically from the incoming yuv4mpeg header? >> >> Hmmm, interesting thought. The capability exists to do that of >> course. Maybe it's just an oversight that it was not done sooner. >> Also if it had been automatic the bug would have surfaced sooner ;) >> >> I imagine though if it's made automatic an option to disable it >> would be needed. > >Then how about this as a suggestion: > >No -I on command line - use value from yuv4mpeg header. >-I 0 - force no-interlace mode, ignoring yuv4mpeg header. >-I 1 - force interlace mode, ignoring yuv4mpeg header.
Um, I'd vote for no option at all (use interlacing as specified in the stream header only); but if the option is staying in there, *please* document it in the manpage as "Overrides what is specified in the header; this option is not necessary with normal use." Otherwise, people will be confused and throw "-I" in for no good reason --- much like they still continue to use such options for mpeg2enc/etc even though all this great info is now passed around in the headers. (The poor mir.com network has been mostly screwed all week; I'm just getting some of these e-mails trickling in... maybe this has allll been taken care of already.) -matt m. ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ Mjpeg-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mjpeg-users
