Automatic SDF/HK downloading is disabled or failed messages
Posted: Mon Jul 05, 2021 11:50 am
This has been raised a few times in the past that makemkv reports:
Note: I have downloaded https://www.makemkv.com/svq/sdf.bin into the .MakeMKV directory and restarted to no avail.
I've done some debugging of the request flow and I see makemkv performing 3 requests to hkdata.fairuse.org:443
What I believe is happening is that when disk is being decoded by makemkv and the key isn't know it requests an update.
As it knows the keys it already has from _private_data.tar it requests then next file in sequence, which in my case is hkd_00000188.bin.gz which doesn't exist.
It's not clear if this is because
Hope Mike can confirm either way so others don't get confused by this message.
Code: Select all
Downloading latest HK to C:\Users\steveh/.MakeMKV ...
Automatic HK downloading is disabled or failed.
Saved AACS dump file as C:\Users\<user>/.MakeMKV/<disk specific file>.tgz
The volume key is unknown for this disc - video can't be decrypted
I've done some debugging of the request flow and I see makemkv performing 3 requests to hkdata.fairuse.org:443
Code: Select all
GET /b.txt.gz?c=<REDACTED: possible unique disk identifier?> HTTP/1.1 = 200
GET /svq/hkd.dat.gz?c=2-MakeMKV_v1.16.3_win(x64-release) HTTP/1.1 = 200
GET /svq/hkd_00000188.bin.gz HTTP/1.1 = 404
As it knows the keys it already has from _private_data.tar it requests then next file in sequence, which in my case is hkd_00000188.bin.gz which doesn't exist.
It's not clear if this is because
- It hasn't been created yet - speculative download?
- It should exist and is really missing - hence the 404?
Hope Mike can confirm either way so others don't get confused by this message.