BDSup2Sub - convert and tweak bitmap subtitle streams (VobSub,BD-SUP,BDN XML,HD-SUP)

[0xdeadbeef]

The online help says: "/cropy:<n> crop the upper and lower n lines - default: 0"

Then again, you could also open the "move all captions" dialog.

[ps auxw]

Could you add support for two Graphics in a single Event for BDN XML input? This would be quite useful for animated subtitles, since with big images the Presentation Graphics buffer can overflow. Using two smaller images, which still cover the subtitles, avoids this.

References:
http://forum.doom9.org/showpost.php?p=1321592&postcount=81
http://forum.doom9.org/showpost.php?p=1323369&postcount=91

Example:

<?xml version="1.0" encoding="UTF-8"?>
<BDN Version="0.93" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="BD-03-006-0093b BDN File Format.xsd">
<Description>
<Name Title="Undefined" Content=""/>
<Language Code="und"/>
<Format VideoFormat="720p" FrameRate="23.976" DropFrame="false"/>
<Events LastEventOutTC="00:00:53:19" FirstEventInTC="00:00:53:16"
ContentInTC="00:00:00:00" ContentOutTC="00:01:02:12" NumberofEvents="3" Type="Graphic"/>
</Description>
<Events>
<Event Forced="False" InTC="00:00:53:16" OutTC="00:00:53:17">
<Graphic Width="456" Height="75" X="139" Y="621">00001288_0.png</Graphic>
<Graphic Width="405" Height="167" X="759" Y="176">00001288_1.png</Graphic>
</Event>
<Event Forced="False" InTC="00:00:53:17" OutTC="00:00:53:18">
<Graphic Width="456" Height="75" X="139" Y="621">00001289_0.png</Graphic>
<Graphic Width="404" Height="167" X="759" Y="176">00001289_1.png</Graphic>
</Event>
<Event Forced="False" InTC="00:00:53:18" OutTC="00:00:53:19">
<Graphic Width="456" Height="75" X="139" Y="621">00001290_0.png</Graphic>
<Graphic Width="404" Height="167" X="759" Y="176">00001290_1.png</Graphic>
</Event>
</Events>
</BDN>

[0xdeadbeef]

Could you add support for two Graphics in a single Event for BDN XML input?
Short answer:
No!

Long answer:

I could add support for multiple pictures per frame to the BDN import, but internally, there will be (most probably) always only one picture due to the nature of the internal representation, to allow export to any other format and to not mess with the move/crop features. So when converting from XML to XML or whatever, all pictures of one frame will be merged to one.
Besides, implementation for PNGs using an 8bit palette would be a little tricky and "keep palette" would be impossible for different palettes.

This would be quite useful for animated subtitles, since with big images the Presentation Graphics buffer can overflow. Using two smaller images, which still cover the subtitles, avoids this.
I severely doubt this. The decoded object buffer for PGS objects is 4MB in size by definition. Since an 8bit palette mode is used for PGS, this means that a picture 1920*1080 in size fits twice in the buffer. So it is simply impossible to get an overflow there with only one composition object within an epoch.

IMHO the wish for having two composition object per frame is based on wrong assumptions and the way I could implement it without breaking the whole program would create the very same BD-SUP stream.

[ps auxw]

I severely doubt this. The decoded object buffer for PGS objects is 4MB in size by definition. Since an 8bit palette mode is used for PGS, this means that a picture 1920*1080 in size fits twice in the buffer. So it is simply impossible to get an overflow there with only one composition object within an epoch.

As much as I would like it, if this was true, it isn't. If you read the avs2bdnxml thread (http://forum.doom9.org/showthread.php?t=146493) you will find that Oleg Rode had trouble with flickering subtitles. Later PHD_1976 tried muxing these subtitles with Scenarist, which reported overflows (http://forum.doom9.org/showpost.php?p=1321154&postcount=69). After cutting down on image size, so no overflows occured, flickering stopped. It seems graphics are kept in buffer longer than should be necessary.

(Wait, looking at it, it is not the PGS buffer, that overflows, but the Decoded Object buffer, sorry.)

