Chez_Wimpy
21st December 2003, 11:12
I noticed that my batch encodes using 1.5.10.1 version of Virtualdub mod result in video files with the same length in minutes and seconds... the same as the initial run on a set of jobs. For example, were I to encode a 2 hour avs file named "test.avs" then reset the "Done" jobs back to "Waiting", a 30 minute file now called by test.avs would result in 30 minutes of video and 90 minutes of black in the new avi. It appears that the range of the clip to be encoded is now recorded when a file is first added to the batch, meaning that subsequent encodes using the same Job (I very often use the "All Done => Waiting" function) are limited to the same length. This is a problem in that I am often encoding programs of variable length, yet using the same compression settings, with the same .avs script.
Is this a bug, or a change in the direction of avisynth? If the later, I suppose I will drop back to 1.5.4.1 for the rest of my encodes. The "All Done => Waiting" shortcut saved me a lot of time loading and reloading scripts when the compression settings were otherwise the same.
-CTB
Is this a bug, or a change in the direction of avisynth? If the later, I suppose I will drop back to 1.5.4.1 for the rest of my encodes. The "All Done => Waiting" shortcut saved me a lot of time loading and reloading scripts when the compression settings were otherwise the same.
-CTB