Posts by Creator44

    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.

    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.

    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!

    Do you use IPT or YCbCr Output for master reference, did you see a regression in term of performance? with master reference in beta5 vs RC2? IPT is far more stressful for your iGPU than YCbCr

    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?

    CroqueMr, had started doing my full suite of test clips for YT video, but stopped as I've found two issues already (using AMD 5800H):

    Debug log here.

    CroqueMr I cannot play any of the first 5 Transformers movies. It just returns to the GUI without playing anything.

    I get this:
    error <general>: Dolby Vision playback unavailable: stream=325 source_revision=325 profile=7 reason=4

    I attach the log.

    The more recent Transformers movies and Bumblebee works fine.

    Pretty sure all Transformers movies are FEL.

    P.S. I tried countless other DV movies and everything plays fine, I don't know what these files have that the others do not. They play ok on the am6b+.

    CroqueMr , I assume you already saw this, but here's a picture of the player process infos and there are words that are cutted with the "..." following it because of not enough space to show it all.

    Do you think you can fix this by shortening the names or changing the column length?

    Also, I tested the DV DT file again and this time I can see the text "yous hould not see this text except on TV apps" but there's also a kodi gui interface on top with the name of the file and the 5 star to rate i think? It is better than before because before I could not see the image correctly at all. Am I suppose to see "This device can decode FEL" like with the other two test files that works?

    Kernel. You could do it on a VM with GPU pass through, but not native in Windows. Software / LLDV would work though.

    So tv-led would not work in a vm? These builds running in windows would make a secondary pc just for libreelec useless for windows users but I think there would still be fragrant issues like framerate switching etc which is shaky in Windows so... Libreelec brought a lot of stability for media playback for x86

    CroqueMr , I tested RC1.1 and I am happy to report the freeze when PGS subtitles are on the screen at the same time as any GUI in DV movies is gone! All seems fine now!

    My guess is that fixed it?:

    Fixed mixed PGS subtitles and SDR GUI composition in Master Reference.

    In any case, I want to thank CroqueMr and hadesdevls for their work on this it's really exciting! I didn't test HADES yet because no time but I will check it out too!

    Congrats to CroqueMr to making the most accurate DV of any player according to DMDreview ! This is great to see and makes it so my am6b+ will not be used anymore probably but I'll keep it as an option!

    Open source is so great, especially lately with AI's help it's so refreshing compared to big corpos who makes half-assed products just to make money. The passion in open source projects will always make more refine products in the end because the makers actually care about the end result product.

    between release A LOT of things changed maybe the fix behind L5 is an issue but I don't think so I need to investigate. I think you already sent me a log when your screen is frozen, if it's not the case yes please send me a log and the best is to use the Beta 5 Debug for your log :)

    I did not send any logs no so here is one with a lot of freezing and talking in a scene. Beta5-Debug log.

    Welcome to my world, AMD and Intel are very different, an optimizarion for intel can be a regression for AMD. And in each brand you have a lot of different GPU with their own issue.

    CroqueMr , if it can help find the issue, I went back from beta5 to beta4 and the freeze when PGS subtitles + any GUI is on the screen at the same time4 was still there. Then I went back to Beta3 before the L5 fix with the cutted out GUI and the freeze is not there anymore. Maybe it has something to do with L5? Do you want a log of when it freezes?

    Hi CroqueMr , I tested Beta5 and the DV DT file does not play correctly still, it seems to just display nothing or some vague wavy stuff, I think I was seeing my purple kodi theme in the back or something, like see-though? Not a big deal as nothing is in DT in MKV.

    I found a bad bug for me, if I put PGS subtitles ON, if any GUI is on, may it be the standard kodi gui, or my plexmod gui, etc. everytime there is a subtitle on screen, the video freezes and then plays correct when the subtitle disappears.

    It seems to be fine with SRT subtitles though and there is no freeze on those, only on PGS.

    Can you reproduce that and find a fix please?

    Thanks to you and hadesdevls for your work!

    Since there are discussions about picture quality differences and you guys seems to know a lot about this I will ask the question I am still wondering about today: is there a picture quality difference between VAAPI and ffmpeg software decoding of the codecs (HEVC, H264, etc)?

    I had both yes and no told to me but in my testing I think software looks better but it's close so it's hard to say. Also, the logic that says that the softwatre ffmpeg decoders are probably constantly fine tuned whereas the hardware decoders from vaapi are static in the gpu leans towards software probably got better with time?

    So what's the truth on this?

    I know that VAAPI with the DV builds look super nice to me and I am unsure I see a difference compared to software but I can't test software for DV because DV doesn't work in software. I mainly compared HDR10 or SDR.

    I also know back in the older days software decoding was always better picture quality but it's not that easy to see anymore. For encoding I see the differences easily and still use cpu software encoding.

    Yes I am a purist so I hope DV Master Reference will stay in the builds especially since my mini pc is powerful and only uses about 50% of the rendering engine in master reference.

    Last note, I compared the DV picture between my AM6B+ and my mini PC and I think the AM6B+ is a little brighter than the mini pc with CroqueMR's build but I don't know which is right? When I say brighter I mean in all the picture, like more elevated but it's very minor or I imagine it maybe since I need to switch between two inputs to try and compare and there's 2-3 seconds of switch delay. I also think the Highlights are higher on CroqueMR's build which makes everything more popping, again slightly.

    If there is a difference, can it be due to the HDMI Full versus Limited setting that you need to put to limited by force in that LibreElec build?

    Also, why do we need to put that setting forced to limited so that everything is not overdark? I never had to do that on other LibreElec or CoreElec builds?

    MKVs yes, I saw a lot of issues with VAAPI and FEL thanks to this issue report : https://github.com/CroqueMr/libreelec-x86-DV/issues/29 , I think I already fixed it in my internal build, I need to clean my code before pushing an update of the debug version.

    The issue is wider than MKV, it impacts also MP4, M2TS, everything has been fixed.

    According to the issue report, the person cannot playback DT DV. I have the DT test file of "This Device Can Play DV" but for the DT test file specifically, it only displays black screen on my AM6B+ on CoreElec NG AND on your builds same thing. I thought this was normal and unsupported by ffmpeg or something. If you fixed that too that's pretty neat.

    The explanation is indeed complex. o.O;

    All my files are MKVs. If you want the complete MediaInfo I can send it.

    Could you please try the beta4 debug version and send me back the log even if it fixed your issue?

    https://github.com/CroqueMr/libreelec-x86-DV/releases

    Hi CroqueMr , the DV freeze is FIXED! :) Thank you!

    Here is the log requested with the bunch of "CB1 debug" lines added it seems? I played back the video for 3 minutes.

    What was the problem exactly I am curious? You can be technical I am a programmer.

    Thanks!

    P.S. I tried resuming the file at 3 minutes just to test a resume and it froze after playing for 1 second but with the image freezed instead of black. It seems that's it's the audio renderer that didn't work though so not sure it's from your code or not? I attach the log for that too just in case and the line with the error is line 234. There's a Stalled=true on line 512 from your debug info.

    I tried reproducing the freeze and it does not happen every time but it happened a second time now, I attach that log too, (2ndFreeze). Also, when the video plays correctly, I can scan in the file backwards and forward and all is working fine.