Subtitle Edit

[Janusz]

That's right. In this thread last June, we made it clear. During the first few lines, nOCR learns to recognize
the correct size of symbols further. Maybe I am wrong, but I think that in such a situation the first scan can
always be wrong, only with the second scan nOCR will use the previously acquired skills stored in our database.

[Nikse555]

@Janusz: thx for the feedback :)
I've tried to fix the bug about updating nOcrDb with new casing here: https://github.com/SubtitleEdit/subtitleedit/releases/download/3.5.18/SubtitleEditBeta.zip
How does that work?

The beta can also read the weird .sup file (transport stream subtitle).

About the screenshot of main window - it's just the frame that's been removed, right?

[Janusz]

@Nikse555
Many thanks for another quick fix in the program.
So far, I have checked the files I used earlier on submission. The fix works fine.
The very first scan with a verified character database gives an error-free result in all cases.
Another, new file during OCR showed an error of the type: upper / lower case replacement.
However, after correcting - assigning the correct letter to its symbol in the database, the first OCR works flawlessly.

[deusexe]

Why recently I can't enter the Polish character "ó"? Other "ń", "ż" etc. can be. And the "remove ellipses at the beginning of the line" option has disappeared in the most common mistakes?

[Janusz]

Why recently I can't enter the Polish character "ó"? Other "ń", "ż" etc. can be.
In Shortcuts, the "Alt+o" keyboard shortcut has been added. Clear it or change it to a different one and everything will return to its previous state.

And the "remove ellipses at the beginning of the line" option has disappeared in the most common mistakes?
I don't know where to look for it at all.

[deusexe]

In Shortcuts, the "Alt+o" keyboard shortcut has been added. Clear it or change it to a different one and everything will return to its previous state.

Thx it helped.
And I will write the latter in Polish because maybe the translator translated it wrong;) Chodzi mi o Narzędzia -> Popraw najczęstsze błędy... i tam była opcja usuń trzy kropki z początku wiersza. A teraz tego nie ma.

[Janusz]

@deusexe
You can find this in: Tools/Fix common errors - now as: Fix continuation style: ...
You can find out what and how it will be included in the [Edit settings for fixing continuation style ...] button in Option/Settings/Tools.

[deusexe]

Thanks @Janusz, I found it, but now this function finds the ellipses at the beginning and end of a sentence. But it's better than nothing.

[Nikse555]

@deusexe: "Remove ellipses at the beginning of the line" will be available if you set "Continuation style" to "none".

[deusexe]

However, I looked wrong. The continuation style is not what I'm looking for at all. This does not find any already existing dots at the beginning of a sentence, it just creates them!

@deusexe: "Remove ellipses at the beginning of the line" will be available if you set "Continuation style" to "none".

Where, how can you turn off the Continuation style?

[Janusz]

@deuexe
Disabling this option, as @Nikse555 replied above, does not create new ellipsis. It also does not remove ellipsis from the original text.
Enabling this option fixes the continuation style by adding/removing ellipsis where the assumed logic requires it.
The continuation style is not what I'm looking for at all.
For what you want to achieve use now "Edit/Multiple replace ...".

[Janusz]

@Nikse555

Last NEXT, beta 525 creates an srt file with errors in the nOCR process:

https://www.mediafire.com/convkey/580d/fqrv1zpx88iit1o6g.jpg

The word "Wjakim" should be split into "W jakim" (The whole sentence: In what sense.) as in the NEXT, beta 487 version below:

https://www.mediafire.com/convkey/1168/v9l6c5vyv6yl4kp6g.jpg

And compare srt files. Correct text on the left.

https://www.mediafire.com/convkey/c98b/jm7e3pjjykj9in56g.jpg

This is what the section of my pol_OCRFixReplaceList.xml file responsible for this correction looks like.
<PartialWords>
<!-- Will be used to check words not in dictionary.
If new word(s) and longer than 4 chars and exists
in spelling dictionary, it is (or they are) accepted -->
<WordPart from="~~" to="I" />
<!-- "f " will be two words -->
<WordPart from="~~f" to="f " />
<WordPart from="ą" to="ą " />
<WordPart from="j" to=" j" />
<WordPart from="W" to="W " />
<WordPart from="w" to="w " />
</PartialWords>

