Rip successful only when I clicked start immediately
Posted: Sat Jan 04, 2020 9:27 pm
I mentioned this in a recent post about Game of Thrones 4K, but I felt this issue needed a separate thread since this appears to be a MakeMKV issue and not a disc or drive issue.
In a nutshell, I was able to successfully rip a GOT 4K disc only because I clicked on the start button very quickly. If I had waited about 30 seconds, what always happened is that while I was typing in track information, selecting output folder, etc. (after MakeMKV already successfully scanned the disc and brought up the track list), the drive would spin as fast as possible, slow down to nothing, spin as fast as possible, slow down to nothing, and then (even if I was in the middle of typing a track title) all the information would go away with MakeMKV suddenly deciding like there was no disc (or a blank disc) in the drive. People cannot tell me that my drive or disc need cleaning, because if that were true, clicking to start the ripping process should have eventually produced a similar error, or at the very least corrupt files. But neither happened. Successfully ripping the 4K content or not relied upon how quickly I pushed the start button.
In a nutshell, I was able to successfully rip a GOT 4K disc only because I clicked on the start button very quickly. If I had waited about 30 seconds, what always happened is that while I was typing in track information, selecting output folder, etc. (after MakeMKV already successfully scanned the disc and brought up the track list), the drive would spin as fast as possible, slow down to nothing, spin as fast as possible, slow down to nothing, and then (even if I was in the middle of typing a track title) all the information would go away with MakeMKV suddenly deciding like there was no disc (or a blank disc) in the drive. People cannot tell me that my drive or disc need cleaning, because if that were true, clicking to start the ripping process should have eventually produced a similar error, or at the very least corrupt files. But neither happened. Successfully ripping the 4K content or not relied upon how quickly I pushed the start button.