![]() ![]() Images aren't too bad and I could probably support them, but animations are a real problem the way SSA supported them was simply to spawn a control to play them on-screen, and that obviously doesn't work when you need the animation in a memory bitmap. I don't have image or animation loading code in the filter. Why don't my pictures and animations show up? If you wish to report such a bug, please give a script file with the problem that uses stock Windows XP fonts and also indicate which language edition of OS you are using. I suspect there is a disconnect (bug) between the way the subtitler filter and SSA handles font encoding 0, but haven't gotten a concrete repro case for such a bug yet. You can tell the subtitler renderer to use a particular font by using the tag. If you choose the wrong encoding, the OS won't know that it doesn't match, and will display missing character boxes or gibberish instead. This is necessary because SSA scripts are narrow (8-bit) text and thus the text itself is not sufficient to determine the character set of the text. The character set specifies the encoding used for 8-bit text that is rendered through that font. When a font is selected in Windows, it can either be created with a specific character set or with a generic character set, such as DEFAULT_CHARSET (1). Nor should you rely on this behavior when making your scripts, even if your script creation program does so. The subtitler does not assume the encoding of a font by its name. Why does my foreign-language text appear garbled? If the PlayResY: field is missing entirely, the subtitler simply uses the border and size fields verbatim as pixels. If you are using Sub Station Alpha, remember that it was meant to be WYSIWYG, so the width of your screen will be shrunk to the width of your video! The catch is that if the PlayResY field is altered, all values in the script will be scaled. For most values of PlayResY it assumes a 4:3 aspect ratio, except for 1024, where it assumes 5:4 to fit the common 1280x1024 resolution. The subtitler filter assumes that you want to subtitle your video as though it were a full screen, so it scales all measurements in the script to match the screen resolution in the script. Unfortunately, all of the sizes in an SSA script are in pixels, so the size of the screen is relevant SSA stores the height of the screen in the PlayResY field. Sub Station Alpha was meant to be used with a genlock, so it displayed your subtitles at desktop resolution and the entire screen was overlaid on top of the incoming video. ![]() ![]() This field indicates the vertical height of the subtitling screen. This generally happens due to a missing or mis-set "PlayResY:" statement at the top of the file: Title: VirtualDub 'subtitler' filter demonstration Why are my font sizes and border widths screwed up? Why don't my pictures and animations show up?įortunately, both of these are easy to fix.Why does my foreign-language text appear garbled?.Why are my font sizes and border widths screwed up?.The two most common questions I get about the subtitler filter I wrote are: I think it may have actually just been to display some on-screen lyrics to music - probably Yuzurenai Negai from the Magic Knight Rayearth opening. I'd like to say it was because I fansubbed some anime, but my Japanese skills are extremely minimal and my access to unsubtitled anime even less, so that couldn't have been it. I don't remember why I originally wrote the subtitling filter. ¶The "subtitler" filter, screen size, and font encodings
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |