yashsingh1/xdaforums huggingface dataset:
[MX Player] user822:
The hell are you all keen on software playback?

Watch the first 10min of a movie and then have a dead battery?

For me it is hardware decode or gtfo before buying a new phone.
[MX Player] CDB-Man:
You must realize that no commercial consumer hardware will

ever

officially support the Hi10p profile on H.264; meaning there is no alternative other than software decoding, re-encoding of the video, or using Tegra devices. MX happens to support "hardware decoding" on Tegra, because the developer basically gets around the "no support" issue with CUDA hacks; it's not a perfect solution or officially supported by Tegra.
[MX Player] user822:
And H265 high bit depth will not be used in Bluray or video streaming either?

Why are companies so dense :confused:
[MX Player] CDB-Man:
The H.265 spec was only recently approved on by the media companies, but even now they are trying to water down what is considered "supported" hardware. I don't expect widespread HEVC BDs for many more years. That and also, there's no guarantee that these BDs will use the 10-bit profile of HEVC, either.
[MX Player] user822:
Just an Update:

Nvidia GTX 9** and Intel Skylake HD **** and 4K Bluray do all support Bit Depth of 10bit, don't give hope up to see it happening in mobile phones!

Source: x265 deveoper on irc
[MX Player] Fenrir007:
How does the Zenfone 2 Deluxe fare with 10bit videos? I suppose it cant do HW, but can it play at least 720p 10bit without frames dropping? I'm looking into buying one, but this is something I must know before taking the plunge.
[MX Player] USBhost:
The nexus player plays 1080p 10bit just fine

I actually thinks it plays it better than my nexus 9

So you would be just fine
[MX Player] int0x13:
Hello, can you tell me if the S812 SoC is able to decode HW an encode with HEVC 10 bits? And same for a file with H.264 10 bits?
[MX Player] Dante of the Inferno:
You have absolutely nothing to worry about. Asus phones (meaning all Zenfones) use Intel Atom processors. Processors with x86 architecture (meaning all Intel products) have been able to run Hi10p for 9 years now, not least of all, the Atom processors from 2014 onward. As long as your content is H.264, there shouldn't be any problem.
[MX Player] CDB-Man:
No consumer hardware will officially support H.264 10bit, ever. As to HEVC 10bit, I remember reading that the Snapdragon 812 will

not

support the 10bit profile. I also remember reading rumors that the Snapdragon 905

might

support the HEVC 10bit profile.
[MX Player] Fenrir007:
Are you saying that the Zenfone 2 can decode it on hardware instead of software?
[MX Player] USBhost:
Only S/W
[MX Player] Dante of the Inferno:
As USBHost said, Zenfone 2 will still use software decoding to render your video, but x86 architecture is so powerful in comparison to ARM that it doesn't matter. No hardware acceleration is necessary.
[MX Player] vNa5h:
Does OPO2 play it.. THE SD810
[MX Player] Freakazoid128:
How is 10-bit h264 playback on the Snapdragon 410 and 615? Are any of them capable of decoding 720p with ASS subtitles?
[MX Player] CDB-Man:
The Snapdragon 410 won't be able to handle it. See the OP for estimated minimum specs.
[MX Player] Freakazoid128:
The Snapdragon 600 uses the Krait 300 architecture, while the Snapdragon 615 has 8 cores Cortex-A53, so I was curious if these new 64-bit ARM processors are more efficient per clock than the 32-bit architecture from Qualcomm.
[MX Player] Dante of the Inferno:
Here's what I do know on the matter. My 2013 Moto X that can play 720p H.264 anime with ASS subtitles uses a Snapdragon S4 Pro (model MSM8960DT). That has a 1.7 GHz dual core Krait 300 CPU and a quad core Adreno 320 GPU. In modern terms, only the 8030AB, 8230AB, 8630AB, 8930AB models of the Snapdragon 400 series have the same or better specs, which covers all 2014 Samsung phones, the HTC Desire 601, and the Nokia Lumia 1320. The entire Snapdragon 600 range has higher specs, with only a couple 2013 chips running at 1.5 GHz (13% lower clock speed), but they are quad-core CPUs, so there really should be no trouble there.

