mplex vs IfoEdit vs MuxMan

[mpucoder]

I'm trying to make this comparison fair, but having some difficulty. First is no VB runtime, and no intent to install it. So I tried running just mplex in DVD mode and got horrible results.
The results are not quite public (not linked on the MuxMan page) but available here (http://www.mpucoder.com/Muxman/mplex2_0_0.txt)

It's obvious that mplex builds only a skeleton NAV pack, but there are other problems. All-in-all mplex 2.0.0 did worse (broke more rules) than IfoEdit!
The command used is on the page, so if any mplex gurus spot anything that would improve the results, let me know and I'll rerun it.

Q - is there a way to specify the audio buffer size? Mplex reported using a 16K buffer - that's wrong for DVD.

[Sir Didymus]

Some time ago (on last October) I carried out some little comparisons -- just looking at the STD buffer handling, no other aspects involved -- among some remuxing and authoring tools available to me...

This picture (http://img96.exs.cx/img96/7972/Original.gif) is showing the STD buffer occupancy of the video stream contained in the source material. The graphics has been produced with Excel, and the data have been acquired using the Philips DVD-Video Verifier. The X axis is the time scale (in microseconds, so 45.000.000 means the first 45 seconds of the video stream...). The material has been produced using Scenarist, and the video stram is encoded at constant bitrate. See this thread for further information about the Fritzdis tests and the generation of the original:
http://forum.doom9.org/showthread.php?s=&threadid=82485&perpage=20&highlight=fritzdis%20test&pagenumber=1

The size of buffer is 237568 bytes. As it is possible to see, in no parts of the source the real time simulation shows buffer underflows or overflows.

This picture (http://img96.exs.cx/img96/6087/IfoEdit.gif) is related to a test based on compressing the source at 85% with CCE and using Ifoedit fo re-authoring a new title. It's possible to see that some "special" care should be present into the code of Ifoedit for preventing underflows and overflows. Despite of this, frequent overflow situations are present, a little bit over 250.000 bytes...

This other picture (http://img91.exs.cx/img91/9996/Mplex.gif) is obtained using mplex for remuxing the m2v and the ac3 streams. The result is very similar to the one of Ifoedit, even though Ifoedit is a little bit better, since the overflow speaks are less deep...

This picture (http://img96.exs.cx/img96/1597/DVDLab13.gif) is obtained using DVD-Lab 1.3 for re-authoring the m2v and the ac3 streams. Here the situation is "quite" good: just four overflow have been detected...

This picture (http://img27.exs.cx/img27/1084/DVDLabProB16.gif) has been produced with DVD-Lab Pro (beta 16 release). Finally the authored stream is fully compliant. No overflows, no underflows. Only drawback is that the average usage of the STD buffer is below 150.000. Nothing to worry about, but keeping this value higher, helps in preventing underflows...

This last picture (http://img96.exs.cx/img96/911/Scenarist30.gif) has been produced using Scenarist 3.0 for re-authoring the video and audio assets. Other than being fully compliant, the usage of the STD buffer is very very good...

As I posted some days ago, I am observing that the Muxman authoring quality is very similar to the one of Scenarist. That's all. Hope my point of view (which is by sure at least independent) is giving some contribution to the topic.

Cheers,
SD