FAQ
From Aegisub Wiki
This is a list of commonly asked questions.
Contents |
[edit] General
[edit] What does Aegisub mean? Does it stand for anything?
Please see Aegisub.
[edit] Why does Aegisub fail to load the audio?
Version 1.09 has a number of known audio loading issues. Either downgrade to 1.08 or upgrade to 1.10.
[edit] When will the next version be out?
It'll be out when it's done. Meanwhile, check the pre-release builds.
[edit] Help! Bork bork!
[edit] File Encoding
[edit] I have a karaoke file in japanese. However, when I load it in Japanese, I get a bunch of gibberish. Why is that?
The file is most likely encoded as Shift_JIS. Go to File->Open with Charset and open the file selecting Shift_JIS. After that, save it and it'll be saved as UTF-8, which can be read on any machine, regardless of its local setting, as long as the program supports Unicode (Medusa and Substation Alpha don't, but Aegisub and Sabbu do).
[edit] Why do my files fail to display properly in VirtualDub? All the non-ascii characters become gibberish!
That is because some versions of VirtualDub ships with an ancient (2.23) version of TextSub (now part of VSFilter). That version only supports unicode as UTF-16, and breaks with UTF-8 (handling it as if it were ASCII). By default, Aegisub saves its files as UTF-8. This can be solved by either:
- Updating your TextSub in VirtualDub
- Using Avisynth
- Saving as UTF-16 (either manually via the Export dialog or by setting Aegisub to do it automatically in config.dat).
[edit] Subtitle formats
[edit] How do I save to SRT or SSA?
Use "Export" under the "File" menu. There you can choose to save as ASS, SRT, SSA or PRS.
There are no plans to add support for saving directly in SRT or SSA. Aegisub is an ASS editor and as such, ASS is the working format. You are encouraged to save all working copies in ASS, and only export for another format when you actually need it. Remember that ASS is a superset of both SSA and SRT and as such, you won't lose any functionality by using ASS as working format.
[edit] Will Aegisub support USF?
There are no plans to implement USF support yet, however, if it ever does support it, it will most likelly convert to ASS on load and convert back to USF on saving - in much the same way that SRT support works. If you're willing to write the parser and writer for this format, feel free to contact us on the IRC Channel.
[edit] Video
[edit] Aegisub's video window doesn't seem to play video correctly!
Mantra: Aegisub is not a video player. Do not expect it to play video correctly.
The video display in Aegisub is intended purely for typesetting, ie. making sure on-screen text appears and disappears at the correct frames and match up to the original picture. It is NOT intended as a "playable preview" and has never been! If you want a playable preview, you should save your file and open the video in an external player.
[edit] Automation
[edit] My syllables are incorrectly spaced!
Checklist:
- Check the Script Resolution (Tools -> Properties). It should match the video resolution (before any anamorphism is applied!) It can also be an exact multiple of the video resolution.
- Check that spaces are timed as separate syllables. This means "{\k10}foo{\k0} {\k10}bar". This has the added benefit that any pauses between the words in the song can also be dealt with.
- Are you using the right alignment? If you use $X in multi-template and line-per-syllable, you must use alignments 2, 5 or 8. If you're not using factorybrews, you'll want alignment 1, 4, 7 for things based on syl.left, 2, 5, 8 for things based on syl.center and 3, 6, 9 for things based on syl.right.
- Try using a different font, Arial is the de-facto test font. If things look better then, you've had bad luck picking font. Some fonts just result in incorrect calculations for a yet-unknown reason.
If the spacing is still way off, there is no known cure.
[edit] I don't want to program Lua!
You didn't read the tutorials, did you?
[edit] Where did the Apply Now button go in Automation 4?
It was removed for one simple reason: It doesn't make sense given the way Automation 4 works.
One Automation 4 script can define multiple "features", for example macros and export filters. So, one script can for example define two macros and one export filter. Which one should "Apply Now" run?
Macros are run from the Automation menu in the main window. Quite simple.
Export filters are applied when exporting a file with the File→Export function. Here's an important catch: Automation scripts are automatically reloaded when you enter the Export dialog, so you don't need to reload it automatically! (If your script disappears from Export after making some changes to it, it means it no longer parses correctly, so you should go into the Automation dialog, figure out what went wrong, fix the script so it loads again, then you can Export.)
All Automation 3 scripts are export filters.
