![]() But MakeMKV isn't supposed to process things that aren't 100% spot-on. I am OK grabbing a new drive bc that's the nature of this beast. after the 1.9.8 upgrade on 1/6, the external BD drive I use is not functioning normally. on 1/6 at 8pm upgraded to 1.9.8 to process Speedy with aacs v57 - this is the first rip with 1.9.8 and 3. on 1/6 at 7.30pm completed backup of The Third Man BD 2. Even more interesting is the timing of the events: 1. Interestingly, for the rips in the zip that had DTS audio tracks, I put all of them back through ffmpeg/HB - converting the DTS-HD MA audio track to ac3 5.1, ac3 stereo, and aac stereo - and none gave the "overread" error. In the zip, all of my MakeMKV logs since upgrading to 1.9.8. I also put the log of a DVD rip from the LG drive. I tried ripping a DVD from the drive, and that worked, but also gave the "DEBUG" message.Īttached are the 3 MakeMKV logs from the Bourne box, and an HB log for Bourne 1. I'm using an external LG BD drive with both USBs connected to ports on a Win8.1 machine. ![]() Perhaps it's drive related sometimes I start MakeMKV and if there is a BD in the drive, I get thousands of DEBUG messages, which causes me to reboot. I never received this message prior to upgrading to 1.9.8. I have received this message with every rip since upgrading to 1.9.8. ![]() (I upgraded to 1.9.9 yesterday.) On line 6 of each of the posted logs, there is a "DEBUG" message. I upgraded from 1.9.4 to 1.9.8 during the first week of 2016. Win8.1 shows the drive has 5 region selections remaining. Tbh, though, I am thinking that the external LG drive is locked now. I can send a piece of it if that makes sense - as can be seen in the attached HB log, the errors occur in chapter 13. The DTS-HD MA audio track from Bourne 1 movie is 3+ gb. Makemkv Registration Code 1.9.9 Activation Key If You.I get the "Overread auxiliary data by 32 bits" from the dca decoder code in Handbrake for the 3 BDs in the Bourne box purchased at BB. Then, after starting MakeMKV, the known message came again, that the key is expired. There is the most current beta key code for the MakeMKV beta version which can be used in Windows. What few are considering is the fact that, as a beta program, it changes on a regular basis to keep up with copy protection. It seems the Beta key had expired and a new version of the program hadnt come out yet (still at 1.9.9). But after I copied in the old key again suddenly it worked!īut I tried to read in the blu-ray (index.bdmv) I copied yesterday to HDD with windows-explorer but it seems not to Yes, the creaters of MakeMKV would have deserved a donation or the 50 $. The expiring key is intended to encourage you to check for newer versions. ![]() In the old days, new versions were issued more frequently than every 60 days, and new versions had new keys. As stated on a main page all features of MakeMKV are free while program is in beta. You may purchase the full activation key if you like the program and want to show your support, but you also may use the temporary beta key. But at first, I'm a poor man! At second, MakeMKV works not really well (with me), because if I extract the main movie (converting to MKV) and want to play it then with my (Hardware-) Multimediaplayer (Fantec), it sometimes/often judders or breaks completely from. keydate (int): Unix timestamp of the first moment the key is expired. So, what I do at moment is, to copy ("backup") the hole blu-ray content and then extract the main movie with a free version of DVD Fab. You need to send a proper User-Agent header to use the API.Ĭache (int): Next timestamp this website checks for a new key. Check the source code of the auto updater for an example. ![]() This (M2TS-)file I can process further if I want, but it's not needed. Normally my fantec player has no problems wether with M2TS nor with MKV (only if converted with MakeMKV!). #Makemkv beta key 1.9.9 activation key#. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |