Wonka 4k Dump Submitted
Re: Wonka 4k Dump Submitted
I do not believe that the decryption key has been decoded for the new film. It generally takes a few days and the disc was just released yesterday. I had the newest 4k release of "The Princess Bride" recently and submitted the dump. It took about a week before I was able to open the disc.
Re: Wonka 4k Dump Submitted
I think it would be beneficial if the creator of this thread were to change the name to "Wonka (2024) 4K Dump Submitted"
Re: Wonka 4k Dump Submitted
Have your read the thread I linked? Have you tried the suggested way to get new keys for movies?
Re: Wonka 4k Dump Submitted
Holy crap that worked. Didn't realize it was that easy. Thanks!
Re: Wonka 4k Dump Submitted
In it since Monday.crosis wrote: ↑Wed Feb 28, 2024 9:01 pmI downloaded the most recent keydb.cfg file and did a text search through it. Wonka (2024) is not in it. The old Willy Wonka releases are there but the new movie is not. I was surprised to hear it was in the DB when the message stating it was posted the day before the disc was released. I was not surprised to see that it is not in the file LOL
Re: Wonka 4k Dump Submitted
The Wonka key is in the DB since Monday. Run the synchronize .bat and use the newest keydb.cfg file.
Re: Wonka 4k Dump Submitted
Okay. I am very new to using Makemkv. I am not new to ripping discs with another program. However, that other program doesn't work at all with UHD discs, at least not for me.
Can someone point me to the thread that explains this process of finding these keys and dropping them into Makemkv?
Is it this thread I linked earlier? viewtopic.php?f=12&t=33167
Can someone point me to the thread that explains this process of finding these keys and dropping them into Makemkv?
Is it this thread I linked earlier? viewtopic.php?f=12&t=33167
Re: Wonka 4k Dump Submitted
Code: Select all
0xC09FF132158FE2CB5D7E89CD952C98FD1CF153E6 = WONKA (Wonka) | D | 2023-12-19 | M | 0x326C4DA99ABFCF9A6149CE3E80AB9D0C | I | 0x0D484BE0778B3425B09EB0EB81CFF382 | V | 0x27B19CE337F3F85DC16C7E4F1114D95A | U | 1-0xE60C3FF55E274314D68AEB0340814F51 ; MKBv77/BEE/FindVUK 1.72 - MainPlaylist: 00000.mpls - VolumeSize: 87206068224 (UHD)
0x25FC9B7C6EE1E6E0B3761F07BBE5D2EF387C67CA = WONKA (Wonka) | D | 2024-01-09 | U | 1-0x10C8052B3DC622EBAC102100850DEE66 ; MKBv77/BEE/FindVUK 1.72 - VolumeSize: 97243299840 (UHD) (LEGACY) (NOTVALIDATED) (BD)
Last edited by SamuriHL on Thu Feb 29, 2024 12:27 am, edited 1 time in total.
Re: Wonka 4k Dump Submitted
Re: Wonka 4k Dump Submitted
Thanks, I will give it a try.
Re: Wonka 4k Dump Submitted
Ok so this worked for me too but I would like to understand a little more about what is happening.BriBo wrote: ↑Wed Feb 28, 2024 8:55 pmI was able to piece this together from things I read in several places.
In order to resolve this issue (on macOS), the file keydb.cfg needs downloaded (http://fvonline-db.bplaced.net) and placed in the Users/<username>/Library/MakeMKV folder, then the restart the app. No other changes are needed.
Wonka decrypts fine after doing this.
I have never had to do this in the past and have ripped hundreds of 4k blurays over the last few years. So what is happening here? Is it just that the process the MakeMKV developer uses takes a little longer and the app would eventually find this decryption key? Or is this some new thing we will have to do from now on for certain disks?
Re: Wonka 4k Dump Submitted
I've not used the keydb.cfg file method for quite some time since MakeMKV incorporated the automatic downloading of keys. But since the new Wonka film still wasn't working as of this morning (2/29), I thought I'd try it and it worked. Good to know there is an alternative option if the auto process doesn't work. FYI..I'm using a Mac with Mac OS 14.2.1.
Re: Wonka 4k Dump Submitted
If you wait, MakeMKV will eventually provide the decryption key in the usual way. Officially, the Wonka (2023) 4K release date was February 27th although someone posted on Feb 24 that they submitted a dump.bdemiller wrote: ↑Thu Feb 29, 2024 4:22 amOk so this worked for me too but I would like to understand a little more about what is happening.
I have never had to do this in the past and have ripped hundreds of 4k blurays over the last few years. So what is happening here? Is it just that the process the MakeMKV developer uses takes a little longer and the app would eventually find this decryption key? Or is this some new thing we will have to do from now on for certain disks?
The alternative method with keydb.cfg is useful when MakeMKV hasn't provided a key in the usual way yet, but a key is available from alternate sources. It is handy for the impatient.