easySUP/goSUP - an easy way to create BD SUP, BDN XML/PNG & DVD SUB with SRT/ASS/SUB

[nautilus7]

I see. Thanks for your answer.

[skycore]

Anyone?

Maybe you can have a try of SupConverter (http://www.defsoft.com/supconverter.html), it supports the line space, shadow color and other features. Good luck!

[techstuff]

Hi

great apps
i'm trying to create DCP smpte SUB look like this https://dci.foxpico.com/basic/subtitle-test-v7/
is there a way to change the Format and background color in easySUP.

In 2K, for Scope (2.39:1) presentation 2048x858 pixels of the imager is used
In 2K, for Flat (1.85:1) presentation 1998x1080 pixels of the imager is used
In 4K, for Scope (2.39:1) presentation 4096x1716 pixels of the imager is used
In 4K, for Flat (1.85:1) presentation 3996x2160 pixels of the imager is used

what i need is free format and color change as output i need the XML+PNG

thanks for your help

[gluegun]

Want to say THANK YOU Dean for such a great app (I just donated to you). EasySUP saved me from so much work. Now I can use Aegisup .ass formated subs and put them on Blu-rays. This is a much needed app because there are a lot of hard-working subtitlers who have done nice work on Blu-ray rips to .mkv and have the subs already formatted and positioned in Advanced SubStation Alpha format (.ass). This pretty much opens up a lot of Blu-rays to people who can now drop .ass subs in with easySUP.

[mariner]

Two questions:

1. What's the correct frame rate to use for standard interlaced 1080/59.94i video? 29.97 or 59.94?

2. Where can one download latest version of complete easySUP package dated 15th July 2010?

Many thanks.

[qknet]

I've been told by my friend about EasySUP and I like it a lot. Its vobsub outputs are the only idx/sub that I can get displayed by my hdplayer at 720p or 1080p resolution. Idx/sub made by text2vobsub can be displayed too, but the program does not support resolution higher than dvd. But I faced two issues. The first one is the generation speed, which is very slow, but I could wait before it is improved. The second is vobsub for 4:3 movies. When the vobsub is displayed, it is narrowed (and become very thin) to match with the width of 4:3 frame on a 16:9 TV.

I had no problem if the movie is in wide frame.

[lipithink]

I have some bluray movies on my hard disk and I am trying to add subtitles to them and then burn into bluray disks to be played on bluray players such as panasonic DMP-BDT310 or ps3 but i dont know what to do or can i use youre program or not.
i am so sorry because i searched this site and found nothing please help me

tanx

[Lyris]

Wondering if anyone can help me with a synchronization error. I'm trying to make subtitles for a 23.976fps Blu-ray Disc. The subs are in sync to start with, but slowly drift out over the duration of the film.

By comparing the timecodes in the input file (SRT format) vs the output (BDN XML), it's clear something is going wrong.
For example, the 700th and final subtitle in my SRT file is timed from 01:25:54,449 --> 01:25:56,440. In the XML output, it's timed from 01:25:49:08 until 01:25:51:06. A difference of about 5 seconds.

Why is it altering the timing in such a way?

[setarip_old]

@Lyris

Hi!

Without speculating as to how or why, it sounds like you should be using 24fps rather than 23.976fps, or vice versa...

[Lyris]

That would be my first guess too, but it's not the case. I've tried both and neither has the same timecode value as the input file.

[laserfan]

Have you tried simply making your .sup from the .srt using tsMuxeR?

[Lyris]

Not totally sure I understand - can tsMuxeR output a SUP file which could then be further processed?

The end usage is professional BD authoring; so if need be I can pay for Annotation Edit, but it's always worth exhausting all options :)

[laserfan]

tsMuxeR will (very quickly) create a .sup file that can be muxed into a .m2ts. Don't think it's pro quality but at least you can see if EasySUP is the culprit with your timing problems. I make english.srt files and then a subtitle.meta file that I edit as needed, e.g.

MUXOPT --no-pcr-on-video-pid --new-audio-pes --demux --vbr --vbv-len=500

#For 1.33 and 1.77 composition
S_TEXT/UTF8, "D:\video\english.srt",font-name="Aharoni",font-size=54,font-color=0x00D4D4D4,bottom-offset=36,font-border=1,text-align=center,video-width=1920,video-height=1080, fps=23.976, lang=eng

#For 1.85 composition
#S_TEXT/UTF8, "D:\video\english.srt",font-name="Aharoni",font-size=54,font-color=0x00D4D4D4,bottom-offset=48,font-border=1,text-align=center,video-width=1920,video-height=1080, fps=23.976, lang=eng

#For 2.40 composition
#S_TEXT/UTF8, "D:\video\english.srt",font-name="Aharoni",font-size=48,font-color=0x00D4D4D4,bottom-offset=154,font-border=1,text-align=center,video-width=1920,video-height=1080, fps=23.976, lang=eng

Then I have an SrtToSup.cmd that contains this:

"C:\Program Files (x86)\tsMuxeR\tsmuxer.exe" "D:\video\subtitle.meta" "D:\video"

Won't hurt to try. Wicked-fast compared to EasySUP iirc.

[Lyris]

I'll give that a shot. I also downloaded AVS2BDNXML and ran it manually - it produces the same timing errors.

I wonder if I could write an AutoHotKey script (that's the extent of my programming ability!) to write the subtitle script I need and just have this generate the PNGs...

[Lyris]

Well, I've found out that the XML output of SubtitleEdit has the correct timings: http://www.nikse.dk/SubtitleEdit

Unfortunately it writes the wrong PNGs; the authoring tool will not accept them.

But I was able to get things to mux by using easySUP's 8-bit PNGs and the XML from SubtitleEdit.

[TheSkiller]

I'm using easySUP to create subtitles for PAL DVD from an *.ass subtitle created with Aegisub. The subtitles come out really great, it allows great control over your DVD subtitles! :cool:
Thank you very much for making it possible to put such great subtitles on DVD (and Bluray) in an easy way using avs2bdnxml.

However there's one minor problem: I really need the subtitles that come out of easySUP to be uncropped, full frame (720x576). Currently they are always automatically cropped to the text area.
I saw that avs2bdnxml has a switch for that:
-a, --autocrop <integer> Automatically crop output. [on=1, off=0]

Would it be possible to include a checkbox for this in easySUP? :)

[Boulder]

Is there any way to check the properties of SUP files? I have a problem in which the subs created by goSUP seem to be positioned too high on the screen with bottom offset set to 60 when viewed on my TV (playback with Mede8er MED500X2) but appear fine on MPC-HC. What bothers me is that this problem started showing up only recently, and I'd like to compare working and non-working SUP files.

Actually I noticed one bug when testing various combinations: if you use bottom offset 0, it actually uses something else, at least according to the console output shown when AVSInfo is running.

[JonL]

goSup has been working fine, but now I get this error: "avsInfo.exe has stopped working".

Probably, it has something to do with Windows Update, because it always worked fine.

Does anyone know if there's a new version of avsInfo available?

[Rectal Prolapse]

JonL, a crashing AVSInfo likely means it cannot find AVISynth, or that AVISynth is crashing itself.

[Atlantis]

This is a great tool. Thank you very much. I finally found a tool that can read unicode srt and I tried them all. I have 2 questions.

What is the difference between Fast Mode and Full Frame.

When I create DVD SUB files, the result is always flagged as English. Possible to change the language tag?

[Pawpcorn]

Hi! Love your apps!!!
The GoSUP app has a flaw, where if you select 576i, you get a sup file in 480i format.
The easySUP works without this flaw.
Thanks again!:thanks:

[alfixdvd]

:None of the srt files (sub1, sub2) contained on rar file attached I can convert to sup.

When it finish analysis of lines/frames gives an error.

¿What's wrong?

¿Where easysup stores log?

TsMuxer can convert them :)

