So when the fuck is pic related going to take off? /a/ has been

do you have any comparison graphs or shit
i want to know the advantage to h264

>>56580181
H264 is good enough.
BluRay isn't adopting H265.
Only a few anime rippers are using H265
Hell the movie SCENE is still on old ass XVID with only modern movies being ripped to H264

Hardware support is lackluster unless you're running the latest hardware.
By support I mean full hardware acceleration so, not software decoding.

It will never take off

http://x265.org/proposal-accelerate-hevc-adoption/

HEVC is pretty much dead

https://en.wikipedia.org/wiki/AOMedia_Video_1

AV1 will crush it in adoption

>>56580181
Some fan"subbers" on /a/ already use h265.

But from what I hear it has massive increased encoding time and very little gain over h264. So mist don't use it.

>>56580257
Size/Bandwidth at the cost of computational power and memory.

>>56580257
>>56580267
The problem at the moment is also the people doing encodes are shit at it. There's h265 rips that are twice the size but worse than the equivalent h264 versions.

>>56580181
>a fucking g4400 can play 10-bit 4k or at least 1080p
It can't do FHD 10bit much less 4k 10bit.

>>56580181
I'm not into chinktoons, but I download all new movies in HEVC, because you get a watchable quality at under 1GB and my internet is slow.

>>56580181
>/a/ has been promising me for years
That would be diaz, noboday in scene want to pick up HEVC.
Also reminder he's the one that introduced 10bit, and killed many people in house fires.

Hevc good for low bitrate. For high bitrate, h264 is still winning

File: 2016-09-13-235118_1920x1080_scrot.png (2MB, 1920x1080px) Image search: [Google]

2MB, 1920x1080px

i do some HEVC encoding

>>56580181
>>56580181
>/a/ has been promising me for years that it'll be any minute now but it just hasn't happened.

Why dont you reencode your x264 downloads and convert it into x265, then upload them it yourself (assuming you downloaded from private trackers in the first place)

>>56580278
>It will never take off

I am actually seeing a lot more x265 releases in public trackers.

Its already taking off thanks to ease in Transcoding and piracy

Explain yourself op, i encode hevc for work, 10 videos a day.

>>56580341

>The problem at the moment is also the people doing encodes are shit at it

True that. What's worse is that they're using scene encodes instead of untouched sources.

>>56580388

This

Good thing a lot more independent uploaders are cropping up every year who are not completely autistic with their uploads/releases.

KAT definitely was the gateway for non scene releases getting more popular in public trackers. Helped provide a lot more variety in quality and sizes that otherwise would not have been available

>>56580849
>reencode your x264 downloads
Wouldn't that result in quality drop?

>>56580940

Only if you are shit at it

The only way to get less shit at it is through trial and error

>>56580940
most anime releases are remuxes or transcodes of the raw releases
so anyone could grab a remux or the raws and do their own encode from the same material others use

H265 takes too long to encode and the scene folks always want to be the first one to show up with their rips, so it's low bitrate 264 all the way for them.

>>56580940

Handbrake does a decent job imo

>>56581055

There are few x265 scene releases but I doubt if these scene groups are associated with the kabal

>>56581055
>H265 takes too long to encode

It's not that big of a difference, around 30% longer.

The reason scene doesn't use it is because they're all about standards, that's why they still used Xvid a few years ago.

What are the hardware requirements to run this shit? What's the cheapest intel processor capable enough for 1080p 10 bit?

People are freaking out about this like when x264 Hi10p or whatever was going to be a thing. Half a decade later and there's barely anyone using that.

>>56581113
Anything Intel based on Skylake has is capable of 10bit decoding via Intel QuickSync, which can be enabled even if you have a dedicated GPU
http://wp.xin.at/archives/3561

>>56580181
>/a/ has been promising me for years that it'll be any minute now but it just hasn't happened.

There is x265 anime, though, anon.

>>56581113
10bit won't be a thing for a while.

Consumers are too stupid to care about colors and shit. 4K is all that matters.

>>56580181
>Hardware decoders are
A meme, i just brute force it with my CPU.

>>56581145

w-where?

>>56581171
The usual place.

>>56581187

gotcha

>>56581136
Hardware decoding on Intel is available only for 8-bit H265 on skylake.

10-bit H265 hardware decoding is only available on a handful of intel processors. I think it's mostly mobile ones. It won't be until Kaby Lake when it will actually be widespread throughout their line up.

Latest GPUs have it though so you can go that route. The problem is really with HTPCs and such

Kaby Lake has HEVC Main10 hardware decoding

No reason to buy anything but Kaby Lake, AYYMD has nothing until next year for Main10 hardware decoding

