Related
I know that we can get better quality video recording out of the TP2, with the first WinMo phone shooting WVGA @ 30fps with the exact same hardware (minus cam module), I'm excited to see if someone can work their magic to incorporate better recording from the TP2.
Anyone else?
Cyph
I too am curious about this. I have actually always been curious as to whether the video capabilities are more software dependent or hardware... Though if the phone is capable of displaying the video on the viewfinder at WVGA at 30fps it should theoretically be possible to record at that quality. Anyways, we'll see what crops up later
Not at all
solsearch said:
I too am curious about this. I have actually always been curious as to whether the video capabilities are more software dependent or hardware... Though if the phone is capable of displaying the video on the viewfinder at WVGA at 30fps it should theoretically be possible to record at that quality. Anyways, we'll see what crops up later
Click to expand...
Click to collapse
Unfortunately the above statement is not at all true. Recording depends heavily on the camera hardware in terms of possible frame rate at a given resolution. Furthermore real-time compression and encoding is a significantly different proposition to the CPU than decoding and playback. This is not to say the TP2 hardware may not be capable of doing better than it does, just that playback capabilities are no indication.
Dennis
Like I said, I don't know how much the camera module affects it. And what I meant by theoretically is that if it can display that on the viewfinder at that res then theoretically it could be recorded in raw format (as long as the transfer to the memory could handle the speed), but it would not be practical by any means. But if the x2 is capable of it and IF the ONLY difference is the camera module, and IF the camera module is just the sensor and no graphics processing then it could possibly happen. And I'd love to see it. But neither am I going to hold my breath.
http://www.youtube.com/watch?v=5OEIZvXqzxs
You see minutes 4:29 ..... But WVGA recording resolution is 720x480? or 800x480?
Thanks
The Xperia X2 has the same CPU as the Rhodium and in theory the video recording abilities can therefore be ported. The drivers for video recording must be extracted and put into the Rhodium ROM.
Even if the Rhodium camera or drivers doesn´t handle WVGA widescreen recording it´s possible with some development work to use better encoding drivers - i.e record VGA but let a good MP4 encoder with good quality do the encoding job (i.e replace the original HTC video encoder with a better one).
In this case the original HTC camera application is retained but with replaced encoders. The user only sees a quality difference - the handling of the camera app is the same otherwise.
E90 Commie said:
The Xperia X2 has the same CPU as the Rhodium and in theory the video recording abilities can therefore be ported. The drivers for video recording must be extracted and put into the Rhodium ROM.
Even if the Rhodium camera or drivers doesn´t handle WVGA widescreen recording it´s possible with some development work to use better encoding drivers - i.e record VGA but let a good MP4 encoder with good quality do the encoding job (i.e replace the original HTC video encoder with a better one).
In this case the original HTC camera application is retained but with replaced encoders. The user only sees a quality difference - the handling of the camera app is the same otherwise.
Click to expand...
Click to collapse
That's definitely be a good thing. Maybe it could even up the fps a little bit.
The Xperia X2 has the same CPU as the Rhodium and in theory the video recording abilities can therefore be ported. The drivers for video recording must be extracted and put into the Rhodium ROM.
Even if the Rhodium camera or drivers doesn´t handle WVGA widescreen recording it´s possible with some development work to use better encoding drivers - i.e record VGA but let a good MP4 encoder with good quality do the encoding job (i.e replace the original HTC video encoder with a better one).
In this case the original HTC camera application is retained but with replaced encoders. The user only sees a quality difference - the handling of the camera app is the same otherwise.
Click to expand...
Click to collapse
Well if we can get someone on that I'd be willing to pay (big - ROM COOKERS LISTENING?? :-D ) for the capability to enhance the video recording capabilities. I just need an additional 10 fps and maybe another 200 kb/s bit rate for excellent video. That would make the video recorder to 30 fps @ ~ 1Mb/s..niiice.
If they can accomplish WVGA or even D1 (720x480) that would be cool too (or better).
I wish I had the skills/tools to do that, I'd be all over it like white on rice! LOL
Cyph
Personally I don't need 30fps (though it'd be nice). I'd be happy with a video standard such as 23.976fps or whatnot. 20 does look stuttery. Just a few more would fix that. Well. Let's hope someone looks into it. Though it might be necessary that we wait until the x2 is actually released
Ok, so people have found that standard USB cameras don't work on these units. The only known working camera is actually a fully self-contained recording device, that really only uses the USB wire for power and a few pointless controls.
https://www.carjoying.com/car-acces...-for-joying-new-android-system-head-unit.html
Really, if you're going to make the camera self contained, then what the heck is the point of bothering with the hookup with the head unit to begin with? Makes no sense.
Now the reason they did this is quite obvious... in their OLDER head units, they used the complete piece of trash ROCKCHIP 3188 SoC. I'm referring, of course, to MTC units. Those units would be *completely crippled* if you tried to record video on them, since they had neither video encoder nor even video decoder hardware blocks, which means that the video processing would be done entirely on the CPU! So they sold a camera that would mask this problem by recording the video itself!
The Intel SoC's have a video CODEC, so obviously the right way to do this now is to actually record the video on the head unit, using standard file formats.
I initially theorized that they had crippled either the kernel or the camera HAL.
So last night I watched the kernel log while plugging a PROPER USB camera in, and found something very interesting;
1) The kernel detected the camera, and properly associated it with the UVC video driver!
2) It was assigned a devfs entry of /dev/video5 --- 5? FIVE?
That's interesting. Why 5? Because there are already entries of /dev/video0 through /dev/video4.
Wonder what those extra inputs correspond to? Typically, when you plug in a device like a camera, the devfs entry is created dynamically. Yes, in this case, it was! But it was created at 5 (the 6th video device). Very likely, the HAL is hardcoded to use specific inputs from 0-4. I'm not aware of any Android mechanism for manually selecting the device. So blank screen on "DVR"? Because its trying to pull video from a video device that has no video INPUT.
It is certainly worth some investigation. I wonder what those inputs correspond to. Don't suppose that they could actually have video feeds from things like BACKUP camera and VIDEO IN, that feed Android, could they? Note that some video devices can create multiple devfs entries that correspond to different modes of operation, which could explain why there are so many.
It is also possible that the FYT5009 SoM has video input option that may not even be hooked up. Depends on how the MCU board is wired up.
I also note that in the configuration options for backup camera, there is an option for it to use a USB camera.
EDIT:
Checked into the camera HAL, it has hardcoded values for /dev/video0 through /dev/video3. What this means, is that there is currently no way in hell that Android can access /dev/video5, which is where an external USB camera is attached.
THIS IS SOMETHING WE CAN WORK WITH!!!!
AOSP USB Camera HAL:
https://android.googlesource.com/platform/hardware/libhardware/+/master/modules/usbcamera
Found something more...
There is an executable at /sbin/camcap
What it is, is a butchered build of ffmpeg
Which, of course, is licensed as GPL/LGPL.
So... intentionally and knowingly violating GPL, else why would they be hiding the identity of the program!
Great findings!
I have a USB camera I'd like to use as a DVR on one of the intel headunits. I really hope this can be done/
Good news, everyone!
I have successfully captured a video from a generic uvcvideo USB camera! And even better, over a test with a duration of about 2 minutes of HD MJPEG at whatever maximum frame rate it was able to deliver, the CPU utilization never exceeded 2% of *one* core.
Now truth is that I completely bypassed Android for this test, and ran ffmpeg directly with /dev/video5. Now this actually is a great option for running dashcam, since it is low overhead, greater running stability (no worry about Android coming around and killing the process!), and very effective.
I will begin working on a utility for managing it.
I would like to be able to capture the camera's audio stream as well, mux multiple cameras into a single video file, time based auto splitting, and a subtitle track containing a coordinate / speed readout from GPS. Ffmpeg should be able to handle all of it, except interfacing with the GPS, I will need something else to come up with the data stream for that.
doitright said:
Good news, everyone!
I have successfully captured a video from a generic uvcvideo USB camera! And even better, over a test with a duration of about 2 minutes of HD MJPEG at whatever maximum frame rate it was able to deliver, the CPU utilization never exceeded 2% of *one* core.
Now truth is that I completely bypassed Android for this test, and ran ffmpeg directly with /dev/video5. Now this actually is a great option for running dashcam, since it is low overhead, greater running stability (no worry about Android coming around and killing the process!), and very effective.
I will begin working on a utility for managing it.
I would like to be able to capture the camera's audio stream as well, mux multiple cameras into a single video file, time based auto splitting, and a subtitle track containing a coordinate / speed readout from GPS. Ffmpeg should be able to handle all of it, except interfacing with the GPS, I will need something else to come up with the data stream for that.
Click to expand...
Click to collapse
Well, that's worth being an app on Play store. Keep up the gr8 work!
KamaL said:
Well, that's worth being an app on Play store. Keep up the gr8 work!
Click to expand...
Click to collapse
I have no interest or intention of touching play store.
doitright said:
I have no interest or intention of touching play store.
Click to expand...
Click to collapse
Well, that was a sort of a compliment, but I'm not surprised of your reply...
KamaL said:
Well, that was a sort of a compliment, but I'm not surprised of your reply...
Click to expand...
Click to collapse
One of the great strengths of Android is that you don't need to mess around with the "manufacturer's only authorized software source" -- as in apple. Reality is that play store is only there for people who don't have the faintest idea about how powerful their devices actually are. Apple's store is there to restrict their users' freedom.
So I've been playing with ffmpeg, and have figured out how to use it to capture any number of v4l2 video streams into a single mkv file, with unequal video configurations, and automatic time-based file splitting.
Its pretty cool what you can do.
For instance, BETTER camera does mjpeg at high resolution (say 800x600, or even higher), 30 fps. Crappy camera only does raw 320x240 at 5 fps. I can simultaneously shove BOTH of their streams into a single mkv file **WITHOUT TRANSCODING THE STREAMS***.
This makes sense because (1) you might have a bunch of leftover cameras that you want to use, (2) you probably want to go with a higher quality on the front than the back -- backwards cameras are a lot less interesting (though still useful enough to make sense to record).
In any case, this is going to be pretty nice.
I wonder if our head units have one USB port with a hub chip? Or if they have two genuine USB ports? Easy enough to find out, I just haven't bothered to look yet.
One "issue" I'm having with the CHEAP USB cameras I'm playing around with, is that I can't select framerate or quality. It would be nice to be able to tell the camera to increase the compression ratio and drop the framerate down to, say 5 fps.... since it would make the storage requirements significantly lower. Of course, I could turn on transcoding, but couldn't use the hardware codec with ffmpeg, which means it would be on the CPU. I wonder if the cameras support it? Or if its a limitation of uvcvideo (the driver)?
Great job!
What USB camera are you currently using?
This is the one I bought, thinking it was a rear view camera! Oh well....
http://www.ebay.com/itm/351843416292?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT
Claims resolution to be 728 * 582 , not sure if it's true. It would be great if I could use it for basic DVR functionality on the Intel 2GB units.
Now that @doitright is banned, is there anyone capable of continuing his work with this issue?
I'd love to use my USB camera for DVR.
I contacted Joying with this regard, and they weren't helpful at all. They keep claiming on their USB camera is supported. True nonsense.
why was he banned????
gtxaspec said:
why was he banned????
Click to expand...
Click to collapse
Read some of his posts on the forum and you'll understand.
Is anyone here capable of doing the same changes for adding support to USB DVR ??
KamaL said:
Read some of his posts on the forum and you'll understand.
Is anyone here capable of doing the same changes for adding support to USB DVR ??
Click to expand...
Click to collapse
I ve read his last 25 posts and I cant see anything that would get his account temporally disabled (XDA doesnt ban people).
typos1 said:
I ve read his last 25 posts and I cant see anything that would get him banned.
Click to expand...
Click to collapse
AFAIK Some were deleted , but it doesn't matter. Let's get back to topic
Weird, he was a helpful user, giving us full bluetooth and all. Seems counterproductive to ban a good resource, oh well....
Hilari0 said:
Weird, he was a helpful user, giving us full bluetooth and all. Seems counterproductive to ban a good resource, oh well....
Click to expand...
Click to collapse
Yep, I know. I'm trying to contact him through the official Joying forums, he was active there too, but no traces of him yet. I'm sure he could have found a solution for this issue.
I have my USB dvr cam installed in the car, waiting for a fix.
Hilari0 said:
Weird, he was a helpful user, giving us full bluetooth and all. Seems counterproductive to ban a good resource, oh well....
Click to expand...
Click to collapse
KamaL said:
Yep, I know. I'm trying to contact him through the official Joying forums, he was active there too, but no traces of him yet. I'm sure he could have found a solution for this issue.
I have my USB dvr cam installed in the car, waiting for a fix.
Click to expand...
Click to collapse
Not weird at all if he broke forum rules (which he must have to be suspended).
Unless you think that if someone is helpful then theyre allowed to break the rules ?
Great news everyone, we have a working solution for running any USB cam on the joying intel units!
I'll let you guess who is working on it. check the progress on github:
https://github.com/lbdroid/FFMpeg-DashCam
It's working pretty well for me!!
KamaL said:
I'll let you guess who is working on it.
Click to expand...
Click to collapse
Thanks to the wonderful worker(@doitright), everyone can talk, only some can and will work!!Kudos
KamaL said:
Great news everyone, we have a working solution for running any USB cam on the joying intel units!
I'll let you guess who is working on it. check the progress on github:
https://github.com/lbdroid/FFMpeg-DashCam
It's working pretty well for me!!
Click to expand...
Click to collapse
Kudo's to him! Hopefully he still read this forum.
Why is it that despite of having same configuration as OnePlus3, ZUK can't play 4KHDR @60fps as smooth as OP3? Though it can, after some tweaks, but not as efficiently & smooth as OP3(unrooted). I used same Version of MXPlayer and same file for comparison.
I tried all custom kernels available (Heliox,Jaguar,Darkmoon) and Latest versions of major ROMs(RR,AEX,ViperOS). And still didn't match the playback quality of OP3.
Please tell me if there are more kernels or ROMs yet to be tried, which can bring substantial step-up in performance, or which will just Play 4KHDR @ 60fps.
Overall, the User Experience is super-smooth but
this small thing is eating my brain :crying:
d3vyarth said:
Why is it that despite of having same configuration as OnePlus3, ZUK can't play 4KHDR @60fps as smooth as OP3? Though it can, after some tweaks, but not as efficiently & smooth as OP3(unrooted). I used same Version of MXPlayer and same file for comparison.
I tried all custom kernels available (Heliox,Jaguar,Darkmoon) and Latest versions of major ROMs(RR,AEX,ViperOS). And still didn't match the playback quality of OP3.
Please tell me if there are more kernels or ROMs yet to be tried, which can bring substantial step-up in performance, or which will just Play 4KHDR @ 60fps.
Overall, the User Experience is super-smooth but
this small thing is eating my brain :crying:
Click to expand...
Click to collapse
First of all, You are comparing "THE BEST" SD820 phone with probably the 3rd or 4th best SD820 phone (antutu wise). Secondly, even on the OP3, why would you choose to play 60fps 4K videos that too HDR ones?! That's ridiculous for anyone. I'm hoping the logical explanation to why you're doing this is to kinda benchmark the phone. But even then a lot of SD653 and SD810 phones can breeze through this benchmark easily. It's even more ridiculous that you've tried almost all roms and kernel combos just for a luxury video playback.
Anyways coming to the point, I tried the Sony 4K 60fps HDR Swordsmith video on my Z2+ (AEX4.6 Official with HelioX 3.18.80) via MX with HW (not plus) decocer and the video was running smooth AF. Infact, compared to playback my friend's OP3 running OxyOS 5.0, my Z2+ had zero hiccups throughout the video while the OP3 had 2 or 3 towards the middle. The interesting thing is that I achieved these results while running CPU underclocked to 1996 & 1401. But technically speaking that shouldn't be a problem in the video playback coz HW decoder runs exclusively on the GPU. Concluding my point, don't watch ridiculously high quality videos on phone and don't change roms and kernels to achieve desired playback, just adjust and optimize them.
Incrovantilist said:
First of all, You are comparing "THE BEST" SD820 phone with probably the 3rd or 4th best SD820 phone (antutu wise). Secondly, even on the OP3, why would you choose to play 60fps 4K videos that too HDR ones?! That's ridiculous for anyone. I'm hoping the logical explanation to why you're doing this is to kinda benchmark the phone. But even then a lot of SD653 and SD810 phones can breeze through this benchmark easily. It's even more ridiculous that you've tried almost all roms and kernel combos just for a luxury video playback.
Anyways coming to the point, I tried the Sony 4K 60fps HDR Swordsmith video on my Z2+ (AEX4.6 Official with HelioX 3.18.80) via MX with HW (not plus) decocer and the video was running smooth AF. Infact, compared to playback my friend's OP3 running OxyOS 5.0, my Z2+ had zero hiccups throughout the video while the OP3 had 2 or 3 towards the middle. The interesting thing is that I achieved these results while running CPU underclocked to 1996 & 1401. But technically speaking that shouldn't be a problem in the video playback coz HW decoder runs exclusively on the GPU. Concluding my point, don't watch ridiculously high quality videos on phone and don't change roms and kernels to achieve desired playback, just adjust and optimize them.
Click to expand...
Click to collapse
My point on playing the best video quality I have, bcz ZUK can, why not. I tried LG Cymatic Jazz HDR to test the playback(details attached).
Back when I had ZUI, it could not play the video at 60 fps. But when I flashed first RR, I was surprised by the result. In MX Player Pro with HW+, it could play super smooth with absolute 0 lag.
Then came updates and further more I flashed many ROMs but never got that playback. Changing kernels didn't help. And now I've same ROM and kernel as you do, because you know.
The fact that you can play 4KHDR @ 60fps, may be bcz ur video isn't having 10 bit color depth. Please attach your video details, I wanna see. If our videos are of same quality, then I may be having some other issue.
Its strange however, you're playing 4KHDR on HW.
Also, do you have Substratum theme or Xposed modules installed? Just curious if these affect performance in any way.
d3vyarth said:
The fact that you can play 4KHDR @ 60fps, may be bcz ur video isn't having 10 bit color depth. Please attach your video details, I wanna see. If our videos are of same quality, then I may be having some other issue.
Its strange however, you're playing 4KHDR on HW.
Also, do you have Substratum theme or Xposed modules installed? Just curious if these affect performance in any way.
Click to expand...
Click to collapse
No Substratum No Xposed. And the video I tried has same video specs as yours (attached).
Incrovantilist said:
No Substratum No Xposed. And the video I tried has same video specs as yours (attached).
Click to expand...
Click to collapse
Is it possible that Xposed and Substratum are somewhere causing pain to the system?
Also, I once changed some screen values through Kernel auditor and tried to undo that. I don't know if they're default now, I'm attaching SS just tell me if they're same. I'll try uninstalling Substratum and Xposed and keep system as Lite as possible and then check.
Thanks for your attention and help
d3vyarth said:
Is it possible that Xposed and Substratum are somewhere causing pain to the system?
Also, I once changed some screen values through Kernel auditor and tried to undo that. I don't know if they're default now, I'm attaching SS just tell me if they're same. I'll try uninstalling Substratum and Xposed and keep system as Lite as possible and then check.
Thanks for your attention and help
Click to expand...
Click to collapse
Substratum can have some slowing effect on GPU due to its theme engine but that'll be possibly unnoticeable in a SD820. Xposed should be harmless (afaik with my previous phones) unless you are running GPU affecting modules. I don't use substratum because I was perfectly happy with CM theme engine and now that it's gone, I'm not so keen for a replacement. Xposed went meaningless after Lollipop & the birth of Magisk (for me atleast). And lastly about Screen values in KA, they don't have any effect on GPU unless ofcourse you're running grayscale which might actually save you some power (but might be unstable). If you want to reset the values, just uncheck apply on boot under screen settings and reboot. FYI, I ran almost all KCAL profiles I found online and "Perfection" (that's the name of the KCAL profile) for OP2 is giving the best visuals in my perspective. Try it if you want. Happy to have helped you ?✌?
Imo the zuk z2 is not as good at playback than I expected. Even 1080p60 video drop frames constantly at 2x playback speed
Also the phone dont have a hdr screen so why even try to play hdr content anyway
pipyakas said:
Imo the zuk z2 is not as good at playback than I expected. Even 1080p60 video drop frames constantly at 2x playback speed
Also the phone dont have a hdr screen so why even try to play hdr content anyway
Click to expand...
Click to collapse
Playing a 60fps video at 2x speed would mean 120fps, that's out of our screen limit. For that purpose display needs 120Hz refresh rate as in New Razer phone, or some frames will get skipped(frame drops) as you noticed.
And the reason why I wanna play that, I search of playing that thing smoothly, I've learned many things. It simply gives me satisfaction.
Incrovantilist said:
Substratum can have some slowing effect on GPU due to its theme engine but that'll be possibly unnoticeable in a SD820. Xposed should be harmless (afaik with my previous phones) unless you are running GPU affecting modules. I don't use substratum because I was perfectly happy with CM theme engine and now that it's gone, I'm not so keen for a replacement. Xposed went meaningless after Lollipop & the birth of Magisk (for me atleast). And lastly about Screen values in KA, they don't have any effect on GPU unless ofcourse you're running grayscale which might actually save you some power (but might be unstable). If you want to reset the values, just uncheck apply on boot under screen settings and reboot. FYI, I ran almost all KCAL profiles I found online and "Perfection" (that's the name of the KCAL profile) for OP2 is giving the best visuals in my perspective. Try it if you want. Happy to have helped you ?✌?
Click to expand...
Click to collapse
I removed Substratum and Xposed, even Shox audio mod, but result was same.
Though Performance as CPU Governor gives 100% results, but you said you've Under-Clocked ur CPU to 1996MHz, that did surprise me.
Which CPU & GPU governor do you use? Also which I/O Scheduler? I'm curious.
d3vyarth said:
I removed Substratum and Xposed, even Shox audio mod, but result was same.
Though Performance as CPU Governor gives 100% results, but you said you've Under-Clocked ur CPU to 1996MHz, that did surprise me.
Which CPU & GPU governor do you use? Also which I/O Scheduler? I'm curious.
Click to expand...
Click to collapse
Fiops scheduler.
CPU Governor is Interactive. (default on HelioX)
GPU Governor is Msm-adreno-tz. (default on HelioX)
Incrovantilist said:
Fiops scheduler.
CPU Governor is Interactive. (default on HelioX)
GPU Governor is Msm-adreno-tz. (default on HelioX)
Click to expand...
Click to collapse
I use same settings
I think I need to do more research on this.
Updating to Oreo smoothed everything out :fingers-crossed:
So one thing that I understood from the launch live is that google has collabbed with Snapchat to bring full implementation of HDR within the app.
My biggest doubt is.. will it also fully integrate with all the other social network apps or not? I mean apps like TikTok, Instagram and most of all, Whatsapp..
What makes an android phone so bad for socials is that they totally cripple camera performance once you use a third party camera app. On the other end iPhone's do it perfectly. If only the Pixel filled this gap, it would be a no brainer choosing Android over iOS..!
I currently have a Pixel 3 XL and every time I use the camera to take photos in Whatsapp or videos in tiktok, its utterly ugly, it looks like the pic was taken from a Galaxy s4.
I'm still not so sure if we even have "true" HDR10 (or better, like Dolby Vision on Iphone 13Max) on the Pixel. Did anyone actually try to look at picture/videofootage at a HDR capable monitor/TV and did HDR kick in?
As far as I know, it's all some fake-ass SDR vivid-algorithm BS.
Morgrain said:
I'm still not so sure if we even have "true" HDR10 (or better, like Dolby Vision on Iphone 13Max) on the Pixel. Did anyone actually try to look at picture/videofootage at a HDR capable monitor/TV and did HDR kick in?
As far as I know, it's all some fake-ass SDR vivid-algorithm BS.
Click to expand...
Click to collapse
I used HDR Display Check
plasticarmyman said:
I used HDR Display Check
Click to expand...
Click to collapse
I wasn't talking about the Panel. All Pixels have HDR10 Display capabilities, I was talking about the camera.
Morgrain said:
I wasn't talking about the Panel. All Pixels have HDR10 Display capabilities, I was talking about the camera.
Click to expand...
Click to collapse
ah fair enough, i need more coffee i guess
Morgrain said:
I wasn't talking about the Panel. All Pixels have HDR10 Display capabilities, I was talking about the camera.
Click to expand...
Click to collapse
how would I potentially test this?
plasticarmyman said:
how would I potentially test this?
Click to expand...
Click to collapse
I guess we/you'd have to transfer footage of your phone (video/photos) to a HDR capable device (like an LG CX or something like that) and see if HDR kicks in. It's also possible to detect this with Windows tools like MediaInfo. If the video is recorded with HDR it will have a color space of BT. 2020 also know as REC.2020.
Even though it's kinda tricky to determine if it really is shot in 10bit. There is a differenec between color depth and color space, meaning a video can be shot in 8bit and can still output a HDR signal, even though it lacks all basic features that HDR should offer. This whole HDR story is a joke at this point, it's basically broken in Windows, the whole industry is split in several factions (HDR10, HDR10+, Dolby Vision...), there is almost no cross-compatibility and then you can't even trust the output of a file, as explained earlier.
It sucks, and it sucks hard. I - for example - tried to get Mass Effect: Andromeda working with Windows 11 (Dolby Vision) and stopped after about 9 hours of troubleshooting because of Black Screen problems, rainbow color issues, crashs, forced restarts because the Windows UI crashed/became invisible...
HDR is just a mess. It only works well if you put a streaming device directly into an HDR capable Television and use Apps like Disney+, Netflix, HBO MAX or something like that.
It's a shame, because footage shot in true HDR look simply stunning.
Morgrain said:
I guess we/you'd have to transfer footage of your phone (video/photos) to an HDR capable device (like an LG CX or something like that) and see if HDR kicks in. It's also possible to detect this with Windows tools like MediaInfo. If the video is recorded with HDR it will have a color space of BT. 2020 also know as REC.2020.
Even though it's kinda tricky to determine if it really is shot in 10bit. There is a differenec between color depth and color space, meaning a video can be shot in 8bit and can still output a HDR signal, even though it lacks all basic features that HDR should offer. This whole HDR story is a joke at this point, it's basically broken in Windows, the whole industry is split in several factions (HDR10, HDR10+, Dolby Vision...), there is almost no cross-compatibility and then you can't even trust the output of a file, as explained earlier.
It sucks, and it sucks hard. I - for example - tried to get Mass Effect: Andromeda working with Windows 11 (Dolby Vision) and stopped after about 9 hours of troubleshooting because of Black Screen problems, rainbow color issues, crashs, forced restarts because the Windows UI crashed/became invisible...
HDR is just a mess. It only works well if you put a streaming device directly into an HDR capable Television and use Apps like Disney+, Netflix, HBO MAX or something like that.
Click to expand...
Click to collapse
i'm getting ColorSpace YUV with video and pictures, even when using Open Camera with HDR enabled.
I haven't had any issues in Windows with my second Monitor that has HDR capabilities....but there are times when I turn it off because it doesn't look the best in some games.
Mass Effect Legendary Edition was having wash out issues on my pc until I turned it off
Hi guys, I've tried to watch some movies with HDR (1080 and UHD movies) but the image is really really dark even on max brightness level in a dark room; I've tried both Plex and MX Player Pro but still nothing, even the HDR videos on YouTube are very dark.
Also I am sure that the HDR of the video works correctly because on a samsung galaxy s10 it works perfectly and I can see it very well.
Here is a comparison to show you the difference indicatively (S10 VS Mi Pad 5): Imgur Comparisons
Does this happen to you too?
My tablet: International Xiaomi Pad 5 with MIUI 12.5 (12.5.8.0 Stable)
different display, different hdr format. s10 use hdr10+ with a amoled screen so def better than ips panel with standard hdr10.
different display, different hdr format. s10 use hdr10+ with a amoled screen so def better than ips panel with standard hdr10.
Click to expand...
Click to collapse
It's not a question of better or worse panel, here with the mi pad 5 the HDR does not work completely.
It is sold as HDR10 & Dolby Vision certified but then they don't work at all; I've also seen a user on reddit report the exact same thing so I'm starting to think it's a software problem...
Filippo255 said:
It's not a question of better or worse panel, here with the mi pad 5 the HDR does not work completely.
It is sold as HDR10 & Dolby Vision certified but then they don't work at all; I've also seen a user on reddit report the exact same thing so I'm starting to think it's a software problem...
Click to expand...
Click to collapse
when you open hdr video, if it's too dark, yes, that's because hdr is working, but ips panel is not really good at dark color so that's the problem.
I also subscribe to this issue, I own the Non-Pro and HDR videos are way too dark, some movies on Netflix are almost impossible to watch despite cracking the brightness up manually (it makes the subtitle too bright compared to actual video).
I hope Xiaomi will implement a fix in future updates.
Also, when playing Dolby Vision files, the aspect ratio is something bad such as 20:9 (actual videos are played in some ultra-wide aspect ratio), the actual dark frames on top and bottom eat 50% of the vertical space, this is also a bug.
If I knew the software is that bad I would had gone with Samsung tablet instead.
@OP is not wrong at all, this is a software issue, the screen is bright enough for HDR content but the software is lacking.
Bug has been reported on a lot of forums, including here :
https://www.reddit.com/r/PleX/comments/rofr22
icsterm said:
I also subscribe to this issue, I own the Non-Pro and HDR videos are way too dark, some movies on Netflix are almost impossible to watch despite cracking the brightness up manually (it makes the subtitle too bright compared to actual video).
I hope Xiaomi will implement a fix in future updates.
Also, when playing Dolby Vision files, the aspect ratio is something bad such as 20:9 (actual videos are played in some ultra-wide aspect ratio), the actual dark frames on top and bottom eat 50% of the vertical space, this is also a bug.
If I knew the software is that bad I would had gone with Samsung tablet instead.
@OP is not wrong at all, this is a software issue, the screen is bright enough for HDR content but the software is lacking.
Click to expand...
Click to collapse
Thanks for confirming my theory, it needs a bug fix otherwise so the device is really unusable for HDR content.
Have you also reported this to Xiaomi hoping that it will solve as soon as possible?
The problem is that hdr videos are made for really bright screens (hdr10 1000nits, hdr10+ 4000nits, DV up to 10tsd nits). Now on TVs this is normally not a problem because the TVs know what there max. brightness is and they can adjust the brightness of the movies. The tablet itself does also know the max. brightness but the Netflix or whatever player does not (or at least it does not work). What you can do is, use a player like mpv, and set the target-peak or, which i would not recommend, set the video brightness. Sadly, once again, the users who pay and watch movies legally are the ****ed once.
Its a night and day difference.
Filippo255 said:
Have you also reported this to Xiaomi hoping that it will solve as soon as possible?
Click to expand...
Click to collapse
Did you used the feedback app that they include in the actual ROM? Or on a website?
icsterm said:
I also subscribe to this issue, I own the Non-Pro and HDR videos are way too dark, some movies on Netflix are almost impossible to watch despite cracking the brightness up manually (it makes the subtitle too bright compared to actual video).
I hope Xiaomi will implement a fix in future updates.
Also, when playing Dolby Vision files, the aspect ratio is something bad such as 20:9 (actual videos are played in some ultra-wide aspect ratio), the actual dark frames on top and bottom eat 50% of the vertical space, this is also a bug.
If I knew the software is that bad I would had gone with Samsung tablet instead.
@OP is not wrong at all, this is a software issue, the screen is bright enough for HDR content but the software is lacking.
Bug has been reported on a lot of forums, including here :
https://www.reddit.com/r/PleX/comments/rofr22
Click to expand...
Click to collapse
I noticed that the "standard" display mode was way better for me than Vivid on Netflix. I can see dark scenes way better with it
manu_jedi said:
The problem is that hdr videos are made for really bright screens (hdr10 1000nits, hdr10+ 4000nits, DV up to 10tsd nits).
Click to expand...
Click to collapse
By your logic, DV must be completely black but instead, it's the only HDR that works on Pad5.
icsterm said:
Also, when playing Dolby Vision files, the aspect ratio is something bad such as 20:9 (actual videos are played in some ultra-wide aspect ratio), the actual dark frames on top and bottom eat 50% of the vertical space, this is also a bug.
Click to expand...
Click to collapse
This is a "just player" bug, use mpv.
Critical Hit said:
By your logic, DV must be completely black but instead, it's the only HDR that works on Pad5.
Click to expand...
Click to collapse
No, bad wording. It is made for screens up to ...nits. Now when you want to display it on a screen, not as bright, you need to map the colors to a lower brightness. And you don't wan't to simply cut it off on the dark or bright side. But you can tweak the mapping and the default players are really bad at it. Also i have no clue why DV should be the only one working.
Critical Hit said:
This is a "just player" bug, use mpv.
Click to expand...
Click to collapse
I also highly doubt that mpv fixes anything. It uses the same HW decoding than any other player for DV or if it uses the SW decoder the colors will not be correct. Here is the issue: https://github.com/mpv-player/mpv/issues/7326
You don't understand. DV _and_ hdr10 should work, but right now it's only DV and only with mpv and JP. The image is dark but not too dark as with hdr10. Just Player has a bug with black bars (it's not the aspect ratio because the image is cut on top and bottom.), not colors.
Critical Hit said:
You don't understand. DV _and_ hdr10 should work, but right now it's only DV and only with mpv and JP. The image is dark but not too dark as with hdr10. Just Player has a bug with black bars (it's not the aspect ratio because the image is cut on top and bottom.), not colors.
Click to expand...
Click to collapse
I don't wan't so sound rude but mpv just does not support DV. IF mpv playes your DV files i would be highly interessted in those files. I can imagine that you have some hdr10 compatible DV files? These will play in mpv just like hdr10 files. You can check with mediainfo and look for the HDR format string. E.g Lotr DV BD would be :
Dolby Vision, Version 1.0, dvhe.07.06, BL+EL+RPU, Blu-ray compatible / SM PTE ST 2086, HDR10 compatible"
you can also see the mastering brightness here
Mastering display luminance : min: 0.0050 cd/m2,m ax: 4000 cd/m2
Also the cropping for files happens on all DV files (that i could find). All of these players have in common that they use the HW decoding for DV and afaik there are no DV players which do not use HW
manu_jedi said:
These will play in mpv just like hdr10 files.
Click to expand...
Click to collapse
Ok, it looks like you're right but results are still completely inconsistent.
manu_jedi said:
Mastering display luminance
Click to expand...
Click to collapse
Maybe this is the problem. But I can't get this info in MI.
This sample has this mediainfo:
Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU
Click to expand...
Click to collapse
JP plays it perfectly (or ok) without cropping problem and mpv has broken colors (so it really can't play DV).
Sample
Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2086, HDR10 compatible
Click to expand...
Click to collapse
Just Player plays it perfectly but has the cropping problem. With mpv picture is completely broken and with VLC&MXP it's ok (not too dark).
Sample
Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2086, HDR10 compatible
Click to expand...
Click to collapse
JP has cropping&brightness problems, mpv doesn't. But it looks like mpv is using tone mapping (?) - if you pause the file in VLC and tilt the pad the image would be the same as in mpv.
IMO this is a limitation with the physical screen itself, the fact is pad 5 only had a peak brightness of around 500, 478 nits iirc. Trying to play HDR content on a 478 peak brightness screen is impossible without doing some sort down- "tone mapping" which if it does, it's not HDR anymore, just capable of displaying HDR video. (the S10 iirc has 1000 nits max brightness and can peak to 1200 when required on a short time, that;s why the dark part is clear there).
on a 478 nits screen, even if you crank the brightness as high as it could, the dark part of the video is probably too crammed together, thus you're seeing a crushed black on HDR videos, where the dark part actually blends into a blob instead of just being really dark with some sort of defining shape clarity. The only solution is to change the tone mapping to SDR (BT.709 color space) either by transcoding the video itself or use a player with a tone mapping function (which if exist only useful for video files and not streaming services).
Etmors said:
(the S10 iirc has 1000 nits max brightness and can peak to 1200 when required on a short time, that;s why the dark part is clear there).
Click to expand...
Click to collapse
You talking about marketing numbers. Here is a test of S21 https://www.gsmarena.com/samsung_galaxy_s21-review-2218p3.php 416 to 856 nits. https://www.gsmarena.com/xiaomi_pad_5-review-2317p3.php pad5 has 478 nits and they guessing there can be more "Unfortunately, there is no Sunlight Boost even if the settings page suggests that. Maybe it will be enabled with a future firmware update, maybe not. Still tablet can be much brighter when watching HDR content, of course,". Iirc there was a review with 500+ nits max test with this Boost.
And the question is why there is only one player that can show you decent results with dv&hdr10 but has a cropping bug? Why Xiaomi with these hardware specs marketing it as compatible when even their own player can't play this content with decent results?
Updated to miui13 and it looks like the cropping problem on Just Player is gone.
Critical Hit said:
You talking about marketing numbers. Here is a test of S21 https://www.gsmarena.com/samsung_galaxy_s21-review-2218p3.php 416 to 856 nits. https://www.gsmarena.com/xiaomi_pad_5-review-2317p3.php pad5 has 478 nits and they guessing there can be more "Unfortunately, there is no Sunlight Boost even if the settings page suggests that. Maybe it will be enabled with a future firmware update, maybe not. Still tablet can be much brighter when watching HDR content, of course,". Iirc there was a review with 500+ nits max test with this Boost.
And the question is why there is only one player that can show you decent results with dv&hdr10 but has a cropping bug? Why Xiaomi with these hardware specs marketing it as compatible when even their own player can't play this content with decent results?
Click to expand...
Click to collapse
I will refer to displaymate, while 400-800 nits are brightness in manual mode, when used in automatic brightness at high ambient light it could bring up to 900 nits for 50% apl, and 1200+ nits for 1% (which is probably where the 1300 nits marketing came from, while 1% APL is practically useless it's not entirely false either).
I did once owned an S10, and when you play HDR content, the screen will enter that automatic brightness mode, as it does becomes really-really bright, as if I was using it outdoor (high ambient light). So I would assume when comparing HDR vs HDR then the S10 probably should be assumed operated at 800-900 nits. Playing SDR content, you can't achieve the same brightness when playing HDR. I can't comment on s21 since i don't owned one, and can't tell if this automatic brightness thing still exist.
This is the same issue with HDR400, while by specification it is HDR, it sucks. And pad 5 being "Support Dolby Vision" is not equal to a brilliant dolby vision experience, it could be just technicalities that means that it could receive dolby Vision Input.
HDR10 contents usually are mastered at 1000-4000 nits, (I would assume DV is around that or bit higher). HDR TVs are usually only start to have good HDR experience from 600 nits or more, 1000 nits preferable. So I really can't complain if I don't get the same experience with seeing HDR10/DV on a 1000 nits TVs.
OTOH I do agree that there's also a software issues because the inconsistencies I've also experience, like when playing HDR content, even when i pump the brightness to full, it felt like it is not as bright as playing SDR at full brightness. And playing HDR10 in youtube is usually just fine (idk if youtube tone-mapped the HDR), only when playing hdr10 video files or streaming service like netflix/prime that the issue exist.
The only thing I wish it had is a turn off HDR switch or tone-mapping enable switch. Like most dark scene on netflix with DV are unviewable in this device, because it's way too dark, and I'd just rather see the SDR version.
Etmors said:
The only thing I wish it had is a turn off HDR switch or tone-mapping enable switch. Like most dark scene on netflix with DV are unviewable in this device, because it's way too dark, and I'd just rather see the SDR version
Click to expand...
Click to collapse
Youtube app doesn't do tone mapping but you can manually set quality to SDR in the smartube app.
With files (or netflix), if it's too dark, you can set the color scheme to "standard" but the image would be low saturated or use built-in brightness&contrast settings in mpv (+10 both is good).
Tone mapping is an app feature not global, so until Netflix does something you can't do much. Only fake the hardware id/specs that it can't support HDR (idk if it's possible).
Just some more info on mpv with hdr (all for normal hdr, no DV):
Use this if you want to use the hardware decoding that normal player use (like the integrated video player):
vo=mediacodec_embed
hwdec=mediacodec
wid=(intptr_t)(*android.view.Surface)
this will directly use HW decoding and present the result on the screen.
Use the following if you want more details in dark scenes (i think this are the default settings):
hwdec=mediacodec-copy
gpu-context=android
I don't know exactly what mpv uses internally here but the main idea is to use the HW decoding, copy the image back to memory, do some post processing and present it on the screen
What i like to use:
hwdec=mediacodec-copy
gpu-context=android
hdr-compute-peak=yes
tone-mapping=hable
Mostly the same, but not as aggressive in my opinion (only personal preference).
more to read: https://mpv.io/manual/stable/#options-tone-mapping