10 ms·
H.264 Is Magic (2016)
- dang 2y agoRelated: H.264 is Magic (2016) - https://news.ycombinator.com/item?id=30710574 https://news.ycombinator.com/item?id=30710574 - March 2022 (219 comments) H.264 is magic (2016) - https://news.ycombinator.com/item?id=19997813 https://news.ycombinator.com/item?id=19997813 - May 2019 (180 comments) H.264 is Magic – a technical walkthrough - https://news.ycombinator.com/item?id=17101627 https://news.ycombinator.com/item?id=17101627 - May 2018 (1 comment) H.264 is Magic - https://news.ycombinator.com/item?id=12871403 https://news.ycombinator.com/item?id=12871403 - Nov 2016 (219 comments)
- jpm_sd 2y agoWell OK, but what about H.265? It's one louder, isn't it? https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding
- cornstalks 2y agoI've always felt like H.264 hit a great sweet spot of complexity vs compression. Newer codecs compress better, but they're increasingly complex in a nonlinear way.
- TimeBearingDown 2y agoIt also benefits from the extremely optimized encoder x264, which has many easily approachable tunings and speed/compression presets. I’m not sure I’d trust x265 to preserve film grain better than x264 —tune film unless I gave x265 much, much more time as well as pretty similar bitrate.
- LeoPanthera 2y agox265 has a specific "--tune grain" mode specifically for video with a lot of film grain.
- TimeBearingDown 2y agoApologies, I did miss that. However it seems to still underperform. See this thread, screenshots on the first page. http://forum.doom9.net/showthread.php?p=1947856#post1947856 http://forum.doom9.net/showthread.php?p=1947856#post1947856 I was remembering from this a couple years ago, but focused on the parameters shown and missed that they were derived from --tune grain.
- ronsor 2y agoH.264 will probably never die, especially once all the patents expire in a few years.
- palata 2y agoWhen do they expire?
- edflsafoiewq 2y agoAccording to https://meta.wikimedia.org/wiki/Have_the_patents_for_H.264_MPEG-4_AVC_expired_yet%3F https://meta.wikimedia.org/wiki/Have_the_patents_for_H.264_M..., probably September 2027. There are an additional two patents on that list that expire in 2028 and 2030, but it's not clear if they apply. So probably November 2030 at the latest.
- toast0 2y agoH.262 has a long future too. New DVDs and OTA broadcasts (at least for ATSC 1.0) will probably end at some point, but the discs won't go away for a long time, even if disc players are less and less popular.
- ant6n 2y ago…you mean MPEG2?
- cornstalks 2y agoH.262 == MPEG-2 Part 2 Video == ISO/IEC 13818-2. Video codecs are fun because multiple standards bodies publish their own version of the same codec. The ITU-T publishes the H.26x specs, and ISO/IEC publish the other xxxxx-x specs. Pesonally I like the ITU-T because you can get the specs for free from them. ISO/IEC demand $242 for a copy of ISO/IEC 23008-2 (also known as MPEG-H Part 2 or HEVC). But ITU-T will give you H.265's spec (which is the same codec as ISO/IEC 23008-2) for free: https://www.itu.int/rec/T-REC-H.265 https://www.itu.int/rec/T-REC-H.265
- 2y ago
- SirMaster 2y agoBut with hardware acceleration for both encoding and decoding of HEVC it feels like less of a problem IMO.
- ugjka 2y agoVideo piracy is pretty much all in HEVC
- aaron695 2y ago[dead]
- Kirby64 2y agoNot really. Only 4k content and anime seems to use HEVC/h265. Anything lower resolution has stuck to h264 for the time being.
- contingencies 2y agoFWIW IIRC yts.mx began offering H.265 on standard resolution films about a year or two back.
- Kirby64 2y agoYeah, and most people consider stuff off yts to be of poor quality. Encodes are bad and do not meet standards.
- SirMaster 2y agoBut anything made in the last few or more years is 4K now and everything I watch is 4K, so all I find is HEVC stuff for everything. Sure, if you are going to go get an older show that's pre 4K/HDR or a movie that isn't on UHD disc yet, then it will be H.264 of course. But if you primarily watch newly made 4K/HDR content, it's all been HEVC for years now.
- Kirby64 2y ago
- Dylan16807 2y agoDoesn't every state of the art codec do that, including H.264 versus previous? Also I haven't seen charts of decode difficulty, but as far as encoding goes, codecs a generation more advanced can crush H.264 at any particular level of effort. The even newer codecs can probably get there too with more encoder work. https://engineering.fb.com/wp-content/uploads/2023/02/AV1-Computation-Tradeoffs.jpg https://engineering.fb.com/wp-content/uploads/2023/02/AV1-Co...
- cornstalks 2y agoGenerally yes, but I wasn't only talking about compute costs. Mentally grokking H.264's features and inner workings is a lot easier than newer, better codecs.
- ksec 2y agoMPEG 5 EVC Baseline, arguably the improved / refined version of H.264, actually compress better while having the same complexity, Both in terms of mental model and computational cost. Somewhat unfortunate that never became anything.
- fostware 2y agoTwitch... I just had DiVX vs Xvid flashbacks
- SirMaster 2y agoWhat about VVC (H.266)? https://en.wikipedia.org/wiki/Versatile_Video_Coding https://en.wikipedia.org/wiki/Versatile_Video_Coding
- adzm 2y agoVVC has a lot of the same issues that plagued HEVC adoption. There really isn't much reason to not use AV1 if you want the best codec currently.
- jl6 2y agoVVC is a generational improvement in compression ratio over AV1, which might make it the best for a lot of applications. Too bad it will probably languish in patent licensing hell.
- Dylan16807 2y ago> VVC is a generational improvement in compression ratio over AV1 That's probably true, but do you know where I could find a comparison that shows a variety of speed settings for both codecs? And ideally discusses how fast VVC is expected to encode once everything is more finalized. It's easy enough to run everything at default speed but then the results are almost meaningless.
- SirMaster 2y agoIt's always really slow at the start, but once hardware acceleration happens it becomes much less of a problem. Or if you are just an end user consuming streaming video content, then you only care that your player can decode it which I don't think will be any sort of problem if things play out like they did for HEVC vs VP9. If all the streaming services choose VVC over AV1, then all the player companies will put hardware decoders in their SoC.
- jacobgorm 2y agoUnless you need hardware acceleration. I’ve managed to implement live h265 encode and decode with Directx12 on Windows on Intel and Nvidia, but the driver crashes on AMD and they seem uninterested in fixing it, so there I have to fallback to h264.
- asveikau 2y agoMaybe I need to change some options, but I find whatever encoder I get when I ask ffmpeg to encode h265 takes a very long time. Then decoding 4k h265 is very slow on most of my PCs. It sure gets the file size down though.
- adzm 2y agoI really like HEVC/h265. It's pretty much on par with VP9. but licensing trouble has made it difficult to get adopted everywhere even now. VVC/h266 seems to be having the same issues; AV1 is pretty much just as good and already seeing much more adoption.
- radicality 2y agoWhat’s the tldr of the licensing problems? I’ve started reading this article which list the various H.26x proposals - https://en.m.wikipedia.org/wiki/Video_Coding_Experts_Group https://en.m.wikipedia.org/wiki/Video_Coding_Experts_Group Seems like the group that comes with these is eventually part of the UN ? https://en.m.wikipedia.org/wiki/International_Telecommunication_Union https://en.m.wikipedia.org/wiki/International_Telecommunicat... Is it because they come with the codecs “jointly” with the MPEG organization, which is for profit? If the group is part of a standards organization that’s part of the UN, I feel like they should come up with non-patent-encumbered “recommendations”.
- peutetre 2y ago> What’s the tldr of the licensing problems? There are multiple patent pools for H.265 wanting to be paid licensing fees (MPEG LA, HEVC Advance, Velos Media). HEVC Advance and Velos Media even want content distribution licensing fees. And there are patent holders not in any pool who also want to be paid (Technicolor, Motorola, Nokia, etc.). It's a mess.
- ksec 2y ago>HEVC Advance and Velos Media even want content distribution licensing fees. That is not correct. Unless you meant they once "suggested" to ask for content distribution licensing.
- peutetre 2y agoIt's correct. It's category 4: https://accessadvance.com/topic-what-do-we-license/ https://accessadvance.com/topic-what-do-we-license/
- TacticalCoder 2y ago> Well OK, but what about H.265? It's one louder, isn't it? I had some old, gigantic, video footage (in a variety of old, inefficient, formats at a super high quality). So I did some testing and, well, ended up re-encoding/transcoding everything to H.265. It makes for much smaller files than H.264. The standard is also ten years younger than H.264 (2013 for H.265 vs 2003 for H.264).
- Melatonic 2y agoYears ago I was photographing a party in silicon valley (had just graduated college and was taking any job I could get). I take a nice photo of a couple and the wife looks at me and says " You know my husband invented H264? Do you know what that is?". Ended up having a long conversation with the husband (the engineer) and he hinted many times that they were working currently on something even better. Years later now of course we have H265. Everytime I play something in H264 or H265 I think of that moment and how much work that guy and his colleagues must have put into coding such a widely used codec (and how proud his wife was!)
- drmpeg 2y agoShe should say "helped to invent". Video codec standard development is most definitely a group effort.
- illusive4080 2y agoYou worked on MPEG?
- drmpeg 2y agoYes, from 1993 until I retired in 2011. I worked at C-Cube Microsystems and LSI Logic. In 1993-1994 at C-Cube, I helped develop the first real-time MPEG-1 encoder. The rest of the team was busy developing the 704x480 resolution encoder for the roll-out of DirecTV, so I ended up taking sole responsibility for the MPEG-1 product and brought it to market. It's thought that this encoder authored much of the content for China VCD. One notable thing I remember was watching the OJ Simpson chase on a test DirecTV receiver in the C-Cube lab (the same day that DirecTV went live). Here's a picture of the C-Cube chip. It took 12 of these running in parallel to encode 704x480 MPEG-2. https://www.w6rz.net/cl4010.png https://www.w6rz.net/cl4010.png
- rebeccaskinner 2y agoI do a lot of video compression for hobby projects, and I stick with h264 for the most part because h265 encoding requires far too much extra compute relative to the space savings. I can spend an hour compressing a file down to 1gb with h264, or I can spend 12 hours compressing the same file to 850mb with h265. Depending on the use-case, I might still need the h264 version anyway since it's far more widely supported by clients. If I had a data center worth of compute to throw at encoding, or I were running a streaming service where the extra 150mb per video started to add up, then I'd definitely on-board with h265 but it's really hard to justify for a lot of practical use-cases.
- radicality 2y agoWhat about when you’re recording (say your iPhone / android / standalone camera) - are you choosing h264 or h265 (or something else like an intra-frame only codec for easier editing).
- rebeccaskinner 2y agoMost of what I do is working with pre-recorded video, but for projects where I'm doing recording I tend to use h.264 since I don't have a lot of devices that support h.265 anyway, and picking one format with broad compatibility is generally more important to me than the efficiency gains I'd get using h.265 when I could.
- Osiris 2y agoIs GPU accelerated encoding not an option?
- rebeccaskinner 2y agoI haven't actually done the comparison myself, but the common refrain is that the quality of the video suffers when you use GPU accelerated encoding. That's not a tradeoff I want to make, so I've just stuck with CPU encoding.
- 2y ago
- ezoe 2y agoHEVC and AV1 is twice more magic. It keep the same quality to human eyes while reducing the bitrate by 50%. HEVC is patent encumbered. Users who use old hardware don't have hardware decoder. So both requires more time to be adopted.
- tbalsam 2y agoThis is very cool but the use of the terms "Information Entropy" together as if they were a separate thing is maybe the furthest that any "ATM-machine"-type phrase has rustled my jimmies. It is a cool article, just, wowzers, what a phrase.
- cobbzilla 2y agoare signal and noise the same thing?
- ClassyJacket 2y agoI mean, it's obviously not relevant here, but technically there is also heat entropy, isn't there? It's not always information.
- hughesjj 2y agoTo be fair I think information entropy is more self descriptive than Shannon entropy
- tbalsam 2y agoCorporate has asked you to find the differences between these two pictures.
- hughesjj 2y agoThey're two names which references the same concept, but Shannon entropy is not the only type of entropy. I mean maybe everything really is just Shannon entropy if you look deep enough and have a sufficiently powerful model of physics but we're not there today.
- tasty_freeze 2y agoStory time. Back in 1999, I was leaving a startup that had been acquired, but I didn't want to stick around. I had been doing in mpeg encoding; this is relevant later. One of the companies I interviewed with had come up with a new video compression scheme. They were very tight lipped but after signing NDA paperwork, they showed me some short clips they had encoded/decoded via a non-realtime software codec. I was interviewing to create an ASIC version of the algorithm. Even seeing just a minute or two of their codec output, I guessed what they were doing. I suggested that their examples were playing to the strengths of their algorithm and suggested some scenarios that would be more challenging. I also described what I thought they were doing. They neither confirmed nor denied, but they had me come back for a second round. In the second round I talked with the founders, a husband/wife CEO/CTO (IIRC) team. That is when I learned their plan wasn't to sell ASICs, but they wanted to keep their codec secret and instead create DSL-based cable network using the ASICs for video distribution. I said something like, it sounds like you have invented a better carburetor and instead of selling carburetors you are planning on building a car factory to compete with GM. It was cheeky, and they didn't take it well. Getting to the point of how this story relates to H.264, their claim was: conventional compression has reached the limit, and so their codec would allow them to do something nobody else can do: send high-def video over DSL lines. I replied: I think compressors will continue to get better, and even if not, higher speed internet service will eventually come to houses and remove the particular threshhold they think only they can cross. Oh, no, they replied, physics dictates the speed bits can be sent on a wire and we are at that limit. I didn't get (and didn't want) a job offer. The company did get some VC money but folded a few years later, much more efficient codecs were developed by others, and 2 Mbps internet connections were not a limit. I'm sure the actual algorithm (which I describe later at a high level) had a lot of clever math and algorithmic muscle to make it work -- they weren't stupid technically, just stupid from a business sense. This retelling makes me sound like a smug know-it-all, but it is one of two times in my life where I looked at something and in seconds figured out their secret sauce. There are far more examples where I am an idiot. What was their algorithm? They never confirmed it, but based on silhouette artifacts, it seemed pretty clear what they were doing. MPEG (like jpeg) works by compressing images in small blocks (8x8, 16x16, and a few others). That limits how much spatial redundancy can be used to compress the image, but it also limits the computational costs of finding that redundancy. Their codec was similar to what Microsoft had proposed for their Talisman graphics architecture in the late 90s. From what I could tell, they would analyze a sequence of frames and rather than segmenting the image into fixed blocks like mpeg, they would find regions with semi-arbitrary boundaries that were structurally coherent -- eg, if the scene was a tennis match, they could tell that the background was pretty "rigid" -- if a pixel appeared to move (the camera panned) then the nearby pixels were highly likely to make the same spatial transformation. Although each player changed frame to frame, that blob had some kind of correlation in lighting and position. Once identified, they would isolate a given region and compress that image using whatever (probably similar to jpeg). In subsequent frames they'd analyze the affine (or perhaps more general) transformation from a region from one frame to the next, then encode that transformation via a few parameters. That would be the basis of the next frame prediction, and if done well, not many bits need to be sent to fix up the misprediction errors.
- samlinnfer 2y agoTo nitpick, comparing with PNG is misleading, because it's comparing a lossless format with lossy. a JPEG would be around the same size has H.264.
- bigstrat2003 2y agoYeah that jumped out at me as well. It's a really unfair comparison.
- edflsafoiewq 2y agoIt's not supposed to be a "fair" comparison, it's just an observation. You already understand where the difference comes from. The article goes into some detail to explain it to a person who doesn't. The actual point of that example isn't even about lossy vs lossless anyway, it's about how 300 frames can take up nearly the space as one frame (interframe compression).
- eviks 2y agoit's not misleading, but leading - to the concept of lossy compression
- IvanK_net 2y agoLossy compression is possible in PNG to a certain degree. This is the "same PNG", but 94 kB instead of 1015 kB: 1015 kB: https://sidbala.com/content/images/2016/11/outputFrame.png https://sidbala.com/content/images/2016/11/outputFrame.png 94 kB: https://www.photopea.com/keynote.png https://www.photopea.com/keynote.png
- SigmundA 2y agoPNG is not lossy, your example uses a preprocessor to quantize colors before being compressed with PNG. PNG loss no information from the image being fed to it, the loss was done before creating a simpler image.
- 2y ago
- g4zj 2y ago> Suppose you have some strange coin - you've tossed it 10 times, and every time it lands on heads. How would you describe this information to someone? You wouldn't say HHHHHHHHH. You would just say "10 tosses, all heads" - bam! You've just compressed some data! There appears to be some lossy compression on that string of "H"s.
- lupusreal 2y agoTry saying each of those though.
- zerocrates 2y agoThey're just jokingly noting that the string of H's is only 9 letters long, not 10.
- lupusreal 2y agoYeah I get it, but it's ten utterances vs four.
- NewJazz 2y agoAlso, it's not really compression because "10 tosses, all heads" is more characters.
- Agingcoder 2y agoI remember when h264 appeared. At that time, I was obsessed with mplayer and would download and build the latest releases on a regular basis. The first time I got an h264 file, mplayer wouldn’t read it so I had to get the dev version and build it. It worked, and I realized two things : the quality was incredible, and my athlon 1800+ couldn’t cope with it. Subsequent mplayer versions ( or libavcodec ?) vastly improved performance, but I still remember that day.
- cheema33 2y agoYep. Same here. Man, I have not used mplayer in a very long time. But, it was the bee's knees. I used to work for a company that was developing some video based products. And this other company in Vegas sold our bosses a "revolutionary video codec" and a player. We had to sign NDAs to use it. I used it and observed that it worked like mplayer. Too much like it. 5 more minutes of investigation and the jig was up. Our execs who paid a lot of money to the Vegas company had an egg on their face. It is shockingly easy to scam non-tech decisions makers in the tech field. They are too worried about being left behind. Smart ones will pull in a "good" engineer for evaluation. Dunning Kruger subjects will line up with their wallets out.
- peutetre 2y agoAV1 is more magic with better licensing. For their use case Meta is gradually getting to a baseline of VP9 and AV1 streams for their video streaming: https://www.streamingmedia.com/Producer/Articles/Editorial/Featured-Articles/Is-the-AVC-H.264-Codec-Finally-Fading-163413.aspx https://www.streamingmedia.com/Producer/Articles/Editorial/F... And AV1 for video calls: https://engineering.fb.com/2024/03/20/video-engineering/mobile-rtc-video-av1-hd/ https://engineering.fb.com/2024/03/20/video-engineering/mobi... Microsoft is starting to use AV1 in Teams. AV1 has video coding tools that are particularly useful for screen sharing: https://techcommunity.microsoft.com/t5/microsoft-teams-blog/enhancing-screen-sharing-with-av1-in-microsoft-teams/ba-p/4096056 https://techcommunity.microsoft.com/t5/microsoft-teams-blog/... Most of the video I see on YouTube these days is in VP9 or AV1. Occasionally some video is still H.264. H.264 will still be around for quite some time, but AV1 looks set to become the new baseline for internet video.
- MrDrMcCoy 2y agoIn an 8-bit colorspace, h.264/5 suffer from virtually no block artifacts. AV1 can't get rid of them without upping to 10-bit. Not that it's necessarily a problem. The real problem with AV1 is how darn computationally intensive it is to compress.
- chii 2y ago> how darn computationally intensive it is to compress. which i think is fine, as most decompression is on user side, but compression is on server side (and mostly only ever done once!).
- ninjin 2y agoVP8, VP9, and AV1 are all wonderful and unencumbered. However, as awful as the licensing of H.264 is, it does yield reasonable quality even on hardware that is over a decade old. It is true that for many purposes we can offload encoding onto servers. However, as someone that frequently deals with live video streaming, AV1 is still out of reach on most hardware I am on and VP9 has only been viable for less than a decade. Yes, VP9 and AV1 are superior in terms of quality, but it is truly remarkable that H.264 runs as well as it does and I wish we had a similar unencumbered lightweight/portable codec (VP8 in my experience is about as heavy as VP9 and offers about the same quality as H.264). At least for audio we now have Opus and Flac (plus MP3 having had its vile patents expire), so hopefully video is the last frontier and VP9 and AV1 will become the standard over this decade.
- userbinator 2y ago8 years after that article was written, many of the patents on H.264 are actually approaching expiry soon (i.e. within a year or two): https://meta.wikimedia.org/wiki/Have_the_patents_for_H.264_MPEG-4_AVC_expired_yet%3F https://meta.wikimedia.org/wiki/Have_the_patents_for_H.264_M... This is not surprising, given that the first version of the H.264 standard was published in 2003 and patents are usually valid for 20 years. Its predecessors, H.263 and MPEG-4 ASP, have already patent-expired and are in public domain.
- amelius 2y agoI bet that the successor algorithms will be implemented everywhere in hardware, and we're stuck with the patent problem once again.
- kragen 2y agoin 02016 it was patented magic in many countries. now the patents have all expired, or will in a few months, since the standard was released in august 02004 after a year of public standardization work, patents only last 20 years from filing, and you can't file a patent on something that's already public (except that, in the usa, there's a one-year grace period if you're the one that published it). if there are any exceptions, i'd be very interested to hear of them userbinator points at https://meta.m.wikimedia.org/wiki/Have_the_patents_for_H.264_MPEG-4_AVC_expired_yet%3F https://meta.m.wikimedia.org/wiki/Have_the_patents_for_H.264..., but most of the patents there have a precedence date after the h.264 standard was finalized, and therefore can't be necessary to implement h.264 itself (unless the argument is that, at the time it was standardized, it was not known to be implementable, a rather implausible argument) what's surprising is that the last 20 years have produced a few things that are arguably a little better, but nothing that's much better, at least according to my tests of the implementations in ffmpeg it seems likely that its guaranteed patent-free status will entrench it as the standard codec for the foreseeable future, for better or worse. av1 has slightly better visual quality at the same bandwidth, but is much slower (possibly this is fixable by a darktangent), but it's vulnerable to patents filed by criminals as late as 02018
- 293984j29384 2y agowhy do you put an extra zero in front of the year?
- ozarker 2y agoHe’s a time traveler from 38056
- AnimalMuppet 2y agoBecause he's a true believer in the Long Now religion. But not enough of a true believer that he uses six or seven digits ;-) Also, he uses that (and no capital letters) as a "bozo filter" - anyone who replies about that rather than the substance of the comment, he defines as someone he doesn't want to talk to anyway. Personally, I think it's rather an obnoxious move. He's deliberately derailing discussion about the content, and he has decent content. But he insists on playing this game instead of just talking about the substance.
- kazinator 2y ago> Because you've asked the decoder to jump to some arbitrary frame, the decoder has to redo all the calculations - starting from the nearest I-frames and adding up the motion vector deltas to the frame you're on - and this is computationally expensive, and hence the brief pause. That was 2016. Today, it's because Youtube knows you're on Firefox.
- ngcc_hk 2y agoH.265 is ...?
- ant6n 2y agoH.265 is magic (2021)
- P_I_Staker 2y agoIf it's magic, it's spells have been greatly disenchanted. It's like gandolf.
- tomjen3 2y agoOne of my surprises when I started to investigate video encoders was that, because the details in a scene comes at the high frequency, you can drop the bandwith requirements on the fly, by just not sending the details for a frame.
- simonebrunozzi 2y agoV-Nova has developed a very interesting video compression algorithm, now in use at some major media companies [0]. It is software but it will also be built-in in certain hardware for Smart TVs, etc. Disclosure: I'm an investor. [0]: https://www.v-nova.com/ https://www.v-nova.com/
- BSDobelix 2y ago>>V-Nova’s 1000 patents: not size that matters, but how you use it Oh no, not again....
- IvanK_net 2y agoLossy compression is possible in PNG to a certain degree. This is the "same PNG", but 94 kB instead of 1015 kB: 1015 kB: https://sidbala.com/content/images/2016/11/outputFrame.png https://sidbala.com/content/images/2016/11/outputFrame.png 94 kB: https://www.photopea.com/keynote.png https://www.photopea.com/keynote.png
- isametry 2y ago(What's happening here is a reduction of the color count: https://en.wikipedia.org/wiki/Color_quantization https://en.wikipedia.org/wiki/Color_quantization)
- SigmundA 2y agoThats not PNG being lossy, the image was preprocessed to lose information by reducing color count before being compressed with PNG.
- IvanK_net 2y agoThat is what a "lossy compression" means. Instead of encoding the original image, you look for a similar image, that can be losslessly encoded into a smaller file. In PNG, you look for an image with 100 - 200 colors (so that colors repeat more often) and losslessly encode it with DEFLATE. In JPG, you look for an image with with a reduced description through DCT, and losslessly encode it with Huffmann trees.
- SigmundA 2y agoNo thats image preprocessing to lose information before compression. JPG would be smaller if color count was reduced as well. If color quantization using a specific algorithm was part of PNG you could say its lossy compression, its not, PNG is not lossy compression by any definition. Your specific image processing pipeline might be lossy, based on various tools you ran the image through or equipment used to capture, PNG is not.
- bob1029 2y agoMy favorite part of these codecs is how the discrete cosine transform plays so well together with quantization, zig-zag scanning and entropy coding. The core of any lossy visual compressor is approximately the same theme. Those I-frames are essentially jpegs.
- Rakshith 2y agoI think VVC is even better, MXPlayer streaming already has shows streaming in VVC in India! I dont know how they're doing it but its live. VVC is supposedly 20-30% more efficient than av1