(2018-05-19, 17:19)rudrood Wrote:

(2018-05-17, 02:13)Milhouse Wrote:

(2018-05-16, 21:22)rudrood Wrote: @Milhouse : Is the 23.976 file working oke for you with the legacy driver?

Yes the 23.976 file is switching correctly - the log includes the playback of both 23.976 and 24.0 fps videos on my Revo 3700/ION2 into Onkyo AVR/Philips TV: http://ix.io/1aAw

Grepping the log for "ADJUST":

text:
00:59:28.688 T:139893793081536 NOTICE: Display resolution ADJUST : HDMI-0: 1920x1080 @ 23.98Hz (19) (weight: -0.000)

00:59:30.242 T:139893793081536 NOTICE: Display resolution ADJUST : HDMI-0: 1920x1080 @ 23.98Hz (19) (weight: -0.000)

00:59:56.613 T:139893793081536 NOTICE: Display resolution ADJUST : HDMI-0: 1920x1080 @ 24.00Hz (18) (weight: -0.000)

00:59:58.126 T:139893793081536 NOTICE: Display resolution ADJUST : HDMI-0: 1920x1080 @ 24.00Hz (18) (weight: -0.000)

(Yeah, two ADJUST messages for every video is an Nvidia thing)

Not sure why the "weight" is -0.000 - I tested it several times and the weight is usually a large number:

text:
LibreELEC:~ # tail -Fn+0 kodi.log|grep ADJUST

00:53:43.090 T:140689497344192 NOTICE: Display resolution ADJUST : HDMI-0: 1920x1080 @ 23.98Hz (19) (weight: 474942504742052212056560953720832.000)

00:53:44.677 T:140689497344192 NOTICE: Display resolution ADJUST : HDMI-0: 1920x1080 @ 23.98Hz (19) (weight: 475001306893918267619618662121472.000)

So that's a little odd.

(2018-05-16, 21:22)rudrood Wrote: IF so: could it have something to do with how I load the legacy driver http://paste.ubuntu.com/p/dGvBcqwd3N/?

I don't think that has anything to do with it.    

 Thanks for testing. Will have to live without fps switching on this system.
Don't want to whine, but I think the whitelist function seems to criple more than it brings. Before it was introduced framerate switching was working 100% on this system.
In my opinion it replaces a perfect, easy auto switching system with a method most "standard" users will have some problems to uderstand and make work.  

Quote:21:41:29.091 T:140295208481920 INFO: ID:0x1eb Name:1920x1080 Refresh:23.975760 Width:1920 Height:1080
21:41:29.091 T:140295208481920 INFO: ID:0x1f0 Name:1920x1080 Refresh:23.970909 Width:1920 Height:1080

text:
# uname -a

Linux NUC 4.14.41 #1 SMP Sat May 19 21:06:25 BST 2018 x86_64 GNU/Linux



# lsb_release

LibreELEC (Milhouse): devel-20180519210310-#0519-g85b8697 [Build #0519]



# Kodi version

(18.0-ALPHA2 Git:5afb532). Platform: Linux x86 64-bit

• Includes latest kodi-platform master (e8574b8)
  
• Includes latest libcec master (8adc786, ahead +26)
  
• Includes latest libnfs master (6a33413, ahead +132)
  
• Includes latest p8-platform master (a822e19)
  
• Includes latest addons: inputstream.adaptive (eb7795e, +1), inputstream.rtmp (8920456), peripheral.joystick (80224e1), pvr.argustv (0ed7cae), pvr.demo (20d81d8), pvr.dvblink (19c178e), pvr.dvbviewer (0ae6207), pvr.filmon (470ca1c), pvr.hdhomerun (4639740), pvr.hts (6455047), pvr.iptvsimple (c8356fc), pvr.mediaportal.tvserver (6fab703), pvr.mythtv (9d15025), pvr.nextpvr (5f8c614), pvr.njoy (5a2c2d3), pvr.octonet (54680a3), pvr.pctv (f0c28e2), pvr.stalker (a7f3e1c), pvr.teleboy (dbdc96e), pvr.vbox (48ffcba), pvr.vdr.vnsi (a2880c7), pvr.vuplus (aca7960), pvr.wmc (b62f80e), pvr.zattoo (94cc7dd), vfs.libarchive (1b00b57)
  
• Exclude [env] kodi-0100-temp-add-pr13594.patch: merged upstream
  
• Include [env] compare (perma): dmidecode: initial package
  
• Include [env] patch: RPi/RPi2: enable Broadcom WiFi debugging (see details)
  
