HD subtitle ripping (SUPread)

[jamos]

What happened?

I am not sure whatever you changed in the last release fixed it. but like i said the sync is now off.

[jamos]

I've found a bug and fixed it. The new SUPread generate the same xml as hdsub2bdn.

something broke the sync for 23.976 non drop not sure what it was but they were in sync before this version. about a 12 second delay on the subtitle.

xml output from previous version of supread <Events Type="Graphic" FirstEventInTC="00:02:08:07"

output from current version from same sup file <Events Type="Graphic" FirstEventInTC="00:02:19:22"

[jamos]

Pelican is there anyway we can download older versions of supread? would like to use older version to check this sync error.

edit: ok it seems that using xport i get the correct timings, the sup i was testing that had the wrong timings was demuxed with tsremux. I suggest everyone use xport to demux m2ts streams.


nice photos btw.

[jamos]

ok so now I can confirm that the current version of supread works with scenarist hdmv with both bluray and hd subtitles in both 1080p and 720p.

[hm10]

you can give me the data.pas that you did?
to comapre with i do you well

[Pelican9]

ok so now I can confirm that the current version of supread works with scenarist hdmv with both bluray and hd subtitles in both 1080p and 720p.

Glad to hear! :)
And big thanks for the test.

you can give me the data.pas that you did?
to comapre with i do you well

You can download from my site.
Send it to me with your png and I will check it.

[hm10]

You can download from my site.
Send it to me with your png and I will check it.


you mean this?
http://pel.hu/down/data.pas

i need to put my new letters in the end of the letdat (after 256) and than in the end of letdati (after 256)?

line, x pos', width, dec after, dec before (from left to right)?

(0, 0, 0, 0, 0), //1 ?

[Pelican9]

you mean this?
http://pel.hu/down/data.pas

Yes.

i need to put my new letters in the end of the letdat (after 256) and than in the end of letdati (after 256)?

line, x pos', width, dec after, dec before (from left to right)?

(0, 0, 0, 0, 0), //1 ?
Yes. Yes.
You have to put your data here (line 292-):

290: (0, 0, 0, 0, 0))
291:// ,( // put the new data here (normal)
292:// (0, 0, 0, 0, 0),
293:// ...
294:// (0, 0, 0, 0, 0))
295: );

and here (line 556-):

554: (0, 0, 0, 0, 0))
555:// ,( // put the new data here (italic)
556:// (0, 0, 0, 0, 0),
557:// ...
558:// (0, 0, 0, 0, 0))
559: );


But you can put your data anywhere, I will correct it.

[Sagittaire]

here the code the palette defintion in BDN xml project.

<xs:element name="Palettes" minOccurs="0">
<xs:complexType>
<xs:sequence>
<xs:element name="Palette" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>ID: Alphanumeric ColorSpace: RGB/YCrCb</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="Entry" maxOccurs="256">
<xs:annotation>
<xs:documentation>(R,G,B,A) or (Y,Cr,Cb,T) See Sec 9.11.4.2.3 in BD-ROM Spec 0.89r3 for constraints</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:attribute name="Index" use="required">
<xs:simpleType>
<xs:restriction base="xs:int">
<xs:minInclusive value="0"/>
<xs:maxInclusive value="254"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="Y_R" use="required">
<xs:simpleType>
<xs:restriction base="xs:int">
<xs:minInclusive value="0"/>
<xs:maxInclusive value="255"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="Cb_G" use="required">
<xs:simpleType>
<xs:restriction base="xs:int">
<xs:minInclusive value="0"/>
<xs:maxInclusive value="255"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="Cr_B" use="required">
<xs:simpleType>
<xs:restriction base="xs:int">
<xs:minInclusive value="0"/>
<xs:maxInclusive value="255"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="T_A" use="required">
<xs:simpleType>
<xs:restriction base="xs:int">
<xs:minInclusive value="0"/>
<xs:maxInclusive value="255"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="PaletteID" type="xs:string" use="required"/>
<xs:attribute name="ColorMode" use="required">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="RGB"/>
<xs:enumeration value="YCrCb"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>

1) Perhaps good way to close HDDVD subtitles support
2) Perhaps better way to import palette from m2ts and export directly in xml file
3) Possible to make xml BDN file with direct srt import?

[hm10]

But you can put your data anywhere, I will correct it.


