BDSupEdit

[GZZ]

I created this tool, as I was missing a tool to downscale BD subtitles to be used on 720p encoded movies.



The application is pretty simple, just load the sup file, then set the resolution under options, including all the resize filter, Dither mode etc. then export the sup file and import it into tsMuxeR


Supported resolutions are:

• 1920x1080

• 1440x1080

• 1280x720

• 720x576

• 720x480

I have alot of planned work for this tool, but ideas are welcome. I hope alot of you will like it and maybe donate a little, as I have used >alot< of time (see about in application) on this application and hopefully will continue to do.

Newest version:
BDSupEdit Ver 0.41

Old Version:
BDSupEdit Ver 0.1
BDSupEdit Ver 0.2
BDSupEdit Ver 0.3
BDSupEdit Ver 0.4

Change log:

BDSupEdit Version 0.41
- Hopefully fixed the framerate issue in scenarist xml file. It works on my end.
- Fixed: Another coordinate issue with trimmed image.

BDSupEdit Version 0.4
- Added more code to ensure incomplete subtitle frames are skipped.
- Fixed: A subtitle counter wasnt set properly, not sure it even has any effect, but now its added correctly.
- Fixed: Framerate wasnt set properly when exporting subtitle stream.

BDSupEdit Version 0.3
- Major overall 'code upgrade'.
- Updated the RLE Encoder, it has a few flaws when dealing with sudden streams, you would know when it didnt work!!!
- Updated the Sup parsing code, it should now work alot more stable and accept more streams.
- Updated Color Conversion, it now uses the ITUR-709-5, should I use ITUR-601-5 for 720x480/576 or is it still HD as the source is Bluray ? let me know.
- Parsing Scenarist XML file failed parsing attribute 'forced'. Supread scenarist export uses 'forced', where other use 'Forced',made a check to support both format.
- Fixed the time problem when reading Scenarist XML file.
- Fixed the coordinate problem when importing trimmed image.
- Removed "Join linked subs" as its done internal now.
- Changed "Options" to "Export Options" as they only apply when exporting.
- Changed TFileStream to TMemoryStream, should make loading and saving faster.
- Cosmetic change.

BDSupEdit Version 0.2
- Fixed a bug in the RLE Encoder that occured in rare cases.
- Optimized the resize quality.
- Improved BDsub loading, it should now handle errors better.
- Added support for loading Scenarist XML files - Experimental, so check for errors.
- Forgot to add "Thanks to" to Pelican9 for help on the RLE decoding and 0xdeadbeef for help on the PTS/DTS calculation.
- Cosmetic change.


BDSupEdit Version 0.1
- First public version

[Adub]

Wow, I think you just made tons of people's day. The downscaling capabilities have been missing in almost every tool yet, so this is fantastic for people making 720p backups with subtitles.

I haven't tested yet, but I may later once I have some time.

[avivahl]

How does it differ from BDSup2Sub? Just another option for us users?

[GZZ]

it differ in that way, that my program export to bluray subtitles, its not the same as DVD subtitles. IDX/SUB are in DVD resolution, where Bluray subtitles used on bluray support higher resolutions and it can be used on BD5/BD9 movies, which contains the bluray structure. So its not the same.

Also DVD subtitles only support 4 colors I think, where bluray support up to 256 colors including alpha values for transparent areas.

But at the moment only IDX/SUB can be muxed into mkv movies, so you wont get anything useful out of my program, if your target is mkv, its only useful for BD5/9.

[0xdeadbeef]

Originally Posted by GZZ

it differ in that way, that my program export to bluray subtitles[...]
So its not the same.

Maybe you should have a closer look.

[GZZ]

I might have missed that one, thanks.

[rica]

Perfect; that is what i've been looking for.
Pelican was working on it but he is not come back from Amazon jungles yet.
I resized an 1080 sup to 720 as sup.
I gave it a go with ulf's script before but the output file was not sup.
So, some notes and feature request:
I tried BDSupEdit with an HD-DVD sup; so i had to make it first BD compliant sup via SupRead.
The first feature request.

The second one is PAL speedup feature.
Here is what kind of torture to me:
http://forum.doom9.org/showthread.ph...00#post1181900

Thanks bro.

A sample (FF2 HD-DVD) converted to 720p BD. (i muxed eac3 which is not compliant with BD but no matter to me; i watch them on HTPC.)

http://www.sendspace.com/file/rpdxws

[GZZ]

Made an Update. Check my first post for changed.

Also, take a look at Pelican9's tool SUPread. SUPread can export to PNG's and Scenarist BDN XML file. The PNG's are not trimmed though. SUPread always export 1920x1080 PNG's.

You should check the new version out.

[rica]

Originally Posted by GZZ

Made an Update. Check my first post for changed.



You should check the new version out.

Thanks a lot, i'll give it a go asap.

