![]() "VOLUME_ID" as an additional MeaninglessVolumeName in the config maybe you oversaw this suggestion, so I posted it again. Thank you very much for this update! dumping Unit Keys works now perfectly with BEE drives. Just released 1.08 - fixes the Problem with CloseOnExit, decrypts the UnitKeys earlier so they are written to keydb.cfg even in case the VUK cannot be validated. Thanks for your explanation, thats a nice goal :) #Leawo blu ray player trojans update#We just need to find a decent C programmer to update Videolan's libbdplus to load these tables The ultimate goal will be real-time playback of BD+ protected titles using VLC. So later we can make a database of BD+ tables, similar to keydb.cfg for keys. PS: any discs you own with BD+, please load them in Pavtube at least once This is similar to what MakeMKV shows in it's UI (YEAR.MONTH) for BD+.Īnd as far as bugs, CloseAtTheEnd still doesn't work It's better to simply look at the date of the DiscID file, which is already being extrated by FindVUK. I think DVDFab kept adding a nr whenever they had to update their BDplus code. In Videolan's libbdplus code, you can see the initial version numbers were simply based on supposed release dates when some new BD+ behaviour first appeared. As far as I can tell, there is isn't such thing as an official "BD+ generation" or version number. I don't think the BD+ generation should be added. Passkey reports the following: "BD+ protection (Irdeto) is removed. FindVUK 1.07 detected a disc with a BD+ generation of 254. "VOLUME_ID" as an additional MeaninglessVolumeName in the config file BD+ with its generation number in the KEYDB comment section (like "BD+v1") ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |