In the re-release of RC2 PGS subtitles work correctly again, thank you.
I have a request regarding them. This is already in a test build of avdvplus R11:
Would it be possible to allow PGS subtitles to be moved up and down on-the-fly when manual positioning is enabled? This already works for text-based subtitles while watching a video by binding remote keys to the "subtitleshiftdown" and "subtitleshiftup" actions.
Quick question: Does the YCbCr vs IPT only change the format sent to the TV and not the PQ? Is the PQ completely identical? DMDReviews seemed to say the standard way is to sent IPT so I switched it to that but not sure if it changes anything in the end?
The selector YCbCr / IPT is only available for Master Reference output, Standard output (now called Reference) use YCbCr
To be simple, if you select (except for Profile 5 that is always send in IPT because the file is in IPT) :
- IPT as prefered output, in master reference the conversion YCbCr -> IPT will be performed by your PC,
- YCbCr as prefered output, in master reference the conversion YCbCr -> IPT will be performed by your TV
Using YCbCr means one less conversion step on the PC side, shifting that task to the TV instead, which helps small iGPUs. Your TV should handle the conversion perfectly, so you shouldn't notice any difference, however, if your PC is capable enough, you can opt for IPT, which ensures the conversion is performed with high precision right on your PC.
In the re-release of RC2 PGS subtitles work correctly again, thank you.
I have a request regarding them. This is already in a test build of avdvplus R11:
Would it be possible to allow PGS subtitles to be moved up and down on-the-fly when manual positioning is enabled? This already works for text-based subtitles while watching a video by binding remote keys to the "subtitleshiftdown" and "subtitleshiftup" actions.
I can check that
This is so good that i stopped using my Shield 2019 Pro, Google TV Streamer and my Xiaomi TV Box S 3rd gen with CE.
ok so now both forks are getting stuck, Hades installs itself and after the reboot the same window with the LibreELEC version gets stuck.
The only thing that changed(since the last time I successfully started Hades with zero problems), is that I installed the newest hotfix NVIDIA drivers and I removed the overclock on my GPU.(so one Windows thing and something that should increase stability, not create more problems...)
Could it be the driver update that causes these problems?
The only .log that was created with Hades fork is the "fs-resize.log", I'm gonna assume that's just for the install start and not the real first run?
2026-11-01T20:41:49+00:00
/dev/sdb2 /storage ext4 rw,noatime 0 0
DISK: /dev/sdb PART: /dev/sdb2 NUMBER: 2 LABEL: STORAGE UUID: 2d559a3b-5820-4f3b-b44a-5c05bd0cd045
*** parted -s -f -m /dev/sdb resizepart 2 100% >>/flash/fs-resize.log 2>&1
*** mke2fs -F -q -t ext4 -m 0 -L "STORAGE" -U "2d559a3b-5820-4f3b-b44a-5c05bd0cd045" /dev/sdb2 >>/flash/fs-resize.log 2>&1
*** e2fsck -f -p /dev/sdb2 >>/flash/fs-resize.log 2>&1
STORAGE: 12/7749632 files (0.0% non-contiguous), 632924/30995537 blocks
I can check that
In case it helps with the PGS up/down request: my xbmc#29060 already moves PGS with the existing subtitleshiftup and subtitleshiftdown actions (measured on my RX 7600).
ok so now both forks are getting stuck, Hades installs itself and after the reboot the same window with the LibreELEC version gets stuck.
The only thing that changed(since the last time I successfully started Hades with zero problems), is that I installed the newest hotfix NVIDIA drivers and I removed the overclock on my GPU.(so one Windows thing and something that should increase stability, not create more problems...)
Could it be the driver update that causes these problems?
The only .log that was created with Hades fork is the "fs-resize.log", I'm gonna assume that's just for the install start and not the real first run?
No it's not linked, I used some code from Hades in the RC2, this is why we have the same behaviour, I will check with my 5090 this week what is happening, it will be fixed for RC3.
Display MoreThe selector YCbCr / IPT is only available for Master Reference output, Standard output (now called Reference) use YCbCr
To be simple, if you select (except for Profile 5 that is always send in IPT because the file is in IPT) :
- IPT as prefered output, in master reference the conversion YCbCr -> IPT will be performed by your PC,
- YCbCr as prefered output, in master reference the conversion YCbCr -> IPT will be performed by your TV
Using YCbCr means one less conversion step on the PC side, shifting that task to the TV instead, which helps small iGPUs. Your TV should handle the conversion perfectly, so you shouldn't notice any difference, however, if your PC is capable enough, you can opt for IPT, which ensures the conversion is performed with high precision right on your PC.
I can check that
Thank you for the explanation, I will go with IPT as my mini pc is sleeping at 25% usage on the render engine.
I tested all 5 transformers movies that didn't work before and they all work perfectly now, thanks!
I tested the PGS subtitles brightness and it's working and this is gonna be a lifesaver I find the full white subs too agressive for the eyes. I am surprised that 5% is still quite bright in the sense that I expected to almost not see them but that's not a problem they are still quite dark. I'll probably use 50% or something.
I checked the player process infos and the dots (...) are gone so thank you! I also appreciate others asking for something I wanted, seeing the channels count instead of RAW, RAW, RAW which is useless. I think the only thing that is missing is the fact that we don't see if the CMv2.9 to CMv4.0 is happening or not in the player process infos but that was already asked.
Tested HDR10+ to DV with a HDR10+ only file, seems to work fine I get a scrolling "AI estimates; authored curve not translated text on player process info."
I saw a tool mkvdovi can translate the HDR10+ to DV 8.1, I wonder if that would be better or not since it analyzes the picture completely, maybe that authored curve thing that your conversion skips? Maybe it can be added later? In any case it looks good already. Thanks!
Display MoreThank you for the explanation, I will go with IPT as my mini pc is sleeping at 25% usage on the render engine.
I tested all 5 transformers movies that didn't work before and they all work perfectly now, thanks!
I tested the PGS subtitles brightness and it's working and this is gonna be a lifesaver I find the full white subs too agressive for the eyes. I am surprised that 5% is still quite bright in the sense that I expected to almost not see them but that's not a problem they are still quite dark. I'll probably use 50% or something.
I checked the player process infos and the dots (...) are gone so thank you! I also appreciate others asking for something I wanted, seeing the channels count instead of RAW, RAW, RAW which is useless. I think the only thing that is missing is the fact that we don't see if the CMv2.9 to CMv4.0 is happening or not in the player process infos but that was already asked.
Tested HDR10+ to DV with a HDR10+ only file, seems to work fine I get a scrolling "AI estimates; authored curve not translated text on player process info."
I saw a tool mkvdovi can translate the HDR10+ to DV 8.1, I wonder if that would be better or not since it analyzes the picture completely, maybe that authored curve thing that your conversion skips? Maybe it can be added later? In any case it looks good already. Thanks!
Glad you're happy with the addition.
For HDR10+ conversion to DV, this is a first approach, I need to refine my algorithm, It doesn't meet my standard, we lose some informations (It’s normal, we’ll always lose some, but I’m sure we can do better). I think, I will train a dedicated AI, like I did for HDR to DV conversion and add the model in the build.
I will work on HDR10+ deeply next week.
And also a complet rebuild of the player info panel is planned, this was just some small adjustment
Found a little bug but it's related to using plex4kodi like I do, when I start my HDR10+ video from the beginning and ask for hdr10+ to dv the video does not start. If I resume it works and if I play from beginning or resume directly in kodi it works.
Also, when the credits started because I let the movie play while doing something in the background, at some point I got a message that HDR10+ not available or something and it went back to standard HDR10.
Finally, in the player process infos, when you ask for hdr10+ to dv, even on HDR10 normal I get messages that says it could not do DV Reference AI. The playback seemed ok in normal HDR10.
Found a little bug but it's related to using plex4kodi like I do, when I start my HDR10+ video from the beginning and ask for hdr10+ to dv the video does not start. If I resume it works and if I play from beginning or resume directly in kodi it works.
Also, when the credits started because I let the movie play while doing something in the background, at some point I got a message that HDR10+ not available or something and it went back to standard HDR10.
Finally, in the player process infos, when you ask for hdr10+ to dv, even on HDR10 normal I get messages that says it could not do DV Reference AI. The playback seemed ok in normal HDR10.
Can you send me the log with all your issues inside? I will check what I can do.
*Parachutes in from AVSforum*
Ahoy there! Joined and, after reading more about the advantages of the advancements in this thread over my AM9 Pro's existing DV7 FEL support, hoping to learn enough to get this up and running on a mini PC soon. Aiming for the BOSGAME P3 Pro so I'm not bottlenecked by anything. Thanks to everyone who has contributed to making this happen.
Now to actually read through the entire thread instead of asking AI models ...
Display MoreFirst off, thanks for RC2. It's on my 780M box now and it's looking really good.
I wanted to ask whether you'd consider supporting the OpenGL build of LibreELEC (the Generic.OpenGL device, with Kodi built for GL) as well as GLES.At the moment Dolby Vision only works on the GLES image, so I have to choose between DV for films and the GL image for games. A lot of my time goes into Kodi's game player (RetroPlayer), and some cores and shader presets only work, or only work fully, on desktop GL. It would help beyond LibreELEC too. Most desktop Linux builds of Kodi (distro packages, the flatpak) use GL rather than GLES, so a GL path is what would let your work reach those users, and anything aimed at Kodi itself would need it as well.
What I think it would take, from going through the RC2 patches: most of the Kodi side isn't tied to GLES, but about 6.5k of the ~23k lines sit in GLES-only classes that a GL build never compiles:
DVBridgeGLES (~2.9k lines)
WinSystemGbmGLESContext (~2.7k)
RendererVAAPIGLES, LinuxRendererGLES and OverlayRendererGLES, plus small bits in RendererDRMPRIMEGLES and the GLES screenshot and filter shader code
A GL build uses WinSystemGbmGLContext, RendererVAAPIGL, LinuxRendererGL and OverlayRendererGL instead. The way I'd approach it:
Move the DV/HDR output and DRM handling out of WinSystemGbmGLESContext into WinSystemGbm, or a helper both contexts share.
Make the DVBridge renderer API-neutral. libplacebo's OpenGL backend takes either a GL or a GLES context, so it should mostly come down to small GL and GLES shims for the EGL image import and the shader headers.
Mirror the VAAPI, LinuxRenderer and overlay hooks in their GL counterparts.
Add a Generic.OpenGL build so the GL side doesn't drift.
I'm happy to help with the Kodi side and to test GL builds on the 780M and know some others who would too.
Cheers,
I need to check, maybe it will be a fork not supported once the stable release is finished
Hrrmmm... 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... 
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.
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.
