Originally posted by NobodyXu
View Post
Announcement
Collapse
No announcement yet.
Google Releases AOM-AV1 v3.3 Video Encoder Update With Performance Improvements
Collapse
X
-
Originally posted by Spacefish View Post
I just speculated, that a CPU only supporting SSE2 but not AVX is probably very old.. Using a mix of AVX/SSE is typically really slow, as changing between the modes ist expensive. At least on Intel / AMD x86.
So there are two groups:
- People with CPU older than ~6-7 years who probably won´t do AV1 encoding as the CPU is too slow to do it / it takes ages / is not ussable for live video encoding in video conferencing.
- People with CPUs that do support AVX and will use the AVX-Codepath and not SSE2..
So there is no realworld usecase for the SSE2 Encoder Codepath IMHO.. Decoding yes, but encoding?
It will be a long, long time before distributions can compile for x86-64_v3. If Intel wanted to get any credit for their fancy-pants instruction set extensions, they shouldn't have used them for market segmentation.
- Likes 2
Comment
-
Originally posted by sophisticles View PostI would not do any serious AV1 encoding on a cpu, just testing.
Wait for hardware encoders to be included on video cards.
- Likes 1
Comment
-
Originally posted by yump View PostThe range of quality/bitrate efficiency from hardware encoders has historically ranged from terrible to, "pretty impressive, for a realtime encode". Do you have any reason to expect the AV1 encoders to land more toward the good end of the spectrum or even beat CPUs for offline encoding?
X264, and z265, started out horrible,, both in quality and speed and slowly improved from there.
Now, no one wants to spend huge bucks building a power hungry pc to encode AV1 in real time, they want speed and efficiency.
I expect the first publicly available AV1 encoders to be able to match x265 and SVT-HEVC in quality and only improve from there.
Comment
-
Originally posted by NobodyXu View Post
Using encoding like AV1, it can reduce the time it takes to download video.
This is especially true if your network is slow.
The reason this effects your network is also the same reason behind it taking up more space on servers (i.e. its bigger). They are both related.
@cl333r Is right, Google uses AV1 is because the video files for the same perceptive quality takes up less room on the servers which also reduces the network bandwidth requirements (for the same reason). And yes this is being offloaded to users who are paying for it by hogging their CPU since hardware acceleration for AV1 is still kinda non existent in consumer hardware.
I don't really blame google though, the amount of capital required to run Youtube is ginormous considering its a free service, even taking into account the money they are making off of it via advertising. Video streaming/hosting is like airlines, its so demanding in this regard that most companies in this business are lucky to break even.
Comment
-
Originally posted by sophisticles View PostI would not do any serious AV1 encoding on a cpu, just testing.
Wait for hardware encoders to be included on video cards.
Comment
-
Originally posted by mdedetrich View PostGoogle uses AV1 is because the video files for the same perceptive quality takes up less room on the servers which also reduces the network bandwidth requirements
The size decrease for the same quality is great though since it means more users get access to videos on metered or poor quality connections.
- Likes 1
Comment
-
Originally posted by Orphis View Post
No, you don't only keep an AV1 copy. You have all the other versions as well stored. AV1 increase the storage requirements and the processing time needed to encode videos. So each new codec is detrimental to storage space, but that's usually not a big factor.
The size decrease for the same quality is great though since it means more users get access to videos on metered or poor quality connections.
Not that I have *any* issue with that. More quality from YT is great.
Comment
Comment