Problem with Final Destination 3

[Angelus]

Hi everyone, I've been trying to successfully backup this movie for a couple weeks now but I haven't gotten anywhere. There are 3 different "main movies" within VTS 1, as there are different endings which can be selected for the main movie. On top of this, there are also several angles associated with the main movie. I've successfully ripped the movie in DIF4U by vobid (because of multiple main movies and the angles) and have successfully encoded all the files, but my problem comes when I am importing into Scenarist; it imports for quite some time and then crashes.

I have a feeling that it is the angles that are messing up the import, or it could be the fact that there are 50 seperate parts of the main movie VTS which has to be imported. Anyone have any ideas I could try to see if I can get this movie to work? I don't really care if I have the angles in the final movie, as I would probably never use them anyway.

[influenza]

well this sounds like a challenge :). I have done movies with both (non) seamless angles and a lot of vobids (well over 90 iirc). Importing wasn't much of a problem.

If you do not care too much about the angles you could try to remove those first and see if this makes life any easier. You could also manullay import te assets to see if one of them gives a problem And after this has been done succesfully and scenarist has created the info file stry to import the script again.

Could you also post the relevant parts of the ifo? I'm curious about the structure.

[Angelus]

I couldn't paste the entire IFO summary here, so I've attached it in a text file (I think this is what you were asking for).

[influenza]

Although the structure is quite complex it should be doable in scenarist (well not true ilvu ofcourse;)). So what we should find out is, if it's a script related error or an error with one of your assets. Did you try to import all the assets manually?

[Angelus]

Interesting and I should have realized this before...there are several assets that weren't encoded and when I tried importing them, I get the "bitrate should not exceed... error" Looking at the assets, it is the scenes that have buttons where you can select their destiny (change movie storyline one way or another). I'll try to re-encode these assets manually and see if that lets me import the script finally. Thanks!

Edit: nevermind, it seems these short menus were encoded as .mpv files, and those open up into scenarist fine too. I'll have to see if there are any other problematic files. When I open up Scenaid and scan the VTS 1 folder, it gives me this error:

abnormal cell found (10frames long 12 min - pcg1 Cell21) Dummy will be used in layout

there are about 6 of these in the Scenaid log, could this be a problem for the import?

[influenza]

That could be the problem if the dummy files are not good, can you import those manually?

[Angelus]

I think that this is where ScenAid put the dummies (this is from the .SCP file):


Item=Encoded Still
{
Place Holder=No
Name=dummy_VTS01_P1_C21
Resolution=NTSC
Drop Type=Non-drop Frame
Data Start Time=00:00:00:00
Data End Time=00:00:09:29
File=D:\DVD Backup Programs\ScenAid\dummy_NTSC_169.M2V
Width=720
Height=480
Is Encoded=Yes
Encode Type=MPEG 2
Size=720 x 480
Aspect Ratio=16 : 9
Picture Structure=Frame Structure
GOP Size=15 frames
GOP Structure=N/A
Bit rate=9800000
Average Bitrate=6000000
Minimum Bitrate=4000000
}

so it looks as though it just used the ScenAid dummy files that come with the program, and I can import the dummies manually no problems.

[influenza]

too bad it's a title with angles and stuff, because otherwise we could have tried muxman instead.

I don't know how experienced you're with scenarist, but if I were you I would just manually create the scenario. Will take some time though with this much vobids.....

Maybe d3s7 can hve a look at your script as well

[Angelus]

a little update:

I re-processed the main movie VTS using less of the subs selected in DIF4U. There's 3 EN (W) subs available, and 3 EN (L) sub streams available. I only did the first W and L streams to cut down on the sub folder size. Anyways, to see if it was the subs that were causing a problem, I disabled the importing of the subs in Scenarist. So I tried importing again with the new script and it crashed again, but I was able to see where it crashed when importing. It was during the "Restoring Link" in Title 4 portion of the script. So maybe the scripting in this section is wrong and causing Scenarist to crash?

[Zeul]

Which suggests that a link is trying to be made to a non-existant asset. Even if the asset imprted as a placeholder the link would be made.

Post up the scp file for us guys to have a look at. Zip it up first though!

[Angelus]

Here's the script file:

[Trahald]

scenarist 2.6/2.7 has a hard time with scripts with non-seamless angles. 3.0 does better with fin_dest 3. or at least does better importing the script. it kept crashing on some of the bov sections during compile so i gave up. (scenarist is such a pita!) most compiles go fine with muxman (i havent loaded scenarist in ages) but need to wait for angle/ilvu support.