scenarist subtitle import problem

[pausefisk]

I have used the old "big three" guide for some time now, and with 100% results every time. Suddenly i get this same problem on all movies when importing to scenarist, as follows:

Info -----------------------------------------
Info Start Importing
Info ------ Reading script ------
Info Importing MODIFIER VERSION
Info Importing Data
Info Importing VTS01\VTS__01_P01.16~9_1
Info Importing VTS01\VTS__01_P01-80-448K-[0MS]-CH6ENGLISH
Info Importing VTS01\VTS__01_P01-89-1536K-[0MS]-CH5ENGLISH
Info Importing def_subtitle_01
Info Importing def_subtitle_01st1
Info Importing VTS_01_VSUB_P1A1-00-Dansk_0001_v001_c001.bmp (0 2 718 569) (3163 3
Error Data file(T:\RIPFolder\VTS01\SUBS\VTS_01_VSUB_P1A1-00\VTS_01_VSUB_P1A1-00-Dansk_0001_v001_c001.bmp (0 2 718 569) (3163 3163)) does not exist in VTS_01_VSUB_P1A1-00-Dansk
Error Importing failed


------------

I installed GuardianKnot RIP pack for XVID recently, and i think that might cause the problem, but i dont have a clue where to look and what to fix.

some info from doitfast: CHECKING FOR INSTALLED APPS
DVD Decrypter = 3.5.4.0
Avisynth = 2.5.5.0
DoCCE4U = 1.0.1.5
BatchCCE = 0.9.1.5
ReAuthorist = 1.0.0.0

This (and all others movies i have done) is done using doitfast4u, reauthorist, docce4u, and scenarist 2.7.

The thing is, if i run it trough scenaid and create a new import file for scenarist, every thing works perfect, so how could reauthroist be the problem as i've used version 1.0 for ages? i could use scenaid, but i prefere reauthorist (when i remove from scenaid the dummy files get the same length as original.. how is that fixable?).

I am convinced that the GK rip-pack and some tools from there did this, so if anyone know what to look for, i would be thankfull for some good tips!

[D3s7]

Unfortunatly Reauthorist isn't really supported anymore and if it's not something quick I'm not sure we can really help....

Looking at your post though it appears that there is part of the bitmap path missing. can you check in the .scp that's generated and verify that the full path is listed...

Also, the dummy duration in Scenaid was changed a few builds back so that shouldn't be an issue anymore

[pausefisk]

Hi,

here is a cut from ReAuthorist.SCP file:

Place Holder=No
Comment=
Name=VTS_01_VSUB_P1A1-00-Dansk_0001_v001_c001.bmp (0 2 718 569) (3163 3
Resolution=PAL
Drop Type=Non-drop frame
Data Start Time=00:00:00;00
Data End Time=00:00:04;04
File=T:\RIPFolder\VTS01\SUBS\VTS_01_VSUB_P1A1-00\VTS_01_VSUB_P1A1-00-Dansk_0001_v001_c001.bmp (0 2 718 569) (3163 3163)
Width=720
Height=574
Is Encoded=No

etc etc..

i did check that the file and path on my HD is actually there. the .bmp file seems to be in order to. once again, i imported the doit4u output folder to scenaid and importing to sceanrist was 100% ok. strange thing!

i use scenaid 1.7.0.4 and the dummy-lengt doesnt seem to be "fixed" in my version, however this is easy to fix with pgcedit, not a big problem though. scenaid is working, and its a good tool! it's just that im soooo used to reauthorist, i want it to work! the bmp file is there, and its OK, the link in SCP file is valid.. so what the f*** is the problem :confused:

[D3s7]

yoru problem is the (0 2 718 569) (3163 3163) at the end of the filenames...

never saw that before

what version of vsrip/vsconv are you using??

[pausefisk]

hm, seems like i got vsrip.exe several places;

D:\Programfiler\DVDr\DoItFast4U\VSRip.exe 1.2.0.0
D:\Programfiler\DVDr\NuMenu4U\VSRip.exe 1.1.0.0
D:\Programfiler\DVDr\ScenAid\VSRip.exe 1.2.0.0
D:\Programfiler\GordianKnot\VSRip\VSRip.exe 1.0.0.6

D:\Programfiler\DVDr\DoItFast4U\VSConv.exe 1.2.5.0
D:\Programfiler\DVDr\NuMenu4U\VSConv.exe 1.1.0.0
D:\Programfiler\DVDr\ScenAid\VSConv.exe 1.2.5.0

VSConv.exe was not found in GordianKnot folder...

i think the 1.0.0.6 version in GK is the last one installed, even though i DID try to re-install DoItFast4u after this problem occured. Is there any way to check wich one of those files that is beeing used? or is doitfast using the exe file inside the DoItFast4U folder automaticly?

In case the 1.0.0.6 version is beeing used, that might be a reason to all problems. Howerver scenaid seems to be using the right one. would replacing the 1.0.0.6 version with the 1.2.0.0 mabye do the trick?

[pausefisk]

updated info:

i replaced VSRip.exe in the Doitfast4u folder with an older version i have on my other pc (wich is working 100% with reauthorist mode, same setup), version 1.0.0.4, and then it seems to be OK again!! however, this version doesnt seem to be working with scenaid.. when ripfolder is imported to scenaid, the subs doesnt show in the list. damn. would really be ok to have an version of VSRip that worked with both reauthroist and scenaid.

thanks D3s7 for helping me figure this out anyway!

[D3s7]

Scenaid requires the version that comes with Scenaid (which should also be compat with RA)

you can copy both vsrip and vsconv out of the scenaid folder into doitfast4u

[Orion|69]

I'm having the exact same problem although I started ripping on a complete new fresh install of all program's I used before.

DoItFast4U 1.4.0
ReAuthorist 1.0.0.0
DoCCE4U 1.0.1.5

and I installed Scenaid 1.7.0.0 ONLY to be able to use D3s7 modifications to Gabest's VSConv & VSRip, which -since I investigated subrippers in the early Muxman development- I know to be the superior subripper of em all.

Importing the reauthorist script in scenarist 2.7 gave me the exact same problems when it tried to import the substreams.

It's probably indeed the part at the end of the filename which throws scenarist off, so I'm gonna write a small tool which fixes that for the moment and updates the ReAuthorist.SCP so it can be imported correctly again in scenarist. (File=C:\WORKDiR_DVDR\VTS02\SUBS\VTS_02_VSUB_P1A1-00\VTS_02_VSUB_P1A1-00-English_0001_v001_c001.bmp (0 2 718 452) (1756 1756))

I might look into switching to ScenAid nonetheless tho, coz now that i used it for the first time it kinda looks sweet :)
On the other hand I don't understand why the newer versions of the subripper aren't backwards compatible anymore.

All in all its easy fixable but kinda a drag if u have to change the way you do stuff all of a sudden :)

