On Wed, 2005-09-07 at 23:24 -0700, Steven M. Schultz wrote: > On Wed, 7 Sep 2005, Florin Andrei wrote:
> > But some older mjpegtools versions never had this issue, even at 8500, > > No, they had the problem. I recall various postings with "8500" and > the advice was the same then as now ;) Well, look at it from my perspective. I create DVDs for quite a while using 8500 and never had problems. At some point, switch to a newer mjpegtools release and all of a sudden I start seeing image judder even at 8000. I'm afraid I have no idea when did that happen (between which releases). Also, this DVD player plays all kinds of commercially-available material, hundreds of disks, regardless of the quality and nature of the actual physical disk, and has no problems whatsoever. But throw in a DVD encoded with mjpegtools at 8000 and sometimes the image may start to judder. I guess I could start encoding at lower bitrates, but you know - my DVD player has the option to display short-time bitrate averages (like, 1 sec average or so) as the movie is playing, and with commercial material I often see the bitrate going above 8500, sometimes significantly more. No problems whatsoever. That's why I tend to think of it more like a player that's following the standard to the letter, rather than a broken player. I would replace it, but I still think it's worth keeping it around, to spot issues with encoders and stuff. > Besides, nothing's been done in ages in the encoder except to disable > the threading, fix DualPrime, and use fixed GOP sizes (the variable > gop size logic is inoperative). I'll check the cvs logs but the > rate control hasn't been rewritten/redone in a long time is what I > seem to recall. Then maybe it's not a bitrate problem. > > use packages, but package repositories only follow "stable" releases > > That's their problem to a degree. I think my feelings about package > systems are well enough known to not need repeating. In any case, using packages is becoming more and more a reality, at least among Linux users, as the user base expands. It is merely a fact, beyond our personal preferences. > > Too bad, since it's the best open source MPEG2 encoder I'm aware of. > > Thanks! :) If you think there's rate control issues with mpeg2enc > you should try ffmpeg sometime <grin> I know, that's why I'm trying to stick to mjpegtools. > But have you tried any bitstream verifiers and/or other DVD authoring > software to see if it complains about the files? No, but sounds like a good idea. Any freeware tools I could play with? Ideally on Linux, but I guess I could reboot to Windows every now and then. -- Florin Andrei http://florin.myip.org/ ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Mjpeg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mjpeg-users
