qyot27
15th September 2008, 16:25
I've been trying out avs2avi for the last few days as an alternative to converting files to HuffYUV (YV12). And it works well enough.
But, depending on certain factors, it errors with no warning and shuts down. However, this is only the case when:
A) The script calls FFmpegSource or AVISource rather than DirectShowSource - I don't know if other source filters are affected
B) I use a full commandline, ex.
avs2avi "script.avs" "script.avi" -c ffds
If I only call the script itself, eschew the destination filename, and allow avs2avi to call the codec selector, then things are fine. Of course, that also means it asks me for the codec at every new line/encode, which defeats the purpose of doing it in batch (sort of - if I'm batch encoding, I'd rather it not ask me anything at all). I'm fairly sure using DirectShowSource had no issue when a full commandline was used, but I can't really remember.
If there was something more substantial about the error messages to post, then I'd attach that, but unfortunately it doesn't say anything at all, save for the error messages I also get from wavi when using FFmpegSource with MOVs like the majority of those I was trying to convert* (along with maybe a handful of MP4s and MKVs) - and that never stopped wavi from doing its job correctly.
*mainly the 1080p trailers from the Quicktime site, for reference's sake
Any suggestions? If not, I'll just go ahead and see about using ffmpeg itself to do it, but I would like to know what the underlying issue for avs2avi is here.
But, depending on certain factors, it errors with no warning and shuts down. However, this is only the case when:
A) The script calls FFmpegSource or AVISource rather than DirectShowSource - I don't know if other source filters are affected
B) I use a full commandline, ex.
avs2avi "script.avs" "script.avi" -c ffds
If I only call the script itself, eschew the destination filename, and allow avs2avi to call the codec selector, then things are fine. Of course, that also means it asks me for the codec at every new line/encode, which defeats the purpose of doing it in batch (sort of - if I'm batch encoding, I'd rather it not ask me anything at all). I'm fairly sure using DirectShowSource had no issue when a full commandline was used, but I can't really remember.
If there was something more substantial about the error messages to post, then I'd attach that, but unfortunately it doesn't say anything at all, save for the error messages I also get from wavi when using FFmpegSource with MOVs like the majority of those I was trying to convert* (along with maybe a handful of MP4s and MKVs) - and that never stopped wavi from doing its job correctly.
*mainly the 1080p trailers from the Quicktime site, for reference's sake
Any suggestions? If not, I'll just go ahead and see about using ffmpeg itself to do it, but I would like to know what the underlying issue for avs2avi is here.