In short, 2014 Samsung phones (even the cheapo phones), HTC Desire 601, Nokia Lumia 1320, and all Snapdragon 600 and higher SOCs will run 720p anime with ASS subtitles. It may run on even lower specs, but the above is proven. That said, the Snapdragon 410 is used by the 3rd gen (current) Moto G and at a 720p resolution. I'd be floored if Motorola couldn't get the phone to run what you want, but if any Moto G users are following the thread, we'd love to hear your feedback.
[MX Player] CDB-Man:
Hmm, I missed the part where the Snapdragon added the 64-bit instruction set. Though that being said, 2 major concerns come up:

1a. Is Android even optimized for taking advantage of the 64 bit instruction set (yet)?

1b. If it is, does the ffmpeg build used by MX Player also have the same optimizations? Keep in mind, that codecs generally have to be compiled specifically for the 32 or 64 bit instruction set.

2. Even with the theoretical benefits of the 64-bit instruction set, the drop in absolute power (in Ghz) may just offset any benefits.
[MX Player] gmanhatesu:
i have the 2014 moto g and it can play most 720p 10 bit videos as long as speed up tricks are enabled. The only stuff ive had trouble with are videos that are high bit rate or have lots of grain, particle effects etc
[MX Player] CDB-Man:
I assume you are referring to this device with its Qualcomm MSM8226 Snapdragon 400: http://www.gsmarena.com/motorola_moto_g_(2nd_gen)-6647.php

That's interesting, because the Snapdragon 400 is only on the 32bit instruction set: https://www.qualcomm.com/products/snapdragon/processors/400
[MX Player] gmanhatesu:
yup thats it id imagine the snapdragon 410 would have playback performance similar to a nexus 4 or galaxy s4 since it performs slightly better than the 400
[MX Player] Dante of the Inferno:
It's not even close to matching a Nexus 4's power. Its APQ8064 has an Adreno 320 vs Adreno 306 GPU and a 1.5 GHz quad-core CPU, but is a 25% higher clock speed. The Qualcomm 8916 (Snapdragon 410) has the same clock speed and core count as the 8226, just with Cortex A53 chip arrangement and a slightly more powerful GPU. That GPU would be helpful with gaming and hardware acceleration, but H.264 Hi10 requires software acceleration that only the CPU can provide. Honestly, I'm kinda surprised that the 2nd gen Moto G could handle the requested files at all. That said, with the speed tricks, the 410 may have enough oomph to handle the dreaded grain at 720Hi10p.

Funnily enough, the LTE version of the 2nd Gen (2015) Moto E runs that same Snapdragon 410 processor, but at a lower resolution which should result in even better performance. Anyone have one to confirm?
[MX Player] DonMigs85:
My ZenFone 2 can handle an HEVC 1080p encode of Redline and other stuff mostly fine, but a couple scenes in the former freeze up video for some reason on either MX Player or VLC. Also I think Snapdragon 615 has HW acceleration for 1080p/30 HEVC.
[MX Player] gaetanolip:
zenfone 2 with hw decode in Mxplayer?
[MX Player] Freakazoid128:
Thanks for the info guys.

Think I will buy an LG G4 Beat, which has an Snap 615.

I was thinking about using it only to play HDTV releases, which aren't as heavy as BD rips, so I think the LG will suffice for me.
[MX Player] DonMigs85:
Yes but it appears to behave the same in SW mode too
[MX Player] CDB-Man:
To add to this, I

believe

the HEVC HW acceleration on the Snapdragon 615 is only for the 8-bit profile.
[MX Player] gaetanolip:
on my zenfone 2 ( 4gb ram) i played http://www.libde265.org/hevc-bitstreams/bbb-1920x1080-cfg02.mkv

(mx player and x86 codec)

only sw decoder and it stutters
[MX Player] CDB-Man:
[MENTION=5401789]DonMigs85[/MENTION] and [MENTION=407642]gaetanolip[/MENTION] which Zenfone 2 models do you have? There appear to be many models...

http://www.gsmarena.com/results.php3?sQuickSearch=yes&sName=zenfone+2

Looking at the ZE551ML for example: http://www.gsmarena.com/asus_zenfone_2_ze551ml-6917.php

We can see that the 2GB vs 4GB ram models use different Atoms...
[MX Player] gaetanolip:
I have 4gb ram model , the most powerful one
[MX Player] DonMigs85:
ZE551ML, the highest end one
[MX Player] CDB-Man:
Well then that's odd that you two report differing performance... DonMig perhaps you should try gaetan's linked video out as well and see if you have similar playback stuttering.
[MX Player] Crim Soukyuu:
Didn't see it getting mentioned (sorry if if was), but Mediatek's Helio X10 (@2.2Ghz, Xiaomi Redmi Note 2) can't handle 1080p 10bit h264. Tested with CGI's Shingeki no Kyojin, the OP sequence starts to lag badly towards the end. It does seem to support the H/W+ hack, though, which surprised me cause Qualcomm's SoCs apparently don't.
[MX Player] wwenze:
What's the file name? Want to compare.

Considering buying Redmi Note 2 but afraid that I will actually get less performance than a Galaxy Note 3 and Note 3 Neo
[MX Player] Crim Soukyuu:
[Coalgirls]_Shingeki_no_Kyojin_01_(1920x1080_Blu-ray_FLAC)_[AEF12794].mkv

I doubt you will get less performance by upgrading, but you won't get much more out of it either.
[MX Player] wwenze:
[YOUTUBE]-akEXDLuMZ4[/YOUTUBE]

Note 3 Neo

I see more lags in the first half before the chorus...

Interestingly the hardest part is after the OP, at the episode title screen because of the grains it can load one Skylake core to 100%, the flowers is harder than most of the OP too.

Assuming all cores are used and 100% scaling (i.e. unrealistic load like Antutu)

Note 3 Neo

Quad-core 1.3 GHz Cortex A7 & dual-core 1.7 GHz Cortex A15 = 23480 DMIPS

vs

Redmi Note 2

Octa-core 2.0 GHz Cortex-A53 = 36800 DMIPS

vs

Note 3

Quad-core 2.3 GHz Krait 400 = 31188 DMIPS

vs

Quad-core 1.9 GHz Cortex-A15 & quad-core 1.3 GHz Cortex-A7 = 37080 DMIPS

But how well it can use that theoretical performance is the key...
[MX Player] wwenze:
Something I just discovered about my Note 3 Neo is: If the phone is getting charged, the playback much better. Except that episode title screen again, which I expect to kill every phone anyway.

[YOUTUBE]mbuNefiroWk[/YOUTUBE]

That means the CPU at max speed would actually have the grunt (before it overheats, as I soon learned during testing), but is being capped in the interest of thermals and power consumption when mobile.

Which begs the question: How many phones are artificially capped, and whether CPU-spec-vs-spec comparisons are even relevant. And whether it makes sense to buy a high-spec phone anyway when we'll be limited by thermals anyway - in which case energy efficiency becomes the most important. Which becomes a headache because we have no idea how everything scales. On one hand the A7 / A53 cores are more energy-efficient so more of them can be activated at the same time (Which may be how the Helio X10 i.e. Redmi Note 2 gets such a high score in benchmarks), but on the other hand the task may not scale well with multiple cores so a few high performance cores like A15 / A57 may be faster than many low performance ones. Awaiting the reply on the above playback performance vs Redmi Note 2.
[MX Player] andrei-b76:
is played on P8000 with various decoders without problems (sw and hw decoders)

this video (Overall bitrate : 51mbs) slows http://www.demo-uhd3d.com/fiche.php?cat=uhd&id=45
[MX Player] Crim Soukyuu:
[MENTION=7017427]wwenze[/MENTION]: yours lags very badly compared to mine. The one you posted with the charger plugged in is closer to what I have, but the chains still lag a bit (unless that's youtube).

Can't really film it, but the whole opening doesn't have a single lag up to the point where they all jump up above the roofs, then there are a couple of stutters. The grain in the title display makes it stutter as well, of course.
[MX Player] andrei-b76:
If you are interested to test HEVC on MX Player

i encodes this video http://www.demo-uhd3d.com/fiche.php?cat=uhd&id=45 Here bitrate 51 MBS

lower the bitrate to 5mbs, no brakes

http://depositfiles.com/files/kwuuhewry
[MX Player] wwenze:
Underclocking Redmi Note 2 gives a big improvement to playback.

[youtube]PFuf6_ki_lI[/youtube][youtube]5sxuDrKCoNQ[/youtube]

Wonder if it's scheduler or overheat issue, I'm betting mainly on overheat.
[MX Player] Crim Soukyuu:
Wow, that looks hideous. Which ROM are you on (version)?

Nothing like how it looks on my brother's RMN2. Mine should arrive sometime this week, will test it again and upload a sample... if I can find something to film it with.
[MX Player] gaetanolip:
Hi

The standard will be hevc 10bit 60fps.

So I think it is interesting to test some video files coded like that.

Atm some socs/gpu are announced to play the standards:

1 tegra x1

2 Snapdragon 820

3 helio x20-x30 ( 30 fps only) with Mali t880

4 Kirin 950 (30 fps only?) with Mali t880

Has anyone any video sample hevc 10bit 60 fps links? I would like to test my Rk3288

Thanks
[MX Player] CDB-Man:
That's very interesting; I should try this on my Nexus 5 (2013). The N5 failed with 1080p playback primarily due to overheat.

EDIT: Interesting, underclocking from 2.26Ghz to 1.57Ghz has improved the duration that the N5 is able to play sustained 1080p 10bit video... was the solution really this simple and under our noses this whole time? I'll need to do more testing.

Pinging [MENTION=2925008]Dante of the Inferno[/MENTION] and [MENTION=6118411]vivan000[/MENTION]
[MX Player] Dante of the Inferno:
If possible, post the clock speed, smooth playback duration, and battery drain rate for each configuration. After all, being able to play REDLINE may not be all that practical if it can only be done while plugged in.
[MX Player] gaetanolip:
video sample

http://www.demo-uhd3d.com/fiche.php?cat=uhd&id=26
[MX Player] CDB-Man:
On my Nexus 5, 1.59Ghz cap, smooth playback lasted for ~10mins looping the heavy OP of [UTW]_Nisemonogatari_-_01_[BD][h264-720p_AC3][6376A085].mkv

After which it caps to 1.19Ghz.
[MX Player] usna:
Devices are now able to playback 10bit video even at 1080p, great!

Do these devices and MX Player actually benefit from 10bit compression though?

Does MX Player dither the resulting 10bit output to 8bit for the device's 8bit display, or is the extra precision effectively truncated and wasted?
[MX Player] ChanManDCLXVI:
I own a zenfone 2 ze551ml 4gb ram model and for some HEVC/x265 files it can run hw+ fine, but for others it runs sw and stutters.

I'm not sure what is different between these two files and was wondering if there was a way to tell beforehand if it will use sw encoders or hw+.

I was also wondering if it is possible to run all the files with HW+ encoding (as it runs much more smoothly than using sw)

Any help is appreciated.

EDIT: Upon further inspection, it appears that hevc videos with 10bit depth are giving the HW+ encoder issues.

I read some people saying that most chips don't support 10 bit hevc encoding, but is there any way to play them without stuttering? (i own the zenfone 2 ze551ml 4gb)
[MX Player] CDB-Man:
At the moment, HEVC 10bit can't be hardware accelerated, meaning it must be SW accelerated via CPU. It boils down to "how well you can play it depends on how powerful is the CPU".

[MENTION=5501864]USBhost[/MENTION] yeah, a bunch of people are reporting 8bit HEVC HW support now! It certainly was adopted faster than I expected.
[MX Player] gmanhatesu:
i must say i have a zenfone 2 and a nexus 6p and overall im impressed with the performance of my zenfone 2! playback of 1080p 10bit aswell as 720p hevc is comparable and in most situations superior to the snapdragon 810 as long as thermal throttling does not kick in.
[MX Player] NaturalViolence:
I stumbled upon this thread through google and thought I would try my luck here. I have a Note 4. When playing any hevc video file with 10 bit color I get horrible color banding that makes the content barely watchable. It seems that it is discarding the uppermost 2 bits on every sample. I have tried vlc, mx player, samsung player, etc. all with no luck. It does it in both hw and sw decode. I am surprised that I could not find anything at all on google about this issue. I don't see what I could possibly try to fix this considering it's starting to look like a hardware issue somehow. Does anyone have any advice? Performance is a non-issue for me but this image quality issue makes my 10 bit files all but unusable.
[MX Player] goaspy:
MX Player 1.7.40 plays fine a 4K 10bit HEVC file, 50fps, 28Mbps bitrate on my Philips ATV (Lollipop 5.1), using HW+.

Is HW+ using libstagefright or MediaCodec to make this happen? Somehow it uses the Marvell HEVC decoder correctly while other players like Plex for Android have issues with this file.
[MX Player] ikramii:
I just found something intresting, my phone nexus 6 can handle 10-bit avc BD quality anime. I can play it smoothly if i configure it via synapse. I lock the cpu clock speed to 2.8 ghz change the governor to performance and the gpu clock speed to 600 change to performance governor. But the problem is the subtitle too demanding, cant see the opening and ending sub slide smoothly. I need more future research, this is just a short hypothesis
[MX Player] Ironclad17:
God dammit Daiz

Trying to watch Ajin. It's already an issue that my HTC One m9 is ARMv8-a so I have to use sw decoder, but it's basically impossible to watch underwater's hevc releases. Even if I assign all 6 cores to decoding. Anyone figure out a way to get ARMv8-a devices working yet? It's actually performing worse than my old phone. It's been like a year since they hit the market. Are there any plans for ARMv8-a optimization?
[MX Player] ikramii:
Snapdragon 810 cant handle hevc with hw? How about 10 bit video?
[MX Player] Reyde Viscerous:
On the M9 at least it was capable of decoding HEVC in HW+ (I don't remember if HW worked sadly). 10-bit didn't work on either H.264 or H.265. Since the Marshmallow update however it also doesn't do HEVC at all anymore, not sure why. SW is the only way.
[MX Player] Ironclad17:
Whoa what version of mxplayer supported hw+ decoder for m9? Had a neon armv7 before and when I switched phones I was only able to use sw decoder.
[MX Player] Reyde Viscerous:
It was the normal 1.7.x version. Also got the armv7 neon custom codec not sure if that mattered. I should add that I tried just to be sure to play HEVC on the older 1.7.x build on the new Marshmallow update but it still didn't work.

I'm a bit confused in general as to why there isn't official support to begin with as the HEVC spec is finalised and Google added support in Android already. I guess it might be licensing issues.
[MX Player] ikramii:
Yes i think so about the HEVC license. I read in the wiki the license is very expensive since its new technologies and still in development. but what really pissed me off is why the hardware cant handle 10-bit color decoding smoothly
[MX Player] LEO-037:
Will be watching this thread once we have Snapdragon 820 devices to test.
[MX Player] jisin:
This link might be useful to you all ---> http://kodi.wiki/view/Android_hardware#Compatible_chipsets
[MX Player] Ironclad17:
I'm dumb, HW decoder does work for h.264 once you disable the custom codec entirely. I don't know why it failed everytime when it's suppose to try HW decoder. Still h.265 seems to be hit and miss. Still can't watch those Underwater releases.
[MX Player] CDB-Man:
I'm quite surprised that you encountered issues using SW to play your 10bit H264 videos. Are you sure you have the newest version of MX? Try joining the beta release stream, and use the beta build instead.

https://sites.google.com/site/mxvpen/translation/test-build

This is really good news. Unfortunately, I know nothing about the Philips TV, so I couldn't tell you, and you would have to do more digging. The only thing that I can tell you is that HW+ uses MX's own implementation of calling the system to use system GPU, instead of just passing everything to the Android media framework via default channels. [MENTION=3850543]bleu8888[/MENTION] might be able to give more details.
[MX Player] hyno111:
My shield tablet ( Tegra K1 32-bit) show strange artifacts when playing 10bit H.264 videos, using both hw+ and hw decoder. SW decoder is fine. Is that a known problem?

Official Android 6.0 firmware, MXplayer version is 1.8.4 20160125.
[MX Player] Crim Soukyuu:
From what I know, HW playback of 10-bit h264 is a hack, and those artifacts are a side effect. 10-bit was never supposed to be used for consumer video files, so there is no hardware decoder for it and about the only files that use 10-bit come from the anime scene. It's a bit different with h265 (HEVC) though - there seems to be some hardware that supports 10-bit HEVC decoding without any hacks.
[MX Player] gaetanolip:
Hi

Anyone with a Samsung s7 can try this http://demo-uhd3d.com/fiche.php?cat=uhd&id=26

Inviato dal mio ASUS_Z00A utilizzando Tapatalk
[MX Player] remineur:
Hi, i have a samsung galaxy tab s, she cant play 1080p smoothly at least with mx player. I tried 1080p files (.265) extension with Strongene lentoid decoder, and damn i reach 50 fps ! how can this even possible, so my talet can read 1080p hevc, is there a way to put this video codec into mx player ? thx
[MX Player] The-Awesome:
I tested some Hi10P Coalgirls videos (Durarara S1) on my Nexus 5X and my brothers Xperia Z5 today.

The 5X had a fair bit of trouble. Within a minute it was starting to struggle.

The Z5 handled it really well. I only watched ~5 minutes but it seemed to be handling it really well.

The 5X handled lower bitrate Hi10P files without much trouble. It had no trouble with 720p.

I have been streaming the files over my network so the performance might be slightly better with the files on the phone or attached via USB otg, but probably not much.
[MX Player] DrOreo:
Almost there

Nexus 6P here, all below described is h.264 ~24FPS and played locally from device.

720P 10bit TV Source~24 megabit, Plays fine, no frames dropped

720P 10bit Blu-ray Source High Grain High bandwidth ~57 megabit, Plays okay watchable but not the best experience, frames dropped frequently

1080P 10bit Blu-ray Source Low Grain Low bandwidth~25 megabit, Plays okay watchable but not the best experience, frames dropped frequently, It played better than my 720P 10bit Blu-ray Source High Grain High bandwidth

1080P 10bit Blu-ray Source Low Grain High bandwidth~80 megabit, Not watchable audio stutter/delay frames dropped frequently

Tested about 30 minutes each multiple times a couple of reruns just to make sure, definitely experience thermal throttling with blu-ray as it runs better initially then later.

Overall I would say SD810 is not fit for h.264 10bit.

SD820 should be able to handle all the above since it seems to double in benchmarks but probably not everything out there
[MX Player] Mussels84:
Haven't read the whole thread, but came here to post a 'bug' that may be my device, may be well known.

Using a generic android media player (some chinese thing, Amlogic S805 chipset) i'm having mostly succes with 1080p HEVC, but i cannot seek forward without the player dropping to software mode, or crashing the player.

I *am* playing the files over wifi using ES file explorer to a SAMBA share, which is an uncommon setup and may be part of why its glitching.

If this is well known, is there any fix?
[MX Player] Gorbush2000:
This thread is mostly for reports about 10bit video decoding associated with MX Player. Pleas install that application and then raports your problems.

Some time ago I had similar problem with my Android TV Box based on RK3188 SoC. I can't remember exact solution but I'm almost sure it wasn't media player fault. I use MX Player almost all the time but problem was occuring in other application as well. If I recall correctly that disableing in MX Player settings section "Player" options "Fast seeking" and "Preview while seeking" helped a little with this problem.
[MX Player] CouldntThinkOfAUsername:
Z3 struggles with 1080p mkv 10bit. Anime seems OK but newer movies and TV shows I obtained struggled badly.

I assumed the quad core 2.5ghz would be sufficient.
[MX Player] user822:
Complete bull, where did anyone get the idea that this pathetic SOC can decode 1080p in software. Even if MX were to pull some rabbits out of their hat and release a armv8 version, it would probably only take 2min and the 810 would throttle to a grinding halt.