[0xdeadbeef]

As I said: while this is a nice theory this is technically impossible since even a full screen picture per epoch only fills half of the 4MB.

[ps auxw]

Maybe you have another way to explain that:
Subs were flickering. Scenarist complained about buffer overflow. Splitting the subs shut up Scenarist and got rid of flickering.

Since automatic splitting requires some ugly calculations, I'd be glad to get rid of it again, so another way to solve the problem would be more than welcome.

[Oleg Rode]

a full screen picture per epoch only fills half of the 4MB.
OK, can you help me? I got colorful and beautiful subs (xml+png). BDSup2Sub perfectly eats them. I can accept a little loss of quality in my subs. So, what settings do I need to set in your program to produce Blu-Ray standard compatible subs? I do something wrong and I receive flickering on big objects - especially from 00001288_0.png to 00001483_0.png

Here is a xml+png subtitles pack.
http://rapidshare.com/files/278292300/Valkyria.zip.html

Sorry for my English

[0xdeadbeef]

Firstly, you should rethink the idea of "Blu-Ray standard compatible" (in bold print!) subtitles. It's the authoring tool that is responsible for creating BD compliant streams in the end and only the authoring tool can e.g. guarantee bandwidth limits.

Unfortunately, since some muddlehead decided to leave all the DTS/PTS info from the original multiplexed stream in the SUP files, instead of invalidating or removing it as its the case for HD-DVD and DVD subtitle formats, current free multiplexers seem to assume that the information in the SUP is always valid. Which is a bold assumption to say the least.

This makes the BD-SUP (PGS) format an even more complex beast since in addition to the PGS bells and whistles, it also contains an awful amount of DTS and PTS time stamps which have to consider how long decoding of a composition object takes or how long it takes to render an object. While BDSUp2Sub tries to calculate all of these time stamps to my best knowledge, there is absolutely no checking done if e.g. the created PGS stream hits the bandwidth limits of a Blu-Ray or if there are too many frames to be rendered in a too short amount of time for the graphics processor of a standalone. I must admit that I somewhat doubt this is the case, but then again if you want to display a new 256 color near fullscreen picture every frame, chances are it is.

Apart from this, BDSup2Sub was created to convert typical simple subtitles, not to create fancy animations. It creates the most primitive type of epoch, but doesn't make any use of more advanced PGS features as palette and cropping animations, multiple windows or multiple composition objects per window. All of these features are of course also used to save bandwidth and distribute it more efficiently.

Anyway, chances are that the flickering you observe is caused by simpler causes. E.g. time gaps of a frame due to rounding errors when converting from/to the weird BDN time format. Yet it's also possible that the simple epoch format used by BDSup2Sub (and any other free tool creating BD-SUP format AFAIK) is just not the correct choice for animated subtitles.

