Facebook (Instagram) no longer uses x264!

[PCU]

Facebook (Instagram) no longer uses x264!

File downloaded from Insta:

Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/avc1/mp41)
File size : 817 KiB
Duration : 13 s 488 ms
Overall bit rate mode : Variable
Overall bit rate : 496 kb/s

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L3.1
Format settings : CABAC / 5 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference fra : 5 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 13 s 367 ms
Bit rate : 445 kb/s
Maximum bit rate : 707 kb/s
Width : 652 pixels
Height : 1 160 pixels
Display aspect ratio : 0.562
Frame rate mode : Constant
Frame rate : 30.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.020
Stream size : 727 KiB (89%)
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Codec configuration box : avcC

Audio
ID : 2
Format : AAC LC SBR
Format/Info : Advanced Audio Codec Low Complexity with Spectral Band Replication
Commercial name : HE-AAC
Format settings : NBC
Codec ID : mp4a-40-5
Duration : 13 s 488 ms
Duration_LastFrame : -26 ms
Bit rate mode : Variable
Bit rate : 48.0 kb/s
Maximum bit rate : 55.7 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 44.1 kHz
Frame rate : 21.533 FPS (2048 SPF)
Compression mode : Lossy
Stream size : 78.4 KiB (10%)
Default : Yes
Alternate group : 1

[Blue_MiSfit]

What makes you think that? They may very well be using another encoder, but they might be just not writing the x264 info SEI

[PCU]

Because until a few months ago, MediaInfo showed x264 settings.

[FranceBB]

Open it with an HEX editor like CFF Explorer. Sometimes mediainfo alone isn't enough.
Besides I don't think Facebook encodes anything, they're probably relying on some third party service to encode everything like akamai, Aws, Bitmovin etc. Perhaps they changed whatever they were using. Chances are that if it ain't x264, then it's very likely to be MainConcept

[LoRd_MuldeR]

Because until a few months ago, MediaInfo showed x264 specs.

The reason why MediaInfo and similar tools can show "x264 specs" is that the x264 encoder, by default, embeds that information into the H.264 stream, as a custom SEI message.

H.264 decoders simply ignore this "unknown" custom SEI message. MediaInfo knows what to look for and how to interpret it. Anyway, the custom SEI message is not needed by any means; it's just some "diagnostic" information.

Therefore, x264 could trivially be modified to not write the custom SEI message. Or the custom SEI message could be removed – intentionally or incidental – by whatever MP4(?) muxer they use.

So, as Blue_MiSfit already pointed out, the lack of x264 custom SEI message alone is not a prove that the stream wasn't created by x264. An x264 developer probably could tell by looking at the stream in detail though...

[PCU]

The reason why MediaInfo and similar tools can show "x264 specs" is that the x264 encoder, by default, embeds that information into the H.264 stream, as a custom SEI message.

H.264 decoders simply ignore this "unknown" custom SEI message. MediaInfo knows what to look for and how to interpret it. Anyway, the custom SEI message is not needed by any means; it's just some "diagnostic" information.

Therefore, x264 could trivially be modified to not write the custom SEI message. Or the custom SEI message could be removed – intentionally or incidental – by whatever MP4(?) muxer they use.

So, as Blue_MiSfit already pointed out, the lack of x264 custom SEI message alone is not a prove that the stream wasn't created by x264. An x264 developer probably could tell by looking at the stream in detail though...

Strange!: some Insta videos are MKV (VP9/HE-AAC)
Here is the MP4 file downloaded from Tesla Page: (Lavf58.20.100)
https://www.mediafire.com/file/5fkdz7i8vdff97p/Tesla+(@teslamotors)+%E2%80%A2+Instagram+photos+and+videos.mp4/file

Insta is switching to: MKV (VP9/AAC)!

[FranceBB]

Insta is switching to: MKV (VP9/AAC)!

