mux failure in scenarist

[hms]

consistent mux failure in scenarist:
video file encoded multipass vbr in cce -
video file accepted in scenario editor without error message -
layout editor starts and then fails before 1% complete -
Error message: "ReadFile at sector 3e6e failed"
(sector # different with different encoded video files)
video file plays perfectly in MPEG player -
video file will mux in IfoEdit -

same problem with a different computer-
same problem using different cce version-
same problem using different DVD2AVI version-
same problem using different frameserver version-

problem only occurs with multipass vbr cce encoded video file:
otherwise scenarist works perfectly

[Malow]

try to rewrite the file using restream....

in some files, i have problem importing in scenarist ( 2 minutes to import until 99% after this, take 20 minutes to 100%)

restream may fix a problem with your file...

Malow

[hms]

restream does not solve the problem, even using different settings

[Arky]

Have you made sure to set the timecode correctly when encoding in CCE? I don't use Scenarist, but I am speculating that Scenarist may be looking to the wrong portion of your CCE-encoded video stream, because CCE may have written it with a START timecode of 1:00:00. Not saying it's the actual answer - Just something worth checking!


Arky ;o)

[hms]

In cce I changed the time code to 00:00:00 and scenarist imports the same setting: start is also 00:00:00 -
But this is something I am going to look into a little more:
I am going to re-encode using cce default time code.

Also: The same movie, same computer, same frameserver, same settings but encoded with TMPGnc is accepted and muxed perfectly in same scenarist.

[hms]

problem solved:
bit rate viewer indicated a spot near the beginning on the video file as 0 bit/sec -
scenarist fails at that spot -
that spot was between the logo and the movie -
resolution:
either stream process vob files so as to remove logo or set cce minimum bitrate other than 0 bit/sec

[Arky]

Glad you got it sorted. Thanks for posting the solution for others.

Happy Authoring!! :D


Arky ;o)

[hms]

I have not been able to reproduce the above posted "solution" consistently.
Now I have to admit that my testing was flawed and I am red-faced:
The real problem turned out to be inherent in Scenarist NT itself:
Scenarist NT does not seem to be able to process video files larger than 4GB.
In testing the files at first set at 2000 min happen to result in less than 4GB.
I simply jumped to the wrong conclusion.
Scenarist NT does not seem to be a full fledged NTFS program.

[oddyseus]

I suppose that u will keep the red face :) This is not your problem.
Scenarist is fully capable of handling larger than 4gb video files. I am using it all the time with these kind of files and never had any problems that relate to the file size.

Your problem lies elsewere. If u have changed the file in any way after importing it try to delete the vif file and regenerate it.

[hms]

Oddyseus
I guess I am not as skilled in navigating the Aegean Sea as you are:
I tried what you said several times already and now I cannot think of anything else.
2 different computers, same movie, etc:
7 video files greater than 4GB - none muxed successfully in Scenarist NT.
7 video files less than 4GB - all successfully muxed in Scenarist NT.
You must have a newer version of Scenarist:
As soon as I see daylight and the monsters are no longer there I will go and buy and upgrade.