[laserfan]

Thanks for looking! FYI I just tried to demux the subtitle from the HD DVD using tsMuxeR, and it wouldn't do it ("Some tracks not recognized. This tracks was ignored.." sic). In eac3to's log it said "4: Subtitle (DVD), English, "for the Hearing Impaired" and on import to SUPread (as you will see) it says "D:\video\englishHDDVD.sup loading -- HD DVD (DVD) subtitle found." So they seem to think (correctly I guess) that it's a "DVD" subtitle and not hi-def.

But like I said in my first post, the SUPread-converted output doesn't show-up on playback, only after import/export w/your tool does it finally appear. It just seems to me that maybe as your tool appears to be interpreting it as a 1920x1080 sup then it is re-sizing it un-necessarily.

[Ulf]

Thanks GZZ for taking up the work of implementing Scenarist XML import!

Here is what I have found out so far for BDSupEdit Ver 0.2:

1. I first got the error "Could not convert variant of type (Null) into type (Boolean)". This was resolved by changing all occurance of Forced="False"> to forced="False">.

2. The timings were incorrect in the produced sup file. The XML file had FrameRate="23.976". The timings would have been correct for FrameRate="24". BDSupEdit produces the same timings for both cases. The timings in a BDN XML file are really frame counts. So in the case where fps=23.976, the timings are given in the BDN XML file as if the frame rate was 24 fps. In the cases where the frame rates are 23.976, 29.97 or 59.94 fps, you have to multiply the times Ver 0.2 produces by a factor of 1.001.

3. Subtitle bitmaps that are already trimmed are not handled correctly (as the example in post #16). They will end up in the upper left corner of the bitmap. BDSupEdit seems to ignore the X and Y coordinate placement information in the XML file.

Overall, this is a very good and promising start. The fact that BDSupEdit trims the bitmaps is a nice feature. Keep up the good work!

[GZZ]

1. I first got the error "Could not convert variant of type (Null) into type (Boolean)". This was resolved by changing all occurance of Forced="False"> to forced="False">.

I see the problem in my XML reader. Will fix this in next version.

2. The timings were incorrect in the produced sup file. The XML file had FrameRate="23.976". The timings would have been correct for FrameRate="24". BDSupEdit produces the same timings for both cases. The timings in a BDN XML file are really frame counts. So in the case where fps=23.976, the timings are given in the BDN XML file as if the frame rate was 24 fps. In the cases where the frame rates are 23.976, 29.97 or 59.94 fps, you have to multiply the times Ver 0.2 produces by a factor of 1.001.

I used the timecode without converting it, so this is a clear issue from my side. I will fix this.

3. Subtitle bitmaps that are already trimmed are not handled correctly (as the example in post #16). They will end up in the upper right corner of the bitmap. BDSupEdit seems to ignore the X and Y coordinate placement information in the XML file.

I added a trimming function, because supread always output 1920x1080 png image, so there is properly an error when reading already trimmed image. I will also fix this.

Thanks alot for all the info.

[Ulf]

GZZ!

The syntax for the timings in a BDN XML file (e.g. 01:00:00:12) is:
HH:MM:SS:FF, where FF is frames.
If FrameRate=24 the above timing translates to 3600.5 s.
For FrameRate=23.976 it translates to 3600.5*1.001 s

[Daiz]

Finally a free program that can convert BDN XML + 8-bit PNGs to Blu-ray compatible SUPs I've been waiting for this!

A request, can you add commandline switches? something like BDSupEdit input.sup/.xml [options, like -resize 1280x720 -method lanczos] output.sup would be very nice.

[OptimusX]

These are wonderful developments...MaestroSBT with BDN/xml ability + BDSupEdit = just what I've been waiting for! Thanks to all for sharing your work!

[GZZ]

Posted a new version that hopefully will fix alot of issues as I spend so much time making it overall better. Check my first post for change. Also please donate a coin or two. :P

[GZZ]

Made another update, its a pure bugfix version. Hopefully I didnt mis other things.

[Ulf]

Originally Posted by GZZ

Made another update, its a pure bugfix version. Hopefully I didnt mis other things.

Sorry, but I cant import (otherwise fully functional) XML's with ver 0.4.

I get the error:

Cant parse Scenarist XML file.
'23,976' is not a valid floating point value

BDSupEdit might refer to this line in the XML file:

   <Format VideoFormat="720p" FrameRate="23.976" DropFrame="False"/>

but it's perfectly valid.
I have also tried with Scenarist exports from SUPRead with the same results.

[GZZ]

thats odd I just tested it using a Supread output and with 23,976 and 23.976 and it worked just fine. Maybe I did mis something. Will do a check.

[GZZ]

Added a new version, I changed the framerate detection a bit, might have had issue, but not sure how. Tryout version 0.41 and if it dosnt work, please post your xml file.