Subtitles that are UNripable?!?

[Jo The Veteran]

Ok, i got this movie that comes with english subtitles. I riped the movie and it looks great however about the subs.. although you can see the subs when watching the movie pretty fine, you can't rip then at all no way. I'll let the pics talk for me.


This hapens every 1 subpicture. The first looks fine, the second looks like crap, the third fine, the fourth crap again.
Does anybody know, is this some kind of rip protection and can it be bypassed? Or is it a problem with the Subrip program or whatever?
I eagerly await your opinions.

[rickydavao]

This same thing sometimes happens to me whenever I try to OCR the subtitles using SubRip and using ripped subtitles as the source ... that is, the source is a sub/idx ripped subtitle. Not sure if this is your scenario, or why this problem even happens at all. I have found 2 solutions to the problem in my case ... (1) OCR the subtitles using SubRip straight from the ripped DVD folder on your hard disk, specifying the IFO file for the main movie, or (2) if all you have to work with is the sub/files, then SubResync (included with VobSub) will usually do the trick. The only problem with SubResync is that you can't specify italics and such in your final output - but it should easily identify all of your characters (including the ones that look like "crap", which Resync actually sees normally).

Not sure why this problem happens at all ... maybe another member has the explanation. I guess I'm more concerned with getting it to work! :P

[Squash]

I've run into that before. I was able to fix it by using ai4spam's advice in this post:

http://forum.doom9.org/showthread.php?p=909795#post909795

and look at roli_bark's reply 4 posts down from that. I didn't need to delete the .ini file like he did, just played with the settings, but in roli's case it worked.

His screen shot is no longer on the doom9 thread, but it looked just like yours.

[AlanHK]

You could get them from here
Use your rip to resync if necessary.

[Jo The Veteran]

I don't know rickydavao, the problem appears only in ripped sub/idx subtitles true, however I'm not 100% sure that that is the rule.
It happened to me in a movie and an anime series till now. Both had theyr subs ripped, however they included the subs in sub/idx format and not your standard srts. Why? I think because they couldn't OCR them right from the dvds.
I anycase thanks for all your answers. I'll try and see what happens.
AlanHK you guessed the movie! I'm impressed! However what I (and rickydavao) want, is the anwer to the problem, and not the specific subtitle. Thanks for the subtitle though, I won't have to OCR that one.

[Jo The Veteran]

What Squash suggested actually worked. Take these 2 settings, that is "Use VOB's subtitle map" and "Use IDX's file offsets", from Subrip off and it sees the subtitle crystal clear whithout big red nasty backgrounds.
I now however encountered another problem.
I don't know if this is indused by changing the settings in Subrip but what has happened here has happened to me again some time ago with another subtitle problem i describe in the post https://forum.videohelp.com/topic322420.html, or at least i think it's the same problem.

What the pic from my old post shows is pretty much what happens with my new subs right now.
It's kinda random however when it happens it messes the whole sub.
I didn't get an 100% solution then doing what AlanHK had proposed using excel. This although it fixes the sub in some level, it's not entirelly correct. The time values do not change, only the text is moved, so even thought the lines appear where they are supposed to be, theyr durration is utterly wrong.
For example the duration for the words "Wow!" and "What are we gonna do now man?" are at least 1 second apart (or more). So "Wow!" shows for (whatever the previous line had for durration) while "What are we gonna do now man?" show for the durration of "Wow!", which is pretty small, so you can't actually see the whole line before it disappears.
See my predicament here? I'm seriously thinking of deleting all those %@#$ed up subs and leave the videos raw, which is also what I really am gonna do if I don't solve this.
However now i'm tired.
I bid you all goodnight.

[Squash]

Jo The Veteran,

As regards your old post you linked to above, there've been problems converting vobsubs extracted from MKVs to srt for quite a while. Apparently the damage is done when the vobsubs are muxed into the MKV. There's a PERL script in this post that might help you with that:
http://forum.doom9.org/showthread.php?p=1006101#post1006101

A new version (August 2008) of mkvtoolnix is linked to on the bottom of that page that will hopefully take care of the muxing problem.

As far as the DVD-ripped vobsubs you refer to in your first post in this thread, I have both of those subrip settings turned off and I haven't seen your timestamp problem with the DVD vobsubs that I've converted to srt using Subrip.

[AlanHK]

thought the lines appear where they are supposed to be, theyr durration is utterly wrong.

If the starting times are right, you can load the sub in Subtitle Workshop and use:
Edit/Timings/Automatic durations,
which estimates the durations based on the number of characters and words. You can change the formula it uses.

Subtitle Workshop has some excellent functions for adjusting timing in bulk or individually. Read the manual for details.

[Jo The Veteran]

Brilliant! I'll try the guide from doom9 and the subtitle workshop edit (which had no idea existed ) and come back to you with whatever turns up.
Thanks again dudes.

[roli_bark]

I've run into that before. I was able to fix it by using ai4spam's advice in this post:

http://forum.doom9.org/showthread.php?p=909795#post909795

and look at roli_bark's reply 4 posts down from that. I didn't need to delete the .ini file like he did, just played with the settings, but in roli's case it worked.

His screen shot is no longer on the doom9 thread, but it looked just like yours.

Yes ! - My screen shot was lost, but it looked EXCATLY as the OP shows. Same problem that was resolved as per link above, and it loooks like it is resolved by other method as well.
Cheers.