[D3s7]

In the past this has been a result of another app (not DIF4u and not Scenaid) installing a third version of vsconv/vsrip that adds additional info to the sst and filename.

The problem with that is Scenarist can't parse those names and complains.

You can copy the vsrip.exe and vsconv out of the Scenaid Install dir into the doitfast4u install directory and re-rip (if you've already encoded, just rename your existing dir and then after re-encoding, copy back your encoded assets to the new rip)

[D3s7]

Another option would be to use a rename utliity to rename those bmp's killing the () and spaces to _'s.

if you do that you'll have to fix the .sst's or the RA generated .SCP as well

I will be upping the version number of VSRIP and VSCONV with the next release and add the ability to check for the proper version. DIF4u will check version # as well and let you know on startup that an older version then the recommended one was found

[Orion|69]

it's easy to solve by just deleting the last part in the script reauthorist makes or just by fixing the .sst reauthorist uses to make the script.. the .bmp's themselves are named correctly so just by editting the .sst and removing the values in the .sst after the filenames before u press author in reauthorist, everything goes like it should be (if yar too late u can also edit the .scp but thats ofcoz a bigger file and a bit more work - but not something thats not doable either).

so everything is fine since i made myself a little tool to just parse the .sst without the values behind the .bmp filename :)

so its not a biggie at all.. just something that wasnt expected but there's a solution for everything ofcourse :D

[influenza]

You could attach your little tool for other users with the same problem ;)

[D3s7]

More importantly to me is where this version of vsrip/conv is coming from and why it's overwriting the version in the DIF directory.....

[Orion|69]

You probably dont wanna hear this... but It's scenaid 1.7.0 which dumps the those vsrip & vsconv in the dif4u dir. Maybe that works for the non-public newer versions of DIF4U.. but it doesnt in combination with 1.4 and reauthorist 1.0.

Well.. doesnt isnt true.. like i said.. its easy to fix the problem. I'll rewrite my small tool to fix stuff like this in the reauthorist.scp and make it work for more substreams and more pgc's than i have at the moment ;) I didnt make it flexible yet. By next week I should attach it here coz I prolly wont have time to really test before the weekend. :)

[D3s7]

actually, no you are wrong

if you compare the version of vsrip / vsconv in the scenaid install dir to the problem ones in the dif dir you'll find they are different

the scenaid version does not add the info to the .sst which is causing the problem.

[Orion|69]

Hehehe. I wonder why you don't believe me, but I guess you are bugged alot by people from a lesser background in PC related issues, and therefor assume I prolly am of the same caliber... Well.. since i really mean well.. here's the proof :)

C:\-= ENCODiNG =-\DoItFast4U\VSConv.exe = 156 kB (159.744 bytes)
version 1.2.5.0
VobSub subtitle format converter - D3s7 custom build (based off 1.0.0.6)

C:\-= ENCODiNG =-\ScenAid\VSConv.exe = 156 kB (159.744 bytes)
version 1.2.5.0
VobSub subtitle format converter - D3s7 custom build (based off 1.0.0.6)

C:\-= ENCODiNG =-\DoItFast4U\VSRip.exe = 209 kB (214.528 bytes)
version 1.2.0.0
VobSub Subtitle Ripper Wizard - Custom build by D3s7 (based off 1.0.0.6)

C:\-= ENCODiNG =-\ScenAid\VSRip.exe = 209 kB (214.528 bytes)
version 1.2.0.0
VobSub Subtitle Ripper Wizard - Custom build by D3s7 (based off 1.0.0.6)

Both the VSRip.exe and the VSConv.exe are from your ScenAid 1.7.0.0

I'll also include two screenshots (dutch windows xp pro but u'll get the message) where i show u that these are in fact the only two copies of each tool on my hdd.

Another screenshot is the .sst file opened in Ultraedit where u can see that it actually writes the display area and twice the duration of the sub BEHIND the filename, which it clearly shouldn't do and I have the feeling that there are maybe some debug lines in your code left which werent commented out yet. Has to be something like that.

Last screenshot is a view of the actual dir where the .bmp's are stored so you can see that everything in there is ok besides the extra values in the .sst file behind the filenames of the bmp's.

Again.. this is not meant as an attack or something. I only want to help you resolve the bug. Hell.. post the sourcecode and i'll even find out what goes wrong for you :)

[D3s7]

the only problem with your logic is there has been 3 people who have had this issue and over 6000 downloads of scenaid 1.7

1 of the persons who had the issue fixed it by coping the files from the sceanid dir into the doitfast4u dir and re-ripping

Not to mention I myself have had to install/reinstall and this problem does not exist

the SST files i generate are 100% compliant w/ scenarist

so, perhaps dif isn't using those files or RA is modifing the .sst's

whatever the case, it's not my version of vsconv that's causing the issue

Not that I don't believe you persay but if that was it, believe me I"d have heard about this LOOOONG before now

[Orion|69]

I investigated this issue some more and while - as you state and I have no reason to doubt this whatsoever - it works for 99.99% of all people, VSConv.exe doesnt give me the .sst I expect it to do. All the .bmp's are fine.. just in the .sst it's again like :


SP_NUMBER START END FILE_NAME
Color (4 4 4 3)
Contrast (15 15 0 15)
0001 00:00:03:01 00:00:07:02 VTS_01_VSUB_P1A1-00-English_0001_v001_c001.bmp (0 2 718 475) (3637 3637)
0002 00:00:07:05 00:00:09:03 VTS_01_VSUB_P1A1-00-English_0002_v001_c001.bmp (0 2 718 475) (1918 1918)
0003 00:00:09:05 00:00:13:13 VTS_01_VSUB_P1A1-00-English_0003_v001_c001.bmp (0 2 718 475) (3926 3926)
0004 00:00:13:15 00:00:15:28 VTS_01_VSUB_P1A1-00-English_0004_v001_c001.bmp (0 2 718 475) (2237 2237)

