[Boards: 3 / a / aco / adv / an / asp / b / biz / c / cgl / ck / cm / co / d / diy / e / fa / fit / g / gd / gif / h / hc / his / hm / hr / i / ic / int / jp / k / lgbt / lit / m / mlp / mu / n / news / o / out / p / po / pol / qa / qst / r / r9k / s / s4s / sci / soc / sp / t / tg / toy / trash / trv / tv / u / v / vg / vip /vp / vr / w / wg / wsg / wsr / x / y ] [Search | Home]
4Archive logo
why aren't the Animefags and the Scene...
If images are not shown try to refresh the page. If you like this website, please disable any AdBlock software!

You are currently reading a thread in /g/ - Technology

Thread replies: 108
Thread images: 8
File: Screenshot_3.jpg (53 KB, 909x411) Image search: [iqdb] [SauceNao] [Google]
Screenshot_3.jpg
53 KB, 909x411
why aren't the Animefags and the Scene jumping on this shit right now?
>>
>>52288396
Because nobody gives a shit about 400kbps? Try the same comparison at a decent bitrate.
>>
>>52288451
I definitely give a fuck about disk space, specially when I just saw a 720p episode with 198 MB when the original was like 700 MBs. And there was 0 drop in quality.

here, check it out
magnet:?xt=urn:btih:F4436ABE6A70BE9D18662027347C97B0F375EC7C
>>
>>52288396
tfw I record clips with x265 but my browser can't play them back
>>
>>52288396
Because there are So Many other important variables than just codec resolution and bitrate. If we're going to give side by side comparisons, we need verifiably identical source data, and a full list of all options, keeping as many of them the same as possible.
>>
>>52288517
the end user doesn't give a shit, they just want good quality at smaller size, and that's what the scene is about
>>
>>52288396

>that image

Fuck where's that "60fps / 120fps" image? This is the same shit.
>>
>>52288552
https://s3.amazonaws.com/x265.org/video/Tears_400_x265.mp4

690 KB, VP9 BTFO
>>
>>52288552
https://x265.com/hevc-video-files/
>>
>>52288534
Yes, but without those things, I could make a side by side comparison that shows mpeg1 at 400kbps with a superior image.
>>
>>52288504
>what is a media player
>>
>>52288396
videophile here. they dont use it because it's shit and blurs the film grain as you can see in the op. good thing yify is dead or they would be all over this shit
>>
>>52288396
because encoding thousands of movies from source isn't that easy. especially considering x265 isn't nearly as fast as x264 yet.
just give it some time. it will become more widely used as the encoder gets better.
>>
>>52288607
yes my media player can

do you enjoy opening it up every time you click on a webm/mp4 though?
>>
>>52288477
youll be receiving a 'notice' from your isp shortly. very shortly.
>>
>>52288768
how is it any different than opening it with your browser?
>>
Yes i love non hardware decoding codecs that make my pc an oven to save a couple of megabytes.
>>
>>52288793
I doubt it, my neighbor might, though.
>>
>>52288396
Because 265 was made for streaming service to skimp on bitrate. Do your own comparison and you'll see it doesn't do much better than 264, which is tried and tested.
>>
>>52288793
my isp doesnt give a shit cus they're bros
>>
>>52288685
I assume when you're not trying to drop it to the minimum size it doesn't blur the video at all.
>>
>>52288798
>click webm/x264 mp4
>it embeds, or opens in a new browser tab

>click x265 mp4
>what should firefox do with this file
>open
>opens in new window in front of browser, notably cannot open multiple in background tabs like I can with x264 or vp8 webm

alternately

>this video file is corrupt
>have to save page as then open then go to downloads and open it in an external media player
>>
>>52288571
cool. this will be awesome for streaming
>>
>>52288451
>Because nobody gives a shit about 400kbps?
comcast-users ekxdee
>>
>>52288811
aren't the weaboos making it worse with their hi10p bs?
>>
>>52288396
>no documentation of the used program-versions, commandlines or the source-material
peer-review-status: DENIED!
>>
First GPU that supports full HEVC hardware acceleration is njewdia 960. I do have that card.

