Scenarist Error: Number of frames in a VOBU is out of DVD spec. Please check MPEG ...

[stanjr]

I can't seem to get around this error during the build in Scenarist 3.0:

Error The number(20959.8) of frame in the last VOBU of a CELL is more than 35.96 (around 00:18:09:02).
Error dvd_mux : DoMux Multiplexing Error
Error Terminated Multiplexing (ScenAid30-VTS02_001_Track_t.vob).
Error Number of frames in a VOBU is out of DVD spec. Please check MPEG video file or move CELL boundary.
Error Multiplex is failed.
Error Multiplexing failed, Track "VTS02_001_Track"

Error MuxFromDB:MuxVTS failed
Error Multiplex failed
Error DVD Video files could not be created

I used DoItFast4U 1.4.7 for demux and ScenAid .27 for script writing and BatchCCEWS encoding.

Does anyone have any ideas how to get around this roadblock?

[Trahald]

wow..cant say ive seen that error before. one thing tho.. it does say move the cell boundary to fix it.. so check the scene for that track that lies here -> (around 00:18:09:02). and see if it falls too close the the one before it or after it (and possibly too close to the track end if its the last scene) and just adjust the scene so its not so close.

also make sure the track duration is where it should be (a frame or 2 off from the .avs file time duration)

[t610425]

Originally posted by stanjr
I can't seem to get around this error during the build in Scenarist 3.0:

Error The number(20959.8) of frame in the last VOBU of a CELL is more than 35.96 (around 00:18:09:02).
Error dvd_mux : DoMux Multiplexing Error
Error Terminated Multiplexing (ScenAid30-VTS02_001_Track_t.vob).
Error Number of frames in a VOBU is out of DVD spec. Please check MPEG video file or move CELL boundary.
Error Multiplex is failed.
Error Multiplexing failed, Track "VTS02_001_Track"

Error MuxFromDB:MuxVTS failed
Error Multiplex failed
Error DVD Video files could not be created

I used DoItFast4U 1.4.7 for demux and ScenAid .27 for script writing and BatchCCEWS encoding.

Does anyone have any ideas how to get around this roadblock?

@stanjr,

I once had this error and it turned out that somwhow cell boundaries were mixed up, ie say cell 24 was starting before cell 23.

So check cell boundaries near the offending time.

All the best