Scenarist errors using ReAuthorist Scripts

[LakersFan]

Hi Gang,
Is just used the big 3 almost successfully for the first time! But as I was compiling in Scenarist, I got these errors...

Error The number(0.0) of frame in a VOBU is less than 11.99 (around 01:38:32:22).
Warning Exiting is canceled because "ExitVobuSizeError" is 0 in the file Scenarist.ini.
Error Can not read a GOP at 01:38:39:07 (try to read = 171860 B; read done = 42040 B).
Error Please check the video stream (E:\BRINGITON\VTS06\VTS__06_P01.P-TFF.16~9_1.MPV.M2V) or the .vif file or re-generate them.
Error dvd_mux : DoMux Multiplexing Error
Error Terminated Multiplexing (BRING_IT.scn-VTS_06_PGC_01_t.vob).
Error Can't read the input stream.
Error Multiplex is failed.
Info Multiplexing failed, Track<VTS_06_PGC_01>

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

Now, I did a forum search for these particular errors, and I came up with this thread (http://forum.doom9.org/showthread.php?s=&threadid=32287&highlight=EXITVOBUSIZEerror) that seems to think it has to do with a bunk version of scenchap. The thread said the problem was fixed in v1.27. I'm using v1.28...

Any ideas?
Maybe I'm heading down the wrong path for a fix?

Thanks in advance for the help.
-LakersFan

[ShaneZ]

Well, if you used RA to generate the scripts for you, you shouldn't have to worry about using scenchap to set your chapter points in scenarist. RA parses the IFO file and sets it from there.

You may want to try delelting the vif files and reimporting the script. Looks to me like your file may be damaged but I am no expert. :(

[D3s7]

everytime I've had that error it's due to a problem w/ the m2v file...

save yourself the headache (not time though) and delete the m2v/vaf/mvp files and re-encode

[LakersFan]

Thanks for the replys...
I'll reencode and see what happens...

[MedicineMan]

Exactly some problem here.

I'm following your advice and re-encoding. I'll post the results as soon as i can. Maybe you could post your results also.


Thank you.

[LakersFan]

Hi,
I deleted m2v/vaf/mvp files and re-encoded. Same error. :(

Will try a different movie...

-LF

[Zarduk]

Same problem as above also. I will take your advise. Delete the files and try re-encoding. I will post back my result when completed.

[Zarduk]

*Update*

Ok. Deleted everything and started over again, ripped and encoded again. Made scripts with RA, imported into Scenarist and same problem again when trying to compile project.

So I did it manually, dragging all assest into Scenarist, then exported to a .scp file. Added chapters with ScenChap. Did New from script in Scenarist, and compile project and it worked.

So somewhere in the script making for Scenarist in RA there must be a bug.

-Zarduk-

[LakersFan]

Not sure where the bug is at, but at first it didn't work with Bring It On. I tried a different movie (Ghostbusters) and it worked just fine...
Not sure if it's movie specific or not.

[MedicineMan]

Encoded 3 times. It worked perfectly the third time. I've used Doom9 guide. The only problem is that the size was 6Mb larger than the size of a DVDr. I'm now encoding the same movie for the fourth time.

[aquabubble]

I have seen this error before. It is to do with the encoded video not being as long in duration as ReAuthorist expected it to be. I get the video duration by parsing the AVS file through the Windows AVI API. In 99.9% of cases, the encoded video is the same length as the AVS reports itself to be, but in some rare cases the encoding process seems to "lose" some seconds from the video. Quite why this happens is beyond me, but it would cause problems with Scenarist since the ReAuthorist script is reporting a longer length for the video than what it should be. When Scenarist comes to mux the video, it then tries to read past the end of the video file, resulting in these errors.

To correct the problem you must manually import the problematic video into Scenarist and look at its "data end time". If you then perform a search and replace on the ReAuthorist.SCP file for the old data end time, replacing it with this new value. You also need to search and replace on the (old data end time + 1 frame) with (new data end time + 1 frame). Following this, a reimport should be successful UNLESS there is a scene marker past the end of this new video duration, in which case you will need to manually adjust its position in the track editor to just before the end.

HTH! :D

[int 21h]

Originally posted by aquabubble
...I have seen this error before. It is to do with the encoded video not being as long in duration as ReAuthorist expected it to be. I get the video duration by parsing the AVS file through the Windows AVI API. In 99.9% of cases, the encoded video is the same length as the AVS reports itself to be, but in some rare cases the encoding process seems to "lose" some seconds from the video. Quite why this happens is beyond me, but it would cause problems with Scenarist since the ReAuthorist script is reporting a longer length for the video than what it should be. When Scenarist comes to mux the video, it then tries to read past the end of the video file, resulting in these errors...

I believe this relates to the Mpeg2dec/DVD2AVI losing frames bug, that still has no fix.

http://forum.doom9.org/showthread.php?s=&threadid=44150

[aquabubble]

I don't think that's quite right, because the frame loss occurs in the parsing of the d2v. This is after that step, so there is something else influencing it...

[MedicineMan]

I've read this thread, because i'm one that has this problems. I've just finished the 4th encodingof the same movie. I did it the always the same way. It failed the 1st and the 2nd at exactly the same point (i don't have anymore the exact error message, but the error was the same as reported), and it didn't fail the 3rd and the 4th time (i encoded the 4th time because Reauthorist failed, by 6Mb, the size calculation). The only thing i did different was that i didn't touch the computer during the third and fourth encode. But i think that shouldn't be the problem (afterall, i'm running WinXP).

And, as i'm encoding the some movie, how can it happen? Sure the size reported by the API should be the some, or shouldn't it? Even if it is different than the real size, does the API always report the same size, or does it report different sizes in different runs?


Well, afterall, i managed to do the encode. So all is well. Tahnk you for your programs.



Sincerely


MM