Ripping Issues - Noise and delays
Posted: Mon Nov 28, 2022 10:28 pm
Note: I've found more information I think is critical on this. It's several posts down, in the post that starts with "More Information" in bold.
I'm having problems using MakeMKV almost every time I try to rip a BD. I'm now using an Asus CD/DVD/BD RW drive bt this has been going on with other drives as well.
In the past, by mistake (or without thinking, maybe), I put a BD in my drive and clicked the icon in MakeMKV to scan it and then dropped the Finder icon in VLC and got a budda-budda-budda-budda sound as the head moved back and forth, reading stuff for MakeMKV and stuff for VLC. That is the kind of sound I'm getting now - it just goes on. It was happening with DVDs recently, too. (I tried a few DVDs a few weeks back, the new complete Mythbusters collection.) Now I'm ripping Murdoch Mysteries BDs to my drive.
When I start ripping, I hear almost nothing at first and things seem okay, but, always, after it's read data (maybe 2-3 GB at most, if I'm lucky) I start hearing this sound and the data transfer drops WAY down. I've had bad DVDs and BDs that have had bad sectors and that's a different sound. (And it can try reading forever without more data being read in, according to the "Output Size" value in the MakeMKV display.)
It occurred to me that I might be dealing with some kind of "battle" between MakeMKV and another program. I used "lsof" to see what files are open on my system. The output was overwhelming, so I checked and this volume is "MURDOCH MYSTERIES S15D1" and is in the file system as "/Volumes/MURDOCH MYSTERIES S15D1" but it does not show up when I try "lsof|grep MURDOCH." I do see the output file on my hard drive show up. So I tried "lsof|grep makemkv." I see a lot of files listed, but I don't see anything that tells me that MakeMKV is actually reading a file from the BD.
So, with "lsof" I don't see anything indicating ANYTHING is reading this volume, including MakeMKV. I'm wondering how I could find out if any other program is trying to access this drive in some other way. I do have Handbrake open, and it's usually running when I'm ripping. (Once I've ripped 1 disc of data, I start converting it in Handbrake.) I don't know if Handbrake has any reason to be reading this BD through the optical drive while it's doing other work or not.
I also realize I could be on the wrong track. It could be something entirely different that's causing all this noise and the slow transfer speeds.
Is this a known issue in some situations and, if not, what else can I do to troubleshoot this?
I'm having problems using MakeMKV almost every time I try to rip a BD. I'm now using an Asus CD/DVD/BD RW drive bt this has been going on with other drives as well.
In the past, by mistake (or without thinking, maybe), I put a BD in my drive and clicked the icon in MakeMKV to scan it and then dropped the Finder icon in VLC and got a budda-budda-budda-budda sound as the head moved back and forth, reading stuff for MakeMKV and stuff for VLC. That is the kind of sound I'm getting now - it just goes on. It was happening with DVDs recently, too. (I tried a few DVDs a few weeks back, the new complete Mythbusters collection.) Now I'm ripping Murdoch Mysteries BDs to my drive.
When I start ripping, I hear almost nothing at first and things seem okay, but, always, after it's read data (maybe 2-3 GB at most, if I'm lucky) I start hearing this sound and the data transfer drops WAY down. I've had bad DVDs and BDs that have had bad sectors and that's a different sound. (And it can try reading forever without more data being read in, according to the "Output Size" value in the MakeMKV display.)
It occurred to me that I might be dealing with some kind of "battle" between MakeMKV and another program. I used "lsof" to see what files are open on my system. The output was overwhelming, so I checked and this volume is "MURDOCH MYSTERIES S15D1" and is in the file system as "/Volumes/MURDOCH MYSTERIES S15D1" but it does not show up when I try "lsof|grep MURDOCH." I do see the output file on my hard drive show up. So I tried "lsof|grep makemkv." I see a lot of files listed, but I don't see anything that tells me that MakeMKV is actually reading a file from the BD.
So, with "lsof" I don't see anything indicating ANYTHING is reading this volume, including MakeMKV. I'm wondering how I could find out if any other program is trying to access this drive in some other way. I do have Handbrake open, and it's usually running when I'm ripping. (Once I've ripped 1 disc of data, I start converting it in Handbrake.) I don't know if Handbrake has any reason to be reading this BD through the optical drive while it's doing other work or not.
I also realize I could be on the wrong track. It could be something entirely different that's causing all this noise and the slow transfer speeds.
Is this a known issue in some situations and, if not, what else can I do to troubleshoot this?