>>56581237
>No reason to buy anything but Kaby Lake, AYYMD has nothing until next year for Main10 hardware decoding
Newer GPUs have it. Besides, all skylakes can brute force 1080p HEVC Main10.

The only issue is 4k HEVC Main10. That one's a bitch. Pretty much all mainstream processors struggle there with software decoding.

You guys are forgetting that trying to decode it on a PC isn't really all that important. H264 is well supported by all kinds of consumer hardware as was xvid. This is what ensures adoption by people other than random transcoders on p2p. When you see hardware decoding in game consoles, phones, and raspberry pi like devices it will have a better chance.

>>56581348
This is the real problem.

No one in the industry gives a fuck about the PC (mac and linux included) space, as of course the hardware will be powerful enough. Its all about low power mobile and console-like devices.

>>56581294
Brute force software decoding isn't power efficient & kills battery life

>>56581465
luks gud tho

>>56581502
No it does not

Hardware decoders must match the output of software decoding as in the H.264 and HEVC spec

The outdated meme about hardware decoding being worse than software decoding has long been debunked

Go ahead, software decode 4K 60FPS or even 120FPS HEVC 100Mbps
Do you get smooth playback like on Pascal GPU's hardware decoding or Kaby Lake's hardware decoding?

>>56581548
the post was ironic, hence the memetext

here i tested with hand brake sometime ago.

http://abload.de/image.php?img=original0klbc.png original h264 around 30 Mbps

http://abload.de/image.php?img=h265itapf.png h265 10 Mbps

http://abload.de/image.php?img=h264sga5e.png h264 10 Mbps


look at geralt legs and tree.

>>56580181
>What's the excuse now /g/?
Royalties for distributing HEVC-encoded content.

>>56580862
P2P is an absolutely terrible indicator for the global video distribution market.

File: 1464464363438.png (282KB, 2800x900px) Image search: [Google]

282KB, 2800x900px

Here is an old 10-bit HEVC thread we had a few months ago for anyone interested:

https://archive.rebeccablacktech.com/g/thread/S54788597

OP was using the 10-bit x265 encoder, version 1.9+183

Latest 10-bit x265 encoder can be found here:

https://builds.x265.eu

Anyway it looks like HEVC might still be a pain in the ass to encode, taking more than 3X longer than H264 to encode so we need cheaper processors with better performance to encode video at 30+ FPS especially in 1080p. Zen sounds promising, but i dunno.

Another issue is software decoding on phones. Currently you need something like a snapdragon 805 to decode 10-bit 720p HEVC and it uses up battery life quickly. So until hardware decoders for 10-bit HEVC arrive for phones, mobile users are fucked.

>>56581640
That was actually a good thread, I remember trying to start some encoding threads before that one but none of them too off. Too much shitposting from amd/nvidia fucks.

Also the only good thread that tripfag has ever made.

>>56581640
Adding to this: the latest x265 encoder is version 2.0 but I don't think much has changed in terms for encoding/decoding efficiency, at least not by much.

>>56581635

P2P is a good indicator of mass usage, the legal market is forced to use whatever standards the big companies shove down everyones throat

HEVC will become mainstream simply because people will find content in smaller sizes with relatively less loss in quality

>>56581674
Lol, not until tablets and phones adopt HEVC will it actually take off.

>>56581674
P2P is not the masses though, its likely a fraction of a percent in terms of usage. Especially when you factor in Netflix, Amazon, and YouTube.

File: le_meme_font.jpg_large.jpg (65KB, 588x328px) Image search: [Google]

65KB, 588x328px

>>56581699
I really fucking hate this. The HW decoders exist yet qualcum refuses to put them on phones. Why are they doing this to us? We pay close to a fucking grand for a phone yet we don't get something as simple as a little embedded HEVC HW decoder? Fucking bullshit man.

>>56581640
>3X longer than H264
its probably match same speed with x264 if encoding on haswell cpu because of heavy avx2 optimizations in x265

Got 131 movies in HEVC/x265 10-bit 1080p format (Tigole, excellent encoder), they play on my LG G Flex 2 with hardware decoding using MX Player Pro, no issues for me.

Kinda miss his encodes actually, as soon as KAT died he decided to take a break, hope he'll become active again with some other site if one happens along.

>>56581674
I think you're a bit off base. P2P can support all kinds of niche formats. This usually comes by way of transcoding scene releases. A good example is what happened when the scene dropped xvid, iptorrents set up scripts to automatically transcode all scene TV releases to xvid then upload them. The shit trickles down to p2p. They're now doing the same with x265 and the download numbers really aren't that great. There's more people downloading xvid still even.

