Closed VegethB closed 3 years ago
Can you paste the script's output from the Aegisub log window?
I'm not understanding anything anymore 🤣😵 Yesterday I was behind the trim of motion and encode clips all day, here are the results: After a restart, to have only the two written:
Raw video clip; Clip with subtitle;
All options appeared (strange because I had installed scripts months ago but never used it until yesterday). But now from "feedDump" mpv also wants it in "log". Without it it doesn't work. I have already tried to put mpv in the windows path but it doesn't want to see it, so I had to put 2 MPV, one in FeedDump and one in Log.
New problem: For some clips the number of exported frames is wrong (for example I have a 54frame scene in the subs and in the video, but export a 52frame clip).
As you may have noticed from this log, it didn't even export. This is because when it gets the video directory, it fetches it from the garbage in the script. Which is out of date if I open a script that was passed to me by others, because there will be the destination used by that person and not my open video file now.
It's a problem because I opened the subs from the video.
To solve I have to:
Save the .ass somewhere;
Re open the video.
At that point, in the garbage, the new video location (which I am using) on aegisub is saved now.
Now that I've "solved" this little setback,
As you found out, the script is not intended for use with subtitles loaded from video. I think you can open the video file again in Aegisub (after loading the subtitles from it) to set the correct video file in the properties, though.
To my knowledge, it is not possible to get the path to the currently open video otherwise.
Yesterday I was behind the trim of motion and encode clips all day, here are the results: After a restart, to have only the two written: Raw video clip; Clip with subtitle; All options appeared (strange because I had installed scripts months ago but never used it until yesterday).
Are you saying that you previously had only those two options, but after restarting Aegisub you have all the modes (audio only, four video modes, GUI)? That would be caused by DependencyControl automatically downloading a new version of the script when you run it (but it needs to be reloaded, which doesn't happen automatically).
This would also explain how you previously ended up with subtitles in the raw clip. A prior version of Encode Clip didn't actually disable subtitles, if the original video file happened to have them.
There are obvious problems with the export command: It changed framerate from the usual 23.976 to a 24.434; He used VRF instead of CRF (and export quality is too low, 120kb for 2 seconds vs 4mb for 2 seconds on ffmpeg with CRF 4);
VFR seems to happen because the export isn't exactly lined up with the frames. The actual video should still be 23.976 fps except for the very first and last frames. I will look into this more, but I don't see it being a problem.
120 KB seems like a reasonable size for a two-second clip. This is not meant for making trims for use in motion tracking, it's more meant for easily rendering a short clip to show subtitles/audio or similar.
I exported with the GUI and removed the ticks on Audio and Subs but the audio is still present.
Seems interesting. The log output shows the audio options being enabled (--oac=aac_mf --oacopts="b=256k,frame_size=1024"
, as well as the filename not including _noaudio
). However, I can't replicate this behaviour.
Without it it doesn't work. I have already tried to put mpv in the windows path but it doesn't want to see it, so I had to put 2 MPV, one in FeedDump and one in Log.
This should not be necessary, if mpv is correctly on your system path. You might need to restart Aegisub (and possibly log out) after making changes to your path variable, though.
Are you saying that you previously had only those two options, but after restarting Aegisub you have all the modes (audio only, four video modes, GUI)?
👍 😆
VFR seems to happen because the export isn't exactly lined up with the frames. The actual video should still be 23.976 fps except for the very first and last frames. I will look into this more, but I don't see it being a problem.
I don't know how to explain, I didn't mean problem as "big mistake", but that something doesn't seem to work as expected. On FFMpeg with the -vframe option you are able to export the exact number of selected frames (I saw that mpv includes a build of ffmpeg, so with that command in theory it would solve the problem).
120 KB seems like a reasonable size for a two-second clip. This is not meant for making trims for use in motion tracking, it's more meant for easily rendering a short clip to show subtitles/audio or similar.
I can't argue 😂. In desperation to create the trim ffmpeg command, I was handed this script but not what I thought from the name it was obvious what it was for. Thinking about how it was designed, it does its duty (except for MPV who just don't want to find it).
Seems interesting. The log output shows the audio options being enabled (--oac=aac_mf --oacopts="b=256k,frame_size=1024", as well as the filename not including _noaudio). However, I can't replicate this behaviour.
It must have been my oversight then.
This should not be necessary, if mpv is correctly on your system path. You might need to restart Aegisub (and possibly log out) after making changes to your path variable, though.
I changed MPV path and rebooted, now it works 🙃, thanks.
In the end, somehow it's working. The only things I report: VRF and the 2 frames skipped from the selection. Thanks anyway, hopefully they will update Aegisub to 3.3.0 soon as they need it (especially with MKS).
It is likely that I did not understand how this script works but when in doubt I write the problem. Technically it should create sequences based on the selected times using MPV (which I put in the feedDump folder) latest version for windows. Whether you use RAW or subtitle mode he exports the clip with subs overlayed.