fields_g
4th April 2007, 15:54
I've noticed a little bug on a couple of systems now that has eaten several hours of encoding tests. At first I thought I was me just crazy and not being careful, but it seems to be MeGUI.
After loading the AVS script in the video portion, I rename the output file below to something else (in my case something descriptive of the encoding params tested). I found that I wasn't getting any other filename as output, only what the AVS file was called.
For example: test.avs loaded, rename output to output.mp4. Actual file created is test.mp4. The command line inside MeGUI shows test.mp4, as well as the queue screen (which is wrong).
I know of some workarounds such as copying and renaming the AVS file or renaming the output after each encode, but this isn't the intended use of MeGUI.
Anyone else confirm this issue?
After loading the AVS script in the video portion, I rename the output file below to something else (in my case something descriptive of the encoding params tested). I found that I wasn't getting any other filename as output, only what the AVS file was called.
For example: test.avs loaded, rename output to output.mp4. Actual file created is test.mp4. The command line inside MeGUI shows test.mp4, as well as the queue screen (which is wrong).
I know of some workarounds such as copying and renaming the AVS file or renaming the output after each encode, but this isn't the intended use of MeGUI.
Anyone else confirm this issue?