The encode time is a big factor. The scene is all about groups racing to be the first one to upload and pre something, especially on the TV side of things. Hardware support is important to them as well as you can see from the comments from the time when they dropped xvid.

Even without the scene it will take more than what's currently happening for us to see widespread adoption. Hardware decoding is what's truly important and I'm not just talking about your PC either. I can decode 1080p H264 with a shitty $30 android box I imported from China. In 2007 I was watching xvids on a $30 DVD player. That's where the demand for piracy is at, low cost devices.

>>56581743
>its probably match same speed with x264 if encoding on haswell cpu because of heavy avx2 optimizations in x265
Nope, that there is 10-bit HEVC video being encoded so intel processors don't get any shortcuts.

>>56581707

Considering exclusive content like ones on Netflix or HBO are outnumbered in viewers who pirate them, I would say P2P is relatively more mainstream than other content providers

>>56581740
Hell SnapDildo won't have them for a long time.
Qualshit still insists to segregate features between the 4xx 6xx 8xx series lineups.

Like noCA on the 4xx, 2CA on the 6xx and 3CA on the 8xx. Hell they also force the phone manufacturers to license the bands they want to use although the chipset can work with all of them.

Fucking jews and fucking features restricted to only the 8xx housefire CPUs.

>>56581740
They arent free senpai. it would force they to pay a royalty per-chip/device produced. And that shit adds up fast.

Good luck beating AV1 (successor to VP9) + Opus.

Pretty much every major software company (besides Apple) is on board the consortium behind it, CPU/GPU powerhouses like Intel, AMD, ARM and Nvidia, as video streaming providers such as YouTube, Netflix and Amazon, and browser developers such as Google, Mozilla and Microsoft.

http://aomedia.org/

https://en.wikipedia.org/wiki/AOMedia_Video_1

Well I did try some encoding and it took like 36h and saved like 1GB on a 3GB h264 that only took like 3h to encode. As long as processing power does not catch up and storage keeps cheap I don't see myself using it.

>>56581802
(in general) This is absolutely false, who told you that?

The only scenario where this may have been true, is where content wasnt available in a given country (ie, GoT and Canada etc).

Other than that, P2P is no where near as popular as legal means.

>>56581811
hopefully those dumb fucks cant sort out the patent problems and AV1 hits market before HVEC adoption.

>>56581827
Storage density is hitting its physical limit iirc. 12tb hdds being the logical stopping point before NAND becomes cheaper per gig.

>>56581811
AV1 is a streaming codec you dumb fuck. Also why would anyone use it when VP9 is already here?

AV1 will just be a meme video codec for personal use, most will start using HEVC.

>>56580862
>I am actually seeing a lot more x265 releases in public trackers.

Does HEVC have any activity outside of piracy?

I mean, having illegal activity be the central use for your format can't exactly be good PR; look what that did for BitTorrent, an awesome legitimate downloading method with a not-so-great reputation due to disproportionate piracy use, unfortunately a lot of people think that crime is the only use BitTorrent has and that includes people who make laws.

>>56581750

Well shit on me, just discovered Tigole's back doing UTR stuff, excellent.

Also, if you want a great guide on HEVC/x265 encoding, you can find it here:

https://katcr.co/community/index.php/topic,310.0.html

>>56581827
>Well I did try some encoding and it took like 36h and saved like 1GB on a 3GB h264 that only took like 3h to encode. As long as processing power does not catch up and storage keeps cheap I don't see myself using it.
You obviously have no idea how to encode video.

Replace whatever shitty stock encoder meGUI has with the latest one from:

https://builds.x265.eu

Then encode it using the fast preset and use a CRF instead of bitrate (28 is default). ALWAYS use the fast preset, the slower ones take more time and only reduce file size by like 5%.

>>56581850
>AV1 is a streaming codec

That's why it will win, because streaming is the future of video distribution.

YouTube isn't going to use H.265 anytime soon, so it's not a big concern to me.

>>56581902
>the slower ones take more time and only reduce file size by like 5%.

nope, you're the only one who dont know about encoding

File: 1464464977343.png (21KB, 1070x575px) Image search: [Google]

21KB, 1070x575px

>>56581979
>nope, you're the only one who dont know about encoding
He's right though, anything faster than the "fast" preset is diminishing returns especially at high bitrates. Unless you're trying to beat YIFY and cram movies into 200MB then the fast preset is always the best preset.

>>56580813
how comes it's memecodec, 1080p, yet so blurry?

>>56580813
>>56582097
This is why you never choose the bitrate, always use a CRF unless you are a video streaming website.

