FlaskMPEG also giving troubles when adding subs to Bridget J

[poopyhead]

sorry for the 3rd post about this. the previous 2 posts was about vobsub/virtual dub having problems with adding subs to Bridget Jones's Diary. thus, i switched to using FlaskMPEG to add the subs.

i used Sefy's guide. however, after i load the .ifo file into FlaskMPEG and select the only subtitle (english), FlaskMPEG gave me this error, which is very similar to the error vobsub/virtual dub gave me:

error parsing .ifo file

i've ripped the .ifo file with both smartripper and lastest version of dvddecryptor and still problems. anyone help?

btw...if i choose to not add subs with FlaskMPEG, i get no error msgs.

[vitualis]

I presume you are ripping in "File Mode"?

Are you using the "subtitle fixed" version of Flask 0.6 prev1.1?

Regards.

[poopyhead]

o...i'm ripping in "movie" mode.....am i suppose to rip in "file" mode? if so, does it take care of multi-angles?

i'm using FlaskMPEG 0.5.9.4, that already comes with subtitle capability without any extra plugins...Sefy also mentioned it's more stable...so i don't think i need the "subtitle fix"

[vitualis]

File mode, file mode, file mode!!

FlaskMPEG has its own IFO parser. It expects to see the VOB files exactly as they do on the DVD (minus CSS of course). If you rip in "movie mode" the structure of the VOB files will have been changed and FlaskMPEG will baulk.

0.594 may be more stable but there are BIG benefits in the subtitled fixed version (0.6 prev1.1). That version is relatively stable and the subtitle support is much better. Many subtitles won't display properly (or at all) in the non subtitled fixed versions. 0.6 prev1.1 is also 20% faster (with Panasonic) compared to 0.594 on my machine.

Regards.

[Sefy]

vitualis, movie mode, movie mode, movie mode
I always rip the Movie, and you can even see in my guide that i'm using Flask 0.6 and it worked pretty good, so sorry

As for speed, I find that a bit weird, considering the encoding is still done by Panasonic, and that isn't affected by any ver of Flask no matter how fast it will be

I've found that for Flask 0.6, for every little thing you need to download a plugin, and it's rather annoying, you wanna read IFO's ? you gotta download a plugin, you wanna read subs ? you gotta download a diffrent version, annoying!

On the other hand, you can download an optimized version of Flask 0.594 (I use the AMD optimized) and you will get the same performance (Panasonic doesn't care about how optimized your Flask is!) and you get all the required tools in one go!

[poopyhead]

vitualis, does file mode take care of multi-angles cuz i believe Bridget Jones's Diary has some in it..

Sefy, were u being sarcastic in saying "movie mode, movie mode, movie mode"?

[Sefy]

Actually I was being rather serious in a sarcastic sort of way, basicly, i've always ripped my movies in Movie Mode and never in file mode, and I just disagree with what vitualis said

[poopyhead]

Sefy, err...well..i'm kinda running into problems with the .ifo file in Bridget Jones's Diary. I'm trying to use FlaskMPEG to add subs according to your guide. It had errors parsing the .ifo file and vitualis sez i have to rip it in file mode in order for FlaskMPEG to correctly parse the .ifo file.

is that true?

if it is, does file mode remove multi-angles and if not, how do i remove it afterwards then?

[Sefy]

I've not had problems with FlaskMPEG using Movie Mode, I think it can handle File Mode and Multi Angles cause it reads the IFO files directly, just like a DVD Player.

[poopyhead]

Sefy, ok...if i rip it in file mode....how do i remove the multi-angles afterwards?

[Sefy]

You don't need to remove them, when you use Flask to Encode, it knows how to handle it, remember, it has it's own IFO parser, it knows how to play it back correctly.

[poopyhead]

Sefy, hrm.....ok...how about if i were to frameserve from Flask to tmpgenc, as stated by your guide, will Flask also take care of the multi-angles?

[Sefy]

Technicly it should, as it handles what the encoder will get, using Frame Serving is same as using any other Plugin within Flask.

[poopyhead]

thnx Sefy, i'll give it a try after i come back from winter break

[vitualis]

Actually, I have to strongly disagree with your Sefy...

FlaskMPEG can only do subtitles if you load the IFO file. When it does that, it expects to see the VOB files exactly as what it is on the DVD. If the movie has multi-angle or seamless branching, then it will select the correct sequence. To do this, ALL the angles and seamless bits must be present -- which requires "FILE MODE".

If you use "MOVE MODE" on a VOBSet with seamless branching or multi-angle, then all the other "non-relevant" parts are striped out. When FlaskMPEG then subsequently reads the IFO file to access the VOB files, there are parts of the VOB file missing --> to a parsing error.

Also there is definitely a speed increase on my PIII from 0.594 --> 0.6, near 20%. Although Panasonic does the encoding, Flask still has to do resizing and decoding of the MPEG-2. 0.6 is simply more efficient at this than 0.594. If you persist in using 0.594, there is a "subtitled fixed" version of 0.594 as well.

The "subtitle-fixed" version is a MUST. Many DVD subtitles do not work properly otherwise (e.g., Crouching Tiger Hidden Dragon).

There is one other significant benefit of 0.6 over 0.594. For PAL R4 DVDs (Australia), 0.594 does not correct decode many (newer) Dreamworks titles (e.g., Prince of Egypt) --> skipping of video and audio. v0.6 does not have this problem.

Regards.

[Sefy]

vitualis, I just checked your theory on File Mode and Movie Mode, and i'm gonna persist you are wrong on this one, all that happens as far as I can see, in File Mode YOU select the VOB's and in Movie Mode, Smart Ripper selects the VOB files that are used for the Movie only, the files that were extracted were identical! (using file compare utility! man that took long!), therefor, all Smart Ripper does is RIP! it does NOT make any changes to the VOB file itself, the maximum change you might get is the IFO file.

AS FOR THE IFO file, I ALWAYS rip in Movie Mode, and both 0.5 and 0.6 load the IFO, and still have the entire movie and the Subtitles, and the movie encodes just perfectly.

Lastrly, regarding speed, I can't argue there, you might be right, hey, when i'm wrong, I admit it, but i'm still puzzled as to how much performance can you really get when Panasonic is the one doing the encoding! that program is slow, face it! how can Flask increase the performance of a program that does NOT use any CPU features ?

[P@iNKilleR]

I have to agree with sefy for one I'm ripping briget jones's diary now using the flask 045 as it produces a nicer picture!!! argue if U want but it does just try the new version to the old one and see. To my next point I've used flask & panasonic for 2 years now & for one ripping in file mode & ifo parsing is exactly the same only U can see what subs U wanna add in newer versions ie 594 & 06 preview with subfix also to prove a good point I just done a test & there is bugger all difference! stick to what U know is right sefy as U R There again virtualis has his points aswell 06 is faster but there is a decrease in the quality with such a speed increase ie blockyness & motion blur & shadow. If anyone still has an old copy please try it as I know I'm right this time....

Right off my soap box & hopefully shed light on the subject but 06 preview with subfix is fine & works ok along with dvdx for subs is fine aswell.

cya l8r all

Kev!
A nurse who has just come off a 12 Hr night shift

[poopyhead]

vitualis, u said there was also a "subtitle" fix for Flask 0.5.9.4. if there is, can you provide a link to it? i can only find fix for Flask 0.6.

Sefy, i believe Vitualis was referring to movies with multi-angles. Then the vobs ripping in "movie mode" and "file mode" will be different between smartripper removes the multi-angles that are present in the "file mode" but not in "movie mode". i guess there's no difference between movie and file mode if there are no multi-angles.

also, for vitualis, will all the "extra" benefits u speak of for Flask 0.6 still be there if i plan to frameserve from Flask to tmpgenc?

[vitualis]

<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR size=1 color=black></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>
On 2001-12-21 13:30:07, poopyhead wrote:
vitualis, u said there was also a "subtitle" fix for Flask 0.5.9.4. if there is, can you provide a link to it? i can only find fix for Flask 0.6.</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR size=1 color=black></TD></TR></TABLE>

It used to be on Apachez's site but that has since closed down... I'm not at my home PC at the moment (or for the next few weeks) so I can't send it to you. I can only suggest that you try to search for it. The "subtitle-fixed" version of 0.594 is made by the same person that made the subtitle-fix of 0.6prev1.1 and he has a page somewhere.

<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR size=1 color=black></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>Sefy, i believe Vitualis was referring to movies with multi-angles. Then the vobs ripping in "movie mode" and "file mode" will be different between smartripper removes the multi-angles that are present in the "file mode" but not in "movie mode".</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR size=1 color=black></TD></TR></TABLE>

Exactly!! For example, on the R4 version of Independence Day, it uses seamless branching to include both the standard and "special" versions of the movie. If you rip in file mode, you get to select which version you want to encode in flask when you load the IFO. If you use "movie mode", then SmartRipper parses the IFO and only rips ONE of the versions. If you then use Flask mpeg to load the IFO, you will eventually get a parsing error.

File Mode and Movie Mode IS NOT the same if theres is seamless branching or multi-angles.

As for the quality difference between 0.594 and 0.6, I hadn't noticed anything... but now I'm paranoid about my next rip...

<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR size=1 color=black></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>also, for vitualis, will all the "extra" benefits u speak of for Flask 0.6 still be there if i plan to frameserve from Flask to tmpgenc?</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR size=1 color=black></TD></TR></TABLE>

For my P3 500 machine 0.6 is definitely 20% faster than 0.594 (with Panasonic). This is referring to the standard versions (not the "optimised" versions of 0.594). The main source of this I believe is that the MPEG-2 decoder has been better optimised (for those not convinced, "play" the vob files through FlaskMPEG rather than doing any conversion -- it is faster on 0.6).

The problem I referred to with Dreamworks DVDs is definitely present. I've encountered it enough times to know that it is real (with v0.594). This problem is not present with 0.6. I believe that some Disney DVDs have the same problem with 0.594 (e.g., R4 PAL Fantasia 2000).

These benefits should still be present with frameserving to TMPGEnc.

Regards.

[Sefy]

Well, you've just confirmed me vitualis, i've said that the only change you might get is the IFO file, there is no way the change is being made to the VOB files themselfs, cause they are identical in File Mode or Movie Mode.

Now, since you aren't using the Optimized version of 0.594, i'll not take your performance boost seriously, cause i've used the Optimized and 0.6, and they both gave the same speed for me

Oh, and i've got about 10 Disney VCD's now, and most of them were done back in the old days of Flask/Panasonic, and i've had no problems ripping them, and again, I always use Movie mode.

PS: Will you stop quoting ? look at the length of the post

[vitualis]

Grrr.... read what I wrote Sefy.

The change IS NOT in the IFO file. In movies with seamless branching or multi-angles, the resultant VOB files are different. "Movie Mode" was invented for the benefit of DVD2AVI as DVD2AVI does not parse IFO files. If the VOB files are not stripped of the extra angles or branches, you get duplication of scenes when ripping with DVD2AVI.

Read doom9's comparision of different rippers if you want confirmation.

The performance boost is REAL. I never used the optimised versions of 0.594 because there weren't as stable on my PC. In any case there isn't an "optimised" version of the "subtitled-fixed" version of 0.594. Simply, on a P3 500, using the Panasonic encoder, standard 0.6 is about 20% faster than standard 0.594.

As for Disney/Dreamworks DVDs, this problem is only evident in NEWER ones. For example, R4 PAL Fantasia 2000. You may not have encountered this, but I have NUMEROUS times with 0.594. In fact, my VCD rip of Prince of Egypt is still flawed with occasional skips because of this (and I didn't notice until after I burned the VCD).

There are numerous other benefits of the 0.6 branch over 0.594 including better audio options as well as MUCH better "start" and "stop" points.

Regards.

[Sefy]

vitualis, I think i'm a very lucky person then, cause I happen to have Fantasia 2000 R4 (PAL, i'm in Israel you know) and it's one of the easiest and fastest rips, not to mention shoortest and most disappointing movies

And yes, I know DVD2AVI doesn't parse IFO files, but I tell ya again, i've ripped using Smart Ripper using File and Movie mode and there was no diffrence in the VOB file.

Lastly, i've never argued that 0.6 doesn't have more features, although it's more annoying then improved with all the need for external files just to do what the previous ver already had build in, as for the speed, i've not used any fix version, just the Optimized (still use it) and the speed you mentioned is identical to the 0.6.

[vitualis]

Sefy, rip in File Mode and Movie Movie on a DVD that uses seamless branching or multiangles. Then compare the VOB file sizes to the original. There is definitely a difference (e.g., ID4, Matrix, etc.)

The subtitled-fixed version of Flask is a must if you use subtitles. For example, CTHD (R4 PAL Australia), the subtitles don't come up at all without the fixed version. With Star Trek 5 (R4 PAL Australia), most of them come up but a few don't.

In any case, in response to poopy's original question, he was using subtitles and I strongly recommend using the "subtitled-fixed" version of Flask 0.6 if you are going to use Flask at all.

Furthermore, he ripped in "Movie Mode" and not surprisingly, he got a parsing error with Flask.

Regards.

[Sefy]

Oh, I didn't know you were a Classic Star Trek fan! i'm also! i've got all the movies, unfortunatly on VHS though

Well, i'm not gonna debate on Flask, I find that program rather annoying myself, especialy 0.6, too many plugins, Flask is only a shell for other programs, That's why I liked DVDx better, it has everything intergrated instead.

[poopyhead]

vitualis,

i also won't be back on my home PC for about 2 weeks. do you think u can send me the subtitle fix for flask 0.594 when u do get back to your home PC? i'm not in any rush and won't be at my home PC for awhile too.

[vitualis]

Not a problem.

I suggest that you send me an e-mail though as I'll probably forget otherwise.

Regards.