Yes, as Graham noted I think there’s too much to chase down here. It’ll be interesting to see whether there are further reports down the road, but for now I’m not sure whether it’s worth pursuing, especially given the use case in question here.
Let me know if I can help further, though.
In the particular case of JCs Vampires the problem was that the EL (RPU) layer was out of sync with the base layer, and that also seems to cause the seeking problem because with the new source is now gone.
You’ve told me in PM that for other titles with problems you’ve obtained other versions that worked OK. It does seem profile 7s can be prone to poor ripping. It would be useful with these rips to know if other devices play them OK before we investigate further.
I can provide problematic files but I don’t own any other device that can play FEL (like Ugoos AM6B+). It’s important to note that problems happens when seeking or jumping to specific chapters. I’ve tested 10 files so far, but I’ve much much more. Will see.
I have an AM6B+ and a V.
Link the problematic files and I’ll test them.
this thread has been quieter than I expected. Watched the first Transformers film on an LG C5 this evening and it was epic. Thanks for giving us future proof FEL support.
I’ve been waiting for all the bugs to be shakenout. I like to try the beta
Can I compile OSMC with Kodi v22 (Piers)+FEL for Vero V from source?
Same, it’s been quiet indeed, but like you said … it works very nice!
Is there any good way yet within osmc to tell what DV profile I’m viewing?
Team Kodi does not support AMlogic so the source is not available from them and we haven’t yet worked up v22 for Vero V.
Kodi v22 has added info labels to give you that information. We’re looking at backporting that to v21.3 but it would need a hack to the database which may break shared DB (MySQL) setups.
Profile 5 thumbnails are displayed with the green/magenta colours so you can use that for files which haven’t been scraped for cover art.
Does that show if a file is FEL though?
It would be nice if during playback, you can hit info (or other button) to bring up advanced video information that tells us the file is MEL or FEL.
Yes. That’s how it will work on v22. Profile, FEL/MEL and HDR10+. The patch didn’t make it into alpha 3 but will be in the first beta of v22.
And what about now in current build? Something like playerprocessinfo that can show it during playback?
Also curious how v22 can know if a file is MEL or FEL. Doesn’t it need to open/scan the file to verify this, just like you need to now to verify it externally with dovi tools?
I understand you’ve tested a few titles and are finding similar problems with the AM6B+. So the working theory is that these rips date from early versions of MakeMKV which didn’t get profile 7 quite right. If so, that’s a relief - one less headache for @tanio99.
Thanks for looking into it, you and @doctorsirius.
As I said, we’re looking into backporting it.
Yes, it does. But only once to store the info in the database. When you play a file, it’s open anyway. The idea is to show what’s actually being played (eg if there’s no DV support, a P7/8 file would show ‘HDR10’ or ‘HDR10+’. Just like with the audio tracks. That part of player process info is being worked on still.
Cool thanks! Kind of like plextuary does.
I also wanted to let you guys know I had those washed out colors (whole screen was greyish) with the Marty Supreme movie (Cineph… version) when movie started. After a small seek it looked normal.
I am using PM4K.
Can’t do anything with that without logs.
To be fair, seems to be more a problem with my old workflow mixing MakeMKV + MKVToolnix (when it still didn’t support profile 7 remuxing), so it’s not MakeMKV fault, neither MKVToolnix, just my workflow. Thanks to everyone involved in testing and make FEL possible in Vero V. Solid path to public final release I think!