[Nikse555]

@Janusz: Tried to fix the ""Wjakim" issue in latest beta: https://github.com/SubtitleEdit/subtitleedit/releases/download/3.5.18/SubtitleEditBeta.zip

[Janusz]

Thanks, @Nikse555.

I just downloaded the NEXT beta 566 and it looks like it's fine and working as it should again.

[Ghitulescu]

Well, :thanks:

I used the latest (well, at the time :) ) version, to convert from SRT (Unicode) to BD SUP, and the result was very acceptable.

The only issue is that there was a noticeable gap (white space, blank) between any italic or bold characters and the rest of the subtitle. Otherwise, splendid job.

Would it be possible to add another checkbox near the "forced" to allow changes in format for the ticked subtitles (like a bigger font, for movie title or a different placement etc)? I mean all subtitles share the common format except for the ticked ones that may have their own? Just a suggestion...

[von Suppé]

Hi Nikse

SUPs used on UHD-BD's with HDR video-content are authored darker. It often happens that when home-created SUPs are muxed together with HDR video, during playback they appear too bright.
Sometimes a UHD (BD-)player has extra settings to compensate for this brightness, but not all (if not most of them) don't.

Without having to OCR and re-export, is there a way in SE to only edit the palette of a SUP file?

[Nikse555]

The only issue is that there was a noticeable gap (white space, blank) between any italic or bold characters and the rest of the subtitle. Otherwise, splendid job.
Hm, yes. Thx. Noted.


Would it be possible to add another checkbox near the "forced" to allow changes in format for the ticked subtitles (like a bigger font, for movie title or a different placement etc)? I mean all subtitles share the common format except for the ticked ones that may have their own?
You can use font size tags for .srt files - or setup styles for .ass files - both support alignment tags an1-an9 + .ass supports margins in styles.

[Nikse555]

Hi Nikse

SUPs used on UHD-BD's with HDR video-content are authored darker. It often happens that when home-created SUPs are muxed together with HDR video, during playback they appear too bright.
Sometimes a UHD (BD-)player has extra settings to compensate for this brightness, but not all (if not most of them) don't.

Without having to OCR and re-export, is there a way in SE to only edit the palette of a SUP file?

Added a "Change brightness" in latest beta: https://github.com/SubtitleEdit/subtitleedit/releases/download/3.5.18/SubtitleEditBeta.zip

(File -> Import -> Blu-ray (.sup) subtitle file for edit... - and then "Tools" or "list view context menu with selected lines")

[Janusz]

@Nikse555
Note: the described case is general in nature and also occurs in earlier versions of the program.

The animation shows how during nOCR, after enabling the [Use color] option, the images were split incorrectly,
and also not split although they should be because they contain two lines of text in different colors.

https://www.mediafire.com/convkey/d93a/wmvjwqytlsbs9m76g.jpg

With the ts source file I could get color text, but this is impossible in this case as only with
Greyscale=on and Use color=off can I get error free text for the whole file.

The archive (https://www.mediafire.com/file/g0eurz2aolh2ehc/hikari.sup_srt.zip/file) contains 4 sup files to trace the program operation saved with different option settings and the srt files obtained from them.

"g" in the file name means [Grayscale] 0/1 - off/on, "c" in the file name means [Use color] 0/1 - off/on

Perhaps this is an isolated case and should not be dealt with, but if we can fix it... thank you in advance.

Added a "Change brightness" in latest beta:Do you ever anticipate changing the text color separately for the top and bottom lines in one image (as two combined images)?

[von Suppé]

Added a "Change brightness" in latest beta

Awesome, gonna check it out. :thanks:

[ismail0100]

I bother you sorry, but language master file change and after I change translate. :) Here is the latest Turkish language version. You write "remove redundant language tags" so I use latest source and translated file.

https://www.mediafire.com/file/o9pc44uy8txcsxo/tr-TR(13.01.2021).xml/file

And three little problem for your XmlContentTranslator.
First for now, open lanuage master file not working.
Second on the first picture you see version info need update.
And latest, second picture you see, may the problem text include ctrl+v, just guess.

I am using CareUEyes so may picture be a little warm.
https://i.imgyukle.com/2021/01/13/a7Yx0b.png
https://i.imgyukle.com/2021/01/13/a7YTGQ.png

[von Suppé]

Hi Nikse,

I noticed your posts @ https://forum.videohelp.com/threads/400290-Tonemapping-PGS-subtitles-for-use-with-HDR-video
In the new SUP edit function there is the possibility to save the result as BDN xml/png. Considering what has been discussed in the formentioned thread, would it be a good idea - if possible - to implement the opposite possibility too?
I mean in the same way that it works with SUP now, add something like File --> Import (non-OCR) --> "BDN xml/png subtitle file for edit" ? And after the edits, being able to save as SUP?

I think it's really weird that BDSup2Sub's SUP --> xml/png conversion is not lossless and that a filter comes into play when not resizing, but purely extracting SUP images to lossless xml/png as-is. And vice-versa, for that matter.

BTW the brightness tool works nicely. Thanks!

[Nikse555]

@ismail0100: Thx for the updated translation :)
EDIT: Xml Content Translator updated a little...

@von Suppé: In latest beta the sup edit can now also open BdnXml files: https://github.com/SubtitleEdit/subtitleedit/releases/download/3.5.18/SubtitleEditBeta.zip
(also added "Adjust alpha").

[von Suppé]

Great! Gonna check it out :thanks:

[EDIT] During my first quick and dirty testing the PNG/XML import --> save as SUP, it seems to be working okay.

I did notice something. After importing a xml file with a framerate of 23.976, the "Frame rate" window in the editor screen says 25. This is only the case with SE-created xml files.
For framerate, there's a - small - difference in SE's exported xml script, compared to other ones.

SE uses <FrameRate="23976">

Other xml use <FrameRate="23.976">

After adding the "dot" in your xml-script, framerate is showed properly. But I have a question about that properly shown framerate.
When I save that xml (so, with the framerate properly shown 23.976) as SUP again, can you confirm that this framerate is honoured in the exported SUP?
I ask this because when I open this SUP in another tool, it shows framerate 25 again, instead of 23.976.

Another - minor - thing, concerning SE's xml export: it would be nice to be able to set "language".

Thanks Nikse. This already great non-OCR editing tool has a worthy addition with the XML to SUP conversion.

Thereby, it is more than a relieve to see that during the export from XML to SUP, SE honours the transparent rectangular background of the image and leaves that intact in the resulting SUP. This will keep sequential subtitles "seemed to be written on the same line".
It can be very uneasy to the eye when subtitles are "bobbing" up and down, especially when there is little or no time between them.
This unwanted behaviour is often overlooked and not dealt with properly by other subtitle tools.

Keep up the good work, Nikse! :)
Will continue testing.

Cheers

[deusexe]

For what you want to achieve use now "Edit/Multiple replace ...".
For this you would need the wildcards option. Maybe in the next versions. Or it would be easier to restore what was "remove ellipses at the beginning of the line" ... ;)

[Nikse555]

@von Suppé: thx, frame rate stuff hopefully fixed here: https://github.com/SubtitleEdit/subtitleedit/releases/download/3.5.18/SubtitleEditBeta.zip

@deusexe: I think if you set "Continuation style" to "none", then "Remove leading '...'" will be shown in "Fix common errors".

[Atlantis]

I have come to situations where there are - for one person talking like this.

-This is a sub-title
example on 2 lines.

So removing - at the beginning of subtitles is necessary. It should not remove - in the middle of the sentence. It should not delete - if there are 2 at the beginning of 2 lines like this:

-How are you?
-I'm good.

Currently I do it by replace which is a pain. Anyway to automate this?

[Nikse555]

I have come to situations where there are - for one person talking like this.

-This is a sub-title
example on 2 lines.

So removing - at the beginning of subtitles is necessary. It should not remove - in the middle of the sentence. It should not delete - if there are 2 at the beginning of 2 lines like this:

-How are you?
-I'm good.

Currently I do it by replace which is a pain. Anyway to automate this?

Try "Fix common errors" with "Remove dialog dashes in single lines" checked.

