>download one season of a show in x264 >12 gigs >download

Because VP9 exists and is the child of prophecy.

PLEASE ENCODE MORE ANIMU IN H265

>>61563398
Storage still cheaper than processing.

>>61563398
Because it's shit.
AV1 soon.

The whole point of x264 was making bloated files to have a sense of superiority.

Doesn't x265 have expensive royalties for websites to provide it as a format for their content?

>>61563398
Yeah sure thing pal. How about posting the source and a comparison?

File: 1474391877184.gif (140KB, 379x440px) Image search: [Google]

140KB, 379x440px

>>61563398
>why the fuck isn't x265 the standard yet?
H.265 uses about 150-250% more CPU to decode a single frame. To save on some bandwidth, you pay in CPU costs.

Download H.265 only if you have HW that supports decoding. Don't bother if you have an older GFX card/CPU.

Only Kaby Lake and Ryzen support CPU HW decoding. Some GFX cards do too.

Also, it's important to note that H.265 will be replaced soon too. It will be a short-lived standard. That means that not much hardware (DVD/BluRay, TVs, tablets, phones) will support it. Everything supports H.264 decoding however.

>>61563481
>VP9
It's a joke of a standard. Uestionable legal status, Google won't indemnify you if someone says it infringes something and no hardware supports it.

File: apu.png (6KB, 612x491px) Image search: [Google]

6KB, 612x491px

>>61563398
>same quality
>larger file
>better

10 bit needs to become standard. Behead all banding.

>>61564087
>10 bit meme

>>61564065
>Also, it's important to note that H.265 will be replaced soon too. It will be a short-lived standard. That means that not much hardware (DVD/BluRay, TVs, tablets, phones) will support it. Everything supports H.264 decoding however.

H265 hw decode support has been around on smartphones for a while now.

File: 1470534930500.png (245KB, 900x827px) Image search: [Google]

245KB, 900x827px

>>61564104
>hey guys I can't find attack on titan on kissanime, what's your favoring streaming site? :)

File: 1500556601977.jpg (155KB, 500x492px) Image search: [Google]

155KB, 500x492px

>>61564083
>frogposter doesn't know the difference between one season and an entire series
Does the_leddit lack basic reading comprehension skills?

>>61564134
>unironically watching anime

>>61563398
because it needs at least 15 times of computational power to encode and 3 times to decode. however HEIF/BGP is a cool idea as JPEG is unsuitable for large photos

>>61564083
Trying reading again

>>61564168
>however HEIF/BGP is a cool idea as JPEG is unsuitable for large photos
Once again Apple leads the way.

>>61564150
I hate summer. Please leave.

File: reddit shown.jpg (77KB, 500x667px) Image search: [Google]

77KB, 500x667px

>>61564200
Only summers ever call anyone summer.

>>61563398
>same quality
Not likely. x264 had very gradual quality deterioration as you lower bitrate. x265 is even better. This doesn't mean they don't degrade.
Most encoders at this point are going for perfection, not mini encodes, and at the same quality x265 is not that much smaller. It's also only gotten over its major quality issues recently, and encoding settings are not a solved problem yet. It's not like x264 where you can just set --preset veryslow and be better than the scene in its entirety. x265 is so slow on current hardware that you have to skimp on settings, and exactly where each one comes out quality-wise can be hard to find. Eyes trained for finding and fixing x264's encoding flaws are not yet trained for x265's. You even have to make a judgment call over whether its smoothing is an improvement over the source.
Basically very little of the work at finding the best settings is done yet, and doing that work yourself is monumental. Once some sort of general baseline is reached and only a few settings need to be messed with I think you'll see more people switching.

>>61565395
Adoption is slow for the same reason that divx and xvid were popular long after h264 was in regular use.

It has nothing to do with scene encoder options.

>>61565477
The existence of people who can't encode has nothing to do with the slow adoption of H.265 by people who can.

>>61563889
This.

I'd rather pay for another 8TB drive than have to upgrade my CPU on my Plex server to hand multiple x265 streams.

>>61565602
Why do you transcode?

>>61564065
I run x265 1080p on my Q6700 + 8800GTX fine

So kek ?

>>61565602
Also, plex is a big blob of shit. Use apache.

>>61565634
No client would be able to handle x265 natively. That's my point, x264 is ezpz, with either direct play, a container change, or simple downscaling to the user's res/bitrate.

However, most of the people that use my Plex server are streaming at original quality, thus reducing the load on the server. I don't think I can handle 10 concurrent streams of x265 like my current server can with x264.

>>61565655
What? Why the fuck would I want to host a web server instead of an entire multimedia server?

>>61565640
Decade old stuff, nice.

Daily reminder that x265 != H.265/HEVC

>>61565640
Enjoy your 0.2 fps :^)

>>61563398
>why the fuck isn't x265 the standard yet?
Who says it isn't?
All of my collection is in HEVC now.

>>61565395
There are groups that have being using HEVC for years. It's pretty much perfect right now, with files getting close to 50% the size.

