Blu-ray subtitle conversion tool (sub2bd)

[schorman]

Of course I'm familiar with AviSynth.

easySUP uses VSFilter as well, and an older version of avs2bdxml, but it outputs everything without issue.

[Beber]

OK please try 0.92.

Got my accents back. Thanks.

[bronan]

Of course I'm familiar with AviSynth.

easySUP uses VSFilter as well, and an older version of avs2bdxml, but it outputs everything without issue.

VSFilter renders the ASS to the Avisynth buffer, then that image is processed for BD format by avs2bdxml. The dropshadows are either there or not when the text is rendered to Avisynth, so I don't think the encoding step is going to effect it much (could be some cropping happening possibly, but I think you'd see hints of them). Have you tried swapping out the VSFilter.dll included with sub2bd with a different version? I don't remember where I got it to be honest.

[schorman]

I'll give it a shot.

[schorman]

Ok, I switched out the version of VSFilter and it now renders the shadows correctly. 

However, I'm seeing quite a few error messages in BDsup2sub when I check the file, and it seems to want to change the color palette resulting in lower quality.

sub2bd


easySUP

[bronan]

Ok, I switched out the version of VSFilter and it now renders the shadows correctly. 

However, I'm seeing quite a few error messages in BDsup2sub when I check the file, and it seems to want to change the color palette resulting in lower quality.

Cool, did you try any of the options to see if that clears it up? The only other thing I can think is that I'm having avs2bdnxml directly output the SUP file instead of doing another conversion from bdnxml to SUP. But if we see what the subtitles look like directly in Avisynth then it should prove if its a rendering or encoding issue.

[theprion]

Hey bronan, could you elaborate on what exactly "strict mode" and "ugly splitting" do and how does "optimize buffer" works?
Thanks!

[bronan]

Please see avs2bdxml for full documentation:
GitHub - koroban/avs2bdnxml: AVS to BluRay SUP/PGS and BDN XML Converter

Code:

  -z, --stricter <integer>     Stricter checks in the SUP writer. May lead to
                               less optimized buffer use, but might raise
                               compatibility. [on=1, off=0]
  -u, --ugly <integer>         Allow splitting images in ugly ways.
                               Might improve buffer problems, but is ugly.
                               [on=1, off=0]
  -b, --buffer-opt <integer>   Optimize PG buffer size by image
                               splitting. [on=1, off=0]

[schorman]

Ok, I switched out the version of VSFilter and it now renders the shadows correctly. 

However, I'm seeing quite a few error messages in BDsup2sub when I check the file, and it seems to want to change the color palette resulting in lower quality.

Cool, did you try any of the options to see if that clears it up? The only other thing I can think is that I'm having avs2bdnxml directly output the SUP file instead of doing another conversion from bdnxml to SUP. But if we see what the subtitles look like directly in Avisynth then it should prove if its a rendering or encoding issue.

Both of those use the same version of VSFilter, so the avisynth output shouldn't be the issue. In fact, most of the subs are coming out perfect. There are about a third of the subs that report "WARNING: fade out detected -> patched palette" when loading in BDSup2Sub. That seems to be the source of the degrade in quality.

It doesn't seem to be a problem with the subtitles being rendered. There's some problem with the SUP that this version of avs2bdnxml is generating.

[bronan]

Have you inspected the subtitles in any program besides BDsup2sub? I remember seeing a warning in the documentation of avs2bdnxml about opening generated subtitles through there, but I don't remember the exact context.

I will look into exporting as bdnxml and doing SUP conversion separately.