Authoring using DVDLab and Muxing in another program?

[some1else]

Is there a way to make an entire project in DVDLab pro and than muxing it in a nother program?

The reason I ask this is that I'm very satisfied with the options DVDLab pro gives u but I'm not satisfied with the dvd it creates!

Full of errors and the dvd won't play on all stand alone players!

Thanks in advanced

[Mr_Khyron]

No

[stickboy]

Mux with something else (e.g. muxman) and then add the VOB to DVDLab's assets afterward.

[Mr_Khyron]

I would not use Muxman yet...
I did a test with Muxman and DVDLab Pro using Philips DVD verifer software.

Muxman v0.8.
************************************************************
*
* ERROR SUMMARY :
*
* No Informations
* No Recommendation violations
* No Oddities
* No Warnings
* 7 Syntax errors
* 59072 Errors
* No System errors
*
************************************************************

DVDLab Pro v1.0 (041215)
************************************************************
*
* ERROR SUMMARY :
*
* No Informations
* No Recommendation violations
* No Oddities
* No Warnings
* 7 Syntax errors
* 1627 Errors
* No System errors
*
************************************************************

Not even Sonic Scenarist will give you a error free DVD.

[mpucoder]

The truth lies somewhere between Scenarist and Philips video verifier. After reading the above post I double checked Muxman. Yes, there are some "errors", and those that are true errors such as > 2048 time map entries and padding streams < 8 bytes will be fixed in the next release.

The others, though, are questionable. The greatest number of errors I got on my test were not from Muxman, but the encoder. Things like stated bitrate exceeding 9.8Mbps, GOP time code not consistent, etc. I will ignore those on further tests.
The next greatest number of errors were from SRI pointers. Scenarist and Muxman 0.8 use non-drop timecode when computing these pointers for NTSC, Philips expects drop timecode. I'll change Muxman (no big deal, it's a variable) for this, but now the pointers and the cell elapsed time will not agree.

But the last thing I will not change, as Philips is WRONG. It claims a VOBU with 14 coded pictures having 5 rff has a video presentation period of 0.533 seconds (16 frames). It does not, 14 + 2.5 = 16.5 (0.550 seconds). It then goes on to say "Number of pictures 32 shall be equal to number_of_displayed_field_gop 33 for video sequence (0) at byte 231558 bit 0;" Which contradicts what it just implied (that number_of_displayed_field_gop = 32).

[Sir Didymus]

Originally posted by mpucoder
The truth lies somewhere between Scenarist and Philips video verifier...

...But the last thing I will not change, as Philips is WRONG....

Agreed. Totally agreed: me too using the Philips Verifier... my feeling is that it is a great tool, BUT IT IS A TOOL, meaning that the presence of bugs in the software is of course possible.

My experience is that it's fundamental to understand and to evaluate the type of the different reported errors. There may be few serious reported errors (that totally prevent the title playback) and there may be a plenty of just formal and totally unrelevent reported errors (like the few ones still present in MuxMan 0.8, and reported by mpucoder)... In any case it is FUNDAMENTAL to double check, manually, or with other specific tools, that the reported errors are actually present, trying to understand if they represent serious troubles or just formal infringements...

On what I see (tested on some PAL movies and on an synthetic NTSC cell, built up in order to stress the vbv compliancy), the authoring quality of MuxMan 0.8 is very very high...

All the best,
SD

Edit:

Originally posted by Mr_Khyron
Not even Sonic Scenarist will give you a error free DVD.

Right!!!

And that's where I see the high potential of MuxMan... i.e. to see an authoring program to perform better than Scenarist [that seemed simply impossible to me just few weeks ago]...