Which brings us back to the original request: as far as I can tell, the only benefit of two composition objects per epoch would be a slightly reduced decoding and rendering time. Since these times are typically pretty short, this could only lead to problems if you're really pushing the PGS format to its limits by e.g. using large palettes and updating images at very high frequency.
E.g. the pixel decoding rate is 128e6 bit/s or 16 Million pixels per second. At 24p, this means that 667334 8bit pixels can be decoded per frame (if I didn't make any dumb calculation error). Unfortunately, this is quite a simplification though since also clearing of the screen buffer etc. has to be taken into account.
Anyway, even if saving a little bit of time would really help in some cases, it surely wouldn't fix the issue itself.

[EDIT]
Ok, I had a look at the sample. The problem is most probably really the combination of fading and large images. Firstly, fading in/out is not supposed to be done this way in any subtitle format since this cost too much bandwidth and needs too many updates in a too short amount of time for the graphics processor. Instead only the palette should be updated. However AFAIK there is currently no free tool chain available that will create BD-SUPs with palette animations. Also it would be very difficult to reverse engineer a palette fade from analyzing images, especially if they are truecolor ARGB images. Instead the fade would have to be defined in the XML format (e.g. alpha start value, alpha end value, fade period). Yet I dunno if there are even keywords defined for this.
Splitting the image into two composition objects would maybe really help in this case, yet the main problem is this brute force fading approach.

[deank]

I posted a week ago in easySUP's thread, but I'll repost here again:


edit: I also changed the default 'merge' and 'min display' times of bdsup2sub, so probably it will cause more smooth processing of animated subtitles and no flickering. Still I had no time to test it yet.

edit2: Ok, so I gave it a try with ASS subtitles uploaded by Oleg Rode. There is no flickering and subtitles show and disappear smoothly (fade in/fade out) with 23.976fps 1280x720 source. I was testing on PAL PS3 (60GB model) with firmware 3.00.

TMT also plays these fade in/out 'animation' just fine.

[0xdeadbeef]

Well, maybe there is no problem at all, but theoretically speaking: a software player running even at a not so fast PC will never have problems to render some subtitles in time. On a standalone things might look different.

[deank]

I agree... and I agree more about PGSs were not supposed to be used for 'fancy' animations in the first place.

I wish one of you gifted guys had more time to take a closer look to IGS... (not that there is a free-tool to mux them into a menu m2ts file, but still).

Dean

[0xdeadbeef]

I agree... and I agree more about PGSs were not supposed to be used for 'fancy' animations in the first place.
Well, PGS supports things like cropping and palette animations. So fade ins/outs are possible, but simulating this by quickly drawing images with modified alpha is nothing PGS is meant for.

I wish one of you gifted guys had more time to take a closer look to IGS... (not that there is a free-tool to mux them into a menu m2ts file, but still).Dean
Dunno if I'm one of these gifted guys ;) What are you then?
Well, the basic decoding/drawing stuff is very similar to PGS, but the interactivity makes everything much more complicated. Besides: IGS can't be simply converted to/from something else. So what would the input/output be?

[deank]

Yes, you're one of the gifted guys for sure! :)

And about IGS... You have:

input:

* Image (active, inactive, action-state)
* Coordiantes in selected plane (1920x1080)
* Actions, associated with active/action states (ordinary navigational commands, used in movieobject.bdmv)

output:

Elementary stream, describing RLE encoded navigational graphics + palette with their attributes (x, y, actions) (max 15 per menu page, tho each page can have multiple 'sub-pages' of IG elements)

Dean

[0xdeadbeef]

I meant which input format for a command line tool to create an IGS stream or what output format to convert an IGS stream to. Creating a full featured IGS WYSIWYG editor is surely beyond the scope of any freeware tool.

[deank]

Okay, then a CLI can handle creation of IGS by accepting a bunch of PNGs/BMPs (like max 15 of them) as input files, reserving space for navigational commands and outputting the elementary stream.

Sure it seams simple, but there is no tool that can do it. Not to say that there is no muxer to mux the IGS (at least at the moment - but I'll think of something).

Dean

[deank]

Just a suggestion for the GUI and the drop-down with resolutions:

Since you know the bottom right x,y of each subpicture, would you add a semi-detection of the imported .sup so it won't always default to 720x576?

(if y is the bottom right Y coordinate)

Something simple as:

default res=480

(checks performed in this exact order)
y>480 - res=576
y>576 - res=720
y>720 - res=1080

It will be useless to use the width but it may help if bdsup2sub detects widths >720 or >1280 to refine the decisions after y coordinate is processed.

[twazerty]

Hello

After some time I decided to use your app in AVCHDCoder. But i am not been able to hook up BDSub2Sub to AVCHDCoder which is also written in java.

I was unable to find the starting point when I add your jar as an external Library. I cannot figure out how to convert a pgs to pgs. (Downscaling)

When I use the commandline version I get other problems. Because you wrapped it as a jar I get the following problems:
Because your commandline gives no information on when it is ready I am unable to detect when the conversion is complete. (BDSub2Sub converts but no progress information)
Techniques like looping and see if the filesize changes doesn't work.

When I wrap you jar into an exe I am also unable to point the main class. The gui shows up with the exe but the commandline doesn't work ('"F:\NetBeansProjects\AVCHDCoder\Tools\BDSup2Sub\BDSup2Sub.exe"' is not recogniz
ed as an internal or external command,
operable program or batch file.)

Maybe some problems are related to the fact that you placed some files in the default package instead of a package. (Always put java files in packages).

As far as my knowledge goes I don't know a solution. Maybe you can help me?

I do have an idea. You can pack your jar (because you have the source) into an exe file as Command Line application. (Launch4j) This way you can use System.out.println() to deliver progress information. Now you also don't have the java -jar problem on 64 bit Vista/7 (Know problem, you have to manually point to javaw in order to use the commandline)

Thanx!

[0xdeadbeef]

@Dean:
IMHO, there is no way to determinate the target resolution, as it's a user choice. How would I know from looking at the source (which has a known and fixed resolution) which target resolution the user wants to select??? I could maybe make the last choice persistent or add a command line option "/res:keep" (just like for fps), but that's about it.
Or maybe I didn't really understand your request or maybe it's just too late right now.

@twazerty:
The best way to use BDSup2Sub from another Java app would be to use the whole JAR as a library. Then you can import functions from the BDSup2Sub classes like from any other library, e.g.

import deadbeef.SupTools.Core;
import deadbeef.SupTools.CoreException;
import deadbeef.Tools.Props;
import deadbeef.Tools.ToolBox;


There's JavaDoc for all important Core/Tools classes embedded in the JAR, so you can even integrate the JAR into the Eclipse help system and get online help and code completion. You just need to add the JAR under "Java Build Path->Libraries" and then edit "JavaDoc location" to "JavaDoc in archive, Worspace file" and set the path to the Jar.

This approach is used by "ToNMT UI" AFAIK.

If you need help, I could create an example, but probably not before Tuesday.

[deank]

@Dean:
IMHO, there is no way to determinate the target resolution, as it's a user choice. How would I know from looking at the source (which has a known and fixed resolution) which target resolution the user wants to select???

:-P

What I meant to say (and got confused) is to auto-select the source resolution in the drop-down list when loading a sup file and not always default to 720x576. It is not important at all anyway...

I just started looking at .sup format yesterday with an idea for a small cli tool for resizing/repositioning...

[0xdeadbeef]

Hm, for SUP/IFO, the resolution is read from the IFO as far as I remember - so it's not fixed to PAL, but maybe there's a bug. Also most probably it defaults to PAL if the info from the IFO is inconsistent or missing.
Problem is that I only own PAL DVDs. I'll try to have a look at this with an NTSC sample later this week when I have time.

Or are you suggesting to use the (DVD)-SUP format for higher resolutions? That is a little problematic as - in contrary to SUB/IDX - there is no way to define the resolution explicitly. The IFO only has predefined values for standard resolutions.

[deank]

No, I was talking about BD SUP files...

I created a small .cmd file and associated .sup files with it so I can double click a bd sup file and open it in bdsup2sub:

java -jar d:\multiavchd\tools\bdsup2sub.jar %1

But then everytime I need to manually select the resolution of the input file.

:-)

