IMPORTANT, PLEASE READ

1 NO REQUESTING MOVIES OR SAMPLES (THIS INCLUDES REQUESTS FOR OTHER GROUPS TO RELEASE THIS FILM!)

2 DO NOT DISCUSS WHERE TO DOWNLOAD MOVIES OR SAMPLES

3 NO FLAMING

4 NO "SPOILERS"

5 COMMENT ON THIS RELEASE ONLY (AND ONLY IF YOU'VE SEEN IT). THIS IS THE SOLE PURPOSE OF THE THREAD!

6 NO "NOOB" QUESTIONS SUCH AS "HOW DO I WATCH THIS?" ASK IN THE APPROPRIATE PART OF THE FORUM

7 NO DISCUSSING TRADING/SELLING. IF YOU SELL COPIES, GO AWAY YOU'RE NOT WELCOME HERE


*** PEOPLE IGNORING THE RULES WILL BE BANNED ***

Report this post to a moderator |

First let me say good to see them fix their own mistakes. Second, this is not a call for a repack, just some information. Replica made the correct call, as a repack would have been overkill. If you feel you need to fix this, just remux the movie.

Regarding the subtitles, well in this case its not just a IfoUpdate fuckup.

In layman terms, a good subtitle (so it's looks better without jagged edges) is buildup out of 4 segments.

Looking at the Replica subs.

First you have the background, which is transparant.
Then you have the outline, which is black.
Then you have the anti-alias which again is transparant.
Finally we have the primary text color (centre) which is black again.

All changing the color codes in a IFO can do is change the color that is displayed. The transparancy setting however is stored in the VOB itself, and therefore cannot be fixed by a IFO fix.

As you can see clearly in the original sub (and not so well after the fix) is that the anti-alias shouldn't be transparant.
After the fix the subtitles still look a bit transparant, and basically ugly on some occassions. For best subtitle viewing the anti-alias should have a transparancy of 15 (fully shown) and with white subs be grey. That way you get the best looking subs IMHO.

The original already could have had this problem, but it probably already went wrong in the remux of the movie. They probably used a method which strips the subtitles down to .bmp's and a .sst file. Somewhere in that .sst file or in the .bmp's anti-alias and background got linked together, or anti-alias wasn't read correctly from the .bmp.

A .sst file will look something like:

Color (3 1 2 1 )
Contrast (15 15 15 0 )
E2 (0 0 255 ===)
E1 (255 0 0 ===)
PA (0 0 0 ===)
BG (255 255 255 ===)

So, how do you read this.

E2 = outline
E1 = anti-alias
PA = primary text / centre
BG = background

The line color is build up like ( E2 E1 PA BG )
This is where you tell the authoring application to which CLUT index (ifo) the specific types should be mapped.

The line contrast is build up like (E2 E1 PA BG)
This is where you tell the autoring application which transparancy level the specific types should have.

The E2 line etc. are build up like ( RED GREEN BLUE r_rule g_rule b_rule)
The authoring application will analyze the colors used in the BMP, and generate a subpicture. In this case everything blue will be mapped to E2, everything red to E1, everything black to PA, and everything white or unmapped will be BG.

So in the case of Replica (under the assumption it was their slipup) 3 things could have happened:

- The transparancy in their .sst was set wrongly so that E1 had a contrast of 0
- The color used in the .bmp was the same for anti-alias and background
- The color detection rules didn't match the .bmp, anti-alias couldn't be found, and therefore authored as background.

Hope this helps anyone who's ever experianced a similar problem and couldn't figure it out.

Report this post to a moderator | IP: Logged

Very nice rip as allways for Rep
9.5 / 10 / 9

Report this post to a moderator | IP: Logged