I use a 1080p monitor and what I’ve noticed is that once creators start uploading 4k content the 1080p version that I watch on fullscreen has more artifacting than when they only uploaded in 1080p.
Did you notice that as well?
Watching in 1440p on a 1080p monitor results in a much better image, to the detriment of theoretically less sharper image and a lot higher CPU usage.
I believe YouTube always re-encodes the video, so the video will contain (extra) compression artefacts even if you’re watching at the original resolution. However, I also believe YouTube’s exact compression parameters aren’t public, so I don’t believe anyone outside of YouTube itself knows for sure which videos are compressed in which ways.
What I do know is that different content also compresses in different ways, simply because the video can be easier/harder to compress. IIRC, shows like last week tonight (mostly static camera looking at a host) are way easier to compress than higher paced content, which (depending on previously mentioned unknown parameters) could have a large impact on the amount of artefacts. This makes it more difficult to compare different video’s uploaded at their different resolutions.
You are right. For example you can upload an avi to YouTube, but they will never host and stream an avi.
AVI is a container, not a codec. An AVI container can contain video encoded with any kind of codec (unlike some other container formats, which are more restrictive). If you want to, you could put e.g. a VP9 or AV1 video stream (so the ones that YouTube is using) into an AVI container. In theory at least, if you uploaded an AVI file containing VP9 video, YouTube could just extract it from the container and stream it as is, but they’ll still re-encode it. Before you think that all of this talk of modern codecs in AVI containers is theoretical, AVI is used a a standard for archiving with some institutions, so it’s more relevant than you might think.
However, you are partially right in that AVI can not be used for streaming, not just by YouTube, but in general, since this requirement obviously wasn’t taken into account when it was introduced in 1992 and thus not incorporated into this standard.
Just to be clear it is probably a good thing that YouTube re-encodes all videos. Videos are a highly complex format and decoders are prone to security vulnerabilities. By transcoding everything (in a controlled sandbox) YouTube takes most of this risk on and makes it highly unlikely that the resulting video that they serve to the general public is able to exploit any bugs in decoders.
Plus YouTube serves videos in a variety of formats and resolutions (and now different bitrates within a resolution). So even if they did try to preserve the original encoding where possible you wouldn’t get it most of the time because there is a better match for your device.
I agree that, theoretically speaking, YouTube might be protecting some end users from this type of attack. However, the main reason YouTube re-encodes video is to reduce (their) bandwidth usage. I think it’s very kind towards YouTube to view this as a free service to the general public, when it’s mostly a cost-cutting measure.