[elit]

Thank you Felice looks great! Pls make sure you implement batch processing as well! I believe there is already xmediarecode frontend to ffmpeg which is quite complex but its always good to have options. Also UI kept freezing for me on that one so if your app have options I need and doesnt give problems I would definitely love to use it instead of command line.

Now as for me, I am against filters, they dont improve anything universally. They improve specific scenes while introducing artifacts to others. They dont operate on context and will never understand underlying content of the video. They can probably be useful if you process already lower quality videos especially with artifacts in it, but for scaling from HQ to LQ it doesnt make much sense to bloat encoder with filters since you can only do so much to universally improve pixel scaler.

I prefer clean, classic pixel scaling to appropriate bitrate and as low as possible to save space until its still bearable. I found 320k to 640x360 res. perfect and universal among different modern codecs(bik, bk2, h264, h265, vp9,...). I want to see at least 3x-4x of saved space and sometimes like above I got in several 10ths to 1. When I tried higher bitrate on multiple sources, I had to go significantly higher to register noticeable improvement but then size started to almost double. Also when lowering it further, drop in quality and especially pixelation became noticeable.

For 640x360 resolution, 320k is just enough, 1920x1080 have 9x more pixels to process so to compare it 9x 320k bitrate mean 320k bitrate for 640x360 res. would be equivalent to 2880k bitrate for 1920x1080. Which, I think we agree should be more than enough.