just save this data file and do png?

and i can add bold style? or don't need

edit: how i do the y coordinates bottom (green in u'r picture) in big ABC letters? the bottom and the base same

[Pelican9]

just save this data file and do png?

and i can add bold style? or don't need

edit: how i do the y coordinates bottom (green in u'r picture) in big ABC letters? the bottom and the base same

1. Yes
2. No, you can't add bold style.
3. No problem if the bottom and the base equals.

You can send me the files for checking before they completely ready...

[mashiwen]

hoping to add "480P" transfer

[Pelican9]

here the code the palette defintion in BDN xml project.
1) Perhaps good way to close HDDVD subtitles support
2) Perhaps better way to import palette from m2ts and export directly in xml file
3) Possible to make xml BDN file with direct srt import?
What can we do with this palette definition? Why did you post it?
1. ??? Why do you want to close the HD DVD subtitle support?
2. ??? SUPread doesn't do anything with m2ts files.
3. ??? srt import and xml export already work in SUPread

[hm10]

1. Yes
2. No, you can't add bold style.
3. No problem if the bottom and the base equals.

You can send me the files for checking before they completely ready...

ok thx

[Pelican9]

hoping to add "480P" transfer
The 720p export is not as nice as I would like to.
The 480p could be much uglier because its size.
You can use SubtitleCreator for SD subtitles.

[hm10]

in hebrew write from right to left so maby i need to write the letters in the png from left to right?
because maby the write will be backward?

[Pelican9]

in hebrew write from right to left so maby i need to write the letters in the png from left to right?
because maby the write will be backward?

Doesn't matter. I will cut the letters one by one.
Could you send me a hebrew srt?

[hm10]

Doesn't matter. I will cut the letters one by one.
Colud you send me a hebrew srt?

take:

[hm10]

when i import srt and export blu-ray the file don't need to be .pgs?
HD-DVD it's .sup no?

[Pelican9]

when i import srt and export blu-ray the file don't need to be .pgs?
HD-DVD it's .sup no?

Both (BD and HD DVD) subtitle stream file use the same (.sup) extension.

[hm10]

Both (BD and HD DVD) subtitle stream file use the same (.sup) extension.

ok, i remembered from older version of supread was write pgs for blu-ray subtitle import and sup for hd-dvd subtitle import
and too tsremux remux from m2ts pgs file

[hero88]

Pelican9, have you tried getting in touch with Taktaal about combining forces?
Suprip is the best for ocr'ing a sup file, but it has issues with timings on some files, where Supread has no timing issues, but on a lot of subs, there are so many chars it cannot detect, but it can do everything else :)

So for the moment, I use suprip to OCR , supread to generate a sup file where the timings are working and subtitle processor to copy the timings from supreads file to suprips file.

It works but would nice to avoid the extra steps :)

[hm10]

dec before it's the left side of the letter (the space)?
and
dec after it's the right side of the letter (the space)?

[jamos]

Pelican can you fix output for BDM (scenarist) from a .srt file?

It almost works, but is cutting off lines of text and the colors are wrong.

[Pelican9]

dec before it's the left side of the letter (the space)?
and
dec after it's the right side of the letter (the space)?

Yes. This values decrement the default space between the letters.

[hm10]

Yes. This values decrement the default space between the letters.

input this or stay blank?
because the values littles... 1 pixel - max' 2 pixel

[Pelican9]

input this or stay blank?
because the values littles... 1 pixel - max' 2 pixel

Leave zero. You can adjust later.

[lance79]

I tried latest Supread 51b6, when opening a srt and converting to png's or use the export sup.My images look like this... Havent seen this problem before i'm sure it can be fixed :)

[Pelican9]

Pelican can you fix output for BDM (scenarist) from a .srt file?

It almost works, but is cutting off lines of text and the colors are wrong.

Send me an example, because it's work here.

[Pelican9]

I tried latest Supread 51b6, when opening a srt and converting to png's or use the export sup.My images look like this... Havent seen this problem before i'm sure it can be fixed :)

You can send me directly, it's more effective.

[lance79]

You can send me directly, it's more effective.


ok pm sent...

[Pelican9]

ok pm sent...
Problem solved. :)

[jamos]

Im getting a invalid character error while trying to import a srt i sent you the file to your email. the file is a direct export using mkvextract and loads fine with subtitleworkshop.

