Which video encoding has the best balance between compression efficiency and speed?
The one used in broadcast, based h264
>>52347060
*satellite broadcast
>>52345527
H264 High 10 Profile. You can use the free encoder x264 if you want to try it:git clone git://git.videolan.org/x264.git
cd x264
make clean
./configure --bit-depth=10
make
>>52347425
I don't think that 10bit is necessary, i'd stick with 8bit for home encoding
>>52345527
h.264. but only if you use x264.
>>52347425
More devices support h265 out of the box than h264 10 bit
>>52348105
It reduces color banding and improves compression efficiency a little. Why would you NOT want to use it?
http://www.x264.nl/x264/10bit_02-ateme-why_does_10bit_save_bandwidth.pdf
>>52347425
Pretty much this (for now). HEVC still needs to mature.
>>52348166
>ateme
kek, are they still in business?
The pdf you linked isn't saying anything, it just shows some boxes and says some buzzwords.
10bit may improve compression of a bit but it's also because you're working on bigger files so you have higher margin
>>52348144
>>52348186
I have one of these
http://www.sony.com/electronics/televisions/xbr-x830c-series
I put Kodi on it and it runs HEVC 1080p flawlessly but lags like hell when playing h264 10 bit stuff.
>>52348254
>The pdf you linked isn't saying anything, it just shows some boxes and says some buzzwords.
Are you retarded?
>>52348301
at least i don't use nickname on an anonymous image board
>>52348314
It's called a tripcode. You're anonymous, you're suppose to make tripfags look bad and correct them. You're not doing a very good job.
>>52348353
sorry anonsan, i'll try to do better
>>52348166
no hardware decoders.
hevc you fucking plebs. Stop being so fucking poor and buy a xeon processor.
VP9 reporting in. GPU based encoder leaves ur shit in the dust, famz
>>52348392
This is a bigger problem for 10-bit HEVC. Not so much for 10-bit H264 especially with modern android smartphones. Yeah hardware decoding saves battery life but I think it's exaggerated. Software decoding for 10-bit H264 and 10-bit HEVC exists though 10-bit HEVC tends to overheat almost all android smartphones.
>>52348432
Let's not kid ourselves, VP9 encoding sucks ass on the GPU. Yeah it's fast but the file sizes are huge thus negating the improved compression efficiency claimed over h264.
cpu encoding or go bust.
>>52348394
enjoy your smartphone fires and only 20% better efficiency over h264 you fucking hevccuck.
H264 is still king in my book. H265 takes way too long and the payoff is very little. Low bitrate H265 looks like garbage compared to using a little more with H264.
>>52348468
>tfw android phone from 2011
>>52348432
>VP9
>hyped in 2012
>4 years later still a meme
>>52348602
>Low bitrate H265 looks like garbage compared to using a little more with H264.
The video codec is still relatively new, it needs time to be optimized and improved. The latest x265 encoder is rumoured to hit ~35% better compression efficiency over the latest x264 encoder. Still not 50% better but we'll get there... eventually.
Who the fuck is virgin enough to watch videos in a 5 to 5.5" smartphone
>>52348623
Youtube uses it so it's not really a meme, at least for video streaming websites. Not like they had much choice. It was either use VP9 or become a hevc cuck and pay them that 0.5% royalty fee thing.
>>52345527
What video player does /g/ recommend for x265's?
>>52345527
What about Daala or Theora?
>>52348622
bruh it's 2016. At least get a 2nd gen moto e.
>>52348748
They're memes at this point until further notice. Theora won't be improved much so I think it's a dead video codec at this point.
>>52348749
but my S2 still werks
>>52348748
>Daala
I heard good things about this, I'm looking forward to it.
>>52348880
maybe family. But it's always good to upgrade to keep up with emerging tech at least every 4 years. I'm not even telling you to shell out 800 bucks for an s6 edge. The 2nd gen moto e can be found for 60 bucks sometimes yet it features a quad-core a53 cpu at 1.2 ghz which is more than enough for at least 720p 10bit 720p.
>>52348715
>It was either use VP9 or become a hevc cuck and pay them that 0.5% royalty fee thing.
>0.5%
>ZERO POINT FIVE PERCENT
Yeah they would sure have gone bankrupt with such huge fees.
>>52348964
I really want to upgrade, but no phone that is not completely overpriced matches my criteria :(
>ARMv8
> 2GB RAM or more
>at least 720p
>removable battery
>good cyanogenmod support
Might get an LG G4 when it becomes a bit cheaper.
>>52349011
For a company as large as youtube it would have meant millions in royalty fees which they can't afford.
Why do you think they launched youtube red as well? Google hasn't really generated that much money from youtube.
>>52349058
what about the 3rd gen moto g? They have a 2gb ram/16gb rom version for like $220 on amazon right now.
>>52349089
sure thing m8
>>52349139
moto g has no removable battery though.
>>52349139
>no removable battery
>no 5ghz wifi
>>52349162
Even IF they could afford paying the fees, why would they when VP9 is about 90% as good as HEVC?
Face it, VP9 shit all over hevc and will soon be adopted by more streaming websites. Yeah it takes a little longer to encode but you don't have to pay that gay royalty fee.
Though to be fair, hevc is still better than vp9 but only for home use.
will we ever be allowed to post vp9 webms?
>>52348964
Why should I "upgrade" from my Droid 4 when it's the best Android phone with a physical qwerty keyboard - not having a keyboard is a downgrade regardless of the specs.
>>52348734
mpv
and stop using apostrophes to form plurals you fucking idiot
>>52350197
>I can't touch type on a touchscreen keyboard in 2016
Sorry to hear you have brain damage.
>>52350247
>wasting effort learning a skill that is only needed because of the removal of an objectively better input device
no
>>52350247
also
>literally wasting screen on buttons
>>52350284
Not really. Physical keys on a phone cause thumb strain faster and overall reduce your WPM. I know because I had a slide out keyboard nokia phone before I got my S3.
>>52350375
Typing against a flat surface that doesn't have any give or tactility causes far more strain for me than using my Droid 4 keyboard.
>>52350303
I don't see the problem. It makes phones more compact and increases their battery lives. They keyboard only pops up when you need to type something.
>>52350403
>Typing against a flat surface that doesn't have any give or tactility causes far more strain for me than using my Droid 4 keyboard.
I can't explain that shit, maybe you have mutated thumbs or something. I regularly tap out long worded responses on 4chins only using my touchscreen keyboard and I only get thumb strain if I type more than ~5 paragraphs at a time.
>>52350428
It doesn't make their battery lives longer.
The only reason they're removing keyboard is because Joe Pleb wants a fuckhuge 2mm thin slab to browse facebook on and smear on his face. Two things have to go when you make it fucking huge and super thin: keyboards, and battery space. Especially with bigger screens draining more power.
Give me a sane sized phone with an actual input device and space for a battery that isn't a joke.
>>52350472
>he gets thumb strain after 5 paragraphs
I can type out fucking emails and blog posts on my physical keyboard and shitpost nonstop, no strain.
>>52350476
>It doesn't make their battery lives longer.
Not same anon but it literally does. Adding a physical keyboard means that for the same dimensions a phone will have a 2,000 mAh instead of a 2,800 mAh one. Keyboards take up space, you can't get around that fact.
If you like physical keyboards so god dam much then go suck lelberry's cock and buy their priv meme.
DAALA
>>52350530
No because as soon as people notice "remove keyboard -> more battery" they also notice "remove keyboard -> MOAR THIN" and then it just ends up wafer thin with still no battery, because Joe Pleb doesn't use his phone for anything more than Facebook.
>>52350585
We have a fuckton of phones with 3,000+ mAh batteries, I have no idea why you keep spouting the thinness meme. Apple is in charge of making phones paper thin to the point where they bend in your pocket but most android manufacturers don't do that.
>>52350661
I still think the Android ones are too thin. Admittedly, them being thicker isn't comfortable with the screens also being so huge, but my suggestion would be to make the screens less huge.
>>52345527
Pied piper
http://aomedia.org/
>Alliance
>just worded and does nothing
>>52348166
If 10-bit encoding is better even with 8-bit material, why does 8-bit encoding exist in the first place?
>>52351787
because jews and botnet
>>52351787
Evil corporations holding back technology.
>>52351787
Don't bother reading that. At the time Ateme was trying to sell 10bit HW decoders for TV broadcast. Of course they'll tell you it's better that whatever you have now ant that you must buy it.
>>52351787
Because of GPU jews. 10-bit hardware decoding for H264 still does not exist except in some APUs.
In addition to this, most encoders are dumb asses who use an arbitrary video bitrate instead of a crf value, use aac instead of opus, and sometimes even bloat their encodes to hell with flac audio streams.
>>52351904
That doesn't mean 10 bit h264 isn't better compared to 8 bit h264. Hardware decoding support is shit for 10-bit h264 but that does not mean 10 bit h264 is trash.
I've done many encodes and 10 bit h264 reduces color banding across all different kinds of bitrates and reduces the overall bitrate (using the same crf value) sometimes by up to 20% in some encodes.
>>52351787
Why you think the industry is still selling people 128 kbit/s MP3? because they've old licenses from the early 2000s old cheap licenses that they won't bother to replace and 128 kbit/s is small which saves a lot of bandwidth and storage for their servers and normies don't even give a fuck about quality anyway, that's why the industry is milking the shit outta them with frauds like iTunes and similar.
10-bit is superior from all points of view to 8-bit, there's a VERY SIMPLE way to confirm it. This:
1) Get a 500+ MB 1080p MP4 file (eg. any HorribleSubs 1080p file ever)
2) Get x264 10-bit and 8-bit ready
3) Change the CRF settings in order to aim to generate two 150 MB output file
4) Encode the raw file with both 10-bit and 8-bit x264
5) Compare visual quality
6) ...
7) Profit.
This will show how differently the two x264 versions work, how they affect the banding/sharpnes and everything. You'll notice the 10-bit output file looks a magniture better than the 8-bit, even if both files are the same size.
>>52350685
ayyyy
>>52348301
>using a tripcode
>calling someone else retarded
why
>>52353287
That's not how you into logic anon. You're more of a retard than the tripcuck might be.
>>52348880
I bet your screen is green by now
I know mine i s.
