I have not tested your build as this issue isn’t easily reproduced on my setup.
I also don’t know what changes you’ve made, please post a patch.
Are you talking about HDR10+ in CE 20.5 or CE 21? Because I’m using CE 20.5 and have not had issues with HDR10+ content, since it doesn’t even use the same flow as DV.
We’re trying to iterate quickly and solve some playback issues, this may create a regression in some other places.
We’ll look at the freezing part, but I think it is probably related to some buffer rework that was added. It’s being worked on.
Edit: I can’t play 4k@60fps videos in DV due to my equipment, so can’t test it myself.
In other “news”, I found my workaround above for the plugout/plugin issue wasn’t that great. Today, I think came up with a better one that seems to work well for me. Will discuss it with team later. Since PurplePlayer hasn’t posted his patch or what exactly he modified in his build, can’t say which solution is better.
I have been following this discussion with great interest.
I think I have the answer… The flux capacitor… That will get true DV working. How much power will it need??
Btw, Kodi 21 RC (in several recent betas–ever since the new Cache logic was added), also impacted my Nvidia Shield TV Pro boxes over in the Android space. For some reason they read several times slower over http vs prior versions. Basically it went from an nearly instant cache fille, to taking several seconds.
So won’t be surprised at all if the skipping with CE 21 is related to this as well.
My theory is that this always forces a refresh rate switch since there is no HDR10+ content you’re playing that is 1080p 60hz.
In the Kodi description for auto cd/cs it mentions that logic is only activated on refresh rate changes.
I prefer my GUI set at 4K x 23.976 fps to minimize refresh change delays when starting 4K content that matches (the majority of film). However I think if GUI refresh rate matches content refresh rate, the auto cd/cs logic is never called since there is no actual refresh rate change. Content immediately plays with no screen blanking.
Maybe this wildcard impacts some of the code behavior as sometimes content is 25FPS, call auto cd/cs; but if content matches refresh rate, then no auto cd/cs call. This could explain some of the inconsistent behavior testers have been seeing.
Just a shot in the dark, maybe I’m totally wrong. Theoretically should work on GUI set to 4K 60hz since that will force the auto cd/cs on refresh rate change.
I have decided on 1080p 60 in the UI setting for a couple of reasons:
It just seems at this point for these fixes I’ve tried, setting resolution, refresh rate and content type just seems to work better. But refresh rate and content type setting alone seems enough to be consistent.
Kodi UI is limited to 1080p anyways. and 60p seems a bit smoother in the UI vs 24p.
setting this to 1080p 60hz triggers my 1080p content to output in 1080p instead of 4K. I feel like my TV upscales better than the box.
is there a current testbuild for the omega branch? with the latest omega nightly I still have wrong colors when a movie is played for the first time after restart.
I do not have this problem on omega nightlies. Can you set your UI to 2160p and 23.987 frame rate and try playing back content again? Verify cd / cs is set to auto.
Has anyone else had problems using a microSD card with these? I used a new SanDisk 128GB card and although it imaged fine, the AM6B+ wasn’t able to write files to it under CoreELEC. I’m having no issues with a 64GB USB drive but I’d prefer to use microSD.