for rendering animations it would be a huge timesaver and also be much safer to have export dimensions,that are preferably also saved in the document. This has a few benedfits. It will keep your sourcefile intact,and speed up exporting for big files. We can indeed just resize manually,but that is a dangerous proposition when in the midst of working you can forget that you resized at all,and continued working on the smaller sized file. Not only do you run the risk of doing wasteful work,you can loose your original bigger file if you save too often.
To what format are you rendering? Anything but gif, and you should be able to add a custom ffmpeg commandline option in the settings dialog that scales the output.
(In reply to Boudewijn Rempt from comment #1) > To what format are you rendering? Anything but gif, and you should be able > to add a custom ffmpeg commandline option in the settings dialog that scales > the output. I see, does that get saved in the file ,though? I will need to test this first. if it works the urgency will be less high. But having a graphical input box would be preferable to some code in a narrow text field where you need to be very careful not to delete a single character by mistake. And you only realise that mistake after a lengthy export process. Since you cant point to existing pngs to encode(another wish i have),messing with the code can result in lots of trial and error. I have already done so. I have also already encoded . manually,it works. Ut really takes you out of krita which is time waste when you're painting. Few normal users are technical enough to manage it
A second reason to do the scale in the krita settings itself rather then with FFMPEG is that you can APPLY the image resize BEFORE export. If you do it AFTER, export will be MUCH slower.
Krita 4.0 has the ability to export out videos with different width, height, and FPS than your original animation settings.