• Include [env] patch: libcec: fix PR390
  
• Include [env] patch: libcec: don't link non-existant libtinfo
  
• Include [env] patch: rev hack for kodi
  
• Include [env] patch: HACK: Disable multiple PVR addons during migration. Always enable inputstream.* and os.*
  
• Include [env] patch: Add experimental splash video for RPi
  
• Include [env] patch: Bump included addon versions to prevent online updates
  
• Include [env] patch: Add kodi binary addons (pvr, adsp, inputstream, vfs, other)
  
• Include [env] PR:2449 (perma): Adding support for AMD GPUs
  
• Include [env] PR:2679 (perma): eventlircd: don't grab power buttons
  
• Include [env] PR:2680 (perma): kodi: mid-May 2018
  
• Include [env] PR:2682 (perma): linux: update to linux-4.14.41
  
• Include [env] PR:2689 (perma): init: add sky42 enhancements/bug fixes
  
• Include [env] PR:2692 (perma): RPi, Generic: fix erratic IR timeout behaviour on Topseed mceusb receiver 1784:0011
  
• Include [env] PR:2694 (perma): Generic: allow lower IR timeouts on ITE CIR devices
  
• Include [env] PR:2696 (perma): linux: update ouya patch
  
• Include [pkg] patch: skin.estuary: reduce system info font size (kodi)
  
• Include [pkg] PR:13721 (perma): Std thread
  
• Include [pkg] PR:13904 (perma): Fix whitelistable resolutions on some platforms
  

1. Minors
   

1. LibreELEC.tv:
   • create_addon: changes for jenkins specific quirks (PR:2706, 1 commit, 1 file changed)
     
2. XBMC:
   • remove --legacy-res command line argument (PR:13906, 1 commit, 3 files changed)
     
   • remove -d (delay) command line argument (PR:13907, 1 commit, 1 file changed)
     
3. inputstream.adaptive:
   • SegmentTemplate in adpset cleanups (eb7795e)
     
4. Additional commits/pull requests/changes not yet merged upstream:
   • Updated: [env] PR:2680 (perma): kodi: mid-May 2018
     

(2018-05-20, 14:00)TimoJ Wrote: When I select in the Display settings "Use limited color range (16-235)" the OSD/user interface remains at the same brightness. Why is this? I seem to recall this setting used to make also the interface darker/lighter. Now video content is correct but the interface remains too dark. Intel Haswell GPU.

(2018-05-20, 14:02)fritsch Wrote:

(2018-05-20, 14:00)TimoJ Wrote: When I select in the Display settings "Use limited color range (16-235)" the OSD/user interface remains at the same brightness. Why is this? I seem to recall this setting used to make also the interface darker/lighter. Now video content is correct but the interface remains too dark. Intel Haswell GPU.

 Cannot reproduce, gets brighter / darker for me   

(2018-05-20, 14:12)TimoJ Wrote: It's in gui section algorithmdirtyregions with value 1.

(2018-05-20, 14:26)TimoJ Wrote: Is the Limited color range setting working correctly? When I enable it, the GUI gets darker but video content near black gets brighter. Shouldn't also the GUI get brighter with limited range? There is a big difference between picture and GUI brightness with video brightness/contrast at their default values.

(2018-05-20, 14:32)fritsch Wrote:

(2018-05-20, 14:26)TimoJ Wrote: Is the Limited color range setting working correctly? When I enable it, the GUI gets darker but video content near black gets brighter. Shouldn't also the GUI get brighter with limited range? There is a big difference between picture and GUI brightness with video brightness/contrast at their default values.

 Depends on many things: hw decoder, Xorg color setting and so on ...    

(2018-05-20, 15:08)TimoJ Wrote:

(2018-05-20, 14:32)fritsch Wrote:

(2018-05-20, 14:26)TimoJ Wrote: Is the Limited color range setting working correctly? When I enable it, the GUI gets darker but video content near black gets brighter. Shouldn't also the GUI get brighter with limited range? There is a big difference between picture and GUI brightness with video brightness/contrast at their default values.

 Depends on many things: hw decoder, Xorg color setting and so on ...     

Is it possible to use xorg.conf to enable limited range with Intel graphics? I found messages that indicate it's not available for Intel.

I tried command line with xrand and it worked, now GUI is at the correct brightness (I hope...). I just haven't got it to work inside autostart.sh, not sure why it's not working.

But now I'm confused why I need to use xrand to get the correct brightness. Why there is no LibreELEC GUI setting for it? Kodi's setting effect only Kodi's part, not the underlying Xorg parts? Or am I missing something?