Thanks

[Conspicuous57]

I create subtitles without any errors using goSUP.
But I have a problem. While I am watching the whole movie I always see that there are some missing lines in every output. Does anyone experience the same?

http://imageshack.us/a/img694/896/easysup.png

[ps auxw]

Wondering if anyone can help me with a synchronization error. I'm trying to make subtitles for a 23.976fps Blu-ray Disc. The subs are in sync to start with, but slowly drift out over the duration of the film.

By comparing the timecodes in the input file (SRT format) vs the output (BDN XML), it's clear something is going wrong.
For example, the 700th and final subtitle in my SRT file is timed from 01:25:54,449 --> 01:25:56,440. In the XML output, it's timed from 01:25:49:08 until 01:25:51:06. A difference of about 5 seconds.

Why is it altering the timing in such a way?

I'll give that a shot. I also downloaded AVS2BDNXML and ran it manually - it produces the same timing errors.

Even though these posts are a little dated, I figure a short explanation might be in order. While I am, of course, not completely sure, to me it seems that what occurred here is a mix-up between drop frame timecodes and non-drop frame timecodes (http://forum.doom9.org/showthread.php?p=480776#post480776). The observed mismatch of timecodes corresponds exactly to the expected ratio of 107892/108000.

avs2bdnxml outputs non-drop frame timecodes. The XML files it produces are also marked as such, so a program importing them should, if necessary, be able to covert between the timecode encodings. A rough, visual comparison between these timecodes and regular realtime timecodes or drop frame timecodes from a source subtitle file will make it look like the timing was altered. In reality, just the way it is encoded differs, similar to the difference in representation between a decimal 10 and a hexadecimal 0xA.

[mariner]

Even though these posts are a little dated, I figure a short explanation might be in order. While I am, of course, not completely sure, to me it seems that what occurred here is a mix-up between drop frame timecodes and non-drop frame timecodes (http://forum.doom9.org/showthread.php?p=480776#post480776). The observed mismatch of timecodes corresponds exactly to the expected ratio of 107892/108000.

avs2bdnxml outputs non-drop frame timecodes. The XML files it produces are also marked as such, so a program importing them should, if necessary, be able to covert between the timecode encodings. A rough, visual comparison between these timecodes and regular realtime timecodes or drop frame timecodes from a source subtitle file will make it look like the timing was altered. In reality, just the way it is encoded differs, similar to the difference in representation between a decimal 10 and a hexadecimal 0xA.

Thanks for these helpful comments, ps auxw, but have to admit having a hard time following the convoluted reasoning in McPoodle's post..

1. Does it mean that xml file created by SubtitleEdit would result in timing error if processed by, say avs2bdnxml based applications?

2. Would you be kind enough to also take a look at the 24fps problem reported by picrade in this post?

http://forum.doom9.org/showpost.php?p=1451113&postcount=145
When you select frame rate of 24 in easySUP the resulting sup file has the frame rate of 23.976.
All other selections, 23.976, 25, 29.970, 50, 59.940, produce correct sup files.
(30 and 60 are not legal frame rates, are they?)

Naturally when muxing this sup file with a video with fps of 24, the subs go out of sync.
The solution above, frame rate conversion from 24 to 24 with bdsup2sub, simply resets the fps in the sup file to 24, without screwing the timings.

I did a BDN+XML, and in the XML file the frame rate was set to 23.976 even though on easySUP it was set to 24.
So maybe the problem is with avs2bdnxml.

Many thanks and best regards.

[mariner]

When you select frame rate of 24 in easySUP the resulting sup file has the frame rate of 23.976.
All other selections, 23.976, 25, 29.970, 50, 59.940, produce correct sup files.
(30 and 60 are not legal frame rates, are they?)

Naturally when muxing this sup file with a video with fps of 24, the subs go out of sync.
The solution above, frame rate conversion from 24 to 24 with bdsup2sub, simply resets the fps in the sup file to 24, without screwing the timings.


I did a BDN+XML, and in the XML file the frame rate was set to 23.976 even though on easySUP it was set to 24.
So maybe the problem is with avs2bdnxml.

It's unlikely to be a avs2bdnxml problem. Looking at the 24fps final xml, I guess Dean simply used 23.976 to feed avs2bdnxml and bdsup2sub at the second stage.

Your observation that bdsup2sub can be used to fix this problem was brilliant. In fact, one can start with 25fps and make use of the frame rate conversion feature of bdsup2sub, using 24fps for both source and target. This avoids the double 1000/1001 conversion (dropped frame?) and therefore smaller deviation from the original time code.

Looks like the same can be done for 23.976/59.940.

[ps auxw]

Late response, but...

1. Does it mean that xml file created by SubtitleEdit would result in timing error if processed by, say avs2bdnxml based applications?
As long as the flag signalling (non-)drop-frame time codes is respected by all applications used for processing, there shouldn't be any problems.

2. Would you be kind enough to also take a look at the 24fps problem reported by picrade in this post?

http://forum.doom9.org/showpost.php?p=1451113&postcount=145
I'm not quite sure what was going on there, especially since the post is very old. In the beginning there were some problems with how timecodes were handled, so it could be a case of that. Or maybe something else. It would be hard to track down at this point in time. I don't see anything in the current avs2bdnxml code that could lead to such behavior.

[mariner]

Late response, but...


As long as the flag signalling (non-)drop-frame time codes is respected by all applications used for processing, there shouldn't be any problems.


I'm not quite sure what was going on there, especially since the post is very old. In the beginning there were some problems with how timecodes were handled, so it could be a case of that. Or maybe something else. It would be hard to track down at this point in time. I don't see anything in the current avs2bdnxml code that could lead to such behavior.

Greetings ps auxw, thanks for the reply.

Can you kindly take a look at the following xml's generated by two different programmes, using a 3-line srt @23.976fps?

frame3.srt
1
01:00:00,000 --> 01:00:05,000
01:00:00,000
3600s (f# 86314, 86400, 90000)

2
02:00:00,000 --> 02:00:05,000
02:00:00,000
7200s (f# 172628, 172800, 180000)

3
02:46:40,000 --> 02:46:45,000
02:46:40,000
10000s (f# 239761, 240000, 250000)

23_BDN_Index.xml
<?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="subtitle_exp" Content="" />
<Language Code="eng" />
<Format VideoFormat="1080p" FrameRate="23.976" DropFrame="False" />
<Events Type="Graphic" FirstEventInTC="01:00:00:00" LastEventOutTC="02:46:45:00" NumberofEvents="3" />
</Description>
<Events>
<Event InTC="01:00:00:00" OutTC="01:00:05:00" Forced="False">
<Graphic Width="538" Height="81" X="691" Y="984">0001.png</Graphic>
</Event>
<Event InTC="02:00:00:00" OutTC="02:00:05:00" Forced="False">
<Graphic Width="600" Height="81" X="660" Y="984">0002.png</Graphic>
</Event>
<Event InTC="02:46:40:00" OutTC="02:46:45:00" Forced="False">
<Graphic Width="617" Height="81" X="651" Y="984">0003.png</Graphic>
</Event>
</Events></BDN>

23_avs.xml
<?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="ep5" Content=""/>
<Language Code="eng"/>
<Format VideoFormat="1080p" FrameRate="23.976" DropFrame="false"/>
<Events LastEventOutTC="02:46:35:00" FirstEventInTC="00:59:56:10"
ContentInTC="00:00:00:00" ContentOutTC="03:00:32:12" NumberofEvents="3" Type="Graphic"/>
</Description>
<Events>
<Event Forced="False" InTC="00:59:56:10" OutTC="01:00:01:10">
<Graphic Width="870" Height="131" X="526" Y="879">00086314_0.png</Graphic>
</Event>
<Event Forced="False" InTC="01:59:52:20" OutTC="01:59:57:20">
<Graphic Width="970" Height="131" X="476" Y="879">00172628_0.png</Graphic>
</Event>
<Event Forced="False" InTC="02:46:30:00" OutTC="02:46:35:00">
<Graphic Width="1001" Height="131" X="462" Y="879">00239760_0.png</Graphic>
</Event>
</Events>
</BDN>

1. Which of the two follow the DropFrame convention?

2. When fed into, say bdsup2sub, would the timing be identical for both the BD sup's created?

3. There appears to be no provision for DropFrame parameter in avs2bdnxml. How's the flag being used? And how does it affect the timing in the BD sup's created?

4. Is the DropFrame flag retained in the BD sup's?

Many thanks and best regards.

[ps auxw]

1. Which of the two follow the DropFrame convention?
According to the flag in the "Format" tag, neither is using drop frame timecodes. The first file (23_BDN_Index.xml) would be the one with drop frame timecodes. Non drop frame timecodes count time as if the video was 24fps instead of 24000/1001fps, so one second is always 24 frames, meaning they look like they lag behind a bit.

2. When fed into, say bdsup2sub, would the timing be identical for both the BD sup's created?
I don't know how/if bdsup2sub handles the DropFrame attribute of BDNXML. In this case, since one of the programs is lying about the type of timecodes (both have DropFrame="false") it generates or is simply generating flat out wrong timecodes, the results wouldn't be identical.

3. There appears to be no provision for DropFrame parameter in avs2bdnxml. How's the flag being used? And how does it affect the timing in the BD sup's created?
avs2bdnxml always generates non-drop frame timecodes in its output. Since it never reads anything but raw video streams, no processing of flags is required.

4. Is the DropFrame flag retained in the BD sup's?
Inside the SUP, there is no such flag. Timecodes are stored as integers, calculated like this: 90000 * frame number * fps denominator / fps numerator

[mariner]

According to the flag in the "Format" tag, neither is using drop frame timecodes. The first file (23_BDN_Index.xml) would be the one with drop frame timecodes. Non drop frame timecodes count time as if the video was 24fps instead of 24000/1001fps, so one second is always 24 frames, meaning they look like they lag behind a bit.

I don't know how/if bdsup2sub handles the DropFrame attribute of BDNXML. In this case, since one of the programs is lying about the type of timecodes (both have DropFrame="false") it generates or is simply generating flat out wrong timecodes, the results wouldn't be identical.

Does it mean if the first file (23_BDN_Index.xml) has DropFrame="True" (is that the correct syntax?), then it would be correct and is equivalent to the second 23_avs.xml?

Inside the SUP, there is no such flag. Timecodes are stored as integers, calculated like this: 90000 * frame number * fps denominator / fps numerator


Using 23_avs.xml as an example, would the timecode for 3rd subtitle line be calculated using the following numbers?

frame number = "02:46:30:00"*24 = 239760
fps denominator = 1.001
fps numerator = 24

Many thanks and best regards.

[ps auxw]

Does it mean if the first file (23_BDN_Index.xml) has DropFrame="True" (is that the correct syntax?), then it would be correct and is equivalent to the second 23_avs.xml?
I think so, but I haven't tested it.

Using 23_avs.xml as an example, would the timecode for 3rd subtitle line be calculated using the following numbers?

frame number = "02:46:30:00"*24 = 239760
fps denominator = 1.001
fps numerator = 24
Yes. (Numbers are stored in big endian format.)

[Conspicuous57]

When I am converting a srt to BDSUP in 1080p Full Frame mode, my graphic card's fan is spinning like crazy during all the process.

My hardware temp values:
http://imageshack.us/a/img849/1421/adsznfd.png

I've "CX640DX-658XTR"
CPU: Intel® Core i5-2430M 2.2 GHz 3MB Cache
LCD: 15.6" HD LED backlight 1366x768
Graphics: NVIDIA® GeForce GT540M 2 GB GDDR3
HDD: 640GB
Memory: 6GB DDR3

Is that normal?

[mariner]

Does it mean if the first file (23_BDN_Index.xml) has DropFrame="True" (is that the correct syntax?), then it would be correct and is equivalent to the second 23_avs.xml?

I think so, but I haven't tested it.



It appears bdsup2sub does not observe the DropFrame attribute of BDNXML. Time code lags by a factor of 1.001.

[Okeeffe1881]

nautilus7
Same thing and I'm looking but have not found

[Conspicuous57]

Do we have a chance to change the safezone in goSUP?

[minhjirachi]

When I using goSUP, it's said "Nothing to do". With the easySUP, it runs until step 2 and said "Error processing" and said DONE. So how to fix those problem?

[Dofin]

Download link: 1.3MB standalone package (http://multiavchd.deanbg.com/goSUP/)

Download link: 125KB executable only (http://multiavchd.deanbg.com/goSUP.exe) (if you have multiAVCHD, just put it in multiAVCHD folder)....


Before doing what you suggested, I tried to add SRT file but multiAVCHD was not working well. I tried both mt2s files. For the first one but the subs did not appeared in TMT6 and for the second one, output result was twice the original.

Standalone program did not worked for me; it stops after step 2. Although I did not have Java installed. So, I did installed both version, 32 and 64. Next time I will try it.

I then put easySUP in multiAVCHD folder and ran it. Of course, it takes longer but the final result was the one expected: file SUP created.

I extracted the SUP, use BDFix to remux and I had my movie done the way I wanted. Thanks a lot Dean, you're a Genius.

[r0lZ]

Click the image to download (http://multiAVCHD.deanbg.com/easySUP/) the standalone application (2.5MB):
The link is dead.
(The links to download the standalone exe and the two versions of GoSUP work fine.)

[thinredline]

Hello.
I'm trying to use this tool (easySUP) but I get an error.
I want to convert an ass file to sup.
When there are 2 lines the resulting sup looks like this:
https://i.imgur.com/lINf9cn.jpg



I guess this has to do with safe zone, margin etc.?
I don't know what setting should I use.

[thinredline]

Ok, i made the software to import the video setting of the file, and it put by itself a margin of 54 and now this problem is corrected.
But, it created another one.
This:
https://i.imgur.com/bN4Gv7B.jpg

Looks like this now in the resuting sup.
https://i.imgur.com/IBrKyqw.jpg


Can't I do anything to keep the ass stylisation,margins etc. EXACTLY as it is originally?

[MaistroX]

Any chance of an update to include UHD 2160p Resolution to GoSup and easySUP? :)

[jerrycan]

Any chance of an update to include UHD 2160p Resolution to GoSup and easySUP? :)

Why would you want that? If this is for UHD rips, the BDROM white paper specifies that PGS files, even for 4K discs, are limited to 1080p. There's really no reason I know of to go to 2160p.

[jediknight]

UHD Discs needs 2160p resolution for subtitle. Is it possible to update program ? Is developer around here ?

Thanks,

[Ignatius]

UHD Discs no needs 2160p resolution for subtitle.
BD subtitles (1080p) fit perfectly.

[r0lZ]

If the player resizes the subtitles to place them where it wants them, then indeed, 1080p subtitles are sufficient. But most players require the subtitles in the right resolution, and 2160p is necessary. 2160p is also mandatory for Full-SBS and Full-TAB 3D subtitles.

[nevcairiel]

UHD Discs no needs 2160p resolution for subtitle.
BD subtitles (1080p) fit perfectly.

Not only that, the UHD Blu-ray spec only gives you a 1080p overlay graphics plane for subtitles and expects the player to upscale this - ie. no 2160p subtitles at all.

[DeafYakuza]

I set the subtitles for 1080p and it fit perfect but if I want for 4k UHD the subtitles are to small. It doesn't fit perfectly!

The developer have to update it, definitely!

[donnje]

is it possible to save a file compatible with MuxMan? the dvd sub it is not recognized

[JimmyBarnes]

When I try I get:

"We can’t connect to the server at multiavchd.deanbg.com."

TIA