More > JRiver Media Center 23 for Mac
JRiver 23 always crashes while ripping CDs
finzic:
--- Quote from: RoderickGI on November 27, 2019, 11:33:51 pm ---Well, on a Windows PC it would be the File Association pointing to iTunes, and the setting that what to do when an optical disc is inserted.
I think iTunes is probably still trying to take control of the optical drive while MC is using it.
To test, with MC closed, insert a CD. If iTunes starts, that is the issue. Find the setting that stops that happening.
--- End quote ---
I tried this one, and it actually solved the problem of having iTunes start. iTunes does not start anymore, but unfortunately the crashes are still there.
Could it be the fact that the library is on the second HDD and sometimes it is stopped when not used for some time?
RoderickGI:
--- Quote from: finzic on November 29, 2019, 03:20:11 pm ---Could it be the fact that the library is on the second HDD and sometimes it is stopped when not used for some time?
--- End quote ---
That's unlikely. If MC needs the drive, OSX will spin it up.
I'm not sure about using a USB Optical Drive with MC to rip files on a Mac. I know on Windows this can be a problem, as MC tries to take full control of the Optical Drive, and the USB connection doesn't allow it. So that could be the problem.
Does MC actually crash, as in close unexpectedly, or does it just become unresponsive, which is a Hang?
If just a Hang, can you leave it for some time to see if it recovers and starts working again?
finzic:
--- Quote from: RoderickGI on November 29, 2019, 03:34:58 pm ---That's unlikely. If MC needs the drive, OSX will spin it up.
I'm not sure about using a USB Optical Drive with MC to rip files on a Mac. I know on Windows this can be a problem, as MC tries to take full control of the Optical Drive, and the USB connection doesn't allow it. So that could be the problem.
Does MC actually crash, as in close unexpectedly, or does it just become unresponsive, which is a Hang?
If just a Hang, can you leave it for some time to see if it recovers and starts working again?
--- End quote ---
MC crashes brutally. Sometimes it crashes with a crash report as the one I posted before here; other times it crashes silently with no message.
Thank you for the reply, in the meantime :)
RoderickGI:
If you are using default drivers for the Optical Drive, you might be able to find specific drivers from the manufacturer that behave better. Or vice versa.
Generally, this issue is a combination of the way MC tries to take control of the drive (low-level control, which provides better CD rips), the hardware in the computer and its drivers (USB port), the operating system, the hardware in the Optical Drive, and the driver used for the Optical Drive.
It can be pretty hard to work out which bit is the problem, and even then, it may not be possible to fix.
I did look at your crash report the other day. I had forgotten that. I can't work out what the cause is from that anyway, but the;
--- Quote ---Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007fa2b5141a2c
Exception Note: EXC_CORPSE_NOTIFY
--- End quote ---
doesn't look good. Probably points to the USB driver in combination with the way MC accesses the drive.
I assume that when the Optical Drive was mounted internally it was on a SATA connection? If you were on Windows, I recommend exposing a SATA (i.e. eSATA) connection and putting the drive in a SATA capable external enclosure. But I guess that isn't going to happen on a Mac?
finzic:
--- Quote from: RoderickGI on November 29, 2019, 03:58:42 pm ---If you are using default drivers for the Optical Drive, you might be able to find specific drivers from the manufacturer that behave better. Or vice versa.
Generally, this issue is a combination of the way MC tries to take control of the drive (low-level control, which provides better CD rips), the hardware in the computer and its drivers (USB port), the operating system, the hardware in the Optical Drive, and the driver used for the Optical Drive.
It can be pretty hard to work out which bit is the problem, and even then, it may not be possible to fix.
I did look at your crash report the other day. I had forgotten that. I can't work out what the cause is from that anyway, but the;doesn't look good. Probably points to the USB driver in combination with the way MC accesses the drive.
I assume that when the Optical Drive was mounted internally it was on a SATA connection? If you were on Windows, I recommend exposing a SATA (i.e. eSATA) connection and putting the drive in a SATA capable external enclosure. But I guess that isn't going to happen on a Mac?
--- End quote ---
Yes you're right. This is the original optical unit of the Mac that I took out to replace with a hybrid 1TB SSHD. I put the optical unit in a USB enclosure. Unfortunately my late 2011 Macbook Pro does not feature an eSATA connector...
By trial and error I noticed that sometimes a full rip gets to completion, with a lot of patience and a mixture of low rip speed and prayers :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version