[twazerty]

....

There's JavaDoc for all important Core/Tools classes embedded in the JAR, so you can even integrate the JAR into the Eclipse help system and get online help and code completion. You just need to add the JAR under "Java Build Path->Libraries" and then edit "JavaDoc location" to "JavaDoc in archive, Worspace file" and set the path to the Jar.

This approach is used by "ToNMT UI" AFAIK.

If you need help, I could create an example, but probably not before Tuesday.

A sample would be helpful. :)

[0xdeadbeef]

But then everytime I need to manually select the resolution of the input file.
No, you need to manually confirm the conversion options. Among them is the target resolution. The resolution of the input file can't be selected, as it's read from the BD-SUP.

A sample would be helpful. :)
Hope this helps:
http://www.sendspace.com/file/80y622

This is basically a version from BDSup2Sub which consists only of one base class which uses all the functionality from the JAR. This is the whole Eclipse project folder, but maybe you need to change the properties after moving it to another folder.

[deank]

I don't want to waste your time on the subject :)

What I was trying to say is that when I load a file in BDsup2sub and I'm presented with a window to chose resolution/framerate and other options, but the default (target) resolution is always 720x576.

I was just asking if you can make it honor the input BD-SUP resolution (like you do with the framerate) and have it as default.

[0xdeadbeef]

That's why I suggested:

I could maybe make the last choice persistent or add a command line option "/res:keep" (just like for fps), but that's about it.

[deank]

Yes :) although you can implement /res:keep as default when using the GUI, instead of explicitly using the option.

[0xdeadbeef]

Honestly, the main reason for the PAL default is that I use BDSup2Sub only to convert BD SUPs to PAL SUB/IDX. So it's unlikely that I will simply default to the input resolution for the target.
Then again, there are probably more clever ways to handle this. I'll try to think of something when I have a little more time. Maybe next weekend or so.

[saint-francis]

I too agree that it would be nice to see BDSup2Sub remembering more of my previous selections upon restart: such as resolution and location of source files. I almost never use it for anything aside from converting BD Sup's to 720p sub/idx so it would be nice if the tool remembered that. After some certain point (I can't recall which version) BDSup2Sub defaults to (remembers?) the language I normally select, English, which has been much appreciated.

[0xdeadbeef]

I too agree that it would be nice to see BDSup2Sub remembering more of my previous selections upon restart: such as resolution and location of source files.
It should remember the last directory used for importing/exporting files since quite a long time. Works for me.
For the conversion options (like target resolution, target fps, scaleX/Y), I guess I will implement a "Use as default" and "Restore factory settings" button and additionally add the "/res:keep" command line option.


After some certain point (I can't recall which version) BDSup2Sub defaults to (remembers?) the language I normally select, English, which has been much appreciated.
This is probably a misconception. BDSup2Sub reads the language from the input stream (if this is possible) and uses it as default. If the stream doesn't contain any language information (e.g. BD-SUP), it tries to determine the language by looking at the name of the input stream. If it contains e.g. "English", it defaults to English.

[Kratus]

Hello there,
I discovered your awesome tool a few weeks ago.
Thumbs up for your great work an level of support!:thanks:
I use it to move subtites into the 2.35 AR area since I use a scaler to view 2.35 movies to avoid black borders on top and bottom of my screen.
Because it is painful to demux, move subs, remux etc, manually, I wanted to do some automation, the way Clown BD makes it (EAC3->BDSup2Sub->TsMuxeR), using CLI in a batch file.

But (there is allways a but :) ) I noticed a strange behaviour:
Here is an example with the "Largo Winch" French BR:

1. The GUI way:
- the original sub ist hosted here: http://www.sendspace.com/file/2r8r1f
- using the GUI it works flawlesly, with following parameters:
http://img16.imageshack.us/img16/2089/guiparameters.jpg
- it ends up with a correctly processed file, sampled here: http://www.sendspace.com/file/nkgu7n

The problem comes up when I want to use CLI-operation for doing the same task.

2. The CLI way:
- I call BDSup2SUb using the following command-line:
"C:\Program Files\Java\jre6\bin\java.exe" -Xmx256m -jar "D:\BDSup2Sub\BDSup2Sub.JAR" "'D:\HD-RIP\Largo Winch\*.sup' 'D:\HD-RIP\Largo Winch\*.sup' /res:1080 /movin:2.35,24 /verbatim+" >"D:\HD-RIP\Largo Winch\BDSup2SubLog.log"
- and I end up with a corrupted file sampled here: http://www.sendspace.com/file/32zz0p
where the bitmaps appear to have disapeared starting at sub nr 59. :confused:
http://img8.imageshack.us/img8/4315/frame59.jpg
- I hosted the log file here: http://www.sendspace.com/file/tz0rlk

Did I something wrong?
Or is this an issue in BDSup2Sub CLI-support?

[deank]

I tried your sample and the output is not corrupted - all captions are moved properly:


java -jar BDSup2Sub.jar "Sous titres_7_French_original-demuxed_by_EAC3.sup" output.sup /res:1080 /fps:keep /movin:2.4,10