>>56582097
it's 720p

>>56582152
not sure why you think i'm not using CRF

>>56582097
Probably reencoded from an already highly compressed release. Also, modern anime has tons of blur applied in production so it's "artistic" or some shit

>>56582164
>not sure why you think i'm not using CRF
The quality looks like ass for 720p HEVC. Use a lower CRF value senpai.

>>56582152
Oh, I see.

>>56582164
> it's 720p
that explains it a bit.
it's still blurry kinda.

>>56582178
got a point there.
so I guess it's both the 720p + muh art.

>>56582189
it's only slightly softer than the source
CRF is 17

>>56582211
Dam nigga, your source is shit. Try to find a blu ray mux.

File: 2016-09-14-021756_1920x1080_scrot.png (3MB, 1920x1080px) Image search: [Google]

3MB, 1920x1080px

>>56582264
the source was pretty soft, which is why i downscaled it to 720p

here's one that is sharp enough to justify keeping it at 1080p

>>56582286
Is this 8bit or 10bit?

>>56582337
can nobody read?
>Pixel Format: yuv420p10

File: 1471759307621.jpg (259KB, 2048x1152px) Image search: [Google]

259KB, 2048x1152px

>>56582346
noice

File: a.png (107KB, 633x356px) Image search: [Google]

107KB, 633x356px

>>56582377
hevc is pretty nice

for such a small amount of additional ringing and blurring artifacts, the filesizes are pretty tiny

if i could afford the hdd's to just keep bluray remuxes of everything, i would, but until then, tradeoffs must be made

>>56580181
The anime community still had not adopted it besides some retarded 100mb rips.

Until that happens it will forever be a meme.

265 enabled TV's are already around, now the TV industry has to switch to 265 encoded broadcasting so we can finally have full 1080p tv channels. 4k tv is a meme created by manufacturers so they can pump up the sales. 4k TVs were not hard to manufacture and yet they advertise them like a fucking singularity. 4k is shilling unless you do digital painting, data analysis, movie or audio cutting.

File: 1473359694407.gif (852KB, 299x374px) Image search: [Google]

852KB, 299x374px

>>56580181
>So when the fuck is pic related going to take off?
Hopefully soon? I'm actually more interested in AV1.

>>56582286
What's your CPU temps when playing this?

File: 10bit.png (3MB, 1688x1064px) Image search: [Google]

3MB, 1688x1064px

It's so taxing just trying to watch 4K 10BIT H264

>>56582286
the second railgun was so shitty, holy hell

>>56582669
This is not the board for it, but I highly disagree.

>>56582620
only uses ~50% (out of 800%, as i have 8 cores) of my cpu during slow scenes, ~120% when there's lots happening

not sure what purpose finding out temperatures would be to you, but it doesn't put a considerable strain on the cpu

cpu is an FX8320

>>56582669
haven't watched it yet

>>56582620
not him but on i-7 x264 is ~4-8% and x265 is ~12-14%

>>56582686
OK.
Then try playing at at X2, and report back also what's the VO and what decoder?

>>56582563
I'm pretty sure Doki does releases HEVC versions for their BDs. In fact their 1080p release of Bakemono no Ko was only released in HEVC.

File: 2016-09-14-030443_1920x1080_scrot.png (3MB, 1920x1080px) Image search: [Google]

3MB, 1920x1080px

>>56582717
here's at 2x speed

>>56582778
Doki
are retards that's why

>>56582984
>128%
Not bad
What's the VO on your profile and are you using hwdecoder?
Also why use cache if you're playing files from HDD?

>>56583061

vo=opengl-hq,opengl,xv
scale=haasnsoft
cscale=bicubic
scale-antiring=1
deband=1

hwdec is set to no, not that my HD7850 could decode H.265 (probably, i don't know, if it was decoding on the gpu my cpu usage wouldn't fluctuate based on the video bitrate)

i have cache set because i use mpv also for playing youtube videos and ones streamed over local network shares, there's probably a way to selectively enable cache for different sources, i guess, but why bother, it doesn't affect ram usage that much

>>56583129
>xv
Windows?
And what's with the scale?

>i have cache set because i use mpv also for playing youtube videos

[protocol.http]
cache=yes
cache-default=200000
cache-backbuffer=10000
pause

[protocol.https]
cache=yes
cache-default=200000
cache-backbuffer=10000
pause

Here you go.

>>56582984
>FX8320
>HD7850
Must be nice being rich.

File: C90.png (281KB, 492x791px) Image search: [Google]

281KB, 492x791px

>>56583338