[deusexe]

I think if you set "Continuation style" to "none", then "Remove leading '...'" will be shown in "Fix common errors".


Either I don't know which option you are talking about and I am doing something wrong, or it is impossible to restore "remove the ellipsis from the beginning of the sentence" in "Fix common errors":(

[Atlantis]

Thank you. Man I wish I knew that much earlier! I think I have spent hours removing -
and I did read the entries in Fix common errors

[von Suppé]

frame rate stuff hopefully fixed here: https://github.com/SubtitleEdit/subtitleedit/releases/download/3.5.18/SubtitleEditBeta.zip
Yep, it works properly. Thanks for the fix

Man I wish I knew that much earlier! I think I have spent hours removing...
:D
I think if you set "Continuation style" to "none", then "Remove leading '...'" will be shown in "Fix common errors".
Damn, I wish I knew thís earlier. I spent hours of removing leading... :D

[darksen]

Updating between betas (I don't exactly remember the date when I installed/updated the 5.1.18 beta) I got this error and also the Text box got bigger so I had to resize it a little:

An application error occurred in Subtitle Edit 3.5.18.664.
Please report at https://github.com/SubtitleEdit/subtitleedit/issues with the following information:

Error Message:
SplitterDistance debe estar entre Panel1MinSize y Ancho - Panel2MinSize.

Stack Trace:
en System.Windows.Forms.SplitContainer.set_SplitterDistance(Int32 value)
en Nikse.SubtitleEdit.Forms.Main.Main_Shown(Object sender, EventArgs e)
en System.Windows.Forms.Form.OnShown(EventArgs e)
en System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
en System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
en System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
en System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
en System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
en System.Windows.Forms.Control.InvokeMarshaledCallbacks()

And now with the latest beta the subtitle preview is much bigger than before without option to change the font size, I'm using mpv option.

[Janusz]

And now with the latest beta the subtitle preview is much bigger than before without option to change the font size, I'm using mpv option.

You can change it here: Option / Settings / Video engine [Subtitle preview font size]

[darksen]

You can change it here: Option / Settings / Video engine [Subtitle preview font size]

I know that, I meant that no changes made in the available options make an impact in the subtitle size anymore. Sorry if I didn't explain myself correctly. Disabling "mpv handles preview text" makes the sub to go past the screen if I increase the font size:

https://gofile.io/d/UqSSml

Thanks for your help.

EDIT: I had to go back to a beta from 13-12-2020.

[Janusz]

Check [mpv handle preview text], set [Preview subtitle font size] = eg 20, then the subtitles will be displayed in the movie area and will be scaled.
In the extra margin at the bottom, the texts are not scaled, so you need to adjust the font size so that long texts or two lines will fit in the margin area, e.g. 12 as the margin height is fixed.

[Nikse555]

I know that, I meant that no changes made in the available options make an impact in the subtitle size anymore.

Thx for the info - should now use info from video preview in latest beta (695):
EDIT: Note that the font in mpv is scaled, and not fixed as the SE preview, so the preview via mpv font size also depends on the video preview size!
https://github.com/SubtitleEdit/subtitleedit/releases/download/3.5.18/SubtitleEditBeta.zip


SE's Blu-ray sup edit (an alternative to BDSup2Sub) will probably look like this in 3.6.0:
https://www.nikse.dk/Content/SubtitleEdit/se-sup-edit.png

[darksen]

Thank you, just tested latest beta and it is working well again.

There are a couple of thing I want to request or inform as I don't know if one of them is a bug.
I've increased the font of the application because I'm using a 40" display and it is painful for me to force my sight reading the text but because I increased the font size now the time columns don't show the total time, I have to resize them every time I open SE, see:

I got this:

https://srv-store5.gofile.io/download/NVL3aq/SubtitleEdit_2021-02-14_16-15-45.png

Instead of this:

https://srv-store5.gofile.io/download/NVL3aq/SubtitleEdit_2021-02-14_16-16-07.png

The text column does preserve its size but the time columns do not.

The other thing is a request, please allow us to reorder the action list in the Batch convert tool, I want to first use "Multiple replace" and then "Fix common errors" and the same with other options but is not possible to reorder them.

Thank you.

[von Suppé]

New SE is looking good, Nikse.
:thanks: for your work.

[varekai]

Thanks for the update Nikse, couldn't do without this one-of-a-kind gem!
Much appreciated!

[von Suppé]

Hi Nikse

The way of checking the "Forced" flag in the SUP or XML-PNG export window can be rather cumbersome. When one has finished with all text lines, often it's rather a hassle to recall/retrieve what lines were meant to be forced.
When you are actually busy with editing/creating text, would be a better time to know. And act.
Therefor, could you implement a column/box in the text-editor where one can "check forced" the desired lines? In such a way, that during SUP/XML-PNG export, these will be auto-checked as forced?

[Nikse555]

Hi Nikse
...Therefor, could you implement a column/box in the text-editor where one can "check forced" the desired lines? In such a way, that during SUP/XML-PNG export, these will be auto-checked as forced?

Something like this?
https://github.com/SubtitleEdit/subtitleedit/releases/download/3.6.0/SubtitleEditBeta.zip

[von Suppé]

Thanks for quick response, but I can't find what I'm looking for. Can you direct me?

[Nikse555]

Thanks for quick response, but I can't find what I'm looking for. Can you direct me?

There should be check boxes in the edit bd sup list view...

[von Suppé]

Oh damn, I see now. You put them in the Import --> "Sup for edit" window. But it's not where I meant them to be (besides, there is already a forced check-box in that window, so it's a bit double).