>>61566958
No doubt the encoder's ready. No one wants to take a month to encode what x264 can do in a day, though, or figure out what can be done to turn that into a mere week.

File: chewtose.jpg (143KB, 962x1063px) Image search: [Google]

143KB, 962x1063px

We need moar animu on VP9

>>61565722
fuck off

>>61564065
>and no hardware supports it.
Intel QuickSync does

>>61565722
Please elaborate? Is there something I could read?

>>61563398
It's proprietary and expensive.

>>61565662
you can literally buy tv boxes from aliexpress with hardware h265 decoding for 50 bucks.

>>61563398
My private tracker has a listing for x265 videos tv shows, I have downloaded couple to test quality and desu I think its the same unless I am missing something.

>>61564065
>His processor can't decode x265
Even my pi can decode 4k x265 at 30fps or 1080p at 60fps you dumb fuck.

Am I the only one who thinks HEVC is too blurry at lower bitrates? Sure there are less artifacts but its a blurry mess and almost all scene releases don't have a bitrate high enough to preserve sharpness. They actually think their 500 MB 1hr episodes are high quality.

>>61567680
x265 is the encoder. H.265 is the codec/standard.
It's the difference between LAME and MP3.

>>61565477
Fuck off pissphone.

>>61563398
you could've been more specific with "download entire series", asshole. Shit like Mission Hill's entire series was one season, and with that presumption in mind, it can completely ruin your example.

>>61567937
No it can't

>>61567947
And the stars align. This makes sense.

Thank you for the straightforward explanation.

>>61564158
>unironically complaining about anime on the anime board

>>61564087
Almost everyone's monitor / gpu* is still 8bit though.

*there's a difference between 10bit color LUTs and a 10bit output signal; the former is missing from non-quadro or firepro lines.

>>61567104
We need more weebs in hell

>>61567937
>decode 4k x265 at 30fps
LMAO. it can't.

File: printscr.jpg (184KB, 1920x1080px) Image search: [Google]

184KB, 1920x1080px

>>61565640
i do to on a duocore and fermi. guess the video cards do everything

File: 1498833668846.png (89KB, 363x475px) Image search: [Google]

89KB, 363x475px

>all this public tracker plebs that have never seen true quality releases arguing

>>61567937
No it can't

>>61568076
>muh sekrit club

File: 1481070957000.png (208KB, 5000x5000px) Image search: [Google]

208KB, 5000x5000px

>>61568387
>muh opinion based on YIFY releases matters

>>61568011
And? There's a difference between dithering 10 bit to 8 and truncating the quantization to 8 bit.

>>61567031
1080p is what, lets say 25gb a movie
4 times that is 100gb (4k)
then you have hdr which should be 4 times the number of colors, how much this adds i am not sure so lets estimate without better compression this would at 20% so 120gb
now you have a potential push to 8k which would be 480gb a movie

And this is completely ignoring the potential of the rise of vr as a viewing device, because not everyone can attend a concert or a sporting event, but there is a good number of people who would get google cardboard or something like it if you could get a virtual seat.

now when you look at streaming, what would be best for you? you have some competition here so an edge will win, if youtube offered 4k video at half the bit rate a competitor does, with the same or potentially better quality, why would you use the competitor?

There is vested interest in making codecs more efficient and better, for normal people who don't demand 100% quality to archive, the less space it takes up the better

>>61568679
Everything you said is true, however the fact of the matter remains that someone has to do the grunt work to optimize the decoding/encoding otherwise we'll just have to wait for hardware and bandwidth to get better. People just can't make money encoding to x265.

>>61568734
you are assuming that the encoders won't get better and that people won't throw hardware at it to make it faster when the results are worthwhile.

File: pcspec.jpg (758KB, 1150x1550px) Image search: [Google]

758KB, 1150x1550px

>>61567937
>>61568195
Educate yourself. Orange Pi Pc has built in hardware 4k video decoding.

>>61563398
>why the fuck isn't x265 the standard yet?
because plebs cant decode it

>>61564065
>Only Kaby Lake and Ryzen support CPU HW decoding.
my skylake can handle it just fine

problem with x255 is the retards using it. they don't bother grabbing the TS or untouched bluray. it's just endless re-encodes of scene releases.

>>61563889
This, but because not enough low end processors/GPU handle HEVC main 10

>>61564065
>Ryzen support CPU HW decoding
Not they don't, they are not SoC

>>61563935
>AV1 soon.
When?

>my UHDTV handles HEVC 4K
>CPU at 80% when trying to stream x265 content through Plex
Why? Is HEVC and x265 not the same thing? The server isn't even reporting anything being transcoded, just says my computer is weak af

>>61569911
do you have vaapi or vdpau supported decoding? if not, that's normal for x86 architecture.

some cheap intel pentiums reach 99% cpu usage on software decoding

tv's and smartphones on ARM have awesome hardware optimization


actually, the whole x265 is targeted for planned obsolescence since old computers will not be able to handle streamed hevc movies

