Is this literally dead, /g/?
people kept using mpeg4-part2 (divx/xvid) for some time after h.264 landed
once hardware support trickles down to the point where it's supported most everywhere, and encoding speed/efficiency gets to comfortable levels, it'll have a chance of taking over
this time around there's some decent competition in the free video codec space, which'll make things interesting
most standards take years to overtake the original.
Media companies have an obligation to cram more shit into the same form factor. Saves money and lets consumers have their ten eighty pee video. Not to mention sales of new hardware.
Would a GPU with H.264 decoding be just as good at playing H.265 or should I stick with H.264? It's for my moms laptop with a Celeron and Intel HD graphics that has problems with some video.
>>51525565
The decoding would have to take place on the CPU so no hardware optimization for that. If hardware decoding for H264 is really working then stick with that.
>>51525353
It's technically good, but the two patent pool situation (with HEVC Advance charging for basically everything) has killed it while stillborn.
Pity, there's some good tech in it. Shame nobody can use it for 20 years. Fortunately, NetVC will be even better.
>>51525353
nice b8 senpai
>>51525565
Like >>51525600 said, it currently has to be CPU based. But from what i recall it's better parallellized than 264 meaning that moar cores can help, which mean you won't have a problem for decoding,
Also it means we can see CUDA\CL GPU Support for GPUs lacking in HW h265 decoders
Sucks that it's in shitty licencing land - If they're smart they'll loosen up before other encoders come along
>>51525353
It's a strong powerful Blu-ray codec that don't need no web.
>>51525353
If you want, you can download Handbrake and start encoding DVDs and Blu-Rays with h.265. Nobody is stopping you. I'm going to stick with h.264 though seeing as how everything can play it.
>>51527306
Handbrake won't do 10bit color which seems like it's not worth the encode time if you're not getting one of the major features.
For streaming sites?, pretty much. VP9 brutally murdered HEVC in that perspective.
For local storage? Not really, it just takes too long to encode video at 1080p even with an i7/fx-8xxx. Encoding times will be improved as time goes on as well as efficiency. Last I checked the latest x265 encoder is 30-40% more efficient compared to H264 and we might see the promised 50% efficiency in 2016.
>>51525353
>the one codec that will be used for 4k streaming
>"Eyo /g/, /g/, is it dead?"
Mate.
>>51528048
It's a dead format for streaming though, nobody wants to pay the 0.5% royalty fee. VP9 automatically wins even if it is slightly less efficient.
>mfw i found out handbrake does h265
>>51528085
Sure thing, potate. Hold on to your "VP9", one day it'll really win over everything! Just like Linux!
>>51528098
It only does 8-bit encodes. Use staxrip instead, it lets you encode 10-bit h265
>>51528115
I'm ripping my twilight zone dvds. I doubt it really makes a difference.
>>51528098
>handbrake
>>51525565
>Would a GPU with H.264 decoding be ju
h265 needs special support
>>51525600
>The decoding would have to take place on the CPU
>>51527128
>Like >>51525600 said, it currently has to be CPU based
wrong, there are GPUs capable of h265 decoding
>>51525353
daala > H.265
muh patents
Literally all next gen blu rays are going to be HEVC 10 bit 4:4:4 I don't know what the fuck you're on about OP.
>>51528101
If HEVC is so fucking cash why doesn't youtube use it? Why are almost all of their streams using VP9 + vorbis/opus?
>>51528217
Probably because they want their videos to look like SHIT
>>51528115
Is it missing other features?
>>51528224
nice meme, unfortunately for you he's right. VP9 might not match HEVC but it's still better than H264 and is being improved constantly.
>>51528256
Not really, does everything handbrake does and more.
>>51528217
I use edge (xd) with flash disabled and YouTube works just fine.
Google is keeping a vp9 and a h264 copies of every video...
What retards.
>>51528275
> unfortunately for you he's right
Which part of your post or your image shows that "he's right"?
Braeburn, just accept HEVC. It will happen and there's nothing you can do about it.
>>51528275
I'd choose a little quality loss over getting buttfucked twice every time.
And so does google apparently.
>>51528299
BRUH, I'm not saying hevc is bad per se, it's the best video codec out there in terms of compression efficiency. The problem is you have to pay a royalty fee to use it for things like streaming video else you get sued into oblivion.
What sounds better: paying 0.5% of your income to the hevc jews or using vp9 which is only slightly less efficient but literally costs 0.000$ to use?
>>51528297
The h264 copies are for mobile devices. Though they'll scrap those encodes when they feel even $40 wallmart chink phones can play 720p vp9.
>>51528592
Or when iOS supports VP9
>>51525453
I thought h.264 was mpeg4.
Speaking of VP9, why doesn't 4chan allow it?
I fucking hate having to make everything 3MB to look decent.
>>51528166
What's the point of 4:4:4? Why not just use RGB?
>>51528761
it is, mpeg4-avc
>>51528146
There are obviously GPUs capable of decoding H265. They're designed to run generic algorithms.
The real question is "Are there any GPUs with hardware dedicated to H.265 decoding"
And the answer is no. Because H.265 is too new. H.264 decoding is available on pretty much every CPU/GPU because the algorithms are well known, but people are still doing research on H.265.
>>51529043
Why did they call them both mpeg4? Confusing as fuck.
>>51528159
>daala
i hope you're joking son. vp9 is pretty nice. i hope vp10 can properly compete with hevc though.
>>51528115
>he fell for the 10bit meme
>>51528275
>PSNR
Wasn't there even a study that showed how poorly that metric correlates with human perception of video quality and/or artifacts? Yes, higher PSNR is usually an improvement within a single codec but encoders trained for it instead of something smarter tend to look like blurry shit.
Which is probably why VP9 scores so high there even at higher bitrates. It's clearly quite efficient at streaming rates though.
When it doesn't completely miss slow motion and cause stuff to pop around on I-frames, but that's probably more of a problem with specific encoders.
>>51528978
RGB is kind of wasteful desu; most of the visual information we want is still in the image's brightness and not color.
Take a bunch of natural images, break them into some luma + chroma encoding and see how much less "busy" the chroma components tend to look. There's a reason color subsampling has survived this long.
>>51525353
HEVC patent collectives are going full jew and asking for a percentage of revenue instead of a flat licence fee. Unless they change that no-one of any size (Facebook, Google, Netflix, etc) are going to use it or will discontinue using it (see: Netflix). VP9 is a likely candidate to replace h.265 where it was planned for use, but both still suffer from the same issue somewhat: they're not mature enough for wide spread deployment (encoder apis are changing too much atm, even decode can be affected, see: VP9 1.4 -> 1.5 notes).
>people using handbrake
>not ripbot or megui
Those two give way better quality tbph
>>51529610
>Those two give way better quality tbph
>megui
Both of those us FFmpeg and or the same encoders / libraries (x264, x265, etc).
>>51528101
Linux did literally win tho
>>51529610
>not just using ffmpeg
wtf xD
>>51525353
>literally
Of course not, death can only apply to living organism. The video standard isn't dead as it couldn't possibly be bereft of life in the first place.
>>51530726
>dead /dɛd/ - adverb 1. absolutely; completely.
>>51530752
Adjective, not adverb.
>>51530814
>dead /dɛd/ - adjective 2. complete; absolute.
>>51525353
Yes. VP9 (short term) and NETVC (long term) are what's actually usable instead.
http://blog.streamingmedia.com/2015/07/new-patent-pool-wants-share-of-revenue-from-content-owners.html
RIP in pieces HEVC
>>51530879
You have a very strange dictionary.
>>51530913
>google is strange
>>51528275
>Graph from 2013
>PSNR
How about a graph from 2015?
>>51530880
>implying the MPEG won't just line Sony's pockets some more and force HEVC as the mainstream codec for another 10 miserable years
the jews always win
>>51529703
>Need a gui for encoding video.
desu senpai
>>51530880
But both of them are worse than h265
H265 literally turns a 1080p h264 into a file 65% of what it used to be in size. The encoding times aren't even bad if you don't use 10 bit color and use some relatively new CPU
I don't want to see h265 die, VP9 sticks dick, I tried transcoding my videos from h264 to VP9 and the encoding time was even longer than h264 to h265, plus the file size was also larger in comparison
Pls don't tell me h265 is going to die, I love it
>>51529232
Doesnt the GTX 960 have dedicated encode decode?
>>51528217
>google is a major dev of vp9
>youtube is owned by google
>why does youtube push vp9
>>51531897
For what? There are 5 standards being discussed here. None of which are compatible with each other.
