Upgrading to 2.3.0 and removing the slash fixed it. Okay, i’ve found the problem: it’s either a 2.2.0 having this bug or a closing slash in the output path. I’m currently downloading 2.3.0 to check if it’s changed, but there’s nothing about it in release notes anyway. Putting “png” after “-f” into quotation marks doesn’t fix it either. * 16 bit tiff is usually rather large, please make sure you have enough hard >drive space available Mov - ProRes HQ encoded video file (high-quality)Ĩtif - for 8 bit uncompressed tiff sequenceġ6tif - (default) for 16 bit uncompressed tiff sequence Mp4 - H.263 encoded video file (low-quality) I’m pretty sure that’s incorrect place for an “-f” argument, but putting it in a right place like this: "veai.exe" -i "path\test.mp4" -o "path\" -f png -b 101842 -s 1.0 -m alq-13 -c 1 Here’s an example of a CMD call that runs JPG upscale regardless of what i’ve set: "veai.exe" -i "path\test.mp4" -f png -o "path\" -b 101842 -s 1.0 -m alq-13 -c 1 I’ve noticed 2 of my last upscales are in JPG format where i requested PNG (i’m using an AHK script that sets it so there’s no mistake on my end). I’ve got a strange bug since 2.2.0 when i can’t set an output format correctly.
0 kommentar(er)