and so on


For this test I just used the 2 utils to rip a substream myself from a vobset and converted it (the way it always worked for me when I did it manually) with the commandline :


vsconv.exe -f "scenarist" -i "VTS_01_0.idx" -o "C:\1\VTS_01_VSUB_P1A1-00-English.sst" -id 0


I have *NO* idea why in my case it doesnt work the way I expect it to work. Maybe coz my XP pro (SP2) is Dutch? This clearly leaves me with more questions as it delivers answers.

I already unpx'ed the exe and will dive into disassembling it to see if I can find anything at all what might explain this weird behaviour.. why the output in my case is so special and stuff.. I really don't know yet.

Furthermore.. by innounp'ing the scenaid 1.0 final inno-setup exe I extracted the older version of VSConv.exe (1.2.1.0).

I did the same thing as mentioned before to convert it to .sst and .bmp's


vsconv_oldversion.exe -f "scenarist" -i "VTS_01_0.idx" -o "C:\2\VTS_01_VSUB_P1A1-00-English.sst" -id 0


and the output was how it used to be on this machine :


SP_NUMBER START END FILE_NAME
Color (4 4 4 3)
Contrast (15 15 0 15)
0001 00:00:03:01 00:00:07:02 VTS_01_VSUB_P1A1-00-English_0001_v001_c001.bmp
0002 00:00:07:05 00:00:09:03 VTS_01_VSUB_P1A1-00-English_0002_v001_c001.bmp
0003 00:00:09:05 00:00:13:13 VTS_01_VSUB_P1A1-00-English_0003_v001_c001.bmp
0004 00:00:13:15 00:00:15:28 VTS_01_VSUB_P1A1-00-English_0004_v001_c001.bmp

and so on


So *WITHOUT* the extra displayarea- and timestamp fields. The only difference I could see at a glimpse is the difference in the SPU color rules (PA,E1,E2,BG) between the old version (... ===) and the new version (... = = =) (which is ofcourse the correct way of using it and was pointed out to me by MPUCoder a damn long time ago =] ).
However since scenarist doesn't really care about that (as far as I know), would it be wise to use the older version as long as I don't know what causes the problem on my machine? I searched for information on your changes to your VSConv/VSRip-mods but couldn't really find any information in your revision history beyond the 1.0 final.

As conclusion : I really appreciate and thank you for your input, and altho it might seem that I'm nagging a bit (:P), in a twisted way I'm trying to help others out too which might encounter this problem in the future (let's hope they don't).

Your mods are still the greatest out there for ripping and conversion and that's no sucking up.. that's a fact. :)

PS. Don't take offense in anything I typed. I tried to be as clear as possible, but since English is not my native language some sentences could perhaps be frowned upon. If that's the case : well.. now you know why :))

[Devit]

Same problem here doesn't happen with Scenaid 1.0 version but does with Scenaid 1.7.0.0. As for 6000 ppl downloading Scenaid, that doesn't mean that 6000 people copied the vsrip/vsconv from 1.7.0.0 over the versions included with 1.0. The installer for Scenaid 1.7.0.0 doesn't ask about installing newer versions of vsconv/vsrip unlike the Scenaid 1.0 one.

[D3s7]

This is a dead point and the fact that people keep bringing it up quite frankly annoys me..

To date, I have had 4 people say there is an issue. I have over 30 VIP members who use the app all the time. I use the app every time and as you mentioned over 6000 others who have downloaded the application - 3824 who have downloaded latest 1.7 alpha.

No the installer doesn't ask, it just does it. That is because it needs those files. If you wish to use an older version, please do so but do not complain when Scenaid stops working

If you are having a problem and you believe that it's caused by the version installed by ScenAid, then I'm sorry... however, I have verified that the file on it's own does not do this and must be something else involved with your specific setup.

Bottom line, this problem only occurs with RA. RA is no longer supported by the developers of the Big3. If you continue to use it, do so at your own risk. We acknowledged that some people may have this issue which is why we stickied orion's utility.

This thread is closed. Any other new threads regarding this issue will be closed. Please use the search function at the top of every page and look for a solution to a problem before posting in a thread 4 months old