I'd suggest you to use the proper name for your input and output subtitle files, instead of *.sup wildcard!

[Kratus]

You are right!

I tried this (because I need to keep the wildcards):
java -jar d:\BDSup2Sub\BDSup2Sub.jar "*.sup" "output\*.sup" /res:1080 /fps:keep /movin:2.35,24and it worked properly

whyle this one:
java -jar d:\BDSup2Sub\BDSup2Sub.jar "*.sup" "*.sup" /res:1080 /fps:keep /movin:2.35,24did not.

Thanks a lot, Deank.

[0xdeadbeef]

I don't want to be picky, but indeed all of your CLI examples are wrong:

"'D:\HD-RIP\Largo Winch\*.sup' 'D:\HD-RIP\Largo Winch\*.sup' /res:1080 /movin:2.35,24 /verbatim+"
You're using the same path and name for input and output which begs for trouble. I'm kinda surprised that this works at all. I thought I had at least checked the identity of source and target.

"*.sup" "output\*.sup" /res:1080 /fps:keep /movin:2.35,24
This is wrong, because it doesn't enclose the whole parameter string in double quotes although wildcards are used.

"*.sup" "*.sup" /res:1080 /fps:keep /movin:2.35,24
This is double wrong since it combines same name/path for source and target with the wrong use of double quotes.

A correct way to do this would be:
java -jar d:\BDSup2Sub\BDSup2Sub.jar "*.sup *_exp.sup /res:1080 /fps:keep /movin:2.35,24"

Still, you must take care of course that the target file(s) can't have the same name(s) as one of the sources and thus overwrite it/them.
Using a different folder for the output is the safest solution of course, but it's not needed if you take care.

Note that double quotes around all parameters are needed if wildcards are used. Single quotes are only needed, if parameters within the double quotes use spaces. It doesn't matter if the filenames that are matched by the wildcards contain spaces or not.

Sample with spaces in parameters:
java -jar d:\BDSup2Sub\BDSup2Sub.jar "*.sup '* export.sup' /res:1080 /fps:keep /movin:2.35,24"

[Kratus]

Thank you for this quick and accurate answer, 0xdeadbeef.:thanks:
I must admit that this quotes-story is a little tricky.

[0xdeadbeef]

I must admit that this quotes-story is a little tricky.
Admittedly. Unfortunately, there's nothing I can do about this as it's a restriction of the Java launcher.

[0xdeadbeef]

Only a GUI update and one CLI option. Not too much testing done.

07.10.2009: 3.9.7 -> 3.9.8

Changed: reworked dialog for conversion options, added: store/reset defaults, stored defaults are automatically loaded in GUI mode
Changed: added "/res:keep" CLI switch to keep the resolution by default. Note that CLI switches overwrite GUI defaults.
Changed: appending "_exp" to the save file name is no longer done repeatedly but only once.

[radius]

Hi,

I needed something to extract forced subs and it's just perfect for what I needed :)
Btw could you please add an option to batch add / remove the "forced" flag ?

Thanks

[0xdeadbeef]

Hm, while I don't really understand why you would need this feature, I guess I could implement it. I won't have much time before the weekend though. Some hints why you need this?

[radius]

I'm muxing Blu-Ray stuff without menus and playing it on a PS3,
the problem is,
when using the PS3 menu for navigation / options you can't manually select a subtitle track without enabling it,
and that is what's required for a forced subtitle to show without the non forced ones,

actually to use forced subtitles I edit my Blu-Ray to select the subtitle track (but not enabling it) on the first playback,
but if I change the selected track on the PS3 then I can't go back and select the forced subtitles only (as you can't selected the track without enabling it).
now I'm using your nice tool :) to extract the forced subtitles as a new track,
it's no big deal but my request is just to say as I won't need the forced flag in any of the subtitles anymore,
it's cleaner to have no forced flags (and because I'm maniac ^^)

[mrr19121970]

@0xdeadbeef

Did you see Slumdog? The forced subs have the palette changed. Is this correct? See sample:

