www.makemkv.com

So not giving out the correct VID is a "feature"?

I can (and I do) dynamically load both and use both at the same time (in sequence, one after the other, not both at the same same time ;) ) is just a case of using dlopen/dlsym, although i tried using libmmbd exclusively and the same issue arises, hence why I'm certain libmmbd's implementation is in...

The result from libmmbd's aacs_get_vid looks like dirty memory. Library might be returning some stale memory instead of the correct value pointer (or a null pointer / null key if not valid). 95 f5 54 0e 78 1b 42 44 cf fc 3e cd a5 21 5c c9 |..T.x.BD..>..!\.| 95 55 c2 35 35 18 42 44 0b 0a 23 cc f9 65 ...

I am making a project using both libaacs and libmmbd. Ever since a MKBv82 disc failed to decrypt and noticing that a combination of the MKB tarball, libaacs (via aacs_info) and then makemkv could solve the issue together, I wanted to integrate the two together to make the process more streamlined us...

I used aacs_info (from libaacs utils) alongside the latest device keys to get the disk VUK, added it to the KEYDB.cfg, and then MakeMKV had no trouble decrypting the BD.

I tried to decrypt the same disk, and the same error happens.

So far this has been the first time a disk I bough failed to decrypt.