Trouble logging in?If you can't remember your password or are having trouble logging in, you will have to reset your password. If you have trouble resetting your password (for example, if you lost access to the original email address), please do not start posting with a new account, as this is against the forum rules. If you create a temporary account, please contact us right away via Forum Support, and send us any information you can about your original account, such as the account name and any email address that may have been associated with it.

While Aegisub is not running:
Go to Start->Run, type "%appdata\aegisub" and select OK, open "config.dat" in Notepad and delete all lines that start with "automation". Then save the file. Things should work right now.

Also "latest build" is rather inaccurate, figuring out the actual build number is very easy (it says in the title bar) and I would really appreciate if you (and anyone else) would write the exact build number instead of just "latest".

Thanks jfs for your very quick answer, I will try that right after writing this message.
Concerning the build number of the release, it is r1564, but I thought it was clear enough when I said that I installed the program with the lastest .exe file.
Sorry for this imprecision, I keep this simple point in my mind for further messages

Thats actually not the best picture of the problem.
I've fixed the overlapping syllables, but the spacing is the same. I think it might have something to do with the video being 16:9 although I'm not sure.

Here is a better picture of the problem, this is after I fixed the overlapping syllables:

If I resized the video to 4:3, the karaoke effect works fine.

And I've put {\k0} before every space which I know does fix another spacing problem, I just don't know how to fix the one in the picture above.

If it means anything, I'm using \pos($x,20) in the template (if I use multi-template or line-per-line syllable, same thing happens).

I believe that's 2.0 (though I suppose you mean the build number), because I used to get similar errors, and still do. However this is on a system which couldn't even open AVI files in the 1.10 version, so... Cursed. ;_;

__________________

"Light and shadow don't battle each other, because they're two sides of the same coin"

I believe that's 2.0 (though I suppose you mean the build number), because I used to get similar errors, and still do. However this is on a system which couldn't even open AVI files in the 1.10 version, so... Cursed. ;_;

How about you tell WHAT those error messages say? Lots and lots of things can go wrong, you need to tell what error you get for anyone to be able to help you at all. (Sometimes just reading the message yourself is enough to tell what the solution would be.)

There has, for several weeks now, been a message right next to the Aegisub 2 r1564 download link which says:

Quote:

There is a minor bug in this version: A wrong build of VSFilter is distributed with it, and it might not work on all systems, resulting in no subtitle display. Download and install this package to correct the problem. The package required to make VSFilter work will also be required for later versions of Aegisub, but will be distributed as part of the installer then.

You need to do that on ALL Windows versions. If you aren't sure whether you have it already or not it's safe to just install it either way.

Also, there is a bug in r1564 and earlier versions where it doesn't look in the correct location for VSFilter when using it through AviSynth (the default) - usually this won't be a problem, because it will also attempt to use the system VSFilter, assuming one is installed. If you do not have VSFilter registered as a DirectShow filter, Aegisub might not be able to find it at all. The workaround is to put a copy of VSFilter.dll into the same folder as Aegisub.exe - there has to be one in both that folder and in the "csri" subfolder.
This will be fixed in the next build.

And note that r1564 says "1560" in its title bar, this is a minor glitch and doesn't mean anything, it is 1564 despite this.

Hey, I had a quick question regarding scene-timing in Aegisub that you guys might be able to answer.

When I load certain videos (XviD) sometimes the scenes won't appear, making it impossible to scene-time.
This only happens with certain raws, and not all but the ones I have experienced were with XviD.

Is there a way to force Aegisub to detect scene changes?
Do I have to re-encode the vid?

Aegisub can unfortunately not read keyframa data from AVI files that only have OpenDML indexes. This will change in a later version, but probably not as one of the first things.
If you re-write the file with VirtualDub (just use direct stream copy on both video and audio) you should get a file Aegisub can use, assuming it's smaller than 2 GB.

Aegisub can unfortunately not read keyframa data from AVI files that only have OpenDML indexes. This will change in a later version, but probably not as one of the first things.
If you re-write the file with VirtualDub (just use direct stream copy on both video and audio) you should get a file Aegisub can use, assuming it's smaller than 2 GB.

I have another quesiton about Aegisub's Unicode support. I tried to use Vietnamese keyboard to type in Aegisub, but the character will disappear whenever I use a special character, like á, à, ả, ã, â,...