View Full Version : Textsub and Textsubmod not displaying some fonts in 4K


FranceBB
23rd December 2017, 22:06
Hi,
I've been using tekton pro for some captions since 2006 with avisynth. I use several other fonts for other things like normal subs, signs etc.
I never had any issues.
Now, we just changed our workflow 'cause we receive masterfiles in 3840x2160p. Our scripts are 848x480 since 2008 when we switched from 4:3 to 16:9. When the HD arrived, textsub flawlessly scaled text to 1280x720 and when FULL HD arrived it scaled flawlessly to 1920x1080. Unfortunately though, I assumed textsub would have scaled as well - and it did scale - but not all fonts were displayed. One of these fonts is tekton pro. I tried with Textsubmod, same result. Other fonts like Berlin Sans and Impress BT were scaled correctly. Since these other fonts were correctly displayed, I think that it's not Textsub nor Textsubmod fault, however what's weird is that if I change the resolution in Aegisub to 2160p and let it scale, all fonts are displayed correctly, including tekton pro.
I tested it on Windows XP Professional SP3 x86, Windows Server 2008 R2 and Windows Server 2016: same behaviour.

I don't know whether it's supposed to behave like that or not and I don't know whether it's because of Textsub/Textsubmod or the font itself.

Thank you in advance.

GMJCZP
23rd December 2017, 23:38
The tekton pro version you have is open type, true type or post script?

ilko
26th December 2017, 06:09
Of what I know, scaling is just like a zoom effect, not true sampling. I've just tested tekton pro on a 4k dummy video, it works. What is the version of your rendering module ?

I'm using this one : https://github.com/HomeOfVapourSynthEvolution/VSFilterMod/releases

There is also a most recent recent version which fixes the floating point crash here, but the dev has not included binaries and there is no way to contact him : https://github.com/sorayuki/VSFilterMod/releases

FranceBB
26th December 2017, 16:22
The tekton pro version you have is open type, true type or post script?

Just checked. It's Open Type.

Of what I know, scaling is just like a zoom effect, not true sampling. I've just tested tekton pro on a 4k dummy video, it works.

Uh, I didn't have the very last one. Thanks for the link. Tomorrow I'm gonna compile the latest version myself, not a big deal. I'll let you know if it works.

ilko
26th December 2017, 22:27
I already tried to compile it myself too many times, it always fails with a "brace" error left somewhere in the code and some other errors/warns. Unfortunately, I don't have C++ skills.

https://zendama.visualstudio.com/VSFilterMod

FranceBB
27th December 2017, 04:59
I already tried to compile it myself too many times, it always fails with a "brace" error left somewhere in the code and some other errors/warns. Unfortunately, I don't have C++ skills.

https://zendama.visualstudio.com/VSFilterMod

Something is not working as it should.
I tried the VSFilterMod version you are using, but it doesn't display subs.
(I resized both images 'cause at 2160p it would have screwed up the page layout)

https://i.imgur.com/Fn32hb6.png


I also tried with xy-VSFilter stable v3.0.0.306, same result.

ilko
27th December 2017, 11:54
Well, I did some more tests just to be sure, I've did an encoding test, and everything gone well. However, I'm using Avisynth+.

Picture generated by ImageWriter :

http://www.hostpic.org/images/1712271617000098_tn.jpg (http://www.hostpic.org/view.php?filename=1712271617000098.jpg)

→ Encoded sample (http://uptobox.com/2es66ilw2tip)

ilko
27th December 2017, 13:10
Wow, guess I should had read the mail with more attention... will try it, thanks !

GMJCZP
27th December 2017, 13:13
Just checked. It's Open Type.


Being the font OpenType you have the best version, the problem is no longer there, I'm sorry.

FranceBB
27th December 2017, 18:14
The binaries are in the forum attachments here (https://www.nmm-hd.org/newbbs/viewtopic.php?f=17&t=1989), as I should have told you on github issue.

不支持Windows XP系统 = Does not support Windows XP.

I see... I had to test it on Windows Server 2016, but again, same result.

Well, I did some more tests just to be sure, I've did an encoding test, and everything gone well. However, I'm using Avisynth+.

It's weird. Although I'm using Avisynth instead of Avisynth+, we are using the same plugin, so I expect it to be consistent between these two frameserver.
I'm gonna test it on another machine with another setup: one of my colleagues has a box running Windows 7 x64, an older version of Avisynth and VSFilter, I'll let you know.

EDIT: same on my colleague computer running Windows 7.

EDIT2: doesn't display it with VSFilter 1.0.0.9 (the old one, from warp enterprise) as well.

EDIT3: it doesn't display it with Avisynth 2.6.1 alpha1 as well.

EDIT4: doesn't display it with VSFilter 1.0.1.1

EDIT5: doesn't display it with VSFilter 2.39.5.2

EDIT6: changed colour space to RGB32, same behaviour, as expected.

EDIT7: I was able to reproduce the error on four machines running different version of Avisynth, different version of VSFilter and a different version of Windows, but I wasn't able to reproduce the issue with Avisynth +. On such machines, Avisynth + displayed the subs flawlessly. At this point, I think we can say that it's a bug and that it affects Avisynth only.