I meant the checkboxes to be possible in the main list view in text editor mode. So that the checked lines will be auto-checked as forced in the File --> Export --> Blu-ray SUP (or XML-PNG) export window.

[Easymanandvan]

Thanks, that worked for me as well :)

[tormento]

Just noticed that I can't find source view anymore...

Where has it gone? :)

[von Suppé]

Rightclick in list-view, it's there. Or press F2.

[nekrovski]

I have a file like this

General
ID : 1 (0x1)
Complete name : C:\Users\User\Desktop\h\zz.ts
Format : MPEG-TS
File size : 170 MiB
Duration : 11 min 24 s
Overall bit rate mode : Variable
Overall bit rate : 2 086 kb/s

Video
ID : 256 (0x100)
Menu ID : 1 (0x1)
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L3.1
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 4 frames
Codec ID : 27
Duration : 11 min 24 s
Bit rate mode : Constant
Nominal bit rate : 1 800 kb/s
Width : 960 pixels
Height : 540 pixels
Display aspect ratio : 16:9
Frame rate : 29.970 (30000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.116

Audio
ID : 257 (0x101)
Menu ID : 1 (0x1)
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Format version : Version 4
Muxing mode : ADTS
Codec ID : 15-2
Duration : 11 min 23 s
Bit rate mode : Variable
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 44.1 kHz
Frame rate : 43.066 FPS (1024 SPF)
Compression mode : Lossy

Text #1
ID : 256 (0x100)-CC1
Menu ID : 1 (0x1)
Format : EIA-608
Muxing mode : SCTE 128 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Duration : 11 min 24 s
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)
CaptionServiceName : CC1

Text #2
ID : 256 (0x100)-1
Menu ID : 1 (0x1)
Format : EIA-708
Muxing mode : SCTE 128 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Duration : 11 min 24 s
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)

Menu
ID : 4096 (0x1000)
Menu ID : 1 (0x1)
Duration : 11 min 24 s
List : 256 (0x100) (AVC) / 257 (0x101) (AAC)
Service name : Service01
Service provider : FFmpeg
Service type : digital television



Why can't Subtitle edit read the subtitles from this file?
A ffmpeg command successfully converts them to a .srt so I made sure they are actually in the file but what needs to be done for Subtitle Edit to be able to read these kinds of subtitles?

[Nikse555]

@nekrovski: SE only supports DVB/BD images and teletext from ts files.
I did not even know that other subtitle types were possible in ts files.
Could you supply a link to the file? (PM or email is also fine)

[tormento]

@Nikse555

I think you forgot the French characters menu during OCR: à, â, è, é, ê, ë, î, ï, ô, œ, Œ, ù, û, ç, Ç.