thanks - i think the way is right - so everyone can decide for themselves what they like better
I also think discussio SDR2HDR yes or no is not much relevant. Its like 23.976 vs counted middleframes / soap opera effect. We can agree, what is “the norm” (and myself I am within conservative category), but some people like higher saturation, higher FPS etc. For my father sport channel satured looks better, for me, watching BBC Seven Worlds so oversatured (as I am more used to raw photography and color balancing) is just sad, and saturated TV channel hurting my habit to see things more natural. Some people like less dramatic soap opera effect and cant stand less framerate (I as retired FPS player can notice immediately any framerate difference, my mother doesnt recognize anything). For some people with lower contrast image with projector, due to too bright room/surface could also have better result with overcontrasted and saturated settings. And so on and so on. As I said, personally I dont even know, how those transitions of original color range looks @HDR TV, but I dont have reason to not believe that some users found this beneficial despite warnings.
TL/DR: I think we can all agree, that “pure” solution should be always present, but safe (in term overall functionality) richer available options - better for all users (everyone can just choose their preferably choice).
So I welcome any SDR <-> HDR mapping, with warning some transformations are not standardized and could result in wrong result, even when I even do not own HDR TV (yet? nah, 4k projector would be first in future anyway, but I am happy with 1080).
I bet that devs presented those additional features when they worked, and as be mentioned, they are aware of some problems coming from recent commits, so I believe they will worked this out, or (temporary) disable non-working features.
1 Like
so a joint solution is better than a dictation - thanks for your understanding
It’s not a final fix to the sdr2hdr not doing anything issue, but I just pushed a patch that will be included for tonight’s nightly build for testing that should make the sdr2hdr setting work again, for the people that want always on HDR.
3 Likes
I hope the HDR2SDR will also be configurable again…
Not only SDR2HDR, isn’t it?
I added the SDR2HDR stuff to be tested first because it was the first one that I figured out a possible solution for.
I’m still looking for a way to make it so that HDR2SDR is configurable again. Currently it seems to be always on for displays that don’t support HDR.
I will post an update once I figure out a solution to HDR2SDR being always on.
If anybody wants to continue to debate their opinions for or against the use of SDR2HDR or HDR2SDR, can you please make a separate post in the general section of the forum instead of cluttering up the Nightly Build thread. That way it’s easier to see what is working and what is not working when reading this thread.
thanks,
4 Likes
GT King Pro does not receive IP. The IP it receives is as follows 169.254.26.229.
1 Like
Try to unplug power cable, plug it again and check if it fixed
I’m getting the same error. My device GT King Pro.
sdr to hdr works on vim3/lg oled -> many thanks for the support
1 Like
HI. I first tried the nightly dated 14th February. Then the 15th Auto updated. The hit rate for scraping is now down to 20%, and I have tried many manual variations without success for the other 80%.
In the end i gave up and reinstalled the 14th Feb with the lan cable removed. I then changed Auto update to manual, plugged in the lan cable, and rejected the 15th when offered.
I thought Manual was the default for nightlies?
Please paste a link to your kodi.log before reverting so we can look at it further.
Will do…
How do you that? Any logs appear to be in the ext4 which i cannot see when i plug the SD card back in my PC.
With the last nightly, when pausing and restarting, my N2 restarts. This problem continues …
I’m glad to hear that that worked for you.
If it becomes a problem again in the future let me know. I can’t routinely test the current status of HDR related features, since I unfortunately don’t have a TV that supports HDR, so I’m dependent on feedback from people that do to keep me updated about such issues.
1 Like
Just tested nightly on my device and still working as before. Also update Android to latest version and CoreELEC still works.
So it must be something on your side.
will be done - thanks for your support
A 169.254 . x.x usually means that you are getting a physical Link, but cannot get an IP address from your router.
Ethernet or WiFi?
Are you using DHCP?
Do you have any VPN or firewall setup on the device or router?
Can you try to manually configure an IP address?
[You will need to know what IP range your router is setup to use, and the IP address of the router to do this. Also need to make sure that you pick an IP address that is not currently being used by another device on the network.]