>>56580940
>download 14gb Blu-ray h264 rip
>reencode to 4gb h265
Yeah it will be a quality drop, but people would much rather download a 4gb h265 than a 4 gb h264

>>56581809
Then at least include a vp9 decoder.
Sure it isnt as good as hevc, but its better than h264 and a lot more free.

>>56583422
Why encode a 14 GB BD RIP in the first place?
Also VP9 when?

>>56581740
My nexus 7 can play HEVC.

>>56583258
xv is just as a fallback, so mpv can still run even if opengl isn't available
i'll try those options

>>56583338
yea man, it's awesome, got the 7850 second hand for only AU$80

>>56583641
14gb rip is fine if the source/remux is something like 20-40gb

>>56583738
No it isn't.
When I encode I try not to exceed 5GB.
Many people have no idea of using proper encoding parameters.

>>56580181
I prefer hardware decoding on my 6 year old pc so no thanks. I wont buy anything with hevc logo on it. I even disable vp9 on my browser so that my gpu can decode h264 video
h265 won't be popular until the majority of computers are new generation machines with windows 10 installed on them. (dxva h265 is not available on windows 7)
h264 with "slow" preset is pretty efficient and you can also choose to preserve detail.
many devices wont support h265 high profile for a while because it's so computationally expensive. people just wont buy those devices. simple. hevc is not efficient for decoding. it's efficient at reducing file size or preserving detail with the same file size. vp9 is a direct competitor with way lower decoding workload.

>>56583894
>5gb
1080p?
>Many people have no idea of using proper encoding parameters
i usually encode with preset "very slow" and use tunings (film, animation etc)

>>56580341
when have they been good at encoding?

>>56583928
>1080p?
Yes.
But to be honest I cheat a little bit.
I use very slow preset as well.
But it takes too long with my Core i5and have to pause the process every time the CPU temps became high.

File: vlcsnap-00013.png (539KB, 751x576px) Image search: [Google]

539KB, 751x576px

would x265 be good for blackadder
i wonder if x264 filesize of ~550mb per episode is too much of space

>>56583927
people used xvid/divx/mpeg4p2 for a long while after h264/mpeg4p10 became available for the same reasons (slower to encode, slower to decode, less hardware support available)

>>56584280
h264 was still at a point software encoding was viable. With h265 hardware encoding is mandatory and that won't change for the life of the respective codec generation.

>>56584310
Maybe I'm missing something, but I tried encoding with x265 and it was around 1.5-2x slower than x264, really no big deal.

>>56584504
with what settings?

>>56584530
I'm pretty sure just whatever was the default in Xmedia Recode. Single pass, probably average bitrate. I might check later.

File: mpv-shot0036.jpg (286KB, 1440x1080px) Image search: [Google]

286KB, 1440x1080px

>all those threads on /a/ a while back when the Evangelion blurays came out
>talking about h254,h265, different film stocks, how Anno kinda half assed the color correction for the DVDs and kept it the same for blurays

>two encoder fags sharing all this information
>one of them goes to the trouble to color correct the entire goddamn series so it looks on par with better remasters, collabs with a bunch of niggas to make new more accurate subs for End of Evangelion
>By his combined autism he makes a better product that Commie, roundabout insults them, and gets one of his torrents banned on nyaa because Commie runs that shit.
>releases patched versions that are all but fucking perfect, as they use 8bit instead of 10bit since the grain of the medium already provides enough noise for quantisation.

I fucking love the spergs on this site too. He even managed to make good Eva threads for a while that weren't full of Reifags whining about how they're victims and tumblr Asukafags shitposting.

>>56584280
>mpeg4p2
I still use mpeg 2

>>56584761
Was it daiz? What were the releases? And yeah committee run their encodes through the same script regardless of source.

>>56584761
>I fucking love the spergs
You need to be one to post on this site anon.

File: mpv-shot0033.jpg (458KB, 1920x1080px) Image search: [Google]

458KB, 1920x1080px

>>56584867
Dude's a BR by the name of Sephirotic.

https://sephirotic.wordpress.com/2015/10/11/neon-genesis-evangelion-an-article-about-color-correction-the-hideous-renewals-episode-19/

If it was Daiz it would have been in 10bit. He's got a HEVC 720p version

>>56584504
>>56584530
I checked for sure and did a quick test.
x265 takes 3.5x the time compared to x264.
Slower than I remembered, but manageable.

>>56582050
>PSNR is a good metric
lol

>>56585191
It is. While fine tuning is done in the end to better suit human vision, PSNR can give you an idea how good something is being compressed at a specific bitrate.

Also you can even try the fast vs slow preset thing at the same bitrate, both will literally look the same hinting that anything faster than the fast preset is just a waste of computational power and more importantly, time.