I downloaded an HEVC animu in order to test if mpv properly supports it via hwdec. Sadly, it's still CPU accelerated but it peaked around 10% usage of all my 4 cores of my 3570k.

It's a wonderful format for small size encodes with negligible "loss" in quality or for nice low-bitrate streams. Give it enough time and I say it's gonna explode.
>>
>>52288811
>he doesn't have a Carrizo APU
>>
>>52289026
some benchmarks can be found here
>http://forum.doom9.org/showthread.php?p=1706902

tl;dr: 8-bit works fine in Win/LAV filters
>>
>>52288396
I encode my movies at 400kbps with x264, and I have left quality, not right.
>>
>>52288933
Rightclick link
Play with mpv

There's a firefox addon for it. I've stopped using youtube in browser entirely, and just send the link to mpv.
>>
>>52288811
Intel IGPs have been able to fully hardware decode H.265 since the start of last year
nVidia GPUs have had full hw decoding since the start of last year, and the first-gen Maxwell cards also have partial support
AMD GPUs have had full support since the launch of the Rx 300 series in June

>>52289015
Yeah hardware support of hi10p is lacking
Fortunately 720p TV streams and 1080p upscales with mostly flat colors aren't terribly demanding.
>>
>VLC
>>
File: 1446421315326.webm (245 KB, 1280x720) Image search: [iqdb] [SauceNao] [Google]
1446421315326.webm
245 KB, 1280x720
A] 10-bit x265 encoding time is long as fuck ( ~8X as long as 10-bit x264)

B] 10-bit x265 is only ~30% more efficient than 10-bit x264 depending on source material (for now). Not sure about closed source HEVC encoders.

C] Very few android phones can play 10-bit HEVC without overheating (no hardware decoding exists for it AFAIK).

>inb4 "but 10-bit is a may may!!"
http://www.x264.nl/x264/10bit_02-ateme-why_does_10bit_save_bandwidth.pdf

10-bit HEVC is the future no doubt but it still needs time to mature.
>>
>>52289287
Very few android phones can play 10-bit AVC either.
>>
>>52289467
my i9505 plays it just fine with MX player
>>
>>52289467
Old ones, yeah. My phone has a quad-core A7 @ 1.2 GHz and it plays 10-bit 720p H264 just fine. Doubt most people have shitier hardware on their phones than I do. The Note 2 can play 10-bit 1080p H264 just fine for example (quad-core A9 @ 1.6 GHz).
>>
>>52288793
>living in Freedomistan
>>
>>52289287
I never thought I'd agree with vomit_chan, but that's pretty accurate. Once the encoding times are competitive I bet H265 will take off. Hardware decoding don't mean shit to anime encoders.
>>
>>52289524
>>52289538
Oops, I meant very few phones have hardware decoding for it. I remember struggling to get my tablet to play 720p 10-bit h264 smoothly back in early 2011, so I'd imagine it's a similar situation nowdays with h265. Just a case of waiting for processing power to improve.
>>
File: 1337891064398.jpg (144 KB, 1280x720) Image search: [iqdb] [SauceNao] [Google]
1337891064398.jpg
144 KB, 1280x720
Summoning Daiz
>>
>>52288860

would a video in x264 of "standard" bitrate have lower image quality than an x265 with the same bitrate?
Would be kinda a waste if it was only good for peddling stuff in low bitrates (._.)
>>
>find tv series 720p h264
>find 1080p h265
>same size
>prefer 1st one
>>
>>52288396
I wish that where real, but I'll call shit until I see some files to compare.
>>
>>52288571
Is this a new spy kids movie?
Because it looks fucking awesome.
>>
>>52288811
Mine handled >>52288571 fine, it's got a bloody 4260U.
>>
>>52290381
>400kbps
Of course it handled it fine.
Not to mention:
>4260U is 75% as fast as top-end haswell/skylake i7s per thread
>has HD Graphics 5000 which has hardware decoding support for HEVC