for x264 tvs, youll need either a separate transcoder ( and the decoder to output x264/mpeg4 on the tv ) or just buy another tv lol
... if the transmission is changed to hevc in the future (coaxial cables do not allow enough data rate even for 1080p, not even to talk about 4k, its upscaled, lol)

probably for native 4k everyone shall have to skip to hevc or they will keep upscaling 1080i and directly do 8k hevc

>>61563935
Waitfag detected

>>61570009
Works fine on my z3735f and Snapdragon 820.

Only processor I've seen struggle with x265 is my turion x2 laptop.

File: vKkFX.jpg (132KB, 500x375px) Image search: [Google]

132KB, 500x375px

>>61569870

>>61563935
>>61569870
We will have it in year 2122 so just wait and use xvid + ac3 instead and save it as .ogm and have subtitles in seperate .str or .txt files.

Personally I prefer intel indeo (IV32) and wma sound with burned in yellow subtitles, it's the best!

My second option is good old .rm for streaming. Who needs more than 512kbps bitrate in total? Even my old dumb phone supports this and not h265.

File: 1480313620386.png (275KB, 465x450px) Image search: [Google]

275KB, 465x450px

>>61568014
rude

>>61564083
>dumb frogposter

>>61570019
those both have hardware hevc decoding

i'm talking about more or less all pre-skylake cpus under i3 or even i3

>>61570154
>3.5 year old atom has x265 decoding
>2 year old Pentium does not
What the fuck Intel

>>61563398
>Not using 3ivx

>>61564200
Because you're wrong you say they're from summer? That's pretty autistic,
>>>/b/

rip ptg and tl

>>61564065
>It's a joke of a standard. Uestionable legal status, Google won't indemnify you if someone says it infringes something and no hardware supports it.
Intel supports VP9 hw decoding/encoding. And AMD GPUs support VP9 decoding in 4k. Don't know about Nvidia but bet they do too.

Also Youtube delivers much of their HD content in VP9 over H.264.

>>61565662
would you mind adding me as a friend?
[email protected]

I once had a friend with a lot of quality animu but suddenly he's gone.

>>61563398
I have same question about OPUS.
Why the fuck fucking android and ios don't support it out of the box?
And modern hardware portable players like Fiio x1080 too.

>>61573361
it's been supported in android since 5.0, ios getting support with 11

>>61564134
Kissanime

>>61563398
x265 support is still really really limited, and hardware that runs it as well as x264 is still really expensive. AV1 will replace it anyway since nobody wants to pay obscene license fees for something nobody has support for.

>>61574022
>hardware that runs it as well as x264 is still really expensive
>qualcomm snapdragons have had h265 hw decode for the past few generations

>>61574054
i too watch movie on phone
great boliwood action dance movie, song baps poosi very good sir
x265 is future, sexy future of sex robot baps

>>61568679
> 1080p
> 4 times that is [...] 4k

>>61568014
My man

>>61575841
What?

>>61570114

Good post, deserves more (You)s.

>>61575972
He is making the distinction that 4k is 4x 1080p but not necessarily 4 times the space needed.

>>61565662
>no client
Uhh I have an old laptop from 2014 which handles h265 just fine. I leave attached to my tv and it's always on running kodi. Kodi has the DAVS server added, using you guessed it, apache. Encrypted over ssl, with basic auth. My server is an old pentium 4 with 1GB ram running debian. Very low CPU and memory usage. Low overhead protocol, ALL my media is HEVC.

>>61568076
>he uses a website that forces him to use his real ip and then tracks everything he's uploaded and downloaded and how much of each he has done

You're fucked if they get raided and they decide to sue everyone involved boyo. I've been on those sites. They only provide slight convenience that is easily circumvented on public trackers by not being a retard. The risk is nowhere near worth the reward.

>>61576559
>old laptop from 2014
wat

File: 1495093750862.jpg (35KB, 640x640px) Image search: [Google]

35KB, 640x640px

Because people don't know how to encode video or even audio.

10-bit HEVC using the faster preset and a CRF of 22 + 128 vbr opus is all you need for 99% of movies/tv shows out there regardless of resolution or source type.

BUT people are fucking stupid and make it their mission to overcomplicate things to the point where they don't work properly. Instead of doing what I mentioned someone will instead use an arbitrary abr they pulled out of their ass like 15,473 kbps, encode audio with FLAC, and top it all off with the ultra fast preset and an 8-bit encoder.

x265 Hardware is cheap. I bought a China Box (Amlogik S905X Chipset) and installed Libreelec for 20 Dollars on aliexpress. It plays 4K/x265 Files without any problems.

I would download x265 versions but I like things in the far distance to be able to move.

>>61576752
top kek. Post a comparison before you make such claims.

>>61577456
Try it yourself. Most encoders out there agree that the params I mentioned give you the best balance of compression, encoding speed, and quality across all resolutions and source types.

ABR is only to be used for streaming, 2-pass ABR is to be used for achieving specific file sizes, presets slower than the faster one are practically placebos, and anything faster is only good for streaming video.