2018-06-30, 20:49
Could you please try: 5414f7e <- that's not a solution I just want to know if I coded it right. I will revert the offending commit that forces this misbehaviour and I am currently rebuilding.
(2018-06-30, 20:47)fritsch Wrote:I used to do that - but was trying the new BBC UHD iPlayer streams on the Shield TV. Had my default (aka desktop) resolution at 3840x2160p50 and manually whitelist selected 3840x2160, 1920x1080 and 1280x720 frame rates I also wanted to use. When I tried playing 2160p50 streams it didn't stay at 2160p50 - I assumed because it wasn't in the whitelist - and went to 1080p50 instead.(2018-06-30, 20:42)noggin Wrote:I did not code it to be honest. You start kodi in 3840x2160 at 50 right? After that you manually change kodi resolution to 1920x1080 at 50? or do you keep it at 3840x2160?(2018-06-30, 20:32)fritsch Wrote: Wait a moment. The 3840x2160 at 50 hz is your DESKTOP resolution right? So kodi is actually running that, right? Then it is fully clear why it is missing. Cause the whitelist only shows the CUSTOM_MODES not the DESKTOP_MODE.OK - but then when I play 2160p50 without it selected in the Whitelist it doesn't run in 2160p50 it drops to 1080p50 - the only way I could get 2160p50 was to not have a whitelist.
Removing the desktop resolution/frame rate combo from the whitelist is also really unintuitive anyway isn't it?
(2018-06-30, 20:50)noggin Wrote:So - now you have a hidden bug agenda here :-) So even WITH the correct resolution in whitelist it does not switch to it?(2018-06-30, 20:47)fritsch Wrote:I used to do that - but was trying the new BBC UHD iPlayer streams on the Shield TV. Had my default (aka desktop) resolution at 3840x2160p and manually whitelist selected 3840x2160, 1920x1080 and 1280x720 frame rates I also wanted to use. When I tried playing 2160p50 streams it didn't select 2160p50 - I assumed because it wasn't in the whitelist - and went to 1080p50 instead.(2018-06-30, 20:42)noggin Wrote: OK - but then when I play 2160p50 without it selected in the Whitelist it doesn't run in 2160p50 it drops to 1080p50 - the only way I could get 2160p50 was to not have a whitelist.I did not code it to be honest. You start kodi in 3840x2160 at 50 right? After that you manually change kodi resolution to 1920x1080 at 50? or do you keep it at 3840x2160?
Removing the desktop resolution/frame rate combo from the whitelist is also really unintuitive anyway isn't it?
(2018-06-30, 20:52)fritsch Wrote:No - with the correct resolution in the whitelist in your test builds it DOES switch to it.(2018-06-30, 20:50)noggin Wrote:So - now you have a hidden bug agenda here :-) So even WITH the correct resolution in whitelist it does not switch to it?(2018-06-30, 20:47)fritsch Wrote: I did not code it to be honest. You start kodi in 3840x2160 at 50 right? After that you manually change kodi resolution to 1920x1080 at 50? or do you keep it at 3840x2160?I used to do that - but was trying the new BBC UHD iPlayer streams on the Shield TV. Had my default (aka desktop) resolution at 3840x2160p and manually whitelist selected 3840x2160, 1920x1080 and 1280x720 frame rates I also wanted to use. When I tried playing 2160p50 streams it didn't select 2160p50 - I assumed because it wasn't in the whitelist - and went to 1080p50 instead.
(2018-06-30, 21:04)noggin Wrote:Perfect. Curious on the version that is currently building. Would be nice if you could test that one please: fritsch-androidrf-212632f(2018-06-30, 20:52)fritsch Wrote:No - with the correct resolution in the whitelist in your test builds it DOES switch to it.(2018-06-30, 20:50)noggin Wrote: I used to do that - but was trying the new BBC UHD iPlayer streams on the Shield TV. Had my default (aka desktop) resolution at 3840x2160p and manually whitelist selected 3840x2160, 1920x1080 and 1280x720 frame rates I also wanted to use. When I tried playing 2160p50 streams it didn't select 2160p50 - I assumed because it wasn't in the whitelist - and went to 1080p50 instead.So - now you have a hidden bug agenda here :-) So even WITH the correct resolution in whitelist it does not switch to it?
The behaviour I mentioned above was in the nightlies.
(2018-06-30, 21:06)fritsch Wrote:I am - of course - now convincing myself I'm wrong...(2018-06-30, 21:04)noggin Wrote:Perfect. Curious on the version that is currently building. Would be nice if you could test that one please: fritsch-androidrf-212632f(2018-06-30, 20:52)fritsch Wrote: So - now you have a hidden bug agenda here :-) So even WITH the correct resolution in whitelist it does not switch to it?No - with the correct resolution in the whitelist in your test builds it DOES switch to it.
The behaviour I mentioned above was in the nightlies.
Thanks in advance.
(2018-06-30, 21:17)noggin Wrote:There are two design flaws here:(2018-06-30, 21:06)fritsch Wrote:I am - of course - now convincing myself I'm wrong...(2018-06-30, 21:04)noggin Wrote: No - with the correct resolution in the whitelist in your test builds it DOES switch to it.Perfect. Curious on the version that is currently building. Would be nice if you could test that one please: fritsch-androidrf-212632f
The behaviour I mentioned above was in the nightlies.
Thanks in advance.
(But who thought it was a good idea to remove your current resolution and frame rate from the whitelist?)