Yeah slower presets will reduce file sizes a tiny bit if using a CRF but it's just too insignificant to justify.

>>56580181
Never because HEVC Advance coming out nowhere and demanding all HEVC user pay additional royalties to them have all but stopped adoption of HEVC.

>>56585498
Nigga that's just for commercial use. Torrents and people using HEVC for personal use are unaffected.

Even the IGPUs in Braswell support 4Kx2K/30P H265/HEVC level 5 and 4Kx2K/60P H264/AVC level 5.2

>>56582686
>>56582984
I wouldn't call an that an 8 core but the performance there is still interesting. That pretty much confirms to me that all Skylakes and Haswells can handle HEVC Main10 at 1080p.

>>56585563
We aren't getting better HEVC encoders because companies are scared.

You do realize even open-source encoders like x264 are sponsored by large companies and have code contributions from people on payroll of these companies to work on open-source encoder codes, no?

>>56585376
Let's just ignore the literally unwatchable bitrate for a second. 1 Mbps at 720p? Are you fucking serious?

Try the test again at a reasonable resolution (4K) at a reasonable bitrate (40 Mbps+).

And PSNR is absolute garbage. That's what the VP encoders (VP8/VP9) optimized for and that's why they are always 1 generation behind H.264/HEVC. Any reasonable encoder has psy-rd settings that substantially reduce PSNR to improve overall video fidelity. Because trading away quality in faster sections for nonbanded/nonsmoothed/nonblocked static gradients is much more preferable and noticeable.

>>56585809
>PSNR is absolute garbage

Someone read the x264 blog before it got shut down.

>>56585846
It is garbage. At least use VQM, SSIM, or PSNR-HVS, which is what Daala optimizes for.

>>56584119
Honestly most anime fansubbers use set the quality too high. Especially for fucking reencoded crunchyroll 'raws'

>>56585579
just have to keep in mind 2 things;
1. hevc is definately more demanding than avc, but how demanding is avc these days? even my old 2005 laptop can play 720p30 avc youtube videos without an issue (single core 1.6GHz P4M)
2. hevc can do equivalent quality with less bits than avc, and less bits means less stuff to process, which takes away some of the difference in difficulty. what i mean is, say, a 20mbps hevc video will be considerably harder to decode than a 20mbps avc video, but in practice, you might only need 10mbps for the hevc file to be the same quality, which reduces the difference in difficulty

what i said before with my cpu usage in playing back Railgun shows that, low movement, low bitrate scenes used less than half the cpu time as fast moving, higher bitrate scenes. if the video was the same bitrate as the source avc file, the cpu usage would have been much higher

>>56581850
And being designed primarily for streaming uses is somehow going to limit its adoption? VP9 is considerably less efficient than HEVC is and it's slower to encode for similar visual quality too. There's plenty that can be updated and optimized.

>>56583894
>Many people have no idea of using proper encoding parameters.
You clearly encode for filesize, unlike others that encode with quality in mind. 5GB for 1080p will usually result in massive quality loss.

>>56587301
>massive quality loss
Not massive, but very hard to detect.
I miss around with the audio stream, that shaves away 1-2 GB.
Nobody complained.

>>56581850
>>56581913
>>56587193

AV1 is not a 'streaming' codec. Stop this meme. What's that even supposed to mean? You can stream video with every modern codec.

AV1 is basically a rebranded VP10. It's literally just a fork of Google's VP9 code base, with some Daala stuff on top of it and Google's VPX team as the main developer.

Given that VP9 was already not that far behind HEVC on real world data and given it's still in development and given the broad industry support behind it and given the godawful licensing mess of HEVC you can fully expect it to crush HEVC once it's finalized sometime next year or so.

>>56583449
Not sure if VP9 has any hardware decoder.

Actually I'm pretty certain that almost no one has mass distributed a VP9 decoder in a flagship device (excluding Nvidia, but the Shield was considered a failure so I'm not counting it).

No hardware acceleration for it unless you have a fucking 960ti

>>56587499
>transcoding your audio when its anything other than FLAC
JUST FUCK MY SHIT

>>56588877
nope, there is no 960ti famalam.

The 960 supports it though. And so do the 1070 and 1080.

>>56588950
>supporting bloat
JUST

>>56588877
source for >>56588985
http://wiki.webmproject.org/hardware/socs

>>56588985
DTS and AAC aren't bloat they are already compressed formats transcoding them will damage the quality

>>56581113
My intel 560M(Westmere 2.66GHz) does 1080p 10bit hevc decoding on one core. It runs at about 1.8GHz to do it. The laptop cost me $100 with shipping. The CPU costs about $15 on ebay.

