Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

H.264 is Magic (2016)

sidbala.com

Post reply on HN
Print view View original

51–60 of 229 posts

Re: H.264 is Magic (2016)

#51

Post by kalleboo »

throw0101a wrote: post #42
ksec wrote: post #27

Earlier quoted context omitted.

The Broadcasting industry has definitely sided with VVC. So 8K broadcast will likely be using VVC along with possibly LCEVC [1] as announced by the Brazilian SBTVD standard. The AV1 question is harder to answer. One could argue VP9 is good enough and a few more years before it reach 100% VP9 hardware decoding on Smartphone. Of course Google could force the usage of AV1 in the future if they slowly phaseout VP9 video…

> Even to this day I still do not believe Apple will support AV1 decode, at least not until Google forced the AV1 usage. Even though they joined AOM four years ago: * https://venturebeat.com/2018/01/04/3-reasons-apple-just-join... * https://appleinsider.com/articles/18/01/04/apple-joins-allia... * https://bitmovin.com/apple-joins-av1-codec-consortium/ * https://www.streamingmedia.com/Articles/ReadArticle.aspx?Art...

Apple is also on the Blu-ray board of directors but AFAIK have never supported either playback or mastering of Blu-ray in any of it's products.

Re: H.264 is Magic (2016)

#52

Post by gandalfian »

airstrike wrote: post #24

> "a technical walkthrough" > "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! Easy. I saved you hours of mindfuck lectures." Ahh, my favorite kind of technical walkthrough. Love it

Ah ASCII art. Long rows of identical characters. The only thing that actually allowed a dial up modems compression claims to actually live up to the marketing hype....

Re: H.264 is Magic (2016)

#53

Post by kibwen »

latexr wrote: post #46
airstrike wrote: post #24

> "a technical walkthrough" > "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! Easy. I saved you hours of mindfuck lectures." Ahh, my favorite kind of technical walkthrough. Love it

> You wouldn't say HHHHHHHHH. You wouldn’t and shouldn’t. There are only nine “H” in there!

Ah, but perhaps in this encoding scheme the first H is implicit, and a leading T is encoded as _T. Half the time this results in an infinity increase in bytes saved!

Re: H.264 is Magic (2016)

#54

Post by credulousperson »

For those interested, Ronald Bultje (who co-devloped VP9) wrote some information here on VP9 which has some more concrete details about video coding than this article: https://blogs.gnome.org/rbultje/2016/12/13/overview-of-the-v...

It's not H.264 but the coding techniques will be similar.

Re: H.264 is Magic (2016)

#55

Post by fallat »

tmp65535 wrote: post #10

Fabrice Bellard's BPG image format uses H.265's keyframe compressor: https://bellard.org/bpg/ Here is a side-by-side visual comparison: http://xooyoozoo.github.io/yolo-octo-bugfixes/#ballet-exerci... Amazing. I ported his BPG decoder to Android ARM for a pornographic app. See my comment history for details. It reduced data transfer by more than 60%.

I cannot get over how much of a CompSci God Fabrice is. What a person!

Re: H.264 is Magic (2016)

#56

Post by criddell »

tmp65535 wrote: post #35
high_priest wrote: post #18

Earlier quoted context omitted.

Bro. Why are you promoting so much an app that barely does anything (opens a series of images from a hosting), as 'pornographic application that change your life'?

This account exists ONLY to talk about that app. Every one of my projects is isolated from the others by using different accounts, etc. We should all be meticulous about compartmentalizing our online identity. This app uses an unusual image codec (BPG) which illustrates that if you control the encoder and decoder, you can choose a format with no mainstream support. I think it is a good point.

> We should all be meticulous about compartmentalizing our online identity.

I disagree and I believe the HN guidelines do as well:

> Throwaway accounts are ok for sensitive information, but please don't create accounts routinely. HN is a community—users should have an identity that others can relate to.

Re: H.264 is Magic (2016)

#57

Post by jancsika »

> 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! Easy. I saved you hours of mindfuck lectures. This is obviously an oversimplification, but you've transformed some data into another shorter representation of the same information.

Future generations will disagree it's the "same information."

I predict there will be a small but vocal cabal who seize on your example with nine H's to argue that it's not the case.

On a more serious note, if you lose the decoder ring does it cease to be a "representation of the same information?"

Re: H.264 is Magic (2016)

#58

Post by delusional »

airstrike wrote: post #24

> "a technical walkthrough" > "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! Easy. I saved you hours of mindfuck lectures." Ahh, my favorite kind of technical walkthrough. Love it

Doesn't that description basically presuppose that you already understand compression? "HHHHHHHHHH" is 10 characters, but "10 tosses, all heads" is 21. Already understanding compression, I of course know that the second part could be efficient if encoded properly, but someone actually needing the explanation probably wouldn't know that.

It's not really wrong, and not really an "oversimplification" as the parent article calls it. It's just a bad example, and it seems confused about the audience it's trying to reach. Either they already understand compression, and it's superfluous, or they don't and it's just confusing.

Re: H.264 is Magic (2016)

#59

Post by tmp65535 »

torginus wrote: post #48
tmp65535 wrote: post #10

Fabrice Bellard's BPG image format uses H.265's keyframe compressor: https://bellard.org/bpg/ Here is a side-by-side visual comparison: http://xooyoozoo.github.io/yolo-octo-bugfixes/#ballet-exerci... Amazing. I ported his BPG decoder to Android ARM for a pornographic app. See my comment history for details. It reduced data transfer by more than 60%.

What's the patent status? As far as I know, H265 is patent encumbered(and not actually supported on a large chunk of Android devices for the same reason) , so including this somewhere might invite legal trouble.

You are correct, there may be licensing issue.

Re: H.264 is Magic (2016)

#60

Post by tmp65535 »

criddell wrote: post #56
tmp65535 wrote: post #35

Earlier quoted context omitted.

This account exists ONLY to talk about that app. Every one of my projects is isolated from the others by using different accounts, etc. We should all be meticulous about compartmentalizing our online identity. This app uses an unusual image codec (BPG) which illustrates that if you control the encoder and decoder, you can choose a format with no mainstream support. I think it is a good point.

> We should all be meticulous about compartmentalizing our online identity. I disagree and I believe the HN guidelines do as well: > Throwaway accounts are ok for sensitive information, but please don't create accounts routinely. HN is a community—users should have an identity that others can relate to.

We may differ in our interpretation of the phrase "sensitive information".

It used to be that most computer programmers ("hackers") understood the value of privacy.

Post reply on HN