UPDATE!!!! Re: VOBU length & number of sectors disagree

Hey Guys, a client of ours just submitted DDP from DVDSP for replication. Upon running Eclipse Image copy I got the "VOBU length" error. This occurred on both the DDP on DVD-R and DDP submitted via FTP. I inquired with Eclipse (again) about this error and this is what was said straight from Eclipse support.

"The “VOBU length & number of sectors disagree” error that we have seen has mostly been from DVD Studio Pro. The only true way to fix this is per your recommendation. The image needs to be resubmitted back to authoring. "Hopefully" the second time it is output you will not have this issue, but the best thing would be for the authoring company to check with their software vendor for a fix to this problem.

Here is a some information on this problem.

Each Video Object Unit (Vobu) on a DVD is made up of packets of information (actual playback data) which starts with a Navigational Pack (NAV) and ends with the occurrence of the next Navigational pack. Within each Nav pack is a field called the DSI information (VOBU_EA .) This DSI information includes the total number of sectors that make up this Vobu. Eclipse goes one step further by actually counting the Actual number of information packs (sectors) between each of the navigational packs and comparing this to the DSI number.
If the DSI and Actual numbers do not match then either there are missing sectors in the VOBU or the VOBU_EA number is incorrect. If there are missing sectors in the VOBU, that could cause playability issues, even if the players do not access the VOBU_EA.

If you look at your warning of this type. "Vobu length and Number of Sectors Disagree" DSI: 135 <> Actual 47.

This means that the player is expecting to read 135 sectors before the occurrence of the next Navigational pack. When Eclipse counts the sectors we are reading an actual value of 47 sectors before the next navigational pack.
As you can see a playback system would have problems with this if it expects more data and the data actually gets truncated. For this potential playability issue we list this as an error.

I don't believe having more Actual sectors than the DSI specifies will have an effect on playback, but it is still a specification violation."


So this tells me exactly what I have been telling all of you. It is not a media issue it is an authoring issue. I hope this helps Alan so you dont have to send every different type of media at your replicator to get your job to pass.

-Luke