My only guess is hardware support in this case means tablet shit because my CPU doesn't even have the AVX instruction set. It was made in 2010.

>>56589747
Of course that's what it means.

>>56587683
>AV1 is basically a rebranded VP10. It's literally just a fork of Google's VP9 code base, with some Daala stuff on top of it and Google's VPX team as the main developer.
I'm still mad about this
Daala was already pretty competitive when the code base was chosen
Fucking Google
>>56584948
Sephirotic is ridiculously based, his work on color correcting the shit mastered NGE chapters is invaluable
It would be nice if there were people half as passionate for western cartoons
>>56589020
God, the original DTS sure was awful, twice the bitrate of AC3 for the same quality

>>56580181
HEVC has been working fine here for years. I don't know what your problem is, exactly.

File: 108157-Netflix-HEVC-ORG.png (129KB, 1000x505px) Image search: [Google]

129KB, 1000x505px

>>56580257
50% more quality per filesize

>>56581151
But can you play this?

http://demo-uhd3d.com/fiche.php?cat=uhd&id=144

>>56581548
>Hardware decoders must match the output of software decoding as in the H.264 and HEVC spec
Most of them don't

>>56581640
>So until hardware decoders for 10-bit HEVC arrive for phones, mobile users are fucked.
Good riddance

>>56582050
>PSNR
dropped

didn't even look at the graph

>>56581113
>Half a decade later and there's barely anyone using that.
What? Isn't basically every single anime release using 10-bit these days?

>Consumers are too stupid to care about colors and shit. 4K is all that matters.
All relevant 4K standards also use 10-bit colors, especially the HDR ones.

File: 160913 [U⇒FHD]2015_한.드.콘_달샤벳_coreMx265.m2t [00:00:56] .jpg (185KB, 1920x1080px) Image search: [Google]

185KB, 1920x1080px

>tfw Korean stuff already into x265 and 4k

>>56590822
magnet link pretty please?

File: 1459864237560.jpg (159KB, 624x704px) Image search: [Google]

159KB, 624x704px

>>56589873

So HEVC adoption is being held back because people want to watch TV on a screen for ants with fingerprints?

dafuq mang?

>>56590869
Normies, man. Don't gotta understand them. Best just do your own thing.

