Nicholi
25th May 2004, 21:03
And a howdy dudey to you all.
Well the problem starts with a non-Windows font being muxed into an MKV. This font (ArtificeSSK (http://www.ultimatebadass.org/~xclan/lonewolf/fonts/ARTIS___.TTF)) however unlike others is not completely defined, and certain characters such as ' " @ and so forth are left undefined. Originally I had no idea that this font had certain undefined characters, it wasn't until I tried using it in a Word Document and noticed that the undefined characters were being defaulted to Word's default font, Times New Roman.
Now in the interest of softsubbed SSA's in matroska this is very important to be able to use non-standard fonts in an MKV file and have them properly playback. Everything works perfectly fine, of course until the undefined characters come onto the screen.
Here I present a picture using the non-standard font actually installed on the system. All characters are shown perfectly.
http://www.ultimatebadass.org/~xclan/lonewolf/fonts/installed%20fontv2.PNG
In this picture the font has been removed from the system and is being loaded from the matroska file, as you can see the undefined characters are now...undefined.
http://www.ultimatebadass.org/~xclan/lonewolf/fonts/not%20installed.PNG
Now it seems that with the font installed, the undefined characters are Defaulted to VSFilter's default font, Arial. However with the font removed it does not perform this default function.
I present next a side by side comparison of Arial and ArtificeSSK in an MKV. Note the undefined characters will be entered in as Arial as soon as you install ArtificeSSK, here (http://www.ultimatebadass.org/~xclan/lonewolf/fonts/font%20tests.mkv). Here as well is the SSA (http://www.ultimatebadass.org/~xclan/lonewolf/fonts/font%20comparison.ssa) being tested.
Question being, can this problem with the splitter (if that so is the problem) be fixed so that it will default to Arial on undefined characters when the font has been muxed into the MKV? Of course the common quick now is to simply force those characters in the SSA to be Arial in the first place, however this can become quite cumbersome using more and more fonts and checking how complete they are. The problem foremost stems from the fact that as the person making the SSA, and checking timing/positioning/so forth while playing back on my own machine, I cannot notice the sutttle inconsistencies unless I uninstall all the font's I just used the current script.
I tried similar tests on other fonts, as well as fonts from the same author as ArtificeSSK, and actually to no avail I could not reproduce the "defaulting" behavior. They all still contained the big undefined BLOCK characters after installing each font. So it may just in fact be certain krayzie font's themselves, though I have no idea myself. This has all been tested using Gabest's MKV splitter 1.0.2.3 and VSFilter 2.33.
Hopefully some light may be shed on the subject? Where are you font guru's?
Well the problem starts with a non-Windows font being muxed into an MKV. This font (ArtificeSSK (http://www.ultimatebadass.org/~xclan/lonewolf/fonts/ARTIS___.TTF)) however unlike others is not completely defined, and certain characters such as ' " @ and so forth are left undefined. Originally I had no idea that this font had certain undefined characters, it wasn't until I tried using it in a Word Document and noticed that the undefined characters were being defaulted to Word's default font, Times New Roman.
Now in the interest of softsubbed SSA's in matroska this is very important to be able to use non-standard fonts in an MKV file and have them properly playback. Everything works perfectly fine, of course until the undefined characters come onto the screen.
Here I present a picture using the non-standard font actually installed on the system. All characters are shown perfectly.
http://www.ultimatebadass.org/~xclan/lonewolf/fonts/installed%20fontv2.PNG
In this picture the font has been removed from the system and is being loaded from the matroska file, as you can see the undefined characters are now...undefined.
http://www.ultimatebadass.org/~xclan/lonewolf/fonts/not%20installed.PNG
Now it seems that with the font installed, the undefined characters are Defaulted to VSFilter's default font, Arial. However with the font removed it does not perform this default function.
I present next a side by side comparison of Arial and ArtificeSSK in an MKV. Note the undefined characters will be entered in as Arial as soon as you install ArtificeSSK, here (http://www.ultimatebadass.org/~xclan/lonewolf/fonts/font%20tests.mkv). Here as well is the SSA (http://www.ultimatebadass.org/~xclan/lonewolf/fonts/font%20comparison.ssa) being tested.
Question being, can this problem with the splitter (if that so is the problem) be fixed so that it will default to Arial on undefined characters when the font has been muxed into the MKV? Of course the common quick now is to simply force those characters in the SSA to be Arial in the first place, however this can become quite cumbersome using more and more fonts and checking how complete they are. The problem foremost stems from the fact that as the person making the SSA, and checking timing/positioning/so forth while playing back on my own machine, I cannot notice the sutttle inconsistencies unless I uninstall all the font's I just used the current script.
I tried similar tests on other fonts, as well as fonts from the same author as ArtificeSSK, and actually to no avail I could not reproduce the "defaulting" behavior. They all still contained the big undefined BLOCK characters after installing each font. So it may just in fact be certain krayzie font's themselves, though I have no idea myself. This has all been tested using Gabest's MKV splitter 1.0.2.3 and VSFilter 2.33.
Hopefully some light may be shed on the subject? Where are you font guru's?