FindVUK tool - get VUK of all Blurays supported by DVDfab applications [Archive] - Page 20

Bandits

27th April 2025, 19:54

UPDATE.
It's obvious now that this is an Xreveal problem, not a FindVUK problem.

Thank you, MrPenguin.
Thank you, Toad King.

I'm history!

I recommend only having one keydb.cfg file on your system. Place it is the most common spot:
C:\Users\%username%\AppData\Roaming\aacs"
Then hardset any program that lets you set its location. ie.. Xreveal

I had the same issue when first using Xreveal. Once I hardset the keydb.cfg in Xreveal everything was fine.

markfilipak

27th April 2025, 20:31

I recommend only having one keydb.cfg file on your system...
Indeed. Good practice.
C:\Users\%username%\AppData\Roaming\aacs
Done.
Then hardset any program that lets you set its location. ie.. Xreveal
That's 'Settings', 'BD & UHD', 'KeyDB'.
Done.

Am I just being an old fogey? I swear I read "%PROGRAMDATA%\aacs" somewhere.

Oh, well. I'm taking your advice. Thanks!

Bandits

27th April 2025, 22:54

Indeed. Good practice.

Done.

That's 'Settings', 'BD & UHD', 'KeyDB'.
Done.

Am I just being an old foggy? I swear I read "%PROGRAMDATA%\aacs" somewhere.

Oh, well. I'm taking your advice. Thanks!

I think that Xreveal's Pro My Database default location.

Xreveal will prefer to use the keydb.db for decryption: keydb.db > keydb.cfg > AACS Auth > cloud decryption.

