View Full Version : Multiangle DVD compiling error in Scenarist
leeza
19th September 2004, 20:14
I'm using DoitFast4U, BatchCCEWS & ScenAid to backup a DVD but I get errors when compiling in Scenarist 2.7.
The DVD has 3 VTSes and 2 of them(VTS2, VTS3) are multiangle VTSes.
VTS1 has 32subs (but only 1 valid sub) and VTS2 has only 1 sub.
I demuxed VTS1 and 2 (not 3) using DoitFast4U with Vobsub PGC and Demux by VobID checked.
Next, I used Scenaid to re-encode and to create script for Scenarist.
I then imported the script into Scenarist and tried to complie but Scenarist gives errors below.
------------------------------------------------------------------
Info Multiplexing
Info Multiplexing VOB Main Stream
Error Subpicture[1] (1:VTS1_V1_00_419.sp) and (2:VTS1_V1_00_1.sp) offset are overlapped (00:00:00:27-00:00:01:22) and (00:00:00:27-00:00:01:22)
Error dvd_mux : Open Mux_list File Error
Error Terminated Multiplexing (Herlock.scn-VTS01_001_Track_t.vob).
Error Wrong mux_list. Mux_list format or stream ID may be wrong.
Error Multiplex is failed.
Info Multiplexing failed, Track<VTS01_001_Track>
Error MuxFromDB:MuxVTS failed
Error Multiplex failed
Error DVD files could not be created
------------------------------------------------------------------
(I think VTS1_V1_00_1.sp corresponds to the first bmp file in VTS_01_VSUB_P1A1-00-F folder and VTS1_V1_00_419.sp to that in VTS_01_VSUB_V001-00-F folder)
Since Scenarist gave errors regarding subs, I checked the subs folders.
The demuxed folder contains 2 subs for VTS1(VTS_01_VSUB_P1A1-00-F & VTS_01_VSUB_V001-00-F) and 3 subs (VTS_02_VSUB_P1A1-00-F, VTS_02_VSUB_V001-00-F & VTS_02_VSUB_V002-00-F) for VTS2.
I have checked these folders and found out that folders VTS_01_VSUB_P1A1-00-F & VTS_01_VSUB_V001-00-F contain exactly the same subs and
folders VTS_02_VSUB_P1A1-00-F, VTS_02_VSUB_V001-00-F & VTS_02_VSUB_V002-00-F contain exactly the same subs.
I tried deleting VTS_01_VSUB_V001-00-F for VTS1 and then re-create & import Scenarist script. VTS1 then complied fine but Scenarist gave out the same errors when compling VTS2.
I tried deleting two of three sub folders for VTS2 but Scenarist gave out same errors since Scenaid creates dummy subs.
Here are my questions.
(1) why do DoitFast4U create 2 and 3 subs for VTS1 and 2 that have only 1 sub?
(2) What do I do to get rid of the Scenarist errors?
jel
20th September 2004, 04:11
hi leeza and welcome to the forum!I demuxed VTS1 and 2 (not 3) using DoitFast4U with Vobsub PGC and Demux by VobID checked. ermmm ... where is the option to Vobsub by PGC?
anyway that seems to be the cause of the problem as you have two sets of subs for the same video stream.
so ...
i am assuming you demuxed VTS_01 by PGC, not Vob-ID?
if so, delete the 'VTS_01_VSUB_V001-00-F' subs folder (as this is related to vob-id demux, and
delete 'VTS_02_VSUB_P1A1-00-F' folder as this VTS has to be demuxed by Vob-ID because of the angles.
then re-run Scenaid (without re-encoding with BatchCCE) to generate your script and import into scenarist and hopefully those sub errors should disappear.
hth
j
leeza
20th September 2004, 08:45
Thanks for your reply jel. however, I still get the errors.
First, Vobsub PGC option is in DoItFast4U 1.4.0.
Second, since I did a VobID rip, VTS1 and 2 are VobID rips.
I tried deleting 'VTS_01_VSUB_P1A1-00-F' and 'VTS_02_VSUB_P1A1-00-F' because VTS1 & 2 are VobID rips.
I ran Scenaid again to create Scenarist script.
I then imported the script and compiled it, but I get the same error for VTS2 (not VTS1).
I think this error for VTS2 is because VTS_02_VSUB_V001-00-F & VTS_02_VSUB_V002-00-F folders are in VTS2 folder. I tried deleting one of these folders but Scenaid creates a dummy sub. Same problem still appears.
Anybody have solution to this problem?
jel
20th September 2004, 09:17
sorry leeza, it has been a loooong time since i used v1.4.0 (i re-installed just to check ;) )
i think your main problem comes from selecting vobsub pgc, as, from the DIF4U help file:
· Autodetect Subtitles/Closed Captioning will cause vobsub/CC to be checked automatically on all VTSes that contain subs/closed-captioning (very useful!) .SST creation uses a modified Subresync, created by Gabest. .SCC creation uses vobsub2scc v.2.2
which would negate the need to have both selected.
anyways, apart from deleting the sub folders you should also delete the .sub/.idx/.bov files that correspond to the pgc_demuxed subs as well (sorry forgot that part earlier).
eg
VTS_01_VSUB_P1A1.sub
VTS_01_VSUB_P1A1.idx
VTS_01_VSUB_P1A1.bov
VTS_01_VSUB_P1A1.bdx
delete these files as well and re-run scenaid
good luck
j
leeza
20th September 2004, 09:32
Thanks for your reply again.
I have not tried what you have suggested yet, but I came up with one more question while I was reading your reply.
VTS2 folder contains 1 pgc rip sub and 2 Vobid rip subs(VTS_02_VSUB_V001-00-F & VTS_02_VSUB_V002-00-F). Looks like VTS_02_VSUB_V001-00-F corresponds to VobID 1 sub and VTS_02_VSUB_V002-00-F to VobID 2 sub.
I already have tried deleting the pgc rip sub but still get the same errors. What should I do with 2 VobID subs?
P.S. I just tried your method but Scenaid still creates a dummy sub for VTS2 and Scenarist still gives errors.
D3s7
21st September 2004, 01:28
leeza : 2 questions
1) what version of ScenAid are you using? If not 1.0.0 pre7 then please download that and try
2) if you are using the latest, did you install the custom versions of vsrip,vsconv?
from there here's what you need to do:
1) delete VTS_*_VSUB_P* - the "P" at the end signifies PGC demux. what you want to keep should be VTS_*_VSUB_V*
Now, if you didn't demux all three VTS sets by vob replace the VTS_* with the VTS set in question only...
The key to solving your problem is in the error itself: Error Subpicture[1] (1:VTS1_V1_00_419.sp) and (2:VTS1_V1_00_1.sp) offset are overlapped (00:00:00:27-00:00:01:22) and (00:00:00:27-00:00:01:22)
so what you need to do is go to your VTS_01_VSUB_V001-00-F subdir and look for the .sst file. Open this
the interesting thing is that the 2 subs in question are 419 and 1 which is why I'm thinking you don't have the latest scenaid / vsrip/conv
anyway.. when you find that file, please post here the lines for sub # 1 and sub # 419
leeza
21st September 2004, 06:19
@D3s7
1) I'm using Scenaid 1.0.0 pre6. I'll try Scenaid 1.0.0 pre7.
2) although I'm using Scenaid 1.0.0 pre6, I installed the custom versions of vsrip,vsconv with Scenaid 1.0.0 pre6.
I agree with you that solving the problem is in the error itself.
Here's what tried.
I deleted VTS_01_VSUB_P* folder so that only VobID rip sub remains for VTS1.
I also deleted VTS_02_VSUB_P* folder so that only two VobID rip subs(for VobID 1 & 2) remains for VTS1.
I created script and compiled in Scenarist. The error occured during the creation of VTS1 in Scenarist disappeared.
However, the same error occured during the creation of VTS2 in Scenarist appeared. I think error for VTS2 appeared because the error for VTS1 was gone(Scenarist stopped when creating VTS1 and did not go into creating VTS2)
I checked VTS2 sub folders (VTS_02_VSUB_V001-00-F & VTS_02_VSUB_V002-00-F). Each folder contains 180 bmp files. In Scenarist, I checked the Subbmp assets and found out that 180 bmp files in VTS_02_VSUB_V001-00-F folders are numbered as 1-180th subs and 180 bmp files in VTS_02_VSUB_V00200-F folder as 181-360th subs.
I think the error occurs because bmp files in VTS_02_VSUB_V001-00-F & VTS_02_VSUB_V002-00-F are duplicates (I checked .sst files in those folders. thsy are same in its contents and time position).
I tried deleting VTS_02_VSUB_V002-00-F folder and create/import/compile script. Scenaid creates a dummy sub file(.jpg) and this files is numbered as 181st sub in Scenarist and has same time position as 1st sub. The same error occurs.
I think the solution to this problem is to delete this dummy asset in Scenarist or not to create a dummy sub when creating script with Scenaid if I can figure out how.
P.S. I tried deleting in the data folder in Scenarist but the same error occurs.
D3s7
21st September 2004, 14:41
No the error occurs becuase of what I told you.... the issue has nothing to do w/ the subs for another vobid except the one it's giving the error on.
the answer to your issue is to look IN the .sst file itself and find why it thinks 2 times are crossed.
However, before you investigate much farther I personally would re-rip this movie to a new directory, copy over your encoded assets to this new directory, make sure you are using pre7 and rescan
(just out of curiosity, why did you demux VTS 1 and 2 by vobid?)
leeza
21st September 2004, 15:29
I had to demux by VobID because VTS2 is a multiangle VTS.
VTS2 has 2 VobIDs. I think VTS_02_VSUB_V001-00-F folder contains sub for VobID1 and VTS_02_VSUB_V002-00-F sub for VobID 2.
I checked the folders & .sst files and VobID 1 & 2 has the same sub.
I don't know whether multiangle DVD contains different subs for each VobID.
I'm not really used to manual use of Scenarist.
When I imported the script and look at the the Data tab in Scenarist, it includes 360 bmp files.
When I look at the Track tab, it has only one sub.
I think .bmp files from 1-180 are link to sub1 in subtitle track and .bmp files from 181-360 are also link to sub1.
Since the two subs have the same time position and both are linked to sub1, Scenarist cannot compile.
1) Why does Scenaid create 2 identical subs from VTS2 when VTS2 contains only 1 sub?
2) How do you delete subs from tracks in Scenarist?
D3s7
21st September 2004, 16:25
If vobid 1/2 are the angle (1 being primary and 2 being non) then there should not be any imported subs for vobid2 unless ScenAid isn't seeing vobid2 as a seamless angle and/or no angle at all...
If it is creating it properly on the track as an angle, but importing the subs twice, then simply delete the sub dir for the "angle" and rerun.... that'll fix it for now...
If it's a non-seamless angle let me know as there may be some code that needs tweeking (I've only ran across 1 non-seamless angle movie so that part of the code may not be correct)
I'd take a look at the multi angle guide and see how to do this whole thing manually as well... having an understanding of how Scenarist works is the first key to fixing these kinds of issues
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.