Slashdot Mirror
Netflix Uses AI in Its New Codec To Compress Video Scene By Scene (qz.com)
An anonymous reader shares a Quartz report: Annoying pauses in your streaming movies are going to become less common, thanks to a new trick Netflix is rolling out. It's using artificial intelligence techniques to analyze each shot in a video and compress it without affecting the image quality, thus reducing the amount of data it uses. The new encoding method is aimed at the growing contingent of viewers in emerging economies who watch video on phones and tablets. "We're allergic to rebuffering," said Todd Yellin, a vice president of innovation at Netflix. "No one wants to be interrupted in the middle of Bojack Horseman or Stranger Things." Yellin hopes the new system, called Dynamic Optimizer, will keep those Netflix binges free of interruption when it's introduced sometime in the next "couple of months." He was demonstrating the system's results at "Netflix House," a mansion in the hills overlooking Barcelona that the company has outfitted for the Mobile World Congress trade show. In one case, the image quality from a 555 kilobits per second (kbps) stream looked identical to one on a data link with half the bandwidth.
Why are they calling it AI? That's silly.
It's just an improved encoding scheme with better algorithms.
Nothing new to see here. We've been improving video encoding schemes since we started encoding video.
middle-out.
"Win treats sysadmins better than users. Mac treats users better than sysadmins. Linux treats everyone like sysadmins."
What I think is that they devised an algorithm, probably based on neural networks, that is particularly good as estimating the perceived quality of the picture.
This data is then used to adjust the level of compression of each part of the picture, so that the least important parts of the picture get compressed more aggressively to save bitrate for the more important parts.
This is nothing new really, the idea of using AI techniques and perceived quality to help with compression is decades old. The interesting part here is that it is done on a commercial scale.
I don't think that word means what you think it means...
"File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
Bear in mind that while they may be using a new codec - that is, a piece of code designed to convert a video from one format to another - they're not using a new format, if they did, then they could no longer use the hardware acceleration they pretty much rely upon to ensure devices can play their content in real time, and without destroying the battery.
So insofar as they're doing the above, they're not doing it any more than any other codec does, because only compressing changes is what every current codec does well, and pretty much a fundamental assumption behind each mainstream format, from MPEG-1 and H.261 onwards.
You are not alone. This is not normal. None of this is normal.
Netflix does use AI in developing the video compression algorithm. The problem with encoding videos with lossy algorithms is that video quality is a subjective thing. You need a person to watch it and tell you how good the video quality looks. This makes it rather slow and difficult to do A/B testing, not to mention how boring it is watching the same clips over and over with different encoding.
Netflix got around the problem by using machine learning to teach a computer when video quality looked good. They had a bunch of people watch videos with different compression and rate the quality, then told the AI that their ratings were gospel. It then analyzed the different videos and decided for itself which features were associated with good quality. Once the computer was generating the video ratings as people, they had a rapid way to do A/B testing. That allowed them to optimize their compression algorithm in much less time than with using humans to rate video quality.
I'm not sure why Summary links to some popular news article which talks in general about Netflix using AI, instead of linking to the actual Netflix page describing exactly what they did. This used to be the sort of technical detail you'd expect from slashdot submissions.
Soon Nextflix may have only a single video in 1000 categories with compression showing a single frame as all.
https://www.youtube.com/c/BrendaEM
I hate these things, they never work as stated. All it means is they can save money by buffering ahead even less. Days past if you had a poor connection you could load a video and pause it and it would buffer through. Now if you pause it buffers what it seems to think is all you actually need. It never is.
Could be, but when AAC came around for audio compression, the interesting concept was that a pschyoacoustic model was applied to identify which of (at the time 7) multiple compression model paths would provide an the most optimal perceived result of the compression for the given audio samples. Better encoders would choose better paths for encoding. So, the best encoders would identify which compression method to use for each audio segment and how long said audio segment should be.
H.264 and H.265 offer a massive amount of opportunities to tweak encoding of macro blocks. There are spatial considerations (block size), temporal considerations, motion consideration, etc... each individual block can be a differ type (I, P, B, etc...). Each block can be mapped compressed relative to another block considering time and space. Each block can select a different set of coefficients for frequency identification (DCT for example) as well as gradients (quantization). Each block can be stored for optimal management of loss related to congestion (NAL).
To be fair, if I covered every possible case in H.265, I can be here a long time.
I used to write encoders for these standards and I would often target optimal allocation of bitrate relative to PSnR and SSIM. These are great metrics for attempting to model optimal quality following decompression. Unfortunately, I was too early to also optimize bitrate allocation relative to improved perceived quality relative to specific areas of interest which is something we can do today by applying computer vision modules that can simulate what is likely to be most interesting to humans and draw their attention. For example, consider that in "Back to the Future" when watching the scene where Doc types the date into the car computer, a computer can now identify that a human would most likely be drawn to watch the LED digits most closely. So, allocating a greater bitrate there would be better than to Doc's fingers and head movement.
Modern machine learning methods such as those used by Google to recognize a red dress in a photo and catalog it appropriately can easily be used for this type of encoding process and as Audun Mattias Ãygard has been publishing on his blog, these algorithms are public and well known today.
I experimented with this technology for identifying optimal image compression some time back. The tech wasn't ready yet
Bitrate allocation relative to areas of interest could easily allow for 50% bitrate savings. As the tech improves, I could see a great deal more especially in the area of quantization.
Now, if we used more AI for CABAC and CAVLC to precondition the dictionaries, we may have a great model for H.266
Maybe your display brightness/contrast settings are wrong?
#DeleteFacebook
This may well be DRM, not just over-engineering.
I wonder if Netflix worry about a situation where you can dump a movie to disk by doing a save-state on your VM. (See also: their offline-viewing feature is only available on locked-down devices.)
I've seen Chromecast cache over 3 minutes of Netflix, but I'm fairly sure that's about as high as it gets.
"We're allergic to rebuffering," said Todd Yellin, a vice president of innovation at Netflix. "No one wants to be interrupted in the middle of Bojack Horseman or Stranger Things."
Or porn. "Yes, yes, yes..." (buffering ...) [ Nooooooooooooooo.... ]
It must have been something you assimilated. . . .