PDA

View Full Version : Hellboy R1 Information/Bug Report


trigger638
7th September 2004, 13:07
Warning: This is going to be a very long post. It is not intended as a guide, but rather a detailed list of problems assosiated with an attempt to backup this title using the currently available big 3 tool set.

First, I used a DoItFast4U 1.4.7, BatchCCEWS 0.9.1.5, Scenaid v1.0pre7, Scenarist v3.0.

The first problem that I encountered was due to a bug in scenarist 3 that causes highlights to be shifted when forced subs are used in the first sub track. I fixed this by removing the forced subs from the first track main .sst files. I then copied and pasted the sub info into a new .sst that just contained the non-highlighted forced subs. This way I could process everything and just add the problem subs in later. Of course this would not be necessary with scenarist 2.7 or 2.6.

When I first imported the script that Scenaid created I got a few no valid sub errors. After reviewing the track it was obvious where the problems were and I just fixed the time stamp/durations up to match the scene breaks. I won't go into any detail about the chopped sub strangeness I saw, that is detailed in the Scenaid 1.0 prerelease thread.

So I have my import and it is clean from errors. I imported one of the original .sst files that contained the forced BoV material to check it against what Scenaid had imported. What I saw was a lot of missing subs within the BoV scenes. Well at this point I back reved Scenaid to pre6 and tried again. Pre6 imported all the subs. Again a few no valid sub errors that needed to be cleaned up. When I attemped to compile the track I got a HLI buffer error that stated that there were highlights that were too close togather. Well based on where the failure occured I was not buying that because there were highlights within one frame of eachother before it gave the error. After checking things out I realized what was happening. HLI buffer error is misleading, its not how close they are togather, its how long they are. If a sub that has a highlight is too short, thats when you get HLI errors. What I know for sure is that 19 frames is too short and 1 second is long enough. So after I deleted all the short dummy subs my track started looking very similar to what the pre7 import looked like. Well back to pre7 we go.

So I started fresh and imported the pre7 script again. Cleaned up the errors yada yada. I started taking a real close look at the BoV information in the Scenario Editor and noticed that some of the menu buttons had no commands. In fact the ones that did have commands were assigned to the wrong button. Also here is where I noticed that there was only one menu button for each BoV cell. This is bad because remember there are multiple highlights in some of the BoV cells. Well I looked at the import script and saw that the buttons were created on the track correctly, but only one menu button was assigned to each cell regaurdless of how many were created on the track.

So I manually edited the import script and added entries for the additional menu buttons. Here is a snippet of what Scenaid did:

Item=Menu
Name=VTS8_Title1_PGC1_PG2_C2_m
Is Visible=Yes
Left Point=1560
Top Point=480
Linked Highlight=
Command List=List

Item=Command
Name=VTS8_Title1_PGC1_PG2_C2_m1
Is Visible=Yes
Left Point=0
Top Point=0
Command=Nop
To Action=

Item=Command
Name=VTS8_Title1_PGC1_PG2_C2_m2
Is Visible=Yes
Left Point=0
Top Point=0
Command=Nop
To Action=

Item=Command
Name=VTS8_Title1_PGC1_PG2_C2_m3
Is Visible=Yes
Left Point=0
Top Point=0
Command={ Mov GPRM14, 32775 ; LinkTailPGC, button=0 }
To Action=

:

Two things to note with the above, notice that there is actually a button command for button 3. The command is correct, but it should be assigned to button 2. Also worth noting, the other highlights that should have the command in button 3, had no commands at all. The above snippit was linked to cell 5 which contained 3 subs with 3 seperate highlights. Below is what it looked like after I edited it:

Item=Menu
Name=VTS8_Title1_PGC1_PG2_C2a
Is Visible=Yes
Left Point=1560
Top Point=480
Linked Highlight=
Command List=List

Item=Command
Name=VTS8_Title1_PGC1_PG2_C2a1
Is Visible=Yes
Left Point=0
Top Point=0
Command=Nop
To Action=

Item=Command
Name=VTS8_Title1_PGC1_PG2_C2a2
Is Visible=Yes
Left Point=0
Top Point=0
Command={ Mov GPRM14, 32775 ; LinkTailPGC, button=0 }
To Action=

Item=Command
Name=VTS8_Title1_PGC1_PG2_C2a3
Is Visible=Yes
Left Point=0
Top Point=0
Command=Nop
To Action=


Item=Menu
Name=VTS8_Title1_PGC1_PG2_C2b
Is Visible=Yes
Left Point=1560
Top Point=480
Linked Highlight=
Command List=List

Item=Command
Name=VTS8_Title1_PGC1_PG2_C2b1
Is Visible=Yes
Left Point=0
Top Point=0
Command=Nop
To Action=

Item=Command
Name=VTS8_Title1_PGC1_PG2_C2b2
Is Visible=Yes
Left Point=0
Top Point=0
Command={ Mov GPRM14, 32775 ; LinkTailPGC, button=0 }
To Action=

Item=Command
Name=VTS8_Title1_PGC1_PG2_C2b3
Is Visible=Yes
Left Point=0
Top Point=0
Command=Nop
To Action=


Item=Menu
Name=VTS8_Title1_PGC1_PG2_C2c
Is Visible=Yes
Left Point=1560
Top Point=480
Linked Highlight=
Command List=List

Item=Command
Name=VTS8_Title1_PGC1_PG2_C2c1
Is Visible=Yes
Left Point=0
Top Point=0
Command=Nop
To Action=

Item=Command
Name=VTS8_Title1_PGC1_PG2_C2c2
Is Visible=Yes
Left Point=0
Top Point=0
Command={ Mov GPRM14, 32775 ; LinkTailPGC, button=0 }
To Action=

