And in the case of the Bourne BDs or other DVD I posted about, this did not happen. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |