Log in

View Full Version : "ExitVobuSizeError" scenarist error


DaRtHmAuL
8th February 2004, 17:15
Hi guys,
i got some prob with my new backup project Hoodlum.
After reencoding it with The Big 3 (DIF4U 1.4.0, RA 1.0.0 and DoCCE4U 1.0.1.5) i got an output error in Scenarist 2.7.
Here is the log :

Info Preparing to multiplex track VTS_01_PGC_02
Info Creating Multiplexer info
Info Multiplexing
Info Multiplexing VOB Main Stream
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;05).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;05).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;05).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;05).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;05).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;05).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;05).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;05).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;05).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;05).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;05).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error Can not read a GOP at 00:00:07;05 (try to read = 175060 B; read done = 41596 B).
Error Please check the video stream (K:\HOODLUM\VTS01\VTS__01_P02.16~9_1.MPV) or the .vif file or re-generate them.
Error dvd_mux : DoMux Multiplexing Error
Error Terminated Multiplexing (hoodlum.scn-VTS_01_PGC_02_t.vob).
Error Can't read the input stream.
Error Multiplex is failed.
Info Multiplexing failed, Track<VTS_01_PGC_02>

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

Here are time values i use to edit the *.SCP file
Size predicted in RA = 00:00:08;09
Data End Time (in *.SCP file (Item=Video)) = 00:00:08;08
Data End Time (in *.SCP file (Item=Main Video Play)) = 00:00:08;09
Scenarist time (imported from *.SCP file) = Same as in the *SCP file
Scenarist time (manually *.M2V imported) = 00:00:08;11

So, i tried to change the 00:00:08;08 by 00:00:08;11 and the 00:00:08;09 by 00:00:08;12 as Aquabubble explained it.
I got the same error.
What's wrong ?

thks for help
cya

EonBlue
8th February 2004, 19:40
I had a project where I kept getting the VOBuSizeError even after changing my scp file...so what I did was use SceneAid to create the script and everything went fine.

DaRtHmAuL
8th February 2004, 20:10
Thks for the tips EonBlue.
I'll try this method and let you know if it works.
hope it will coz i never use this soft.
cya

DaRtHmAuL
8th February 2004, 20:39
It doesn't seems to work
SceneAid import the demuxed DIF4U dir correctly but when i press the Generate Script button it results with an error : "Path not found".

Severity: Error
Number: 76
Description: Path not found

Nice Text:
Help Text:
User Name: C-3PO\DaRtHmAuL
Computer: C-3PO
EXE Name: sceneaid
EXE Path: C:\Tools\Video\SceneAid RC2 0.9.0.3
EXE Version: Version 0.9.3
Help File:
Help Context: 1000076

Call Stack (lowest level first)

C-3PO::Script_Generate::GenerateScript (line 1790)

I'm not lucky with this project.
Any clue ?
thks
cya

EonBlue
8th February 2004, 20:55
When SceneAid works, it works extremely well...but as it's still an RC, it's kinda buggy. Anyway I usually get errors with SceneAid whenever I strip substreams. To get around this, I had to create 'dummy' folders w/ the dummy subs for the stripped substreams...and I had to name them according to the DIF4U naming scheme. (I also had to delete the dummy subs that RA created) It sounds like a lot of work but it's not really that bad.

There might be an easier way to get around this problem, but I'm not smart enough to figure it out. Maybe one of the mods could provide some more insight.

DaRtHmAuL
8th February 2004, 22:00
I'm testing
A New Hope... maybe
if not working, i'll try to redo my project *.SCP without reencoding the PGC2.
thks for all
cya

DaRtHmAuL
9th February 2004, 11:25
Hi,
i got a new error.
I've change the time values again cause scenarist told me the pgc has a different end time compare to the original M2V.

Info Preparing to multiplex track "VTS_01_PGC_02".
Info Creating Multiplexer info for VOB "K:\HOODLUM\mux_data\\hoodlum-VTS_01_PGC_02_t.vob".
Info Multiplexing VOB "K:\HOODLUM\mux_data\\hoodlum-VTS_01_PGC_02_t.vob".
Info Multiplexing VOB Main Stream
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;03).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;03).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;03).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;03).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;03).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;03).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;03).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;03).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;03).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;03).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error The number(0.0) of frame in a VOBU is less than 10.00 (around 00:00:07;03).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error Video or Audio Buffer underflow: (Dts: 33054, SCR 33133)
Error dvd_mux : DoMux Multiplexing Error
Error Terminated Multiplexing (hoodlum-VTS_01_PGC_02_t.vob).
Error Total bitrate is too HIGH. Please reduce the stream bitrate or the number of stream.
Error Multiplex is failed.
Error Multiplexing failed, Track "VTS_01_PGC_02"

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

I dont know what i have to do.
Should i go to a one click solution then ?
thks for help
cya

influenza
9th February 2004, 16:04
The error you have has to do with the layout of the original pgc. i bet it has one or probably 2 very short vobid(s) on the end of the pgc (15 frames or so).

Sceneaid solves this differently then RA and should not give a problem.

If this doesn't work you have to either manually author this title or try to add a short clip (like 15 frames, demux it from the original to get it) to the RA created script and see if that compiles.

OvERaCiD23
9th February 2004, 16:56
The last time I received this error was due to overlapping chapters in Scenarist. In '8 Mile', it made a chapter that showed to be 1 frame long, which didn't exist in the original IFO. I deleted this from the timeline in Scenarist, and the project turned out perfectly. So I wouldn't necessarily say it's just a short VOBID, but ReAuthorist seems to have passed a small bit of false information in the Scenarist script.

DaRtHmAuL
10th February 2004, 01:47
Well,
I've regenerated the script from RA with dummy PGC02 and it works.
This PGC was Warning screen, that's why it was too short.
Finally, i got it.
thks for all your help guys
bye

jel
10th February 2004, 06:51
i have also noticed this error when a vts contains a vobid of only 10 frames. RA misinterprets this and imports as only 1 frame.
all suggestions made in the above posts are valid, although you could always delete all instances of this vobid (in scenario editor, track editor, and data editor) and re-import the original video (would be non-cce in this case) and recreate a new track etc from this.

btw, i recently re-installed windows on my home pc and it changed all the drive letters. so because i was lazy i didnt change them to what i had originally set. now when i went into an existing scenarist file and tried to compile the layout, it threw out all these "ExitVobuSizeError" messages. this occured even if i generated a new script with RA, re-imported, etc. i remember from somewhere that Eyes`Only stated that the file path names are hard encoded to the files. this was confirmed when i later changed the drive letters to what they originally were and all projects compiled without a hitch.
so, whats the moral of this ramble?
dont move your files between disks or risk the wrath of the "ExitVobuSizeError"!

DaRtHmAuL
10th February 2004, 15:31
Ok jel
thks for the advice but on this project, no files were moved.
I try to avoid this but have done on one project and it results with multiple errors (RA & Scn).
cya