thanks

[kaag]

Hi everybody,

first of all, thanks for SUPRead, it's an incredible tool and very useful for me.

I have a little request about the "abc.png" file. Would you be able to add some new letters, especially french character such as "ê,è,ù,ô" and so on ?

:thanks:

[jamos]

also it looks like supread is not handling | characters correctly in a srt file.

a | character in the .srt means new line. it seem to just truncate the rest of the text after a | character. The file I sent you for the other issue has them.

[hm10]

Hi everybody,

first of all, thanks for SUPRead, it's an incredible tool and very useful for me.

I have a little request about the "abc.png" file. Would you be able to add some new letters, especially french character such as "ê,è,ù,ô" and so on ?

:thanks:

in page 17 you have explain how to add...

[Pelican9]

Im getting a invalid character error while trying to import a srt i sent you the file to your email. the file is a direct export using mkvextract and loads fine with subtitleworkshop.

thanks

Your srt contains 3 characters at the beginning (EF BB BF).
It's non standard, I don't know why mkvextract put there.
Remove it and it will be OK.
But SUPread works well without remove this 3 chars, it gives only an error message about 'xxx1' is not a valid integer value.
Where did you see that invalid character error?

[Pelican9]

also it looks like supread is not handling | characters correctly in a srt file.

a | character in the .srt means new line. it seem to just truncate the rest of the text after a | character. The file I sent you for the other issue has them.

I think .srt format doesn't contain any '|' character. This format use new line for new line.
The test.srt you've sent to me doesn't contain any '|' char also.

[Pelican9]

Hi everybody,

first of all, thanks for SUPRead, it's an incredible tool and very useful for me.

I have a little request about the "abc.png" file. Would you be able to add some new letters, especially french character such as "ê,è,ù,ô" and so on ?

:thanks:
Why don't you do this? :)
See page 16,17.

[hm10]

pelican I'm doing hebrew letters, english little and big and numbers

[Pelican9]

pelican I'm doing hebrew letters, english little and big and numbers
Great!
If you want the English alphabet too, you can start with the original abc.png and put the hebrew letters into new lines.
Copy the whole 256 lines of letdat and letdati in data.pas and change the codes of the hebrew letters only. It saves a lot of work for you.
Email me for checking.

[hm10]

Great!
If you want the English alphabet too, you can start with the original abc.png and put the hebrew letters into new lines.
Copy the whole 256 lines of letdat and letdati in data.pas and change the codes of the hebrew letters only. It saves a lot of work for you.
Email me for checking.

I'm not want to compliacted so i continue with my png...
i will send you when i'll finish the all the letdat

[Pelican9]

I'm not want to compliacted so i continue with my png...
i will send you when i'll finish the all the letdat

OK. It's your choice.
I've just wanted to spare your times.

[hm10]

OK. It's your choice.
I've just wanted to spare your times.

yes, i understand but i think that i will complicate...

[hm10]

I hope when i will arive to the numbers won't be problem because the numbers connected =\ same problem was with some little english letters but succeed (hope well)

[kaag]

Why don't you do this? :)
See page 16,17.

I'll have a try :)

[jamos]

I think .srt format doesn't contain any '|' character. This format use new line for new line.
The test.srt you've sent to me doesn't contain any '|' char also.

maybe it was just subtitleworkshops way of representing the linefeed character.

[jamos]

Your srt contains 3 characters at the beginning (EF BB BF).
It's non standard, I don't know why mkvextract put there.
Remove it and it will be OK.
But SUPread works well without remove this 3 chars, it gives only an error message about 'xxx1' is not a valid integer value.
Where did you see that invalid character error?

Yes that was the error i got 'xxx1' is not a valid integer value, I assumed it was a invalid character.

ok found the error one of the characters exported from mkvextract was invalid, someone really needs to work on mkvextract it is very buggy.

thanks.

[Pelican9]

Yes that was the error i got I assumed it was a invalid character.

ok but its strange that this will load with subtitleworkshop with no errors. wonder if that is a known bug with mkvextract.

If you save the srt with Subtitle Workshop it will be good.
SubtitleWorkshop is smarter than SUPread and ignores the first 3 chars (maybe these 3 chars have some meaning, I don't know).

[hm10]

pelican check pm sent you