I have a huge number of low-res Flash videos (480x270, 30 fps, 800 Kbps) and I want to resample all those videos in 1280x720 with some added spatial sharpening and lomo filters to make them look nicer. I intend to store these larger videos on a HDD and also upload them on YouTube.

The total running time of the videos is around 50 days, so I'm not going to use a lossless codec. I experimented a bit and found that anything over 2 Mbps (H.264) didn't result in a noticeable increase in visual quality, which isn't surprising considering the tiny original resolution. 50 days at 2 Mbps is about 1 TB which would be great.

The problem is that YouTube seems hell-bent on re-encoding anything that is being uploaded regardless of the actual bitrate, so even though the local 1280x720 videos look great the uploaded 1280x720 videos look awful. I found some official recommended upload encoding settings but using those settings still results in compression artefacts.

How can I avoid the artefacts from YouTube's lossy re-encode without uploading videos of a significantly higher bitrate?

(I'm currently using Avidemux for resampling/re-encoding but from what I've read most people use Handbrake or MeGUI; should I switch or is Avidemux fine for my purposes?)

  • Youtube will necessarily transcode everything you upload. Before wasting a lot of time trying out different H.264 bitrates and encoding flags, transcode one of the clips to 720p using a lossless codec and upload that. See how much difference does make that on Youtube. That will set the ceiling on what you can expect.
    – Gyan
    Mar 15, 2016 at 19:23

1 Answer 1


Youtube applies different maximum bitrates to different HD formats. A lot of people these days upscale their original 1080p HD content to 4k, since youtube allows higher datarate for 4k. Probably the same applies to 720p vs. 1080p, you should check. In general, you can optimize a video a lot so the same bitrate encoding will result in better quality, mainly by denoising it beforehand - or in you case, deblocking. I don't know if you are aquainted with AviSynth etc. but there are a couple of deblocking filters for it which might come in handy. From my experience there is no big difference if uploading a h264 with a high bitrate (like 25Mbps) or a ProRes file, after Youtube recompression quality is the same.

  • Could you expand a bit on the denoising & deblocking bit? In particular, Avidemux handles denoising with filters and I have no idea which of the 7 denoising filters to use, and if the denoising filter should be loaded before or after other filters like resampling and sharpening for the best quality/bitrate. Edit: Wait, I see only 3 of those filters seem to actually be denoising filters; "FluxSmooth", "Mplayer Denoise 3D" and "Mplayer Denoise 3D HQ". The HQ filter has the most options but I don't know what those options do.
    – And G
    Mar 15, 2016 at 20:48
  • I am assuming that at 800kbit your flv files show quite some compression artifacts. The problem is that these are not well "compressible"... Mar 15, 2016 at 20:50
  • I'm general, technical noise (imagine all possible values of a signal in random order) is not well compressible since same values rarely happen in succession and therefore cannot be reduced well. So denoising a video works wonders in terms of getting a better result. H264 does denoising in general during compression, so I guess noise will not be the problem in your clips but rather the compression artifacts. Mar 15, 2016 at 20:54
  • Generally speaking the best denoisers use a wavelet algorithm, so check if one of the denoisers that come with avidemux uses that technology (if your clips have noise) - as for deblocking maybe do some tests with this filter: compression.ru/video/deblocking/index_en.html Mar 15, 2016 at 20:58
  • Well the original videos actually don't have many compression artefacts; after all 800 Kbps is quite good for 480x270. For reference, YouTube suggests 300-700 Kbps for 240p.
    – And G
    Mar 15, 2016 at 21:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.