MPEG-LA, making yet another company fly away from MPEG Codecs... :(

[benwaggoner]

MPEG-LA, making yet another company fly away from MPEG Codecs... :(
Facebook has been saying they're doing that for years. But with so many devices without VP9 or AV1, H.264 remains the only codec one can encode to if one wants to encode just one thing. Beyond H.264 requires either a multi-codec strategy or a limited set of players (I think Apple TV is only HEVC, and just isn't available on non-HEVC devices).

Doing multi-codec VP9 isn't such a big deal for web browsers and short form user-generated content without DRM, as the major browsers all include software VP9 decoders. It's movie-length content (due to battery life) and premium content (due to hardware DRM requirements) where using real hardware decoders makes a big difference.

[PCU]

Soon everyone is using MKV (AV1/Opus), no one knows the exact time. I don't think anyone will use H.266 in the future.
It's like FLAC vs: WMAL, MLP, MPEG-4 ALS, MPEG-4 SLS, RealAudio Lossless, ATRAC Advanced Lossless, mp3HD, etc!
Apple is using a codec that it designed on the iPhone 13 and I think all iPhones 14: ProRes.
On Android: needless to say: AV1/Opus.

[Blue_MiSfit]

Besides I don't think Facebook encodes anything, they're probably relying on some third party service to encode everything like akamai, Aws, Bitmovin etc.

Oh no, they absolutely do their own encoding. Dave Ronca of Netflix fame runs their encoding team.

The amount of video they serve is staggering, so I'm certain they spend a lot of time optimizing this.

Here's their blog: https://engineering.fb.com/category/video-engineering/

[PCU]

How we used to encode video on Facebook
Traditionally, once a video is uploaded to Facebook, the process to enable ABR kicks in and the original video is quickly re-encoded into multiple resolutions (e.g., 360p, 480p, 720p, 1080p). Once the encodings are made, Facebook’s video encoding system tries to further improve the viewing experience by using more advanced codecs, such as VP9, or more expensive “recipes” (a video industry term for fine-tuning transcoding parameters), such as H264 very slow profile, to compress the video file as much as possible. Different transcoding technologies (using different codec types or codec parameters) have different trade-offs between compression efficiency, visual quality, and how much computing power is needed.

The question of how to order jobs in a way that maximizes the overall experience for everyone has already been top of mind. Facebook has a specialized encoding compute pool and dispatcher. It accepts encoding job requests that have a priority value attached to them and puts them into a priority queue where higher-priority encoding tasks are processed first. The video encoding system’s job is then to assign the right priority to each task. It did so by following a list of simple, hard-coded rules. Encoding tasks could be assigned a priority based on a number of factors, including whether a video is a licensed music video, whether the video is for a product, and how many friends or followers the video’s owner has.

But there were disadvantages to this approach. As new video codecs became available, it meant expanding the number of rules that needed to be maintained and tweaked. Since different codecs and recipes have different computing requirements, visual quality, and compression performance trade-offs, it is impossible to fully optimize the end user experience by a coarse-grained set of rules.

And, perhaps most important, Facebook’s video consumption pattern is extremely skewed, meaning Facebook videos are uploaded by people and pages that have a wide spectrum in terms of their number of friends or followers. Compare the Facebook page of a big company like Disney with that of a vlogger that might have 200 followers. The vlogger can upload their video at the same time, but Disney’s video is likely to get more watch time. However, any video can go viral even if the uploader has a small following. The challenge is to support content creators of all sizes, not just those with the largest audiences, while also acknowledging the reality that having a large audience also likely means more views and longer watch times.

[FranceBB]

Apple is using a codec that it designed on the iPhone 13 and I think all iPhones 14: ProRes.

Speaking of ProRes, Apple has been more and more bastard-ish by artificially blocking perfectly valid ProRes files encoded by anything that isn't an Apple approved encoder.
For instance, FFMpeg files are all blocked on Apple devices unless you spoof the writing library as Apple with:

-vendor apl0

Soon everyone is using MKV (AV1/Opus), no one knows the exact time.


Uhm... I wouldn't be so sure about it.

I don't think anyone will use H.266 in the future.

Except for broadcasters and studios for the next generation of TX and BD, which is probably gonna be 8K 50p 12bit HDR PQ BT2100 in PAL territories and 8K 60p 12bit HDR PQ BT2100 in NTSC territories, both in H.266.
Still, MPEG-LA should really be learning from the mistakes of the past and open up a bit if they wanna see a wider adoption of H.266 VVC, unless, of course, they don't care about anything other than the broadcasting market... :/

Oh no, they absolutely do their own encoding. Dave Ronca of Netflix fame runs their encoding team.
The amount of video they serve is staggering, so I'm certain they spend a lot of time optimizing this.

Ah! I didn't know that.

Once the encodings are made, Facebook’s video encoding system tries to further improve the viewing experience

Whatever. I've uploaded 3840x2160 60p yv12 8bit planar Linear BT709 SDR H.265 100 Mbit/s recordings of me diving on Facebook this summer and it literally DESTROYED everything.
First of all, they downscaled to 1280x720, the dropped the framerate from 60p to 30p and they re-encoded with such a low bitrate that all the algae and the fish hiding became a macroblock mess. Very disappointed. The reason is that you can upload vertical videos in 1080p, but not horizontal ones (horizontal ones get downscaled to 720p). This sort of compression and resize might be ok for people taking selfies and posting stories with the front camera in vertical and with thousands of useless filters, but for not for general purpose contents like the one I posted.

[ognirats]

Format : AVC
Format/Info : Advanced Video Codec

Isn't AVC just h264?

[FranceBB]

Isn't AVC just h264?

Yes, AVC is H.264, just like HEVC is H.265 and VVC is H.266 eheheheh

[benwaggoner]

Except for broadcasters and studios for the next generation of TX and BD, which is probably gonna be 8K 50p 12bit HDR PQ BT2100 in PAL territories and 8K 60p 12bit HDR PQ BT2100 in NTSC territories, both in H.266.
I don't know of any broadcasters outside of major TV-exporting countries talking about 8K broadcasting at all. Even 4K broadcasting (as in terrestrial/cable/sat) remains pretty rare due to the bandwidth requirements. Of course, VVC is capable of doing 4K in less bandwidth than AVC 1080p. In the end, there really isn't evidence of moving image content that customers can discriminate between a 4K and an 8K encode watching on an 8K screen.

Still, MPEG-LA should really be learning from the mistakes of the past and open up a bit if they wanna see a wider adoption of H.266 VVC, unless, of course, they don't care about anything other than the broadcasting market... :/
If only it was just MPEG-LA. The problem with HEVC is all the patent holders who went to MPEG Advance and the other one instead of doing everything through MPEG-LA, who was quite successful with MPEG-2 and AVC.

[ksec]

Oh no, they absolutely do their own encoding. Dave Ronca of Netflix fame runs their encoding team.

The amount of video they serve is staggering, so I'm certain they spend a lot of time optimizing this.

Here's their blog: https://engineering.fb.com/category/video-engineering/

Yes and he was the one who help push FB to VP9. But considering 95%+ of their traffic are from Mobile, and vast majority of Mobile sans Apple have support for VP9. It make sense to switch to VP9 for them. This is very different to Youtube where they have access from TV, Mobile, Desktop and Tablet.

And before TikTok was a thing FB was the largest competitor to Youtube in terms of Online Video.

Luckily they stayed away from AVIF and seems to be pushing for JPEG-XL.

[benwaggoner]

Yes and he was the one who help push FB to VP9. But considering 95%+ of their traffic are from Mobile, and vast majority of Mobile sans Apple have support for VP9. It make sense to switch to VP9 for them. This is very different to Youtube where they have access from TV, Mobile, Desktop and Tablet.I would have thought that >>10% of Facebook video would be desktop. Of course, Chrome, Firefox, and Edge all support VP9 as well. It's really living room devices where there might not be VP9 decoders.

Luckily they stayed away from AVIF and seems to be pushing for JPEG-XL.
What is that lucky?

[PCU]

https://www.guru3d.com/news-story/netflix-starts-streaming-content-to-tvs-though-av1-codec.html

Netflix starts streaming content to TVs though AV1 codec
by Hilbert Hagedoorn on: 11/11/2021 09:41 AM | source: netflixtechblog | 2 comment(s)
Netflix starts streaming content to TVs though AV1 codec
Netflix has begun broadcasting content that has been encoded with the AV1 codec. In this case, it is specifically about streaming to televisions and not smartphones.

AV1 is the first high-efficiency video codec format with a royalty-free license from Alliance of Open Media (AOMedia), made possible by wide-ranging industry commitment of expertise and resources. Netflix is proud to be a founding member of AOMedia and a key contributor to the development of AV1. The specification of AV1 was published in 2018. Since then, we have been working hard to bring AV1 streaming to Netflix members. Netflix said that all of its AV1 streams are encoded in 10-bit and in the highest available resolution and frame rate including HFR – but not yet HDR. Netflix did not specify bitrates other than saying that "AV1 delivers videos with improved visual quality at the same bitrate" compared to MPEG4 and HEVC and that "some streams have a peak bitrate close to the upper limit allowed by the spec", which probably refers to AV1 level 5.0 (30 Mb/s bitrate for Main) or level 5.1 (40 Mb/s bitrate for Main).

- "Today we are excited to announce that Netflix has started streaming AV1 to TVs. With this advanced encoding format, we are confident that Netflix can deliver an even more amazing experience to our members," Netflix wrote in a blog post. "We compared AV1 to other codecs over thousands of Netflix titles, and saw significant compression efficiency improvements from AV1."

In February 2020, Netflix started streaming AV1 to the Android mobile app. The Android launch leveraged the open-source software decoder dav1d built by the VideoLAN, VLC, and FFmpeg communities and sponsored by AOMedia. We were very pleased to see that AV1 streaming improved members’ viewing experience, particularly under challenging network conditions.

While software decoders enable AV1 playback for more powerful devices, a majority of Netflix members enjoy their favorite shows on TVs. AV1 playback on TV platforms relies on hardware solutions, which generally take longer to be deployed.

Throughout 2020 the industry made impressive progress on AV1 hardware solutions. Semiconductor companies announced decoder SoCs for a range of consumer electronics applications. TV manufacturers released TVs ready for AV1 streaming. Netflix has also partnered with YouTube to develop an open-source solution for an AV1 decoder on game consoles that utilizes the additional power of GPUs. It is amazing to witness the rapid growth of the ecosystem in such a short time.

Today we are excited to announce that Netflix has started streaming AV1 to TVs. With this advanced encoding format, we are confident that Netflix can deliver an even more amazing experience to our members. In this techblog, we share some details about our efforts for this launch as well as the benefits we foresee for our members.

[excellentswordfight]

https://www.guru3d.com/news-story/netflix-starts-streaming-content-to-tvs-though-av1-codec.html

Netflix starts streaming content to TVs though AV1 codec
by Hilbert Hagedoorn on: 11/11/2021 09:41 AM | source: netflixtechblog | 2 comment(s)
Netflix starts streaming content to TVs though AV1 codec
Netflix has begun broadcasting content that has been encoded with the AV1 codec. In this case, it is specifically about streaming to televisions and not smartphones.

AV1 is the first high-efficiency video codec format with a royalty-free license from Alliance of Open Media (AOMedia), made possible by wide-ranging industry commitment of expertise and resources. Netflix is proud to be a founding member of AOMedia and a key contributor to the development of AV1. The specification of AV1 was published in 2018. Since then, we have been working hard to bring AV1 streaming to Netflix members. Netflix said that all of its AV1 streams are encoded in 10-bit and in the highest available resolution and frame rate including HFR – but not yet HDR. Netflix did not specify bitrates other than saying that "AV1 delivers videos with improved visual quality at the same bitrate" compared to MPEG4 and HEVC and that "some streams have a peak bitrate close to the upper limit allowed by the spec", which probably refers to AV1 level 5.0 (30 Mb/s bitrate for Main) or level 5.1 (40 Mb/s bitrate for Main).

- "Today we are excited to announce that Netflix has started streaming AV1 to TVs. With this advanced encoding format, we are confident that Netflix can deliver an even more amazing experience to our members," Netflix wrote in a blog post. "We compared AV1 to other codecs over thousands of Netflix titles, and saw significant compression efficiency improvements from AV1."

In February 2020, Netflix started streaming AV1 to the Android mobile app. The Android launch leveraged the open-source software decoder dav1d built by the VideoLAN, VLC, and FFmpeg communities and sponsored by AOMedia. We were very pleased to see that AV1 streaming improved members’ viewing experience, particularly under challenging network conditions.

While software decoders enable AV1 playback for more powerful devices, a majority of Netflix members enjoy their favorite shows on TVs. AV1 playback on TV platforms relies on hardware solutions, which generally take longer to be deployed.

Throughout 2020 the industry made impressive progress on AV1 hardware solutions. Semiconductor companies announced decoder SoCs for a range of consumer electronics applications. TV manufacturers released TVs ready for AV1 streaming. Netflix has also partnered with YouTube to develop an open-source solution for an AV1 decoder on game consoles that utilizes the additional power of GPUs. It is amazing to witness the rapid growth of the ecosystem in such a short time.

Today we are excited to announce that Netflix has started streaming AV1 to TVs. With this advanced encoding format, we are confident that Netflix can deliver an even more amazing experience to our members. In this techblog, we share some details about our efforts for this launch as well as the benefits we foresee for our members.
Maybe more fitting for the AV1 section. Either way, my first thought was that isnt it a bit odd using AV1 for uhd given the fact that doesnt support HDR. Like how many TVs has av1 support and not HDR-support? I assume that the HDR stream will be preferred if the tv-set support it. I dont know how it is in other regions, but were I live its pretty much only netflix premium content that offer UHD, and that content almost always has an hdr stream. So how many will actually stream the AV1 top stream?

[FranceBB]

Either way, my first thought was that isn't it a bit odd using AV1 for uhd given the fact that doesnt support HDR.

Totally. I mean, the overwhelming majority of UHD contents are either HLG or PQ so limiting it to BT2020 SDR or BT709 SDR is a bit diminishing, however I believe they're trying to do this to make the codec being adopted.


Like how many TVs has av1 support and not HDR-support? I assume that the HDR stream will be preferred if the tv-set support it.

Very few I think. Uhm... is Netflix encoding in standard H.265 the HDR streams?



I dont know how it is in other regions, but were I live its pretty much only netflix premium content that offer UHD


If you're in the UK, Deutschland or Italy, we're here (Sky) with UHD HDR contents in H.265 25 Mbit/s 4:2:0 10bit planar in HLG BT2020nc ehehehehe


UHD contents almost always have an hdr stream. So how many will actually stream the AV1 top stream?

Probably few, then, but I believe it's a start. Still, this is only a streaming-platforms approach 'cause at least in broadcasting MPEG-2 flies high for SD, H.264 flies high for FULL HD and H.265 flies high for UHD and I believe there's gonna be H.266 VVC very soon for 8K.

[benwaggoner]

Maybe more fitting for the AV1 section. Either way, my first thought was that isnt it a bit odd using AV1 for uhd given the fact that doesnt support HDR. Like how many TVs has av1 support and not HDR-support? I assume that the HDR stream will be preferred if the tv-set support it. I dont know how it is in other regions, but were I live its pretty much only netflix premium content that offer UHD, and that content almost always has an hdr stream. So how many will actually stream the AV1 top stream?
AV1 supports HDR in the sense the spec supports the signaling and it supports 10-bit encoding. However HDR's PQ has some different psychovisual properties than SDR's good old gamma, and requires different tuning.

Anecdotally, AV1 encoders seem to have been struggling with this more than makes sense. Perhaps overengineering around SDR's perceptual nonlinearity? I don't see any fundamental spec-level reason why AV1 should struggle with HDR.

[excellentswordfight]

Very few I think. Uhm... is Netflix encoding in standard H.265 the HDR streams?
AFAIK yes.

If you're in the UK, Deutschland or Italy, we're here (Sky) with UHD HDR contents in H.265 25 Mbit/s 4:2:0 10bit planar in HLG BT2020nc ehehehehe

Sorry, I was talking about UHD content on the Netflix platform. Were in my region its almost exclusively only offered for netflix productions which almost always also offer HDR aswell.

AV1 supports HDR in the sense the spec supports the signaling and it supports 10-bit encoding. However HDR's PQ has some different psychovisual properties than SDR's good old gamma, and requires different tuning.

Anecdotally, AV1 encoders seem to have been struggling with this more than makes sense. Perhaps overengineering around SDR's perceptual nonlinearity? I don't see any fundamental spec-level reason why AV1 should struggle with HDR.
I didnt mean it's unsupported by AV1, more in the context that its not implemented in this use case.

But more general speaking, is anyone else doing HDR with AV1 yet? Youtube?

[nevcairiel]

But more general speaking, is anyone else doing HDR with AV1 yet? Youtube?

YouTube indeed has HDR AV1.

[benwaggoner]

YouTube indeed has HDR AV1.
All the YouTube 8K is AV1, including HDR.

Of course, YouTube, so quality is worse than premium 4K.

[Wobrivon]

In addition to such parameters as resolution, frame rate, and picture quality, the decisive factor determining the final video size is the level of dynamism of the scene being shot. This can be explained by the general peculiarities of modern video codecs and H264 in particular. The frame prediction mechanism used allows compressing video additionally without sacrificing picture quality. This saves time for people who often post big videos on travel blogs. So other users can monitor your page activity and watch your videos in the quality and format you want. And to get more people to see your videos, you can increase your active audience. https://famoid.com/buy-instagram-followers/ can help you with this. I hope this information will be useful to you.

[benwaggoner]

In addition to such parameters as resolution, frame rate, and picture quality, the decisive factor determining the final video size is the level of dynamism of the scene being shot. This can be explained by the general peculiarities of modern video codecs and H264 in particular.
Yeah, bitrate requirements for live sports or a grainy action movie can easily be 10x more than for simple animated line art.

[Blue_MiSfit]

One key point -- service providers almost never "switch" formats.

They add an additional format.

This is because they always have a large pool of "legacy" devices (relative to whatever cool new compression format we're talking about). It's very rare to actually turn off an old format. I imagine at this point Netflix has stopped encoding H.263 for their most primitive devices (original Nintendo Wii IIRC) but I'd be surprised if they no longer encode VC-1 for legacy Smooth Streaming endpoints.

For reference, VC-1 has been a legacy codec since probably ~2010.

A service like Netflix with a huge legacy device footprint and cutting edge support for modern formats would have to encode the following:

VC-1
H.264 Baseline, Main, and High profiles
HEVC
VP9
AV1

All of the above would be in many bitrates and resolutions. The "modern" codecs e.g. VP9, HEVC, AV1 would also have separate ladders in SDR, HDR10, and Dolby Vision.

[benwaggoner]

One key point -- service providers almost never "switch" formats.

They add an additional format.

This is because they always have a large pool of "legacy" devices (relative to whatever cool new compression format we're talking about). It's very rare to actually turn off an old format. I imagine at this point Netflix has stopped encoding H.263 for their most primitive devices (original Nintendo Wii IIRC) but I'd be surprised if they no longer encode VC-1 for legacy Smooth Streaming endpoints.

For reference, VC-1 has been a legacy codec since probably ~2010.
I'm not aware of any streaming services still delivering in VC-1 or H.263. Or even Baseline H.264 now. That says, PlaysForSure WMV with VC-1 was still supported on Prime Video until a few years ago.

Telling a customer with an otherwise working device they can't watch a given service anymore is a really bad look, and done only reluctantly. The industry breathed a big sigh of relief when Nintendo turned off all Wii services! Wii's were basically a bronze keyboard MacBook G3 in hardware. Single-core CPU without any HW decode support at all. Even sub-mediocre SD quality took bespoke encodes with a lot of tuning.

A service like Netflix with a huge legacy device footprint and cutting edge support for modern formats would have to encode the following:

VC-1
H.264 Baseline, Main, and High profiles
HEVC
VP9
AV1

All of the above would be in many bitrates and resolutions. The "modern" codecs e.g. VP9, HEVC, AV1 would also have separate ladders in SDR, HDR10, and Dolby Vision.
"Have to" is a bit overstated. One can get away with supporting just H.264 High Profile and HEVC these days.

I can't think of any VC-1 only devices that would still be in use.
H.264 has been a given in new devices for fifteen years now. Baseline-only devices vanished soon after, and Main only over a decade ago.

HEVC is pretty much required for doing UHD or HDR, but a HD SDR only service could get away with just H.264 (albeit with higher bandwidth costs and worse lower bitrate quality).

VP9 never really offered compelling compression efficiency, and was never a mainstream codec for premium services. Some did some stuff with it, but it practice didn't deliver better results than a well-tuned H.264 could do.

AV1 has some impressive low bitrate performance, but HW decoder and DRM implementations remain pretty rare. And it's unclear if there are practical benefits over HEVC for UHD or HDR with today's encoders. AV1 has promise if the ecosystem can get the Film Grain Synthesis process working reliably and perceptual optimizations get more mature. But VVC is coming to devices over the next couple of years, and VVC is manifestly superior to AV1 and all other previous codecs.

AV2 is in development, but is at least a couple of years from standardization, and won't see hardware implementations until after 2025. It's still at too early a stage to even ballpark its real-world performance compared to other codecs.

[Blue_MiSfit]

Good to hear everyone has turned off VC-1 :)

I assumed NFLX or Prime still supported some really old devices where that was the best option but I guess I'm not THAT surprised now that I think about it.

Indeed a new service with a modern device footprint could pretty much get away with ONLY encoding HEVC nowadays, given the recent improvements to Chrome!

[benwaggoner]

Good to hear everyone has turned off VC-1 :)

I assumed NFLX or Prime still supported some really old devices where that was the best option but I guess I'm not THAT surprised now that I think about it.
It was true for quite a while. You could still download PlaysForSure WMV content from Prime Video long after devices that supported it stopped shipping. Maybe 3-4 years ago?

Indeed a new service with a modern device footprint could pretty much get away with ONLY encoding HEVC nowadays, given the recent improvements to Chrome!
Yeah.

It's always so much easier to start without legacy. Ten years ago I was so grateful we didn't need to deal with the legacy stuff that Netflix did, like MPEG-4 part 2 encodes for old mobile devices. But it always converges over time. Being able to deprecate ancient stuff like WMV and Wii support is always a great relief. It's not like an actually good experience was even possible on those devices.

The amount of engineering resources required to maintain support on older devices is tremendous, let alone keep feature and experience parity. Even a single brand of smart TV can have 20+ unique OS and SoC combinations currently supported.