The default location for the keydb.cfg file in Xreveal is within the `%APPDATA%\\aacs\` folder. You can change this location in Xreveal's settings under BD & UHD > KeyDB. If you're using the Pro version, the "My Discs" database, which includes processed disc information, is stored by default in C:\\ProgramData\\Xreveal\\keydb.db.

https://xreveal.com/news?id=71

markfilipak

28th April 2025, 00:25

... Xreveal will prefer to use the keydb.db ...
keydb.db? An SQLite database? That doesn't look to have anything relevant to FindVUK.
... for decryption: keydb.db > keydb.cfg > AACS Auth > cloud decryption.
I have no idea what that chain means. Is there an English translation? :o

I know you're making a point of something, but I don't get it.

PS: This is from "How to use Xreveal":
The default KEYDB.cfg location is %APPDATA%\aacs\, you can change it in Xreveal's Settings > BD & UHD > KeyDB.
I must be an old fogey. ...Ha, ha, ha.
Pro version do not need KEYDB.cfg. Some discs may require an internet connection to search keys.
That's why I didn't buy the pro version. My Windows has no Internet connection. I must use keydb.cfg.

Toad King

29th April 2025, 23:13

I'm having an issue submitting one of my new discs. I can calculate the VUK/keys correctly but every time I try to submit it I get this error:

17:09:37 - ERROR! Couldn't post the BlurayMetaXML to the OnlineDB! (http://fvonline-db.bplaced.net/fv_upload.php) >ERROR! Received a HTTP Status >503<< (503)

Other discs seem to work fine so it looks like something with just this one.

EDIT: Tried again and it works now.

coricopat

30th April 2025, 00:32

Recently had the same (repeatedly)... but trying again the next day it worked.

Karpfly

18th May 2025, 14:27

Hello, i have Dune Prophercy season 1 3x UHD HDR discs, FindVUK shows me this error
21:34:04 - DiscID >53402418D481FAC1787BBC40E4E5359B22270842<
21:34:04 - UnitKeyCount >1<
21:34:04 - >>> UnitKeyDEC (1) >86D2D3745C6E3E49EFFCBEF9159A6573<
21:34:04 - BusDecryption is required - try to get ReadDataKey from dump
............................-......-
21:34:06 - >>> ReadDataKey from dump >452473385195A14B68A891934F71514F<
-------------------------------------------------------------------------------
21:34:06 - BusEncryption enabled => either ReadDataKey or disabling of BusEncryption required
-------------------------------------------------------------------------------
21:34:06 - ReadDataKey >452473385195A14B68A891934F71514F<
-------------------------------------------------------------------------------
21:34:06 - --- PART 2 --- VALIDATE VUK/UNITKEYS ---
-------------------------------------------------------------------------------
21:34:07 - Drive is detected as 'REAL BLURAY' drive
21:34:07 - M2TS files found >27<
21:34:07 - Potentially invalid UnitKey >86D2D3745C6E3E49EFFCBEF9159A6573<
21:34:07 - Unfortunately no candidate to get a correct unit key >86D2D3745C6E3E49EFFCBEF9159A6573<
21:34:07 - There are still 27 files that cannot be decoded with the provided unit keys!
21:34:07 - Validation failed - VUK/UnitKeys are INVALID!!!!!!!
21:34:07 - Please report this in the Doom9 forum and attach the logfile!

How to proceed from now?
I have added log from running all 3 Blueray disc.
I can upload dump files, or if you can give me direction i will try extract keys myself :)

My drive info from MakeMKV:
Drive Information
OS device name: F:
Current profile: BD-ROM
Manufacturer: HL-DT-ST
Product: BD-RE BP60NB10
Revision: 1.02
Serial number: SIKBDI8U41239
Firmware date: 2120-05-07 09:35
Bus encryption flags: 17
Highest AACS version: 77

LibreDrive Information
Status: Enabled
Drive platform: MT1959
Firmware type: Patched (microcode access re-enabled)
Firmware version: 1.02
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

Disc Information
Label: DUNE_PROPHECY_SEASON_1_DISC_1
Timestamp: 2025-03-26 10:26:47
Protection: AACS2.0/C v77
Data capacity: 75.37 Gb
Disc type: BD-ROM UHD
Number of layers: 3
Bus encryption flags: 80

coricopat

18th May 2025, 16:40

Sometimes it helps me by just running it again (restarting DVDFab, re-inserting the medium). But the keys for the DiscID you report seem to be anyway already part of the well known KEYDB.cfg ...

MrPenguin

18th May 2025, 17:19

Hello, i have Dune Prophercy season 1 3x UHD HDR discs, FindVUK shows me this error
21:34:04 - DiscID >53402418D481FAC1787BBC40E4E5359B22270842<
21:34:04 - UnitKeyCount >1<
21:34:04 - >>> UnitKeyDEC (1) >86D2D3745C6E3E49EFFCBEF9159A6573<
21:34:04 - BusDecryption is required - try to get ReadDataKey from dump
............................-......-
21:34:06 - >>> ReadDataKey from dump >452473385195A14B68A891934F71514F<
-------------------------------------------------------------------------------
21:34:06 - BusEncryption enabled => either ReadDataKey or disabling of BusEncryption required
-------------------------------------------------------------------------------
21:34:06 - ReadDataKey >452473385195A14B68A891934F71514F<
-------------------------------------------------------------------------------
21:34:06 - --- PART 2 --- VALIDATE VUK/UNITKEYS ---
-------------------------------------------------------------------------------
21:34:07 - Drive is detected as 'REAL BLURAY' drive
21:34:07 - M2TS files found >27<
21:34:07 - Potentially invalid UnitKey >86D2D3745C6E3E49EFFCBEF9159A6573<
21:34:07 - Unfortunately no candidate to get a correct unit key >86D2D3745C6E3E49EFFCBEF9159A6573<
21:34:07 - There are still 27 files that cannot be decoded with the provided unit keys!
21:34:07 - Validation failed - VUK/UnitKeys are INVALID!!!!!!!
21:34:07 - Please report this in the Doom9 forum and attach the logfile!

How to proceed from now?
i have two thoughts:

Where did you get that RDK from? Are you sure it is correct?
MakeMKV kills Bus Encryption until the disk is ejected. And once bus encryption is disabled, trying to decrypt the disk using the RDK will actually scramble the data instead.

If you're sure you have the correct RDK then trying ejecting and reinserting your UHD. Make sure you don't execute MakeMKV again before validating with FindVUK.

Karpfly

18th May 2025, 18:07

Where did you get that RDK from? Are you sure it is correct?

You mean ReadDataKey? FindVUK give it when i run it, so it "should" be correct, right?

MakeMKV kills Bus Encryption until the disk is ejected. And once bus encryption is disabled, trying to decrypt the disk using the RDK will actually scramble the data instead.
I have rebooted and tried few times without running MakeMKV, i make sure it's not started, should i uninstall it completely?
I have updated today keydb.cfg and paste in %appdata% and VUKbackup folder.
I can see that in my previous post log in attachment is pending validation, so here is new log from run just few minutes ago.
https://pastebin.com/MurvPpTa

Edit: i have uninstalled MakeMKV but still same result
keydb.cfg size: 57,792,364 bytes SHA256: CD57F75A81D6F9D952DDEA6DFE58E6D9F97937F48BC7C8E43DAF248A7BA4C293

MrPenguin

18th May 2025, 19:12

You mean ReadDataKey? FindVUK give it when i run it, so it "should" be correct, right?

Yes, RDK is "Read Data Key". And yes, I would expect FindVUK to extract the correct RDK from the dump.

I have rebooted and tried few times without running MakeMKV, i make sure it's not started, should i uninstall it completely?
No, you don't need to uninstall MakeMKV. Just ensure that you don't execute it when you insert your UHD disk into your drive. Once MakeMKV has activated LibreDrive, the drive is no longer bus-encrypted and so you don't need to decrypt it using the RDK.

Does your FindVUK.ini file have a
Disable_Bus_Encryption_Cmd = ...
entry? This can be another way of executing MakeMKV...

Karpfly

18th May 2025, 19:31

I have this in FindVUK.ini file:
[ExternalTools]
; Disable_Bus_Encryption_Cmd: command line for a tool which is able to disable bus encryption of the disc in the drive
; Supports the following placeholders: $DRIVE$=driveletter (e.g. d)
; Errorlevel=0 is taken as successful result, everything else as error
; Create_RDK_Cache_Entry_Cmd: command line for a tool which is able to determine the ReadDataKey of drive+disc and write it into RDK cache.
; The RDK cache path is: ?FOLDERID_RoamingAppData?\aacs\rdk\<DRIVEID>\<DISCID>
; Supports the following placeholders: $DRIVE$=driveletter (e.g. d), $DRIVEID$, $DISCID$, $FULLRDKPATH$
; Errorlevel=0 is taken as successful result, everything else as error
Create_RDK_Cache_Entry_Cmd =
Disable_Bus_Encryption_Cmd =

MrPenguin

18th May 2025, 22:19

Edit: i have uninstalled MakeMKV but still same result
keydb.cfg size: 57,792,364 bytes SHA256: CD57F75A81D6F9D952DDEA6DFE58E6D9F97937F48BC7C8E43DAF248A7BA4C293
AFAICT, the entry in KEYDB.cfg for your disk is correct, including its Unit Key.

Did your drive support UHD disks "out of the box", or did you need to cross-flash it first?

Karpfly

19th May 2025, 20:27

AFAICT, the entry in KEYDB.cfg for your disk is correct, including its Unit Key.

Did your drive support UHD disks "out of the box", or did you need to cross-flash it first?

I have flashed some firmware, libre drive? I didn't read at all blueray discs, I don't remeber now what excatly firmware i have flashed

MrPenguin

22nd May 2025, 11:46

I have flashed some firmware, libre drive? I didn't read at all blueray discs, I don't remeber now what excatly firmware i have flashed
Since the Unit Key for your disk is correct, the only reason I can think of for validation failing would be bus encryption. So either your RDK is incorrect, or bus encryption has been disabled on your drive somehow.

Can you use MakeMKV to create an encrypted back-up of your disk, and then play that back-up using VLC?

Or maybe delete this disk's RDK from your cache, set
Disable_Bus_Encryption_Cmd = hostname.exe
in your FindVUK.ini file, and then try validating the disk again?

Manni

5th June 2025, 17:09

Hi everyone,

I am getting the following error from an Asus drive when trying to validate a key from an original 4K UHD Bluray disc (it doesn't matter which one, I get that error for all disc titles):

Failed to init disc >AACS UNKNOWN ERROR >-1501

The drive can be used for ripping as long as the keys are known. Any idea?

Here is the drive info:
Drive Information
OS device name: F:
Current profile: BD-ROM
Manufacturer: ASUS
Product: BW-16D1HT
Revision: 3.10
Serial number: xxxxx
Firmware date: 2119-01-04 10:14
Bus encryption flags: 1F
Highest AACS version: 77

LibreDrive Information
Status: Enabled
Drive platform: MT1959
Firmware type: Patched (microcode access re-enabled)
Firmware version: 3.10
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

coricopat

25th June 2025, 00:13

Hey.

Since a few days, the well known online DB website seems to be no longer reachable via Tor. Did anyone else notice this respectively is anyone else downloading/uploading from/to there via Tor (for security reasons)?
I wonder whether it's Tor who blocks it or the page (or rather it's hosting ISP).

It felt always much safer being able to especially doing uploads via Tor.

Thanks,
Coricopat.

coricopat

27th June 2025, 18:21

Hm I guess it's bplaced.net which may be the one who blocks (Tor). Found some other hosted pages there (via Google - not idea what they contain): https://ssodb.bplaced.net/ http://zhoufei.bplaced.net/ ... these seem to work without Tor but not with. And even if Tor would have submitted to some takedown notice or so and now specifically block the online DB page.. why would they block the others, too.

Quite a bummer.

I guess it won't be possible to use a hoster that allows Tor, would it?

Toad King

11th July 2025, 00:31

Not sure if anybody is maintaining the aacskeys program anymore but since it's used in FindVUK: I found a bug when using the tool with a manually-provided VID via the commandline. If the VID starts with a null byte (00) then it won't get parsed correctly and it will calculate the wrong VUK/UKs. I have a patch for it in the Archlinux AUR but I don't know how to build a static version for Windows.
https://aur.archlinux.org/cgit/aur.git/tree/002-BN_bn2bin-fix.patch?h=aacskeys

Since FindVUK gets the VID with the drive/host key it doesn't have this issue, but it might run into issues in the future if there's ever a device key that's leaked that also starts with a null byte.

Another user also provided a patch to get it building with modern versions of OpenSSL:
https://aur.archlinux.org/cgit/aur.git/tree/001-aacskeys-OpenSSL-build-fixes.patch?h=aacskeys

SamuriHL

11th July 2025, 02:42

It's a pain in the @$$ to build. I'm not sure my build environment survived moving to my new laptop. I can take a look this weekend if I can get some time. I know I've built it at least once in the past and it was an absolute nightmare to create a build environment for it.

Also FindVUK gets the VID with a host key, that's true, however with MKB v82 if I'm not mistaken there are no more valid host keys. So getting the VID another way and using aacskeys (or other implementations of the aacs spec) is really the only way to go. At least until (if?) another valid host key is found. Then again I could be wrong. I bypass the whole host key nonsense with my own custom tools.

lamp

11th July 2025, 03:09

I have a C++23 rewrite using OpenSSL 3 that I have been working on in my spare time (using GCC 15 and VS 2022) but I haven't fully tested everything as I don't have recordable discs or HD-DVD. I have been doing it as a hobby project but maybe I'll make it public sometime if there is interest.

coricopat

11th July 2025, 04:14

Would be perhaps good to have some git repo, which imports the history of all previous versions... and could be used for further development?

Toad King

11th July 2025, 06:01

Would be perhaps good to have some git repo, which imports the history of all previous versions... and could be used for further development?

That's obviously the best course of action but I'm not really planning on maintaining a new version myself. I was just posting some patches others might find useful.

A version rewritten to use modern OpenSSL (even with the one patch lots of deprecated APIs are still used) would probably be more useful IMO.

lamp

11th July 2025, 06:17

I still haven't been able to get rid of the ECDSA stuff, it seems like in modern OpenSSL they focus more on security than general projects as there isn't much (any) documentation on doing custom curves with the modern API's as they really want you to use tested named curves.

coricopat

14th July 2025, 16:50

@Nalor
Not sure whether I'va had already mentioned this, but it seems the locally generated VUKbackup/keydb.cfg differs slightly from that from the OnlineDB
Next to comments (which don't matter) this is in particular:
- unit keys are separated by "|" rather than " | ", like "U | 1-0xFOO|2-0xBAR|3-0xBAZ" instead of "U | 1-0xFOO | 2-0xBAR | 3-0xBAZ"
- fields are ordered differently... in the local file it's D M I V U, in the online file it's D V M I U

If it's a simple change, it would be nice if the local output could someday be aligned with the online file.
I usually diff the local stuff from my own keys to see whether it's properly contained online... and that would be easier with that way.

Doesn't hurry though, and no problem if it's too much work or other reasons speak against it.

thx :-)

nalor

17th July 2025, 22:32

@Nalor
Not sure whether I'va had already mentioned this, but it seems the locally generated VUKbackup/keydb.cfg differs slightly from that from the OnlineDB

I think I've fixed this some time ago .... need to check

coricopat

18th July 2025, 00:31

I think I've fixed this some time ago .... need to check

No need for a hurry... but if so, would be nice if you could merge the changes into any future release :-)

bredboi

23rd July 2025, 18:36

Hi all, not sure if this is the right place (let me know if there's a better place to put this pls) but ive run into an error when running FindVUK on a new disc:

18:14:41 - Information: no bdmv-meta-dl directory available on disc - cannot read meta-title
18:14:41 - Drive is detected as 'REAL BLURAY' drive
18:14:41 - M2TS files found >6<
18:14:41 - Potentially invalid UnitKey >C8A584FEBFBD26D05414CB98B0E1D0CB<
18:14:41 - Unfortunately no candidate to get a correct unit key >C8A584FEBFBD26D05414CB98B0E1D0CB<
18:14:41 - There are still 6 files that cannot be decoded with the provided unit keys!
18:14:41 - Validation failed - VUK/UnitKeys are INVALID!!!!!!!
18:14:41 - Please report this in the Doom9 forum and attach the logfile!

MakeMKV fails to read the disc as well - it looks like it's a new version of AACS or something.

full FindVUK log here: https://drive.google.com/file/d/1xksqEmXZPhphBbifhKqKOuzKhOsmYaY_/view?usp=sharing

any help would be appreciated

MrPenguin

23rd July 2025, 21:42

MakeMKV fails to read the disc as well - it looks like it's a new version of AACS or something.
Did MakeMKV also generate a TGZ dump file? And if so, could you provide it too please?

Toad King

24th July 2025, 04:08

Hi all, not sure if this is the right place (let me know if there's a better place to put this pls) but ive run into an error when running FindVUK on a new disc:

MakeMKV fails to read the disc as well - it looks like it's a new version of AACS or something.

full FindVUK log here: https://drive.google.com/file/d/1xksqEmXZPhphBbifhKqKOuzKhOsmYaY_/view?usp=sharing

any help would be appreciated
It looks like the disc you're trying to verify uses bus encryption. If you have a drive that supports Libredrive you can edit the "config/FindVUK.ini" file and set the "MakeMKV_Libredrive_Enabled" setting to "1". Otherwise that disc appears to be MKBv82 and that one revoked all public host keys and you're kind of out of luck for now.

Emulgator

24th July 2025, 14:01

2025-07-23 18:14:32 # 36573 # [I] bluray_aacs / BRAACS_InitDisc / UnitKeys ENC : >1< Key >BA4E09712F5DE64167B7F1B855BD65C8<
2025-07-23 18:14:32 # 36573 # [I] FindVUK_Main / FVMAIN_Mode_AACSkeys_GetMetaInfo_VolumeName / Reading volumelabel from drive >O<
2025-07-23 18:14:32 # 36683 # [I] FindVUK_Main / / VolumeName >BD_ROM<
2025-07-23 18:14:32 # 36685 # [I] FindVUK_Main / / DiscId >4C70595EDD571241C6249543A0E34B99CABC3556< (2025-06-02)
2025-07-23 18:14:32 # 36685 # [I] FindVUK_Main / / DiscType >BD<
2025-07-23 18:14:32 # 36686 # [I] FindVUK_Main / / MKB Revision >82<
2025-07-23 18:14:32 # 36687 # [I] FindVUK_Main / / Disc-BusEncEnabled >1<
2025-07-23 18:14:32 # 36687 # [I] FindVUK_Main / / Drve-BusEncCapable >1<
2025-07-23 18:14:32 # 36688 # [I] FindVUK_Main / / ==> Bus Encryption active!
2025-07-23 18:14:32 # 36689 # [I] FindVUK_Main / / UnitKeyCount >1<
2025-07-23 18:14:32 # 36689 # [I] FindVUK_Main / / >>> UnitKeyENC (1) >BA4E09712F5DE64167B7F1B855BD65C8<

Volume Name "BD_ROM" and MKB v82.
Hm. What may that be ?
MakeMKV from 1.18.0 (04.04.2025) should be able to decrypt MKB v82.

SamuriHL

24th July 2025, 22:11

It should...but it can't.

bredboi

25th July 2025, 10:23

It looks like the disc you're trying to verify uses bus encryption. If you have a drive that supports Libredrive you can edit the "config/FindVUK.ini" file and set the "MakeMKV_Libredrive_Enabled" setting to "1". Otherwise that disc appears to be MKBv82 and that one revoked all public host keys and you're kind of out of luck for now.

That worked, TYSM! :)

Volume Name "BD_ROM" and MKB v82.
Hm. What may that be ?
MakeMKV from 1.18.0 (04.04.2025) should be able to decrypt MKB v82.

its a new concert blu-ray from japan. ive got a few japanese imports with the volume title "BD_ROM" (or variations on it), im guessing whoever authors discs over there doesn't really bother to name them for whatever reason

i did make sure to update to the latest version of makemkv (1.18.1 i think) but no dice

Emulgator

25th July 2025, 22:31

Thank you both for clearing that up.

nalor

27th July 2025, 00:00

I think I've fixed this some time ago .... need to check

OnlineDB changed to ordering of FindVUK - additionally the next FindVUK release will use the same "comment" pattern as the OnlineDB.

coricopat

27th July 2025, 00:19

OnlineDB changed to ordering of FindVUK - additionally the next FindVUK release will use the same "comment" pattern as the OnlineDB.

Thx. ☺️

27th July 2025, 00:30

OnlineDB changed to ordering of FindVUK - additionally the next FindVUK release will use the same "comment" pattern as the OnlineDB.

Thanks for the update nalor.

It would be appreciated if you could add the MKBv82 AACS 1.0 device key posted by candela to the public keydb: Link (https://forum.doom9.org/showthread.php?p=2016431#post2016431)

rdodolak

15th August 2025, 00:10

I have both DVDFab and Passkey installed, but FindVUK 1.82 doesn't find the Passkey application. Any suggestions on why that may be?

SamuriHL

15th August 2025, 14:47

AFAIK Passkey no longer works for FindVUK unless I'm mistaken.

rdodolak

15th August 2025, 19:23

AFAIK Passkey no longer works for FindVUK unless I'm mistaken.

Thanks for that info. I came across an older post and confirmed it will work based on the last supported version.

nalor

1st September 2025, 21:56

Quick information from my side: I've just changed the PHP version from ancient 7.4 to current 8.4 in the FindVUK Online Database backend. In case you notice problems, let me know - thanks!

coricopat

1st September 2025, 22:29

Not sure whether you got my PM ~ week ago or so... there had been some pretty large character encoding mess up in the DB between 2025-08-18 and 2025-08-19 with ~ 16670 entries being changed, things like:
"Lovecká sezóna" => "LoveckÃ¡ sezÃ³na"

Another, though merely cosmetic issue,... it seems that the sorting of entries in keydb.cfg isn't "stable" ... like an entry gets changed (e.g. validated or new volume size), but not only the entry changes but it's also placed a several lines up or down.
As said... not really a big problem (apart from getting ugly diffs, when tracking the file in git).
A nice sorting might be: 1st volume title, then MEK, then VID, then VUK, then UK, then DATE, then Disc ID?

But again... nothing worth to waste a lot of effort for :-)

coricopat

2nd September 2025, 05:52

Oh and can it be, that downloading the bluraymetaarchive.zip is broken? I get an 500 error.

(btw: thanks for your continued maintenance of this, and upgrade to current PHP)

MrMiyagi

10th September 2025, 12:44

Quick information from my side: I've just changed the PHP version from ancient 7.4 to current 8.4 in the FindVUK Online Database backend. In case you notice problems, let me know - thanks!

MetaXML archive download no longer works since the PHP upgrade

nalor

16th September 2025, 22:04

MetaXML archive download no longer works since the PHP upgrade

Strange - will check tomorrow.

I remember I had the idea of creating yearly archive files ... but afaik it was just an idea... as said, will check tomorrow :)

nalor

16th September 2025, 22:05

coricopat

16th September 2025, 22:37

I remember I had the idea of creating yearly archive files ... but afaik it was just an idea... as said, will check tomorrow :)

AFAIU, the files were previously created "immediately" (on HTTP request)?

If you want/need to limit that, it would be nice if at least not to once a year. :-)
Perphaps once per day or week?

Will also take a look tomorrow ...

Thanks... no hurry needed :-)

nalor

17th September 2025, 14:58

Changed 2 things already:
new "reduced" version of keydb.cfg available
It creates a "reduced" variant of the keydb.cfg where only the essential details required for playback are included: discid, vuk or unitkeys and nothing else
to download it used this link: http://fvonline-db.bplaced.net/fv_download.php?reduced

The funny detail on this new feature is, that I implemented 90% of it already in 2022 - but missed to finalize it :(
Now added the missing 10% - and hopefully it's working without problems.
Download size is reduced from ~20MB to ~7MB

sorting stabilized
Initially I only sorted by VolumeLabel when creating the file - but when there are multiple entries with the same VolumeLabel, the resulting order was undetermined. So I've added a 2nd criteria to sort by DiscId as 2nd priority.
As result the order of the entries is hopefully stable now :)

Next I'll check the meta-archive.