That said it also plays back fine on a non-overclocked Q6600 so I'm not sure what the guy you're replying to's problem is.
>>
>>52290638
>>has HD Graphics 5000 which has hardware decoding support for HEVC
You serious nigga? This thing's a mid 2014 unit.
Shieet
>>
>>52289287
>Giving a shit about 10-bit
Found your problem.
>>
>>52290653
Yep, as long as you're using drivers later than early 2015 it should work. I'm not sure how to set up a media player to take advantage of it though.
>>
>>52290697
Go away grandpa. Go back to watching your shitty mpeg2 rips.
>>
>>52288933
ubuntu 15 knows what to do with it
>>
>>52288396
Takes too long to encode including their filterchains, plus fansubbing is essentially dead.
The scene is slow and retarded as a rule so nothing's changed.
>>
>>52289656
STOP THAT SHIT RIGHT NOW
>>
>>52290166
anon, just watch the video
https://s3.amazonaws.com/x265.org/video/Tears_400_x265.mp4
>>
>>52290638
>>52290653
>>52290653
I got hd3000 and it plays just fine
>>
>>52291531

>comparing with 1 file
>>
File: dmV3rYOuZ9.png (2 MB, 1920x1080) Image search: [iqdb] [SauceNao] [Google]
dmV3rYOuZ9.png
2 MB, 1920x1080
>Duration : 2h 49mn
>Overall bit rate : 2 047 Kbps
>this pic
Holy shit, why haven't I heard about x265 meme before? Looks promising
>>
>>52288396
both look like shit desu senpai
>>
File: russia.webm (2 MB, 640x360) Image search: [iqdb] [SauceNao] [Google]
russia.webm
2 MB, 640x360
How can I convert my 264 videos to 265 on Ubuntu, OSX and Windows?
>>
>>52292132
https://trac.ffmpeg.org/wiki/Encode/H.265
>>
File: mpv-shot0001.png (2 MB, 1920x1080) Image search: [iqdb] [SauceNao] [Google]
mpv-shot0001.png
2 MB, 1920x1080
>>52291986
Spacesuit looks good, but her face is smeared out. Compare to this x264 version.
>>
>>52288571
Does it have sound ? I can view it, but it's mute.
>>
>>52288571
>VP9 BTFO
>Doesn't post a vp9 version to compare
>>
>>52288396
Because I don't stream anime? I also have 10 terabytes of disk space.

Either way, H.265 once apart of the hardware decoding will be a good thing.
>>
>>52292438
>4chan
>VP9 compatible
>>
>>52292426
Pls respond.
>>
>>52288396
Very few hardware players support H.265 playback.
>>
>>52295527
they linked the other one too
>>
>>52295562
Who cares? It's about time you put your lazy niger CPU to work.
>>
>>52288396
Scene won't jump until there is ample enough support. That's why they didn't jump on h264 until bluray became popular and suddenly we got tons of hardware HDD players; but they didn't give a fuck about it for the previous 3 years when only anime fags encoded in h264 (which at the time required high-end hardware to decode, and GPU decoding was unreliable).

I'm surprised that the anime scene didn't already switch to it en masse. Maybe the encoders there aren't impetuous teenagers anymore, who jump on unproved new tech because it has 1% better compression or can do two more colours on subtitles (remember OGM?).
>>
Which is better, VP9 or H.265?
>>
>>52288582

Everything posted there looks like complete shit.
>>
>>52288860
>Because 265 was made for streaming service to skimp on bitrate.
No, H.265 is meant to cover all areas. It's just x264 (the best H.264 encoder) has had years of fine-tuning of bitrate allocation for human visual perception. (the best PSNR or SSIM scores don't necessarily result in the best looking encode. The developers keep inventing new algorithms to hit problem areas.)
x264 used to destroy backgrounds. It used to murder fades. Now it does its job much better.
x265 is much better at this point in its development than x264 was. It just hasn't been refined to where it can match x264 at high bitrates though. x264 is less efficient, it's just much better at hitting every area to the exact degree it needs.
x265 surpasses x264 at low bitrates, and it will eventually surpass it at every bitrate. It will just take a few years.
>>
File: 1442020841781.jpg (183 KB, 640x931) Image search: [iqdb] [SauceNao] [Google]
1442020841781.jpg
183 KB, 640x931
>>52295593
>It's about time you put your lazy niger CPU to work.
>try playing it on my htpc
>mfw puts so much stress on the cpu it fucking overheats

