CroqueMr is one guy and probably trying his best to keep up with all the reports and asks. Good to have you here and sharing what's working and not. Think having more testers surfaces more potential bugs or functionality needing to be addressed.
I have confidence in CroqueMr + hadesdevls here, and popcornmix + cinemaONE for all things 3D. Just need to allow some time. RC2 is already so good, and in a matter of mere 6 weeks or so. Crazy fast dev work!
I most definitely wasn't complaining about devs. I'm a bit discouraged because, as mentioned, I'm starting to think that something is wrong with my NUC. Series 11 misbehaved for a while, than it was fine. I thought as long as one connected to HDMI 2 output everything was fine. But who knows, maybe it's not. The intermittently blanking screen is really disconcerting to see.
I know. I did investigate before committing to buying the fanless case and the FLIRC receiver. But then... my experience so far has been quite removed from this being anywhere close to a daily driver for me.
Tried one last time before going to sleep, finally got Hades to start and this time I got a message in the black void window:
systemd[1]: iptables.service: Failed with result 'exit-code'
after that I got the message that my main monitor will be disabled and it will switch to the HDMI output, which is the correct thing to happen and I was able to use Hades normally as before.
I have no idea if that message is in any way related to why all my other starts with Croques RC2 or Hades RC5 failed, but for some reason it worked this time.
Sadly I didn't get a debug output for the failed startup, but now with a succesful startup it finally wrote log files.
Hades has got my debug zip in another issue for my USB dongles for my mouse & keyboard, so maybe there could be a hint on that startup problem. https://github.com/hadesdevls/LibreELEC-Hades/issues/13
Display MoreHrrmmm... tried the new RC2 release.
I suggest having settings for DV conversions the same way as the AmLogic builds have.
If I select HDR10+ ---> DV during a HDR10+ movie, it works. I stop the movie, I play a HDR10 movie and it outputs as HDR10, even if in settings I set HDR10 to be outputted as Dolby Vision.
One setting for Dolby Vision, one setting for HDR10, one setting for HDR10+. During these early days it's fine and dandy to want to test everything. But for real usage I think one wants to configure it once and not have to fiddle in real time for every video started.
I also noticed that SDR videos do not respect limited output setting. My OLED tv is calibrated to 16-235, so I need limited video levels. I set them in the System/Video settings page and for HDR/DV content they are respected. If I play a SDR video, black becomes gray. Tested this with patterns as well, like the classic one with grey bars and black should be at level 16. I see instead grey bars far below 16. Something is amiss.
I also keep on seeing HDR videos blanking the screen intermittently. I have already sent a debug log to CroqueMr about this, I don't know if he has had a chance to look at it. I'll most likely test tomorrow with the official build to see how the situation is over there. I am starting to be very afraid that my NUC 11 i3 might be a lemon of sort. It takes ages to switch screen mode/refresh rate, far longer than what happens with AM6B+ or my HTPC. It often gets the "no signal" screen from my LG tv set. Something I never see happen on either AM6B+ or HTPC.
I was so enthusiastic about this whole development that I bought a fanless case for it before even testing the builds... but everybody seemed so happy. You live and learn...
No worries, HDR10+ is not yet perfect and some of your issues as already been fixed for RC3. Normaly last settings is saved and will be applied to your next playback. And if the rendering output is not correct you can switch the mode on the fly during your play back, press "O" twice to have the quick pannel settings
For SDR and limited video the fix will be simple.
For the support of your NUC please open an issue on github it’s much easier for me to keep track of everything this way. If necessary, I just finished my build with remote access that allows me to make on-the-fly fixes and investigate any hardware issues directly on your minipc. This build is private, of course, and includes all the required consent disclosures. We can go that route if needed and if you agree.
Normaly last settings is saved and will be applied to your next playback.
Yes, but I don't think I am explaining myself properly. There currently are four HDR standards: HDR10, HDR10+, Dolby Vision, HLG.
In CoreELEC builds, for each format you decide how to handle it. And all videos follow those rules, without any need for further manual intervention by the user. It's nice to have the option to switch on the fly (through the O shortcut) but that should not be substituting proper settings for everyday use.
I hope now my explanation is clearer. Thanks for listening and for your patience with the multitude of users...
Yes, but I don't think I am explaining myself properly. There currently are four HDR standards: HDR10, HDR10+, Dolby Vision, HLG.
In CoreELEC builds, for each format you decide how to handle it. And all videos follow those rules, without any need for further manual intervention by the user. It's nice to have the option to switch on the fly (through the O shortcut) but that should not be substituting proper settings for everyday use.
I hope now my explanation is clearer. Thanks for listening and for your patience with the multitude of users...
I agree with this, there should be 4 separate conversion options configure once in the player settings. FOr me I would do this:
HDR10 -> HDR10
HDR10+ -> DV
HLG -> HLG
DV -> DV
So only my HDR10+ without DV files gets HDR10+ to DV conversion while being played back and all the other 3 will be played directly native.
Yes not having a didicated hdr10+ default setting was a mistake. It has been added for the next release
Hello,
Has anyone tested The Last Jedi 4k Blu-ray? I tested it today from a full BDMV rip and in the player information I get FEL reconstructed = No FEL and I believe this Blu-ray has it.
Anyone getting the same result? Is this normal?
FYI : From now on, I'll gradually add fixes and features to the next build. Once enough changes have accumulated, I'll clean up the code, optimize everything, and push a new release.
The RC3 preview is already available here https://github.com/CroqueMr/libre…0.0-RC3-Preview
Feel free to check it out and let me know if it meets your expectations, especially the CM 2.9 to 4.0 information, HDR10+ settings, stability fixes, etc.
CroqueMr Awesome work - Apologies did you see my message about the GL version and whether it's something we could add to your backlog 
?
FYI : From now on, I'll gradually add fixes and features to the next build. Once enough changes have accumulated, I'll clean up the code, optimize everything, and push a new release.
The RC3 preview is already available here https://github.com/CroqueMr/libre…0.0-RC3-Preview
Great work, CroqueMr! 👏
Thank you for releasing RC3 Preview and for all the effort you're putting into this project. It's great to see the continued improvements, especially with Dolby Vision FEL and Blu-ray menu support.
I'm looking forward to testing this release on my Intel Arc NUC and will share my feedback after trying it with different movies and Blu-ray ISOs.
I also found the updated JRE add-on in the release assets.
Thanks again for your dedication and hard work. Really appreciate it! 👍
CroqueMr Awesome work - Apologies did you see my message about the GL version and whether it's something we could add to your backlog
yes here : RE: Dolby Vision w/FEL + 3D for PC (AMD/Intel/nVidia)
Thanks for the update, sadly the HDR10+ to DV playback now just gets stuck at pending for me and never starts or fails.
2026-11-02 11:29:26.164 T:1014 info <general>: [WHITELIST] Searching the whitelist for: width: 3840, height: 2160, fps: 23.976, 3D: false
2026-11-02 11:29:26.164 T:1014 info <general>: Display resolution ADJUST : 3840x2160 @ 23.976000 Hz (32) (weight: 0.000)
2026-11-02 11:29:31.149 T:1014 warning <general>: DVBridge waiting: first_present=false last_stage=gpu-pending first_failure=none stream=24 picture=1 revision=24 policy=20 suppressed=0 truncations=0
2026-11-02 11:29:31.149 T:1014 info <general>: CB1 GUI viewport: before=0,0,3840,2160 after=0,0,3840,2160 framebuffer=1 fbo=3840x2160 window=3840x2160 dv=true hdr_conversion=false stream=24 picture=1 revision=24 policy=20 suppressed=0 truncations=0
2026-11-02 11:29:46.149 T:1014 info <general>: Skipped 2 duplicate messages..
2026-11-02 11:29:46.149 T:1014 info <general>: CB1 GUI viewport: before=0,0,3840,2160 after=0,0,3840,2160 framebuffer=1 fbo=3840x2160 window=3840x2160 dv=true hdr_conversion=false stream=24 picture=1 revision=24 policy=20 suppressed=0 truncations=0
2026-11-02 11:29:56.150 T:1014 info <general>: Skipped 1 duplicate messages..
2026-11-02 11:29:56.150 T:1014 info <general>: CB1 GUI viewport: before=0,0,3840,2160 after=0,0,3840,2160 framebuffer=1 fbo=3840x2160 window=3840x2160 dv=true hdr_conversion=false stream=24 picture=1 revision=24 policy=20 suppressed=0 truncations=0
2026-11-02 11:30:01.149 T:1014 warning <general>: DVBridge waiting: first_present=false last_stage=gpu-pending first_failure=none stream=24 picture=1 revision=24 policy=20 suppressed=0 truncations=0
2026-11-02 11:30:01.151 T:1014 info <general>: CB1 GUI viewport: before=0,0,3840,2160 after=0,0,3840,2160 framebuffer=1 fbo=3840x2160 window=3840x2160 dv=true hdr_conversion=false stream=24 picture=1 revision=24 policy=20 suppressed=0 truncations=0
2026-11-02 11:30:16.151 T:1014 info <general>: Skipped 2 duplicate messages..
2026-11-02 11:30:16.151 T:1014 info <general>: CB1 GUI viewport: before=0,0,3840,2160 after=0,0,3840,2160 framebuffer=1 fbo=3840x2160 window=3840x2160 dv=true hdr_conversion=false stream=24 picture=1 revision=24 policy=20 suppressed=0 truncations=0
2026-11-02 11:30:26.153 T:1014 info <general>: Skipped 1 duplicate messages..
2026-11-02 11:30:26.153 T:1014 info <general>: CB1 GUI viewport: before=0,0,3840,2160 after=0,0,3840,2160 framebuffer=1 fbo=3840x2160 window=3840x2160 dv=true hdr_conversion=false stream=24 picture=1 revision=24 policy=20 suppressed=0 truncations=0
2026-11-02 11:30:31.149 T:1711 warning <general>: DVBridge waiting: first_present=false last_stage=gpu-pending first_failure=none stream=24 picture=1 revision=24 policy=20 suppressed=0 truncations=0
2026-11-02 11:30:31.153 T:1014 info <general>: CB1 GUI viewport: before=0,0,3840,2160 after=0,0,3840,2160 framebuffer=1 fbo=3840x2160 window=3840x2160 dv=true hdr_conversion=false stream=24 picture=1 revision=24 policy=20 suppressed=0 truncations=0FYI : From now on, I'll gradually add fixes and features to the next build. Once enough changes have accumulated, I'll clean up the code, optimize everything, and push a new release.
The RC3 preview is already available here https://github.com/CroqueMr/libre…0.0-RC3-Preview
Feel free to check it out and let me know if it meets your expectations, especially the CM 2.9 to 4.0 information, HDR10+ settings, stability fixes, etc.
Changes since R1.0.0-RC2
Dolby Vision
- Added GPU bilinear FEL upscaling, replacing the nearest-neighbor fallback when VAAPI scaling is unavailable.
- Added the Reference GPU FEL filter as a selectable option for other conversion modes. Master Reference retains its reference filter.
Playback and stability
- Fixed cases where stopping playback during a resolution change could leave HDR signaling active instead of returning to SDR.
- Fixed stale HDR10 session reuse after a rejected output activation, ensuring subsequent playback prepares the required output surface.
Settings
- Separate remembered rendering preferences for Dolby Vision, HDR10 and HDR10+ inputs.
- Automatic fallback no longer replaces the preferred rendering mode.
- Fixed rendering options incorrectly remaining unavailable after stopping a different source format.
HDR10+
- Fixed source-specific preference selection during continued HDR10+ playback, preventing accidental use of the plain-HDR10 preference.
Player information
- Corrected misleading "Unused blocks" reporting: metadata forwarded to the TV is no longer marked unused.
- Displays whether CM2.9-to-CM4 conversion is actually active, including live updates for Auto and Auto 2.
Blu-ray menus
- Updated BD-J Java add-on packaging with matching libbluray 1.5.0 support files.
- Prevented stale or incomplete Java support files from being packaged. Requires the updated JRE add-on attached to this release.
Bro ABSOLUTELY WOW you are obsessed on building all the best ever features into this HATS OFF 🔥 as I said once I am back will test it on my PC & will confirm
Feel free to check it out and let me know if it meets your expectations, especially the CM 2.9 to 4.0 information, HDR10+ settings, stability fixes, etc.
I report from my NUC11TNKI3 (i3-1115G4) installation.
HDR10+ conversion setting works and it's saved. HDR10+ conversion itself does not even start playback. Tried with multiple files.
Dolby Vision seems to work fine, I have activated the CM 4.0 "Always" setting. I've yet to investigate if that's the best setting to use (but that's for another discussion). It works.
HDR10 conversion to Dolby Vision seems to work fine, although once (and only once), while seeking to the next chapter of a UHD remux it reverted back to HDR10 native, with a message saying that conversion was not available. No amount of selecting different conversions with the O menu made a difference. I had to stop playback and restart. At that point seeking went fine and I was not able to replicate.
While we'll have probably a private conversation about this, I tested my HDR10 "screen intermittently blanking" situation and I've discovered that with 12.2.1 stable HDR10 playback is rock solid. No screen blanking. With 13.0-nightly-20261101-f59641e (latest available when I downloaded), instead, HDR10 "screen intermittently blanking" happened exactly like in your builds.
Another thing that I tested and that, at this point, falls outside the scope of your builds I suppose, is the video levels situation. On my machine the Settings/System/Display video levels setting is basically broken. If I selected limited video levels (the correct setting for my OLED TV connected system, calibrated to 16-235), black levels are raised. BUT, and here's why I choose to report it here, they are not raised (they are displayed correctly) when going through a Dolby Vision conversion process. So I have Mehanik HDR10 test files and if I play them with native Kodi HDR10 playback, blacks are raised. But if I select Dolby Vision conversion for HDR10, black levels are correct.
Hi guys,
My RAM sticks have RGB (they were the only ones I could find at the time), and I hate RGB. I don't want the lights on, but turning them off usually requires software running in the background. Whenever the PC reboots, the lights turn back on during boot, then turn off in Windows once the software starts. Now, when I boot into LibreELEC without that background software, the lights stay on. Any idea how to solve this?