http://clownbd.com/Slumdog.jpg

http://clownbd.com/Subtitles_10_German.sup

[0xdeadbeef]

Did you see Slumdog? The forced subs have the palette changed. Is this correct? See sample:

http://clownbd.com/slumdog.jpg

http://clownbd.com/Subtitles_10_German.sup

The link to the picture ("http://clownbd.com/slumdog.jpg") seems to be invalid. And when I load the SUP into BDSup2Sub and choose a non-DVD destination, the result looks pretty much perfect:

http://www9.picfront.org/picture/9aSTRGpZR/thb/test.png (http://picfront.de/d/9aSTRGpZR/test.png)

So I'm a little puzzled what the problem is supposed to be.

[mrr19121970]

Strange http://clownbd.com/slumdog.jpg fails, but http://clownbd.com/Slumdog.jpg works.

I'm using Windows7 x64.

[0xdeadbeef]

Well, as I said, the colors look ok for any non-DVD mode. They look terrible for DVD modes of course but what did you expect when you convert a photo to 4 colors?

[mrr19121970]

OK, I changed the Output format from SUB/IDX to SUP(BD) and the colours came back. I didn't appreciate that, just saw the filesize of
3019324 bytes before and 2802220 bytes after and then opened in the GUI and assumed the palette got lost.

[Ryu77]

Is there no way to tell if a subtitle stream has forced sections? I thought this tool might be able to do this as it can detect forced subtitles.

However, I am referring to subtitles that only have sections that are flagged forced, not the entire subtitle stream.

For example, an English subtitle stream that only comes on when foreign languages are spoken.

[0xdeadbeef]

During the import, the last line that is printed to the console is the number of forced subtitles:

e.g.
Detected 24 forced captions.

[Ryu77]

During the import, the last line that is printed to the console is the number of forced subtitles:

e.g.
Detected 24 forced captions.

Thank You! I can't believe I missed it. Now I can finally remove the guesswork and pre-screening before burning. :cool:

[0xdeadbeef]

I answer this here to don't mess the other thread:


2 questions regarding BDSup2Sub:
1. I've been playing with the colors a bit, but I can't seem to make it work. What I like, is change the white of the letters to a gray-er version. I have a Plasma tv, and bright white burns in very quickly.
If you load a SUB/IDX (or SUP/IFO) file, the menu item "Edit->Edit imported DVD palette" becomes enabled. If you select it, you can edit the 16 color palette. E.g. if you change white to light grey, it will also change in the (source and) target view.


2. If I select 720p (instead of Pal), the N200 mediaplayer shows the subtitles for about 5-10 secs, then the tv turns green-ish and (while you still hear the movie playing) evt returns to the main menu (thus stop playing). This could be a N200 issue though. Too bad, because 720p seems to give me sharper titles...
SUB/IDX was created with only PAL and NTSC in mind and if a player claims to support SUB/IDX, it doesn't mean that it does in higher resolutions. So yes, this is most probably an issue of the player.
BTW: I assume the video stream is in 720p, too? If not, you can't really expect this to work. You an use BDSup2Subs scaling features though to achieve a similar result. E.g. when I convert 1080p BDs to DVD, I usually slightly increase the size of the subtitles by using scaling factors of e.g. 1.2.

[paulal]

thx for redirecting (and the info)... I thought so much, but got excited in the process :)

- reg. colors: I did experiment with that, saw the colors change but no luck when played. I'll do some more work on this...
- 720p: bingo, logical and true: my movies are pal (or ntsc), not 720p. Sure, I'm asking too much :) I've got to stop watching those star trek movies...

pol

[paulal]

update on the colors !

I did some more experimenting, but no change. The N200 keeps it in white and black (if I load the subtitle in SC again, the colors have changed). So I assume that the N200 does not support colored subtitles, and substitute his own color palette.

maybe one day...
cheers,
pol

ps: I've uploaded "my experience" here: http://www.megaupload.com/?d=AXH8OITX
(if you are not happy with this or like to add your comments, 0xdeadbeef, just let me know)