I'm gonna wait for that hardware support.
>>
>>52296025
Unless you have a fucking celeron laptop or dual-core android device then your CPU should not be overheating from HEVC playback.

You either have a virus on your laptop or way too many apps hogging the CPU on your phone.

I mean I have a prevail lte and it can play 720p hevc just fine without overheating on software mode. Though 1080p hevc stutters often and my phone does get pretty hot after a while.
>>
>>52296025
>pc overheating from hevc playback
jesus anon, what kind of cpu do you have?
>>
Is there a chance alternative codec (such as daala, thor or vp9) will take off, or will we be stuck with yet more patent-encumbered codecs?
>>
because most shows are just crunchyroll rips
>>
>>52292426
no it doesn't have sound
>>
>>52295606
it's because of horriblesubs. Fansubbing is getting killed by sub snatchers from crunchyroll or other online sites
>>
>>52295737
not for its size
>>
>>52288396
>why aren't the Animefags and the Scene jumping on this shit right now?

Because Animefags actually do REAL WORLD test encodes with sane bitrates and have unanimously concluded that HEVC still sucks when using decent bitrates compared to h264, mainly due to blurring out details at the same bitrates h264 manages to retain them.

You get the same or better quality encode using x264 in at least half the encoding time compared to x265, so no one is using it.

One thing though, HEVC is optimized for 4k and upwards, once we see anime releases in these resolutions then HEVC is likely to be the winner, for 1080 downwards I doubt it will ever beat h264.
>>
File: 649330859.jpg (29 KB, 250x400) Image search: [iqdb] [SauceNao] [Google]
649330859.jpg
29 KB, 250x400
>>52297917
>using a bitrate instead of a crf value
ISHYGDDT
>>
>>52288396
H.265 is royalty encumbered shit.
Wait for Daala.
>>
>>52298021
>using a bitrate instead of a crf value

When you do comparisons you use a fixed bitrate you dumbass, CRF has no fixed bitrate and the values are not consistent across encoders, like for example x264 and x265.
>>
Anime groups are codec hipsters. When H265 gains wide hardware decode support, someone like Daiz will come along and say "lol we're gonna do H265 but with a profile that NO hardware decoder will support". Then literally every other group will follow, except for shit like Crunchyroll.
>>
>>52298038
>Wait for Daala.

Daala is being assimilated into the next gen royalty free codec from the Alliance of Open Media, consisting of Google, Netflix, Amazon, Microsoft, Cisco, Mozilla, Intel.
>>
>>52288396
>Animefags

Because the creator of x264 is one an animefag for one thing.

>400 kbps

lol.

Also this X265 shit fucks with my CPU heavily.
>>
>>52298092
But aren't h264 and h265 CRF values pretty much the same? ie, 28 for yify quality, 22 for okay-ish quality, and 16 for high quality video.

I did a test encode on a 5 minute clip with both codecs at 22 crf. The h265 version ended up being ~25% smaller and looked pretty much the same.
>>
>>52298126
>Anime groups are codec hipsters. When H265 gains wide hardware decode support, someone like Daiz will come along and say "lol we're gonna do H265 but with a profile that NO hardware decoder will support"

No, they are simply always going for the best quality per bit, 10-bit x264 is what delivered this so they used it, fuck lack of hardware support.

Same will happen for HEVC if x265 comes up with non-hardware compliant encoding settings which deliver better quality per bit.
>>
>>52298126
>codec hipsters

