vobsub 2.10 test

[gabest]

There are a few new features, so I decided to do a little testing before the release.

I can't remember all the requested things, just tell me if any is missing.

click me (http://vobsub.edensrising.com/get.php/test.rar)
(there is no installer, only for experienced users)

[Mikele]

It doesn't display subtitles if I deselect "Advanced Renderer". When it's selected, the subtitles are a little bigger than with 2.09.
What is it that you want to test?

[Yusaku]

Wow, although not much has changed from the outside, it looks like you made huge optimalizations inside the code :)

Ok, here's the buglist:
* When Prebuffer-subpictures is turned on, last dialog of SSA is not displayed
* in SSA, \h is not rendered as hardspace (just as "\h")

* compared to Mikele, I had no problems viewing subs without Advanced rasterizer (but given the fact that my configuration is almost equals to yours, it is not a big surprise)

* not a bug, but I suggest changing default settings after instalation:
Prebuffer: On
Advanced rasterizer: On
Outline: On
Shadow: On

This way, you'll eliminate huge amount of "bugreports" like "Gabest, help! DVobSub is freezing video each time it is supposed to display a new subtitle" (the performance price of advanced rasterizer...); and outline + shadow just looks better ^_^.
(anyways, why wasn't prebuffering on by default already? DVobSub works way better than with it turned off)

And finally, I'm looking forward to seeing source code... How did you do the alpha-aware YUV BitBlt?! :)

[gabest]

First, thanks for the feedbacks.

About the changes. Yesterday I was a bit tired to write them together, but now I will.

dvobsub:
- should work when ogm subtitler filter is installed.
- much nicer alpha blending at the edges.
- new layout for the property page (the bottom got hidden if the desktop res. wasn't high enough).
- advanced text rendering optioins: from subtitler's code everything was replaced except the Rasterizer class, which was good enough to stay :) The new engine is the part of textsub and subresync, too.
- support for microdvd styles and tags (also applies to other tools)
- remote controller support:
VK_F13 - switch subs on/off
VK_F14 - switch subs on
VK_F15 - switch subs off
VK_F16 - next language
VK_F17 - previous language
I used bremote 2.1 for testing, my script.rem looked like this:
Always()
{
"Minus" : PressKey(VK_F13)
"Plus" : PressKey(VK_F14)
"Stop" : PressKey(VK_F15)
"Play" : PressKey(VK_F16)
"TV/FM" : PressKey(VK_F17)
}
- screensaver gets disabled when the video is playing (warning: nobody will turn SS back on if the player crashes :))

subresync:
- preview for both vobsub and text, you can even drag&drop a video file into the checked background when displaying textual subtitles.
- exporting vobsub to scenarist/dvdmaestro (thx for guillep2k for testing this)
- resizing window (wow!:))
- style editing support (also works through dblclicking on a list elem.)
- advanced syncing options: if you right click on the icon of the first column it will cycle between 3 different waypoints.
- "unlink" checkbox orders the list in reading order and disables interpolation between the time codes.
- appending subs

submux:
- Subtitle input type was changed to .ssa :)

textsub:
- VirutalDub and Avisynth interface.
- support for many textual formats.
- auto-reloads like dvobsub. (warning: don't modify the subtitles during the encoding unless you know what you are doing!)

[gabest]

Originally posted by Mikele
When it's selected, the subtitles are a little bigger than with 2.09.Yes... They are drawn in two different ways and that's how it came out :)

Originally posted by Yusaku
Ok, here's the buglist:
* When Prebuffer-subpictures is turned on, last dialog of SSA is not displayedHm, yet again? :)* in SSA, \h is not rendered as hardspace (just as "\h")Oh, so \h means hard space. Is it only meaningful at the beginning of the line?* not a bug, but I suggest changing default settings after instalation:
Prebuffer: On
Advanced rasterizer: On
Outline: On
Shadow: OnOk, good idea.(anyways, why wasn't prebuffering on by default already? DVobSub works way better than with it turned off)The effects won't render in that mode, but in 99% of the cases there won't be any anyway.And finally, I'm looking forward to seeing source code... How did you do the alpha-aware YUV BitBlt?! :) The same way as before, just changed it to work on two pixels at a time. However, the antialiased edges are still rendered agains black background, I can't convert the yuy2 video to rgb32, draw the text and then convert it back to yuy2 in real-time. And yes, textsub used in avisynth on yuy2 also has this problem. But it isn't that bad, hardly noticable with dark outlines.

[mtrooper]

Great, seems to use less cpu than before (if I'm not mistaken).

Don't know if this is bug of DVobSub, but: after seeking in .ogm files subs are restarting from the begining.

Edit:
Stupid me didn't read OGG subtitle filter vs. DVobSub...Well, all I can say is I'm waiting for next release of Ogg DS filters :)

@Mikele:
if I understand correctly - some keyboards do have f13-f17 and their codes differ from f1-f12...so the only way is to emulate them or buy a new keyboard.
Dunno what Girder is...

[Mikele]

@Gabest:
I can confirm that DVobSub works with OGM subtitler installed. But I still don't know if OGM subtitler works with DVobSub installed :)

About the hotkeys, what are the real keystrokes that I should send? I'm using Girder, and I don't know what those F13~F17 keys are. I guess they are Shift-F1~12, right? I tried that but it didn't work.

[gabest]

Originally posted by Mikele
But I still don't know if OGM subtitler works with DVobSub installed :)It won't when there is an external subtitle which loads dvobsub :)About the hotkeys, what are the real keystrokes that I should send? I'm using Girder, and I don't know what those F13~F17 keys are. I guess they are Shift-F1~12, right? I tried that but it didn't work. KB/Special Key/F1-F24

[guillep2k]

Hi! Scenarist info still has some problems on channel assignments (P, E1, E3 & BG). I e-mailed you with details.

Guille

[Yusaku]

Oh, so \h means hard space. Is it only meaningful at the beginning of the line?
Nope, it can be anywhere... (that's how VDub's subtitler draws it, if it is too hard to change this, I'll just replace all \h's with hardspace (#160) on editor-level :) )

- screensaver gets disabled when the video is playing (warning: nobody will turn SS back on if the player crashes)
Oooops - even restart of player (loading DVobSub again...) won't help? !?!

[Mentar]

*whooops and is off to do some testing* :D

[Yusaku]

Bugreport - continued

* SSA: the borders are measured in movie-space coordinates, instead of coordinates (resolution) specified in SSA file.
(e.g. on one of my scripts, I had borders of 180 pixels from each side, thus 360pixels total. Out of my used resolution written in SSA file <1280*960>, this makes about 25% of the width.
Hovewer when rendered directly on the video <640*something> with DVS 2.10, it has just 280 (640-360)
pixels for
whole text,
resulting in
ugly linebreaks
all around.)

* just wondering: ASS format is what? :) SSA with layer support? Haven't found anything about it on http://www.anime-fansubs.org noticed inside the files, and although almighty google came up with a lot info about ass, it wasn't what I was hoping for ^_^

* suggestion for auto-line wrapping: It would be nice if you could add hardspaces after one-letter words during parsing, because it looks terribly ugly, when you have a
line ending with a
single letter word.

[gabest]

Originally posted by Yusaku
- screensaver gets disabled when the video is playing (warning: nobody will turn SS back on if the player crashes)
Oooops - even restart of player (loading DVobSub again...) won't help? !?! It will. Play button diables, stop button enables screensaver.Originally posted by Yusaku
Bugreport - continued

* SSA: the borders are measured in movie-space coordinates, instead of coordinates (resolution) specified in SSA file.
(e.g. on one of my scripts, I had borders of 180 pixels from each side, thus 360pixels total. Out of my used resolution written in SSA file <1280*960>, this makes about 25% of the width.
Hovewer when rendered directly on the video <640*something> with DVS 2.10, it has just 280 (640-360)
pixels for
whole text,
resulting in
ugly linebreaks
all around.)Hm, I set an ssa to be 1280x... with 180 left/right margins and then applied it on a 640x... avi, but it looked alright to me. I checked it with a null transform filter, by cropping it 90 pixels from both sides.[QUOTE][B]* just wondering: ASS format is what? :) SSA with layer support? Haven't found anything about it on http://www.anime-fansubs.org noticed inside the files, and although almighty google came up with a lot info about ass, it wasn't what I was hoping for ^_^LOL :)
About "ass" I can't tell anything more yet.* suggestion for auto-line wrapping: It would be nice if you could add hardspaces after one-letter words during parsing, because it looks terribly ugly, when you have a
line ending with a
single letter word. How would a hardspace help this? If the last word hits the margin then there is nothing which could prevent it from wrapping to the next line.

[Yusaku]

Originally posted by gabest
It will. Play button diables, stop button enables screensaver.

Whew... :)
Hm, I set an ssa to be 1280x... with 180 left/right margins and then applied it on a 640x... avi, but it looked alright to me. I checked it with a null transform filter, by cropping it 90 pixels from both sides.
well, it might also be an improper rendering of old subtitler's filter... Anyway, it is definitely rendering some subs slightly differently than previous version - I sent you mail with one such script.

How would a hardspace help this? If the last word hits the margin then there is nothing which could prevent it from wrapping to the next line.
if it would be done in parser, then it would connect the two words together like&160;this (html-like syntax), thus BOTH words (the one-letter one and the next) would wrap, making
a lines like this,

instead of horrible wrapping that chooses a
worst possible moment to wrap that I
really don't like to read afterwards.

[gabest]

Originally posted by Yusaku

if it would be done in parser, then it would connect the two words together like&160;this (html-like syntax), thus BOTH words (the one-letter one and the next) would wrapOk, I understood the trick :)

[mrSHADOW]

It seams, that subresynch has a problem with charsets. OCR module isn't able to save letters from other than default charset. Every dialog, that has such a letter is ended just before that letter (even \n isn't written).

Normal renderer wasn't able at first to render any files. It started to work, after several changes from Normal to Advanced,

mrSHADOW

[mrSHADOW]

Well, renderer has a problem with drawing such a line (from SSA script):

Wódka - trochê wstrz¹œniêta -\Ni jeden mikroprocesor.


It looks like that:

Wódka - trochê wstrz¹œniêta
-
i jeden mikroprocesor.

And it isn't pretty. VobSub 2.09 and Subtitler shows that line OK.

And one more thing. OCR now has occasionally problems with i, j, Œ, ¯ and other letters that have a dot or coma over a letter. They are recognised as two letters.

mrSHADOW

[gabest]

Both problems fixed :)

[mrSHADOW]

Maybe you could add one option to subresynch, to save dialog.

An option, that calculates display time of subtitles. Their display time is offten too short. Especially in TMP format (in your source known as VPlayer) where they're displayed for 3 seconds and it's not enough for very long lines. So they could be displayed for 1+0.05*length(SubTitle) seconds.

mrSHADOW

[gabest]

test.rar has been updated

[mrSHADOW]

New version is propably using \n as a new line indicator instead of \N, which is not a good idea.

[mrSHADOW]

The picture in DVobSub is moved down and left (and you can't change this) by default and it looks terrible (reduced to half size and then zoomed to original or something ?!).

[gabest]

Could you show me an example of this \n problem?

Do you have a screenshot of that second problem because I just can't picture it :)