>>56590836
I think this is the whole thing, 2160p (my video was re-enconded otherwise I wouldn't be able to play it)

https://www.amazon.com/clouddrive/share/mtyg4PV9MQVW2C8bLoNeIwnKv0kDuOTqgr3dSQLS9S3?_encoding=UTF8&mgh=1&ref_=cd_ph_share_link_copy

>>56580267
>BluRay isn't adopting H265.

What codec do you think 4K Blurays are, dumbass?

File: How Spooky.webm (682KB, 1280x720px) Image search: [Google]

682KB, 1280x720px

>>56590822
>mfw I can't playback 4k HEVC 60fps vids
I think it's time for an upgrade.

>>56590914
>>56590836
no wait, that's not it...


>>56590920
same for me

>>56590914
>not a magnet link
b-but thanks

>>56590945
it must be dead by now, except for me seeding

magnet:?xt=urn:btih:303076bf47bb117f968797a4e1c29ed001123347

File: hevc.png (15KB, 1593x300px)

15KB, 1593x300px

>>56590920
>>56590938
Just upgraded for 4K HEVC 60fps playback and feels good

Still struggles somewhat on HDR videos though. Note to others: Don't expect much scaling past 8 cores or so. Most videos aren't encoded with enough inherent parallelism.

>>56590963

Amazon link works fine... but can someone split the file? 11gb is too big..

ffmpeg -i kpop.ts -t 60 -c copy -map 0 output.ts

>>56590779
>What? Isn't basically every single anime release using 10-bit these days?
Not the ones with actual people downloading. Most of the the few fansub groups that still release are doing 10bit, but almost all the ripping groups are doing regular 8bit. So 8bit has a beastly share compared to 10bit even in anime.

So yeah, It's dead and even that fag, Daiz, knows it. In fact, he's currently scheming to push hard for x265 10bit instead because he fully believes there'll be widespread hardware decoding for it.

>>56590917
That's right but there's more to that. The problem is that Blu-ray isn't exactly winning against streaming. And streaming has its own king.

>>56591118
I just checked my anime folder and almost everything was High 10. The rest were older stuff or HorribleSubs.

I'm not sure what kinds of releases you're downloading, but I'm certainly getting 10-bit

>>56591171
Netflix is also looking to adopt HEVC ASAP

>>56591253
Most get their shit from HS and HS is doing 8bit to this day.

>>56580181
>"god's gift to technology in the form of Zen"
.08 has been deposited into your bank account

>>56580181

HEVC wont be ubiquitous for some time. Look at bloody audio audio codecs....

AAC / mp4 audio has been around for more than a decade. Literally every single device going back a decade supports it. It has better compression than .mp3. It has a clear Sonic advantage over because of the variable length frames in the sub band coding.

AND STILL EVERY RELEASE IS SOME SHITTY SOUNDING 320Kbps MP3 THAT IS HALF THE FUCKING SIZE OF A BIT PERFECT FLAC...

We need to ban mp3 before we start worrying about h.265

>>56591282
Wouldn't the source in this case technically be CrunchyRoll?

Anyway, it's mass market anime, only really matters for normies. For every show worth watching there will be high-quality High10P releases once the Blu-rays come out

>>56591385
So it's in use in a small part of a rather small fandom. There are very few people that actually give a shit. This is the reason why 10bit h264 failed spectacularly, Daiz. And why 10bit h265 will meet the same fate or very similar.

You can't claim the format won when it's unknown even within the target audience that would most benefit from its implementation. It's the mp4 v mp3 of anime.

>>56591490
>There are very few people that actually give a shit. This is the reason why 10bit h264 failed spectacularly, Daiz.
I'm not Daiz. I don't even know him apart from seeing his name spammed on /g/. I'm just an average anime fan.

Most of my friends only seem to have 10-bit releases as well. I really don't get why you think it failed, when literally every competent group is using it.

Who cares about what YIFY (and the YIFY equivalent of anime, HorribleSubs) uses?

>>56591490
>>56591585
Oh, and the irony is that I already have some HEVC releases of anime, too. Hope to be seeing more soon-ish.

>>56581740
720p HEVC on my $50 phone with a Snapdragon 210.
4K HEVC on my Surface 3, or any Intel Chinktablet with an Atom x5 or x7.
No HEVC on Any Apple device, even if the Intel CPU supports it.

File: Capture.png (7KB, 590x74px) Image search: [Google]

7KB, 590x74px

>>56584020
>have to pause the process every time the CPU temps became high

Set Maximum Processor State to 99% in advanced power options. That disables turbo which is a real killer. Intel is rather generous with the voltage they kick it up to.

>>56583894
Get on my level.

>>56591712
second quote meant for
>>56583738

>>56590626
so x265 > libvpx?..

>>56591810
When has this ever not been the case?

I bought a set of five ip cams and they support x265. Its coming, but we'll need hardware support, too.

>>56592663
Aren't Kaby Lake and Zen having build in support for it?

>>56591611

Is that why iOS safari doesnt do webm ?

>>56590963
>0%
:(

>>56580862
>I am actually seeing a lot more x265 releases in public trackers.

This. A lot of uploaders encode whole series to HEVC. Sure, results are mixed (there was a KAT uploader, JoyBell, whose uploads were far too small in filesize compared to the quality they promised), but people are getting there and some are even acknowledging that they are attempting different things with HEVC (i.e. some are trying to replace YIFY, some go for same Filesize as before but try to up the quality, some are halving the filesize and go for the same quality).

So funnily, I think that this codec might actually see adoption through piracy. 4K BluRay uses it, Netflix wants to try. I don't know about the porn industry.

>>56581887

Nice to know. Tigole does good stuff and has a nice balance between quality and filesize.

>>56582664

I have little trouble watching either h264 4K or h265 4K on my i7-2600K

>>56592880
Pirates have always been the early adopters for proprietary media codecs, mostly because pirates don't give a shit about intellectual property laws

hevc is great for my old af galaxy tab 2. decent quality for 200MB file? hell yeah.

>>56590914
>tfw every sweat bead on the dancers' faces visible
MUH DICK

thanks senpai

>>56580257
Pros:
>Smaller size for same quality than x264

Cons:
>Uses more resources
>Old/low power devices arent able to run it.


Personally, im changing my whole video library to x265

>>56593591
hope you're encoding from a good source
instead of transcoding yify

The Copyright issues with HEVC (h265) harm it from ever "taking off" as someone else mentioned, VP10 which was incorporated into AOMedia Video 1 (AV1) will be the "next gen" codec of choice for industry use. All of the major players are behind t he development of AV1. It pretty much combines, VP10, Daala, and Thor. Either way Youtube will witch eventually to a full AV1 spec since google said that VP9 is the last VPx codec. Then you just need to have netflix use it for their 4k/next gen encoding. After you have youtube + netflix using it, the rest of the industry will fall into line.