-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't use Trim Anymore! #49
Comments
Do you have the log? Hard to diagnose with no info. |
maybe I have same problem, here is my logs:
|
I got the same error as @Subarashii-no-Fansub earlier today. Using the a-mo version 1.0.9, x264:
|
I'm not even getting an error message. Using x264, I just get the cmd.exe pop up, and it sits there, does nothing If I close it, I get this error, with no actual output. And it just outputs a 0 byte file. Completely new install of Aegis r8903+1 with Dependency Control, and Aegisub-motion 1.0.9. I've tested running x264 by itself and was able to encode 5 frames of a video without any issues. Edit: Well.. now I can't even run x264 by itself anymore. Just doesn't do anything. I give up, I'm cursed. Edit2: Ok, trim works, but it runs unbelievably slow for some god forsaken reason. |
Finally I have a x264 without trim? or something else that it does not support. using another x264 build fix my problem |
Encoding error:
Encoding Failed. Log has been printed to progress windows.
What happen to my A.motion? Last week i can use it, then this week i got this problem that nobody know how to solve it?
Unistall and Install Aegisub, Reopen Aegisub, Install A.mo again, all of that didn't work a bit.
The text was updated successfully, but these errors were encountered: