Related
This question is for developers. Can devs replace crappy compression codec on Evo recording cam to record with h.264 to improve quality of vids we shoot by far. Current cam codec is SO bad that 720p does no justice for the cam. Basically in my view camcorder is useless. H.264 would change the whole game for this phone. Would love to see the rom with h.264 video camera codec. Would any shead some light on this ?
stewie-droid said:
This question is for developers. Can devs replace crappy compression codec on Evo recording cam to record with h.264 to improve quality of vids we shoot by far. Current cam codec is SO bad that 720p does no justice for the cam. Basically in my view camcorder is useless. H.264 would change the whole game for this phone. Would love to see the rom with h.264 video camera codec. Would any shead some light on this ?
Click to expand...
Click to collapse
they cant do a whole lot with any camera settings till the source kernal is released. Who knows when that will be heh
stewie-droid said:
This question is for developers. Can devs replace crappy compression codec on Evo recording cam to record with h.264 to improve quality of vids we shoot by far. Current cam codec is SO bad that 720p does no justice for the cam. Basically in my view camcorder is useless. H.264 would change the whole game for this phone. Would love to see the rom with h.264 video camera codec. Would any shead some light on this ?
Click to expand...
Click to collapse
Do you even know what the current cam codec is?
It's MPEG-4 Part 2 (generally referred to as "MPEG-4"), which is most commonly known for it's implementations in divx/xvid.
It's not as trendy as H.264 (aka MPEG-4 Part 10 and/or AVC), but generally quality isn't what people take issue with when choosing h.264 over MP4 - it's filesize. When you get into higher resolutions with higher bit-depths, being able to compress a stream allows you to work around issues with slow write speeds.
I think you really aren't familiar with video encoding or codecs in general. You should educate yourself a bit more before announcing that a simple codec change will resolve the camera woes with the Evo.
h.264 is currently patent encumbered, which is part of why you don't see it implemented so widely.
Swapping out the codec isn't going to be a magic fix to improve this camera. It's limited by it's very design. Consider the 720p video a novelty and try to only shoot in situations with lots of ambient light and it'll be far more usable.
Petronic said:
Do you even know what the current cam codec is?
It's MPEG-4 Part 2 (generally referred to as "MPEG-4"), which is most commonly known for it's implementations in divx/xvid.
It's not as trendy as H.264 (aka MPEG-4 Part 10 and/or AVC), but generally quality isn't what people take issue with when choosing h.264 over MP4 - it's filesize. When you get into higher resolutions with higher bit-depths, being able to compress a stream allows you to work around issues with slow write speeds.
I think you really aren't familiar with video encoding or codecs in general. You should educate yourself a bit more before announcing that a simple codec change will resolve the camera woes with the Evo.
h.264 is currently patent encumbered, which is part of why you don't see it implemented so widely.
Swapping out the codec isn't going to be a magic fix to improve this camera. It's limited by it's very design. Consider the 720p video a novelty and try to only shoot in situations with lots of ambient light and it'll be far more usable.
Click to expand...
Click to collapse
I agree with you. But x.264 is not involved in any patent issues, is free, and works very will with the best container format available to date... mkv.
Now the phone will do hardware decoding of x/h.264 but you are right, I don't see any advantage other than the smaller file size. You are right again, on one of those P labeled cams the h.264 stream is much smaller than that of mpeg-2/dvd or others so it works well on those crappy hardware writers.
Changing the encoding profile of this camera would not fix your issues OP.
I've never seen bad quality from h.264 codec but then again i agree i have not research enough on the codecs comparison enough but that's why i'm asking. I just know it looks horrible. Somehow camera pics are acceptable. Thank you for the input.
stewie-droid said:
I've never seen bad quality from h.264 codec but then again i agree i have not research enough on the codecs comparison enough but that's why i'm asking. I just know it looks horrible. Somehow camera pics are acceptable. Thank you for the input.
Click to expand...
Click to collapse
I could encode an h.264 video in a low bitrate and low resolution and it would look bad. The codec is only one factor involved in the end result. Different codecs can squeeze better quality video into a smaller file size but it comes at the expense of CPU use and other bottlenecks. In this case I don't think the choice of codec is what is holding back the video. It's probably more about processing power and overall architecture.
I'm not sure that implementing x.264 compression for the EVO would solve anything. From my experience in order to have better quality with h.264 over h.263 it requires much more processing power due to the higher compression complexity.. This would all have to be done real time by the phone.
With the great hardware being sported by the EVO I wonder if a more unorthodox approach could be implemented to attain the highest quality possible.
How about this:
Capture video using a real time lossless compression. Maybe huffyuv?
Once captured let the phone recompress the source to x.264 or whatever via a background service or at a scheduled time like 3am or something
Maybe via this method a higher frame rate could even be achieved?
amdchip said:
I'm not sure that implementing x.264 compression for the EVO would solve anything. From my experience in order to have better quality with h.264 over h.263 it requires much more processing power due to the higher compression complexity.. This would all have to be done real time by the phone.
With the great hardware being sported by the EVO I wonder if a more unorthodox approach could be implemented to attain the highest quality possible.
How about this:
Capture video using a real time lossless compression. Maybe huffyuv?
Once captured let the phone recompress the source to x.264 or whatever via a background service or at a scheduled time like 3am or something
Maybe via this method a higher frame rate could even be achieved?
Click to expand...
Click to collapse
Uncompressed [email protected] with 8-bit color would be something like 45MB/s. (That's excluding audio.)
No current SD card supports those write speeds.
I'm not sure that you could losslessly compress it down to something that'd support even a class 6 card.
Petronic said:
Uncompressed [email protected] with 8-bit color would be something like 45MB/s. (That's excluding audio.)
No current SD card supports those write speeds.
I'm not sure that you could losslessly compress it down to something that'd support even a class 6 card.
Click to expand...
Click to collapse
Eeeeek!!
I checked it out and you are right on the money.
(8 bit @ 1280 x 720 @ 59.94field = 105 MB per/sec) / (2.33:1 huffyuv) = 45.06
Still I wonder if better video quality could be achieved via a capture now (large file size) compress later (small file size) solution.
Certainly, considering your well taken point, we would need to keep things within the requirements of the EVO's hardware (sd card included). Probably would need to keep the data rates within the EVO's stock microsd specifications in order for it to be viable for everyone.
The iPhone 4 can record in h.264 and its processor isnt *that* much more powerful than Snapdragon (and the camera is similar--same company, same sensor size, same features, just 5MP instead of 8MP). What it comes down to is lazy coding by HTC
I don't know if you guys have looked in the build.prop file but the settings are in there. I just don't have alot of time to play with them but here's what's inside. Sprint/HTC changed the line in 1.47,ro.media.enc.vid.m4v.bps, to 8000000 from 6000000 on 1.32, so I'm guessing that's how they upped the Mbits in the upgrade. I could be wrong and the change may need to be in the kernel also but play with them and see.
Code:
#
# This file describes the media capabilities and profiles
# using system properties.
#
# Note: The property key and value has some length
# limit as defined by PROPERTY_KEY_MAX and
# PROPERTY_VALUE_MAX, respectively
#
# WARNING: We may not use system properties for specifying
# media capabilities and profiles in the future
#
ro.media.enc.file.format = 3gp,mp4
ro.media.enc.vid.codec = m4v,h263
ro.media.enc.vid.h263.width = 176,1280
ro.media.enc.vid.h263.height = 144,720
ro.media.enc.vid.h263.bps = 64000,6000000
ro.media.enc.vid.h263.fps = 1,30
ro.media.enc.vid.m4v.width = 176,1280
ro.media.enc.vid.m4v.height = 144,720
ro.media.enc.vid.m4v.bps = 64000,8000000
ro.media.enc.vid.m4v.fps = 1,30
#
# Increase SKIA decode memory capability for progressive jpg file
#
ro.media.dec.jpeg.memcap = 20000000
I may not be a...
developer but when you are talking about codec you are talking my language (I am an editor). H264 isn't that great itself and won't make the EVO's footage look any better yeah you get some more detail out of the H264 but the real reason the camera doesn't look as good is the variable fps in different lighting conditions. The variable kills it. The cam should be fixed at 24fps or 30fps. If that can be done you will see a major difference. I'm not sold on the white balance either. Also I would love to have h264 but the difference in the two is compression. H264 is better but again FPS is key.
I agree as well as most of the other people that h.264 won't help by itself.
Though one thing it would help with is allowing to bump up to a higher bit rate and or FPS and still maintain speeds sufficient for Class 2 SD cards. So, even though it won't do anything by itself, it will help in that you could in theory record higher quality video to your phone.
billobob said:
The iPhone 4 can record in h.264 and its processor isnt *that* much more powerful than Snapdragon (and the camera is similar--same company, same sensor size, same features, just 5MP instead of 8MP). What it comes down to is lazy coding by HTC
Click to expand...
Click to collapse
Das troo, I emailed Omnivision about the issue, they said that their Evo is great there, and that I should contact HTC about it and had said they created the driver/software for it.
"Hi Steve,
I’m sorry to hear that you are experiencing issues video performance. The HTC EVO we have here works great. OmniVision only makes the sensor. HTC makes the drivers and software that run the sensor. Unfortunately, you will need to contact them with any issues.
Sorry, I couldn’t be more help.
Scott"
Then I had asked them if they have any samples they used. And sent me a video they just recorded.
"We just went outside and took this simple video. Hope it helps.
Scott"
Currently uploading right now, i'll edit the link.
EDIT: here you go
bit.ly/c0lwOb
What do you guys think?
FunYunZ said:
EDIT: here you go
bit.ly/c0lwOb
What do you guys think?
Click to expand...
Click to collapse
Not able to post links yet I'm guessing. Just type it out.
Holyrolla said:
Not able to post links yet I'm guessing. Just type it out.
Click to expand...
Click to collapse
you don't see the link? its a bit[dot]ly link. But yea i can't post links yet, so I used the URL shortening.
bit[dot]ly/ c0lwOb
That video is pretty clear, but jumpy as well (expected). Wondering if they tweaked it or installed the OTA update on it?
Holyrolla said:
That video is pretty clear, but jumpy as well (expected). Wondering if they tweaked it or installed the OTA update on it?
Click to expand...
Click to collapse
Thats what I wondered to, but I guess not.
We are using one of our employees phones he bought from Sprint. All of the drivers and software are stock and from HTC.
Scott
Good god, that video sample is hideous! Look at this video comparison done between the Evo and the iPhone 4 in the exact same scene. There's just no competition between the two.
Good god, our Evo sucks mighty ass in the 720p category.
Questions for all the OP3 Users. Can it play HEVC x265 1080p 10bit 30FPS Videos in HW/HW+ Mode on MXPlayer?
Are there any Artifacts or it lags and sttutters?
i have been Asking This question but only 2 OP3 users have replied.
One says it cant play in HW only SW mode. Other Says It Can on Stock ROM.
If Few more users confirm it does or does not, then it will help me decide to buy this one or Le Max 2.
Please Reply.
Thanks in Advance.
I played h.265 videos encoded in 10bits and 1080p23 through the stock video player as well as mxplayer with HW and HW+ modes. I also played a 4k 60fps 10 bit video used to showcase the samsung 4k tvs with no issues what so ever. HW playback yet again. Both on the stock ROM and kernel.
Mine on stock Oxygen ROM.....10Bit x265 CAN'T play in HW/HW+ mode...only in SW.
However, 8Bit x265 CAN play in HW/HW+ without problem.
EDIT: Got mine solved now my OP3 can play x265 10bit video file in hw+ .
sample from here http://demo-uhd3d.com/fiche.php?cat=uhd&id=45
H265 10bit, up to 23.976fps
Resolution : 3840x2160
File size : 655 MB
Duration : 01min 46sec
Format : TS
Codec : HEVC
Overall bit rate : 51.4 Mb/s
Bit depth : 10 bits
Frame rate : 23.976 fps
rom:
OXYGENOS 3.2.1
Yes it can play without stutters with HW+ turned on
also
this http://demo-uhd3d.com/fiche.php?cat=uhd&id=96
H265 10bit, 59.940fps
Resolution : 3840x2160
File size : 818 MB
Duration : 02min 12sec
Format : TS
Codec : HEVC
Overall bit rate : 51.6 Mb/s
Bit depth : 10 bits
Frame rate : 59.940 fps
rom:
OXYGENOS 3.2.1
Played without stutters with HW+ turned on
and this one: http://demo-uhd3d.com/fiche.php?cat=uhd&id=144
HDR 10bit HEVC, 59.940fps
Resolution : 3840*2160
File size : 1120 MB
Duration : 02min 07sec
Format : MP4
Codec : HEVC
Overall bit rate : 75.8 Mb/s
Bit depth : 10 bits
Frame rate : 59.940 fps
Played without stutters with HW+ turned on
lokr said:
sample from here http://demo-uhd3d.com/fiche.php?cat=uhd&id=45
H265 10bit, up to 23.976fps
Resolution : 3840x2160
File size : 655 MB
Duration : 01min 46sec
Format : TS
Codec : HEVC
Overall bit rate : 51.4 Mb/s
Bit depth : 10 bits
Frame rate : 23.976 fps
rom:
OXYGENOS 3.2.1
Yes it can play without stutters with HW+ turned on
also
this http://demo-uhd3d.com/fiche.php?cat=uhd&id=96
H265 10bit, 59.940fps
Resolution : 3840x2160
File size : 818 MB
Duration : 02min 12sec
Format : TS
Codec : HEVC
Overall bit rate : 51.6 Mb/s
Bit depth : 10 bits
Frame rate : 59.940 fps
rom:
OXYGENOS 3.2.1
Played without stutters with HW+ turned on
and this one: http://demo-uhd3d.com/fiche.php?cat=uhd&id=144
HDR 10bit HEVC, 59.940fps
Resolution : 3840*2160
File size : 1120 MB
Duration : 02min 07sec
Format : MP4
Codec : HEVC
Overall bit rate : 75.8 Mb/s
Bit depth : 10 bits
Frame rate : 59.940 fps
Played without stutters with HW+ turned on
Click to expand...
Click to collapse
Can you play x265 10bit in mkv format in hw/hw+? Mine cannot..Dont know why.
Yup, it can play tested with jellyfish-120-mbps-4k-uhd-hevc-10bit.mkv 438 MB http://jell.yfish.us/media/jellyfish-120-mbps-4k-uhd-hevc-10bit.mkv
and with jellyfish-100-mbps-hd-hevc.mkv 100 Mbps 365 MB http://jell.yfish.us/media/jellyfish-100-mbps-hd-hevc.mkv
give some links with vids that OP3 cannot play so I will check on mine, my op3 have all stock, no root.
lokr said:
Yup, it can play tested with jellyfish-120-mbps-4k-uhd-hevc-10bit.mkv 438 MB http://jell.yfish.us/media/jellyfish-120-mbps-4k-uhd-hevc-10bit.mkv
and with jellyfish-100-mbps-hd-hevc.mkv 100 Mbps 365 MB http://jell.yfish.us/media/jellyfish-100-mbps-hd-hevc.mkv
give some links with vids that OP3 cannot play so I will check on mine, my op3 have all stock, no root.
Click to expand...
Click to collapse
Nevermind....I get it play fine now in hw+. All I did was to change the mkv extension of the 10bit x265 video file that refused to play in hw/hw+ to mp4. It played fine in hw+. Change it back to mkv...it also play fine in hw+. Now all my x265 10 bit mkv can play in hw+. Weird!!
Thanks Everyone.
I think i will buy this.
sorry for jacking this thread, but can anyone try hi10p h264 in this phone? I want to know before getting this phone.
I'm currently on zenfone 2 which is x86, no problems with h264 hi10p.
xjammetx said:
sorry for jacking this thread, but can anyone try hi10p h264 in this phone? I want to know before getting this phone.
I'm currently on zenfone 2 which is x86, no problems with h264 hi10p.
Click to expand...
Click to collapse
Short answer would be "yes, as long as it's not 4k".
For the long version, it depends on several encoding characteristics. These are video grain, bitrate, framerate (taking anime into consideration, there shouldn't be any 60fps releases so it's okay), chroma subsampling (4:4:4 and 4:2:2 being more CPU intensive to decode than the usual 4:2:0) and colour space (BT.601 and BT.709 are more widely supported and easier on the CPU than BT.2020, but you'd need a beast of a desktop CPU to software render anything in the BT.2020 space anyway, not a mere phone).
If the SSA subtitles are heavily animated, you can't do much about it. You'd need to find a video player on android that can properly render it, or hope that overclocking the phone might reduce the subtitle lag. Testing the file you linked on the MX Player 10-bit playback topic, it seems that the CPU usage doesn't increase by much with the subtitles flying around the screen, but the delays are noticeable while MX Player struggles to render them. It ain't as bad as you might imagine, as there aren't many dropped frames, but the frame representation is delayed severely. As a sidenote, reducing the rendering quality of the video doesn't affect the subtitle rendering lag in any way.
Dariusdd said:
Short answer would be "yes, as long as it's not 4k".
For the long version, it depends on several encoding characteristics. These are video grain, bitrate, framerate (taking anime into consideration, there shouldn't be any 60fps releases so it's okay), chroma subsampling (4:4:4 and 4:2:2 being more CPU intensive to decode than the usual 4:2:0) and colour space (BT.601 and BT.709 are more widely supported and easier on the CPU than BT.2020, but you'd need a beast of a desktop CPU to software render anything in the BT.2020 space anyway, not a mere phone).
If the SSA subtitles are heavily animated, you can't do much about it. You'd need to find a video player on android that can properly render it, or hope that overclocking the phone might reduce the subtitle lag. Testing the file you linked on the MX Player 10-bit playback topic, it seems that the CPU usage doesn't increase by much with the subtitles flying around the screen, but the delays are noticeable while MX Player struggles to render them. It ain't as bad as you might imagine, as there aren't many dropped frames, but the frame representation is delayed severely. As a sidenote, reducing the rendering quality of the video doesn't affect the subtitle rendering lag in any way.
Click to expand...
Click to collapse
thanks for the reply.
how about 40Mbps~ coalgirl's level encodes?
Will you test a file for me?
xjammetx said:
thanks for the reply.
how about 40Mbps~ coalgirl's level encodes?
Will you test a file for me?
Click to expand...
Click to collapse
https://www.nyaa.se/?page=view&tid=789147
Tried that one. It's bloated and the noise levels are over the top. Simply put, it lags during high bitrate scenes, doesn't during lower bitrate scenes. It is rather watchable with just a few dropped frames if you lower the colour format from YUV to 16 bit RGB and use speedup tricks which butchers dithering and makes the video blocky with visible dither artifacts. Even so, the processor usage sits usually at 100%
I've also tried: http://coalgirls.wakku.to/657/evangelion the first movie in 1080p.
It works fine, colour format YUV with no speedup tricks. The processor usage jumped between 55 and 90%. Do note that this has only ~17Mbps bitrate. I think that 40Mbps is a bit farfetched as well as useless on a screen this small. Fortunately, most encodes have more reasonable bitrates, so it shouldn't pose much of a problem.
Tested on arter97's CM13 + kernel using MX Player Beta 1.8.6. This also means the processor had stock clockspeeds. For 10 bit h264 decoding, Samsung's Exynos 8890 and Huawei's Kirin 950/955 should be a little better than Snapdragon 820. I don't know by how much, but you should take note that the Galaxy S7 had its codec support gimped by Samsung (specifically, it lost 10 bit h265 decoding) after a certain update for both Exynos and Qualcomm versions, and I am not sure about the current codec support of HiSilicon chips like the Kirin.
Dariusdd said:
https://www.nyaa.se/?page=view&tid=789147
Tried that one. It's bloated and the noise levels are over the top. Simply put, it lags during high bitrate scenes, doesn't during lower bitrate scenes. It is rather watchable with just a few dropped frames if you lower the colour format from YUV to 16 bit RGB and use speedup tricks which butchers dithering and makes the video blocky with visible dither artifacts. Even so, the processor usage sits usually at 100%
I've also tried: http://coalgirls.wakku.to/657/evangelion the first movie in 1080p.
It works fine, colour format YUV with no speedup tricks. The processor usage jumped between 55 and 90%. Do note that this has only ~17Mbps bitrate. I think that 40Mbps is a bit farfetched as well as useless on a screen this small. Fortunately, most encodes have more reasonable bitrates, so it shouldn't pose much of a problem.
Tested on arter97's CM13 + kernel using MX Player Beta 1.8.6. This also means the processor had stock clockspeeds. For 10 bit h264 decoding, Samsung's Exynos 8890 and Huawei's Kirin 950/955 should be a little better than Snapdragon 820. I don't know by how much, but you should take note that the Galaxy S7 had its codec support gimped by Samsung (specifically, it lost 10 bit h265 decoding) after a certain update for both Exynos and Qualcomm versions, and I am not sure about the current codec support of HiSilicon chips like the Kirin.
Click to expand...
Click to collapse
mean/average bitrate of that movie must be near to (((18823.5 * 10^6) *8) / 7200) * 10^-6
or 20.91500 Mbps
try this one
http://coalgirls.wakku.to/6368/nisemonogatari
^
try that, just get the
Code:
[Coalgirls]_Nisemonogatari_OP3_(1920x1080_Blu-ray_FLAC)_[948BD021].mkv
(((458.18 * 10^6) * 8) / 90) * 10^-6
40.7271111 Mbps on average.
^ my zenfone 2 decodes that file with no problems, given that its an x86 architecture rather than arm.
xjammetx said:
try this one
http://coalgirls.wakku.to/6368/nisemonogatari
Click to expand...
Click to collapse
Using YUV there are a few dropped frames between 1:20 and 1:27, otherwise it's a flawless playback. Using RGB32 there aren't any visible dropped frames during the entire run. I've tested it several times. During those 7 seconds, the processor stays at 100% usage, otherwise it sits around 80-85%. Understandably, the phone gets hot and the battery drains like mad.
I don't think sustained playback at these levels of processor usage is good for the device.
Hi guys, moto g4 plus using Snapdragon 617 Processor, this processor support 1080P 60fps record but g4 plus have to feature 1080p 30fps. Will be 1080p 60fps mod ? because as g4 plus same power too phones recording [email protected], for example samsung galaxy S5
https://www.qualcomm.com/products/snapdragon/processors/617
I think the camera sensor is not compatible
But it's just my thinking
mgedik said:
Hi guys, moto g4 plus using Snapdragon 617 Processor, this processor support 1080P 60fps record but g4 plus have to feature 1080p 30fps. Will be 1080p 60fps mod ? because as g4 plus same power too phones recording [email protected], for example samsung galaxy S5
https://www.qualcomm.com/products/snapdragon/processors/617
Click to expand...
Click to collapse
There are 3 things you have to look at when deciding what resolution & speed a phone records a video...
1. Camera sensor
2. The ISP
3. The software implementation
1. Camera sensor - Omnivison OV16860
A quick look at the OmniVision site tells me that the G4 Plus sensor "supports high-quality slow motion video capture with full field of view (FOV). The sensor can capture 16-megapixel images and video at 45 fps, ultra-high resolution 4K2K video at 60 fps, and 1080p high definition (HD) video at 120 fps via high speed D-PHY and C-PHY interfaces"
What does this mean? It means that yes, our phone CAN record 1080p60 videos, & actually a lot more....
2. ISP - Snapdragon 617
It is very well known that this is a decent mid-tier SoC and has good capabilities.... But how much exactly...?
Multiple google searches led me to this -
"14.9GB/s b/w GPU Adreno 405 Adreno 405 "Next-gen" Adreno "Next-gen" Adreno Encode/
Decode 1080p H.264
1080p30 HEVC, decode 1080p H.264
1080p60 HEVC, decode 2160p30, 1080p120
H.264 & HEVC 2160p30, 1080p120
H.264 & HEVC Camera/ISP 21MP Dual ISP"
Which means yes, our phone can decode 1080p60 videos (seems to be HEVC only)
3. Software implementation -
Now this is where your answer is... Motorola has to develop (or fork) device drivers & libraries for the particular sensor & ISP. Now, on a mid-range phone for the masses, why would you spend so many development hours on trying to get 1080p60, only for it to eat away its high-range market's share. The G4 Plus is already more than capable to disrupt high range phones (ex - Moto Z Play), and if you add extra features, it'll either be costlier or everybody will buy ONLY this phone.
Long story short, Motorola hasn't included the SW implementation and/or device libs required for 1080p60. If you want it, you have to develop it yourself from Motorola's device libs & kernel.... Parts of which are closed source... Which means you can't.
Only solution is to reverse engineer/ get open source device libs for the sensor, make your changes, integrate it back into the kernel (& the system) & HOPE it works.
Similar discussion was held in the Moto G2 forums, that device was capable of 1080p recording, whereas it only had 720p in SW... Similar conclusion in the end.
Very interesting.
aditya.upadhyaya said:
There are 3 things you have to look at when deciding what resolution & speed a phone records a video...
1. Camera sensor
2. The ISP
3. The software implementation
Click to expand...
Click to collapse
Thank you, that was a great summary. Much appreciated.
try oxygen for android "ABS TWEAKS" BEST APP EVER! and you'll get your 60fps, you'll need busybox, and terminal on your phone, and Int. n your phone. theres a thread on xda about it. good luck champs!!!
p.s. i take no credit for ABS TWEAKS.
Dr.who? said:
try oxygen for android "ABS TWEAKS" BEST APP EVER! and you'll get your 60fps, you'll need busybox, and terminal on your phone, and Int. n your phone. theres a thread on xda about it. good luck champs!!!
p.s. i take no credit for ABS TWEAKS.
Click to expand...
Click to collapse
Even if that abs tweak work ,It doesn't support nougat.
I think ABS TWEAK is for 60 fps playback and not camera mod. IMHO
aditya.upadhyaya said:
Which means yes, our phone can decode 1080p60 videos (seems to be HEVC only)
Click to expand...
Click to collapse
That is DECODING - processing video files to send data to the LCD screen.
You need to look at the ENCODING process - making data files from data from the image sensor. That is a different hardware block on the chip. All I could find is that SD617 supports: "Up to 1080p video capture @60 FPS".
Datasheet doesn't say more, it's even more confusing because it says [email protected]: https://www.qualcomm.com/media/documents/files/snapdragon-617-processor-product-brief.pdf
Also, remember that, if you save on the external SD card, it's speed might not be enough to keep up with writing the video file. Some cheap cards have horrible writing performance.
It requires driver and HALs
Is honor 8 pro capable of playing X265 10bit 1080p hevc video?
I've tried samples from jelly fish with stock player, mx player n vlc. None works. Tested the same on friend's op3t phone n it played smoothly with stock player. Even X265 10bit 120mbps 4k video was played without lag on op3t. But this honor 8 pro cant even play 5mbps X265 10bit video?
So is this hardware issue on honor 8 pro?
Any suggestions??
Life_sux said:
Is honor 8 pro capable of playing X265 10bit 1080p hevc video?
I've tried samples from jelly fish with stock player, mx player n vlc. None works. Tested the same on friend's op3t phone n it played smoothly with stock player. Even X265 10bit 120mbps 4k video was played without lag on op3t. But this honor 8 pro cant even play 5mbps X265 10bit video?
So is this hardware issue on honor 8 pro?
Any suggestions??
Click to expand...
Click to collapse
Yes. It's absolutely capable. I just tried. Make sure you're using the latest vlc 3.0.0
Sent from my DUK-L09 using Tapatalk
Yes i m using vlc 3.0 but no help. Any settings to change? Attached is the screen grab. It plays for few secs and then hangs.
https://youtu.be/gvWLlUT0jMs
Pls can anyone suggest what would be the prob??
Life_sux said:
Yes i m using vlc 3.0 but no help. Any settings to change? Attached is the screen grab. It plays for few secs and then hangs.
https://youtu.be/gvWLlUT0jMs
Click to expand...
Click to collapse
I really have no idea.
Try turning the hardware acceleration to Full in Vlc.
Are you on EMUI8?
Sent from my DUK-L09 using Tapatalk
Hardware acceleration is to full and m still on emui 5.1, waiting for ota update.
If its of any help, attached is the screen grab from stock player.
Playback is smooth but with distorted colors.
https://youtu.be/YDyZ4vTSJuM
Life_sux said:
If its of any help, attached is the screen grab from stock player.
Playback is smooth but with distorted colors.
https://youtu.be/YDyZ4vTSJuM
Click to expand...
Click to collapse
I too had this problem on EMUI 5.1
Wait for the update. It may solve the problem because I didn't encounter this problem on EMUI 8.
Sent from my DUK-L09 using Tapatalk
Thanks for your help!! Will update once i get oreo update..
So my phone has been updated to emui 8.0 and phone has been factory reset post update but this issue of non playing X265 10bit videos is still there.
Any advise?
1080p hevc mkv videos cannot be played with inbuilt player (due to colour distortion, though videos are played). With MX player, HW decoder is not supported; video automatically starts playing with SW decoder. With VLC full Hardware decoding is supported without color distortion (but still playback is not that smooth, sometimes even videos got stuck).
Overall video playback on honor 8 pro is poor. So don't expect much.
Lakadbaggha said:
1080p hevc mkv videos cannot be played with inbuilt player (due to colour distortion, though videos are played).
Click to expand...
Click to collapse
correct
Lakadbaggha said:
With MX player, HW decoder is not supported; video automatically starts playing with SW decoder.
Click to expand...
Click to collapse
correct
Lakadbaggha said:
With VLC full Hardware decoding is supported without color distortion (but still playback is not that smooth, sometimes even videos got stuck).
Click to expand...
Click to collapse
correct
M facing same issues that u highlighted above. Earlier in my posts I was told that this device is capable of running hevc 10bit videos so I thought its my device specific issue.
Lakadbaggha said:
Overall video playback on honor 8 pro is poor. So don't expect much.
Click to expand...
Click to collapse
OK, so any solutions to play hevc vdo or should I stick to x264 only?
Life_sux said:
correct
correct
correct
M facing same issues that u highlighted above. Earlier in my posts I was told that this device is capable of running hevc 10bit videos so I thought its my device specific issue.
OK, so any solutions to play hevc vdo or should I stick to x264 only?
Click to expand...
Click to collapse
The chipset is surely capable but I don't know why this happens.
Vlc does play the video but if the video is skipped, it gets stuck on that frame.
Maybe because the kirin chipset isn't widely used and thus, there are optimisation issues with many apps. I get dropped frame rates almost in all games and this baffles me because the chipset is fairly powerful.
I am not buying device with kirin chipset again. Lots of optimization issues with 3rd party apps.
Sent from my DUK-L09 using Tapatalk
K.khiladi said:
The chipset is surely capable but I don't know why this happens.
Vlc does play the video but if the video is skipped, it gets stuck on that frame.
Maybe because the kirin chipset isn't widely used and thus, there are optimisation issues with many apps. I get dropped frame rates almost in all games and this baffles me because the chipset is fairly powerful.
I am not buying device with kirin chipset again. Lots of optimization issues with 3rd party apps.
Sent from my DUK-L09 using Tapatalk
Click to expand...
Click to collapse
it would be really sad. u've contributed a lot to this community. to say this means we won't see you in the honor/ huawei section that often since they usually stick to their own processor.
but yes, it does seem sad that there's really not much optimisation... though for the GPU, it is still MALI, which is also on Exynos.
i can only hope things will be better and Huawei/ honor can really work with more developers.
mydragoon said:
it would be really sad. u've contributed a lot to this community. to say this means we won't see you in the honor/ huawei section that often since they usually stick to their own processor.
but yes, it does seem sad that there's really not much optimisation... though for the GPU, it is still MALI, which is also on Exynos.
i can only hope things will be better and Huawei/ honor can really work with more developers.
Click to expand...
Click to collapse
I can't really say if that first line was sarcasm or not.
This device can't play any game without skipping frame rates. It lags pathetically on playing temple run 2.
There are clearly optimisation issues for 3rd party apps because they have optimised it exceptionally well for their own apps and the whole software. This ruins the overall experience because as the OP stated that a device with SD821 plays 1080p 10 bit x265 videos smoothly while this doesn't.
Exynos devices may not be relying from this same problem because Samsung sells those devices in a lot more number than Kirin devices.
Sent from my DUK-L09 using Tapatalk
K.khiladi said:
I can't really say if that first line was sarcasm or not.
This device can't play any game without skipping frame rates. It lags pathetically on playing temple run 2.
There are clearly optimisation issues for 3rd party apps because they have optimised it exceptionally well for their own apps and the whole software. This ruins the overall experience because as the OP stated that a device with SD821 plays 1080p 10 bit x265 videos smoothly while this doesn't.
Exynos devices may not be relying from this same problem because Samsung sells those devices in a lot more number than Kirin devices.
Sent from my DUK-L09 using Tapatalk
Click to expand...
Click to collapse
why do you think it's sarcasm??
as for Exynos devices... they also use MALI GPU, though it's a diff variant of the chip. still, if they can get it optimised... i guess we can hope it's the same for Huawei/ honor. after all, Huawei/ honor is also one of the top manufacturers in the world right now.
mydragoon said:
why do you think it's sarcasm??
as for Exynos devices... they also use MALI GPU, though it's a diff variant of the chip. still, if they can get it optimised... i guess we can hope it's the same for Huawei/ honor. after all, Huawei/ honor is also one of the top manufacturers in the world right now.
Click to expand...
Click to collapse
I felt it was sarcasm because I don't think I have done anything major for the community here. I am not a dev [emoji12]
I haven't used an Exynos device. So, I am just guessing. Yup, I know they both use the same GPU but with lesser number of cores though. Maybe that's the root cause of this or it's just pure optimisation problems, don't know because reviews didn't show any such issues with this device. I am really confused.
Sent from my DUK-L09 using Tapatalk
K.khiladi said:
I felt it was sarcasm because I don't think I have done anything major for the community here. I am not a dev [emoji12]
I haven't used an Exynos device. So, I am just guessing. Yup, I know they both use the same GPU but with lesser number of cores though. Maybe that's the root cause of this or it's just pure optimisation problems, don't know because reviews didn't show any such issues with this device. I am really confused.
Sent from my DUK-L09 using Tapatalk
Click to expand...
Click to collapse
Yes even i am also confused as reviews shows no such issues but it can be possible that not many ppl really tested these specific vidoes on this device. Hence I posted screen recordings of my phone. Need some more testers to see if I m the unlucky one.
Stock player plays video smoothly but with lot of color distortion. VLC just hangs after 1sec and MX player plays through SW decoder with lot of stuttering. XPlayer from Google play plays video much better but still stutter a lot. Overall you can't play x265 10bit HEVC videos with higher bitrate n framerate and of higher file size on our H8Pro. What a disappointment. I tested the Jellyfish sample video which was around ~33mb and main10
Not only in hevc, x264 video playback also have a bug. The 'blacks' are not shown properly in HW decoding of MX player or inbuilt player or VLCs full Hardware decoding or any app using internal codecs including video playback in YouTube app. There is a permanent 'tint' over video (only video screen) when played in these ways. The tint is absent in SW decoding mode of MX player which means the fault is in internal decoding.
To check this pause a black scene of widescreen video (so that there are top and bottom black bars). The black bars are distinctly visible in inbuilt player (and other playbacks that use internal decoding); But screen is full black (black of screen becomes same as that of bars and so can not be distinguished) when SW decoding of MX player or VLC (No harware acceleration) is used.
Not only blacks become greenish black but all colors become slightly dull compared to actual.
This most probably wasn't before oreo update.
Also there is one more magic to it. I tried to attach screenshot, but the screenshots are clear (tint is absent), even when screen recording is on tint dissapears and reappears as soon as screen recording is turned off.
I had to take shot from another phones camera. Pics in attachment is of same black scene (video paused). Screenshot is completely black while photograph shows how it actually appears (distinct top and bottom stripes).
Eye comfort or display color settings has nothing to do with it.
I already reported this issue to honor customer care but I don't think it would do anything.
Anyways, there is NO way to fully enjoy videos in our honor 8 pro. We have to just accept this. To avoid frustrations: stop downloading x265 video, stop comparing with other phones and simply accept what we have.
It seems that although the 2160p shows up in the selection, I can't play 4K60 YouTube videos properly, let along 4K60 HDR ones. I've tried with browser, Youtube app, Vanced, NewPipe, all without luck. Even when I downloaded webm files, A52s still struggles to play.
Interestingly enough, A52s actually can play 4K60 HDR10 HEVC video demos perfectly that I downloaded.
So is this about vp9 codec?
There was a thread about a similar or the same issue once:
No 4K60 playback on A52s - SD778G
Not a pleasant surprise, that this mid-2021 near top 700-class snappy is not able to play 4 year old 4K60 videos recorded with cpu-wise much weaker SoCs. Even A51 Exynos 9611 could play 4K120. Should be considered if buying this phone...:rolleyes:
forum.xda-developers.com
So maybe xplayer might help you? Although I think since that thread was about existing files that user had, it was probably H.264 files?
(I was not involved in that thread, although I remember I did download that test-file that was there and has since been removed, and I indeed could not play that one without stuttering)
Yes, Google showed me that thread before I posted.
I did test samples from 4kmedia.org, and A52s actually can play 10bit h.265 files with high bitrate using built-in player and/or xplayer without problem, albeit the highest bitrate it can handle is around 50-60 Mb/s I think.
So my real problem is about vp9.