You really should just gb2>>>/a/
>>
>>52298200
>But aren't h264 and h265 CRF values pretty much the same? ie, 28 for yify quality, 22 for okay-ish quality, and 16 for high quality video.

No they're not, the only real consistency is that lower values equal better quality, otherwise they don't correspond at all (unless through pure luck), the x265 devs have been quick to point this out.

That you can't see any real difference in motion is very typical, in fact the whole CRF concept is based upon this as it is all about lowering quality in high/medium motion scenes and save those bits for low motion scenes where the quality gains are noticable.
>>
>>52298337
oh ok, thank you for sharing that. I had no idea the crf was different for x265.

It feels retarded though, a CRF is suppose to eliminate all the bitrate guesswork and make encoding excruciatingly easy. I was hoping the devs would have figured out to keep the crf values the same for both codecs. Shame, it would have made comparing these two codecs easier imho.
>>
>>52288607
>Drops glass
A little pile of secrets , but that enough...
>>
>>52296025
>video playback stuttering on an htpc
Unless you built that PC out of old ass parts or shit from a dumpster, you should be ashamed.
>>
>>52298126
>lol we're gonna do H265 but with a profile that NO hardware decoder will support
http://www.dualshockers.com/2015/06/05/new-xbox-one-update-fixes-multiplayer-issues-adds-hevc-10-bit-codec-and-more-patch-notes-inside/
Even Xbox one supports 10bit HEVC.
>>
>>52298683
He probably just did what /g/ told him to do.
>>
>>52288396
because it takes 50 years to encode minimal settings
>>
>>52288571
That's actually pretty impressive
>>
>>52297144
sub snatchers?
>>
>>52288396
i've seen a lot of tv show reencs in h.265, the problem is that right now they only seem to be targeting the "microHD" uses, that is, they're really undershooting the bitrate
a 200MB h.265 720p 45 minute show doesn't look as good as a 1.3GB h.264 720p 45 minute show guys, where's the more sensible ~600-700MB h.265 versions?
>>
>>52300242
Horrible subs. those guys steal subs from the streaming sites
>>
its the future anyways, going to be pretty much required for 4K video.


>The average bit rate reduction for HEVC was 52% for 480p, 56% for 720p, 62% for 1080p, and 64% for 4K UHD
>>
>>52288571
i made an x264 version

https://jii.moe/E1KN37Owl.mkv
>>
>>52301651
>profile [email protected]
>not Placebo
>>
>>52288396
meme format and shitty encoders, also nothing supports it natively yet.
>>
>>52288793
I live in burgerland and have pulled in over a terabyte of anime and no one has said shit.
Thread replies: 108
Thread images: 8
Thread DB ID: 376420



[Boards: 3 / a / aco / adv / an / asp / b / biz / c / cgl / ck / cm / co / d / diy / e / fa / fit / g / gd / gif / h / hc / his / hm / hr / i / ic / int / jp / k / lgbt / lit / m / mlp / mu / n / news / o / out / p / po / pol / qa / qst / r / r9k / s / s4s / sci / soc / sp / t / tg / toy / trash / trv / tv / u / v / vg / vip /vp / vr / w / wg / wsg / wsr / x / y] [Search | Home]

[Boards: 3 / a / aco / adv / an / asp / b / biz / c / cgl / ck / cm / co / d / diy / e / fa / fit / g / gd / gif / h / hc / his / hm / hr / i / ic / int / jp / k / lgbt / lit / m / mlp / mu / n / news / o / out / p / po / pol / qa / qst / r / r9k / s / s4s / sci / soc / sp / t / tg / toy / trash / trv / tv / u / v / vg / vip /vp / vr / w / wg / wsg / wsr / x / y] [Search | Home]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.
This is a 4chan archive - all of the shown content originated from that site. This means that 4Archive shows their content, archived. If you need information for a Poster - contact them.
If a post contains personal/copyrighted/illegal content, then use the post's [Report] link! If a post is not removed within 24h contact me at [email protected] with the post's information.