Item=Command
Name=VTS8_Title1_PGC1_PG2_C2c3
Is Visible=Yes
Left Point=0
Top Point=0
Command=Nop
To Action=

:

Notice the addition of 2 new menu items and the command has been moved to button 2.

After this edit was done I imported again and fixed up the syncing. The BoV's played flawlessly on my software player, so I tested the rest of the disk. This title has a storyboard sub track that just puts up little storyboard pictures in the lower right corner. When playing this back my entire screen would turn dark grey when a sub would show. I checked the original to make sure this was not the intent and it wasn't. Scenaid had imported the background for these subs at 100%. Now I am quite sure the originals were 100% as well, but the sub size was limited just to the picture area. When the subs were imported into my project they were full screen so 100% background was blanking out the screen. I fixed this by changing the stream color so the background was 0%, did not look exactly like the original, but close enough.

This fixed I imported my forced problem subs, recompiled and tested on my software player. Everything was fine except the last 3 BoV's would not play. I found one of the menu buttons was 1 frame off from the start of the highlight. No idea how this happened, but once the highlight and subs were adjusted it was happy.

Then I burned a test disk for my stand alone. Everything worked except the comic BoV's. What worked on the software, did not on the player. No subs were showing up when the comic track was played. So I went back and took a hard look at the import script again. The comic BoV stream uses button 3. Turns out that one of the dummy buttons (button 2) was being set to display as wide, pan, below is the snippit of the original:

Item=Highlight Play
Data=
Start Time To Video=01:32:35:11
Resolution=NTSC
Drop Type=Drop frame
Start Time=00:00:00:00
Duration=00:00:10:19
Button Mode 1=Wide
Button Mode 2=Wide, Pan
Button Mode 3=Wide
Button Color 1=Button Color


Well I modified all the instances of Wide, Pan to Letter. After doing this the stand alone played the entire title flawlessly. All the buttons work and go to the correct place.

Well thats it, I now have a complete working and tested backup. I hope this information will aid in the further development of these great tools. Feel free to post or messege me for any additional information.

Trigger

D3s7
7th September 2004, 22:46
Warning: This will be a long reply, not as long as your post but long nevertheless :)


To Start: Thanks for the update/post Trigger - the problems listed and your resolution is the perfect example of a post that will drastically help these types of utilities make it as far as they can

A few more options have been added that kind of merge what you talked about below w/ the differences between pre6 and pre7. Specifically how subs are treated when a) < 1sec b) marked as highlights but non are found And removing of stops on subs labeled as such

As far as the button information goes, it sounds like there was multiple highlightplay's per cell but only the commands for the first one was being imported? I'll double check the code on this as it could very well be something I overlooked when creating the BoV code.

I'll have to check the buttons as well.. I'm looking at the .bov file you sent me and buttons 1,2 are definatly Nop with the commands being on button3. I'm wondering if it's possible the buttons are out of order which would explain the problem you are seeing below.

The Background of the subs is unfortunatly something I'm not sure I can correct right now without some major rewrites although I'd be interested in seeing the .sub/.idx & .bov/.bdx files from that as well. It's possible to rewrite vsconv to properly do these bmp's but the alignment would then be an issue in Scenarist. more research will be needed on this

Subs and Highlights being 1or2 frames off is something I've discovered of late.. the part that's really frustrating is it seems to be isolated to scenarist 2.6 and 2.7. Scenarist 3.0 imports them correctly (but as we know has it's own problems with BoV) and usually occurs i've noticed when the subs change minutes IE: Starts at 00:33:55:20 and ends on 00:34:01:05 or something like that which leads me to think it's a qwirk in the 2.6/2.7 dropframe code

This is VTS 8 PGC 1 correct? I still have some of the files you sent me and one of the original scripts so I should be able to troubleshoot some of these issues directly

trigger638
9th September 2004, 02:56
I'll have to check the buttons as well.. I'm looking at the .bov file you sent me and buttons 1,2 are definatly Nop with the commands being on button3. I'm wondering if it's possible the buttons are out of order which would explain the problem you are seeing below.

Yes correct, buttons 1 and 2 were always Nop in the script that Scenaid created. However, the ones where scenaid placed a button command in button 3 should acutally have been assigned to button 2, and the ones where a command should have been assigned to button 3 were Nop across the board. If I had to guess I would say that the script is shifted one down, meaning that a button that was in two goes to 3 and a button that was in 3 is going to 4 (except 4 does not exsist so it just Nop's 3).

The Background of the subs is unfortunatly something I'm not sure I can correct right now without some major rewrites although I'd be interested in seeing the .sub/.idx & .bov/.bdx files from that as well. It's possible to rewrite vsconv to properly do these bmp's but the alignment would then be an issue in Scenarist. more research will be needed on this

Im sending you the files, I still have them. I think your right on about this being difficult. I can tell you that I played around with it a little bit and it seems that Scenarist won't let you adjust anything once the import happens. So for me to do any real testing with the script was near impossible as it would be a total guess as to the display area to start with. Its important to note that this problem may be very unique, and it is fixable by a manual color change in Scenarist.

This is VTS 8 PGC 1 correct? I still have some of the files you sent me and one of the original scripts so I should be able to troubleshoot some of these issues directly

Yes it is VTS 8 PGC 1. Again that PGC contains all the features of the film. Both BoV features (that are in the same stream, English = track 00W and 01L), main English/French sub tracks (English = track 04WL), and the storyboard track (English = tracks 06W and 07L)

Glad the info helped.

Trigger