INTERACT FORUM
More => Old Versions => JRiver Media Center 30 for Mac => Topic started by: pjd031 on October 21, 2022, 07:47:44 am
-
I've been a MC user for some time now since MC26. CD ripping on my 2014-spec MAC mini has always been a bit flaky (not recognising that a CD is inserted into a drive and available to rip mainly). At times I have had to revert to using Apple Music to rip and then import to MC and use it to convert from ALAC to FLAC.
However since upgrading to MC30 today it definitely seems worse. Does anyone else have similar problems (on any version)? My operating system is up to date (Monterey 12.6).
Thanks.
-
Did you try the Wiki?
-
I have now (thanks). The only issue that I saw with my setup was with the iTunesHelper process and that was that it doesn't seem to exist for Music any more. The only way I can get it to work is to click on "Drives and devices">"[CD name]" first. Even then, if I navigate away to another page and then come back the page is blank again. After much fiddling I can get a rip to happen but I haven't worked out a route to 100% success.
Sorry to be so vague but it just seems a lot flakier than before.
-
I've just tested with MC30. I see some odd behavior also.
After inserting a CD, MC doesn't indicate anything. Even when System Preferences > CD & DVD > Music CD is set to use MC30, still nothing happens.
But you can go to drives and devices and see the disk right there. Clicking on that disk gets weird quickly. On first click, unnamed tracks appear. Then, in a second or two, they disappear and stay gone. The empty pane says "no disk double click to refresh". Double clicking might do something or it might not. My last trial I had to double click 3 times to get the tracks to appear.
Now I have a list of unnamed tracks. If I click "update from online database", I get a dialog with a selection of possible matches. When I accept one of these, the metadata is applied.
Next, I click the RIP tracks button up top and .... nothing happens. That's because MC has now opened a tiny new dialog at the lower left with "details", "Options", and "RIP".
Finally, pressing the Rip button on this new dialog, the rip happens. When it's over, the disc ejects (as per the options that were set) and the media is automatically imported into MC.
This experience isn't nearly as smooth as what I'm used to with ripping. I would probably use MC's ripping tool if it didn't require as much effort on my part and seemed more consistent. Particularly the fumbling with the disc contents appearing, disappearing, and appearing again after several cycles of double clicks.
It's not the MC's ripping isn't technically good. It's not that MC's ripping isn't well integrated. It's both technically good AND well integrated. The issue with MC ripping is that it is awkward and requires a lot more user action than other tools I am used to.
Brian.
-
Hi all,
The exact same experience here, on Windows,
I've been using and paying for MC since version 24:
Sometimes an inserted CD would not show up. Even not under MC's explorer/drives.
A restart of MC or a reboot of the complete machine is what it would take to show the inserted CD and making it available for ripping.
In more as 50% of the cases a second or additional CD would never be 'seen'. Even not when manually refreshing the drive.
No other soft or AV programmas are installed on this machine.
I'm guessing ripping of optical media is still of some importance, at least i'm still ripping some 10 discs a week.
Thanks for your help and to have a look into the ripping process.
-
I've been having issues on Mac mini running Monterey 12.6 since Media Center 29, as well as Media Center 30. For what its worth if I run Media Center 28, I can rip CDs again.
Media Center 30 does not load the CD. When I select Rip CD, it prompts me to insert and disk which is already loaded.
I though it was my external CD drive, purchased a new one, and same issue.
Any help on solving this is great. I'm ripping CDs to FLAC format.
-
Default settings for FLAC encoding?
-
Same here. After upgrading to MC30 ripping does not work neat anymore. With 13.0.1. nothing works at all. This is bad! I unplugged my 4 drives, rebooted and everything. Anyone with an idea would be appreciate. Thx, MdV
-
More detail please.
I can rip fine in 13.0.1 with the current build.
What is the issue, seeing the drives, ripping or encoding??
-
For me the issue seems to be seeing the drive and loading the disk. Did not get to the actual ripping.
-
I think I've found an issue with that.
When the next build (33) comes out, give that a try and let us know.
-
I'm on build 38 and can't rip a full disk. I get a little further as I can start a rip, but it is really slow. The Media Center 30 aborted abnormally after ripping 6 of 11 songs. Progress.
-
It's still an issue.
I've got a handle on it but working out the kinks.
-
Please try build 30.0.41
-
I've tried ripping with MC 30.0.45. First let me say it's an improvement, ripping speeds are a lot better; however, ripping fails after multiple tracks are ripped. I typically start over at the last unripped song and work my way through. Almost there...
Thanks
-
I've tried ripping with MC 30.0.45. First let me say it's an improvement, ripping speeds are a lot better; however, ripping fails after multiple tracks are ripped. I typically start over at the last unripped song and work my way through. Almost there...
Thanks
I think it's opening and closing the device for each track and there is probably enough of a delay on notifications from the OS that could be causing the issue you see.
For some reason my combination of hardware and OS works fine.
It would be better if it only opened the device at the beginning of the riplist and closed it at the end. Will look at that next week.
-
I think it's opening and closing the device for each track and there is probably enough of a delay on notifications from the OS that could be causing the issue you see.
For some reason my combination of hardware and OS works fine.
It would be better if it only opened the device at the beginning of the riplist and closed it at the end. Will look at that next week.
Please give any build 30.0.47 and newer a try.
-
I updated to 30.0.60 and still have the same problem as others.
-
I updated to 30.0.60 and still have the same problem as others.
OS and devices?
It works perfectly for me on several Mac's with different drives and versions of MacOS.
-
MacBook Pro, 2020, 2 GHz Quad-Core Intel Core i5, 16 GB, Ventura 13.2
Apple USB SuperDrive
Here's part of the crash report:
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00005ffffffffff1
Exception Codes: 0x0000000000000001, 0x00005ffffffffff1
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [16545]
VM Region Info: 0x5ffffffffff1 is not in any region. Bytes after previous region: 105540231364594 Bytes before following region: 15
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
VM_ALLOCATE (reserved) 2f8000000-300000000 [128.0M] rw-/rw- SM=NUL ...(unallocated)
---> GAP OF 0x5ffd00000000 BYTES
MALLOC_NANO 600000000000-600008000000 [128.0M] rw-/rwx SM=PRV
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 Media Center 30 0x10f1f4757 0x10dcb9000 + 22263639
1 Media Center 30 0x10f1f5449 0x10dcb9000 + 22266953
2 Media Center 30 0x10f2be393 0x10dcb9000 + 23090067
3 Media Center 30 0x10f2b0e0c 0x10dcb9000 + 23035404
4 Media Center 30 0x10f2b0e55 0x10dcb9000 + 23035477
5 Media Center 30 0x10f2b0e55 0x10dcb9000 + 23035477
6 Media Center 30 0x10f2b0e55 0x10dcb9000 + 23035477
7 Media Center 30 0x10f2a1469 0x10dcb9000 + 22971497
8 Media Center 30 0x10f2a15ad 0x10dcb9000 + 22971821
9 Media Center 30 0x10f2722b0 0x10dcb9000 + 22778544
10 Media Center 30 0x10f2b7359 0x10dcb9000 + 23061337
11 Media Center 30 0x10e7bd7c8 0x10dcb9000 + 11552712
12 Media Center 30 0x10f2b7359 0x10dcb9000 + 23061337
13 Media Center 30 0x10f201ecd 0x10dcb9000 + 22318797
14 Media Center 30 0x10ee9daf5 0x10dcb9000 + 18762485
15 Media Center 30 0x10f2027ea 0x10dcb9000 + 22321130
16 Media Center 30 0x10f20318b 0x10dcb9000 + 22323595
17 Media Center 30 0x10f2aca7e 0x10dcb9000 + 23018110
18 AppKit 0x7ff81376f144 _NSViewDrawRect + 121
19 AppKit 0x7ff813f543c3 -[NSView _recursive:displayRectIgnoringOpacity:inContext:stopAtLayerBackedViews:] + 1810
20 AppKit 0x7ff81376e870 -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 753
21 QuartzCore 0x7ff817f9eb59 CABackingStoreUpdate_ + 254
22 QuartzCore 0x7ff8180023c1 invocation function for block in CA::Layer::display_() + 53
23 QuartzCore 0x7ff817f9dd66 -[CALayer _display] + 2275
24 AppKit 0x7ff81376e4c5 -[_NSBackingLayer display] + 462
25 AppKit 0x7ff8136e6455 -[_NSViewBackingLayer display] + 554
26 QuartzCore 0x7ff817f9cd08 CA::Layer::display_if_needed(CA::Transaction*) + 900
27 QuartzCore 0x7ff8181166c6 CA::Context::commit_transaction(CA::Transaction*, double, double*) + 648
28 QuartzCore 0x7ff817f7db35 CA::Transaction::commit() + 725
29 AppKit 0x7ff81377f96f __62+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayLink]_block_invoke + 285
30 AppKit 0x7ff813f97767 ___NSRunLoopObserverCreateWithHandler_block_invoke + 41
31 CoreFoundation 0x7ff8104d1092 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
32 CoreFoundation 0x7ff8104d0fba __CFRunLoopDoObservers + 482
33 CoreFoundation 0x7ff8104d0540 __CFRunLoopRun + 870
34 CoreFoundation 0x7ff8104cfb60 CFRunLoopRunSpecific + 560
35 HIToolbox 0x7ff819e1d766 RunCurrentEventLoopInMode + 292
36 HIToolbox 0x7ff819e1d396 ReceiveNextEventCommon + 199
37 HIToolbox 0x7ff819e1d2b3 _BlockUntilNextEventMatchingListInModeWithFilter + 70
38 AppKit 0x7ff813620293 _DPSNextEvent + 909
39 AppKit 0x7ff81361f114 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1219
40 libJRTools.dylib 0x1120312d1 JRUIMessageLoop::PumpMessage(JRMsg&) + 129
41 Media Center 30 0x10e1372d2 0x10dcb9000 + 4711122
42 Media Center 30 0x10e134cfa 0x10dcb9000 + 4701434
43 CoreFoundation 0x7ff8104c73d4 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 137
44 CoreFoundation 0x7ff81056141a ___CFXRegistrationPost_block_invoke + 88
45 CoreFoundation 0x7ff810561369 _CFXRegistrationPost + 536
46 CoreFoundation 0x7ff81049a8f9 _CFXNotificationPost + 735
47 Foundation 0x7ff8112d6abc -[NSNotificationCenter postNotificationName:object:userInfo:] + 82
48 AppKit 0x7ff813627fd4 -[NSApplication _postDidFinishNotification] + 305
49 AppKit 0x7ff813627d26 -[NSApplication _sendFinishLaunchingNotification] + 208
50 AppKit 0x7ff813625a52 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 541
51 AppKit 0x7ff8136256a8 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 665
52 Foundation 0x7ff8113018b4 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 308
53 Foundation 0x7ff811301726 _NSAppleEventManagerGenericHandler + 80
54 AE 0x7ff8169abd9d 0x7ff8169a0000 + 48541
55 AE 0x7ff8169ab608 0x7ff8169a0000 + 46600
56 AE 0x7ff8169a4c1d aeProcessAppleEvent + 419
57 HIToolbox 0x7ff819e2ee3f AEProcessAppleEvent + 54
58 AppKit 0x7ff8136205d0 _DPSNextEvent + 1738
59 AppKit 0x7ff81361f114 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1219
60 AppKit 0x7ff813611757 -[NSApplication run] + 586
61 Media Center 30 0x10e1342ac 0x10dcb9000 + 4698796
62 dyld 0x7ff8100c3310 start + 2432
-
PS, I did install the latest OS update after I installed the .60 MC. That seems to have improved the situation, but not completely cured it. The crash report I excerpted was post upgrade.
That being said, I've ripped three disks since the crash without incident, and then...a crash. No crash report, and the computer forgot it had a CD device.
Followed by another crash, mid-rip. Here is the summary:
Process: Media Center 30 [17956]
Path: /Applications/Media Center 30.app/Contents/MacOS/Media Center 30
Identifier: com.jriver.MediaCenter30
Version: 30.0.60 (5394)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2023-02-07 21:19:57.8984 -0700
OS Version: macOS 13.2 (22D49)
Report Version: 12
Bridge OS Version: 7.2 (20P3045)
Anonymous UUID: EDF73095-B83B-7FD4-DB30-1BD018E614D4
Sleep/Wake UUID: 8FE9F10E-B294-4951-BD44-BA4E38EC56DE
Time Awake Since Boot: 44000 seconds
Time Since Wake: 4044 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [17956]
VM Region Info: 0 is not in any region. Bytes before following region: 4449542144
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 10936a000-10af56000 [ 27.9M] r-x/r-x SM=COW ...dia Center 30
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libJRDisc.dylib 0x1108fae55 JRSCSIMac::Init(bool) + 2549
1 libJRDisc.dylib 0x1108fa2cd JRSCSIMac::Open(bool) + 477
2 libJRDisc.dylib 0x1108feb17 JRSCSIManager::SCSIOpen(JRString, bool) + 359
3 libJRDisc.dylib 0x1108a2a76 CDiscManager::SCSIOpen(JRString, bool) + 198
4 libJRDisc.dylib 0x110a0c56d CMJDriveInterface::Open(JRString, int) + 253
5 libJRDisc.dylib 0x110a049bd CCDRipper::OpenDrive(wchar_t const*, bool) + 445
6 Media Center 30 0x10a504d25 0x10936a000 + 18459941
7 Media Center 30 0x10a505430 0x10936a000 + 18461744
8 Media Center 30 0x109c48441 0x10936a000 + 9299009
9 Media Center 30 0x109c47f34 0x10936a000 + 9297716
10 Media Center 30 0x10a50193a 0x10936a000 + 18446650
11 Media Center 30 0x1098d410a 0x10936a000 + 5677322
12 Foundation 0x7ff81134c190 __NSThreadPerformPerform + 177
13 CoreFoundation 0x7ff8104d1b78 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
14 CoreFoundation 0x7ff8104d1b27 __CFRunLoopDoSource0 + 157
15 CoreFoundation 0x7ff8104d1901 __CFRunLoopDoSources0 + 212
16 CoreFoundation 0x7ff8104d057b __CFRunLoopRun + 929
17 CoreFoundation 0x7ff8104cfb60 CFRunLoopRunSpecific + 560
18 HIToolbox 0x7ff819e1d766 RunCurrentEventLoopInMode + 292
19 HIToolbox 0x7ff819e1d576 ReceiveNextEventCommon + 679
20 HIToolbox 0x7ff819e1d2b3 _BlockUntilNextEventMatchingListInModeWithFilter + 70
21 AppKit 0x7ff813620293 _DPSNextEvent + 909
22 AppKit 0x7ff81361f114 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1219
23 libJRTools.dylib 0x10d6e22d1 JRUIMessageLoop::PumpMessage(JRMsg&) + 129
24 Media Center 30 0x1097e82d2 0x10936a000 + 4711122
25 Media Center 30 0x1097e5cfa 0x10936a000 + 4701434
26 CoreFoundation 0x7ff8104c73d4 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 137
27 CoreFoundation 0x7ff81056141a ___CFXRegistrationPost_block_invoke + 88
28 CoreFoundation 0x7ff810561369 _CFXRegistrationPost + 536
29 CoreFoundation 0x7ff81049a8f9 _CFXNotificationPost + 735
30 Foundation 0x7ff8112d6abc -[NSNotificationCenter postNotificationName:object:userInfo:] + 82
31 AppKit 0x7ff813627fd4 -[NSApplication _postDidFinishNotification] + 305
32 AppKit 0x7ff813627d26 -[NSApplication _sendFinishLaunchingNotification] + 208
33 AppKit 0x7ff813625a52 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 541
34 AppKit 0x7ff8136256a8 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 665
35 Foundation 0x7ff8113018b4 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 308
36 Foundation 0x7ff811301726 _NSAppleEventManagerGenericHandler + 80
37 AE 0x7ff8169abd9d 0x7ff8169a0000 + 48541
38 AE 0x7ff8169ab608 0x7ff8169a0000 + 46600
39 AE 0x7ff8169a4c1d aeProcessAppleEvent + 419
40 HIToolbox 0x7ff819e2ee3f AEProcessAppleEvent + 54
41 AppKit 0x7ff8136205d0 _DPSNextEvent + 1738
42 AppKit 0x7ff81361f114 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1219
43 AppKit 0x7ff813611757 -[NSApplication run] + 586
44 Media Center 30 0x1097e52ac 0x10936a000 + 4698796
45 dyld 0x7ff8100c3310 start + 2432
-
I updated to 30.0.60 and still have the same problem as others.
Those crash reports are very helpful. Thanks. Will look into it.
-
I have been having ripping issues on my Mac for at least a couple weeks. I just updated to 30.0.60 and am still having issues.
Now, MC does not seem to recognize the CD properly. It shows an Unnamed Disc in the sidebar under Drives & Devices, but I cannot get anything to show in the main window.
Prior to this recent update, I would see the correct disc info in the main window, but MC would crash while ripping (I tried FLAC, WAV, and MP3 encoding).
-
OK, I just tried the whole process again for the fourth or fifth time, and this time it worked. I guess I'll just see how things go from here.
-
Just about to upload a new build that should help with detection and the odd crashes (30.0.61) please let us know how it acts.
There is one known bug, the view header isn't updating properly between adding and removing discs (but the disc info will), still working on that.
-
CD ripping is like described. The view header is not updating properly, but the disc info is. Discs are ripping.
-
CD ripping is working better, but I seem to have encountered another issue. I am ripping a series of discs, Harry Potter audiobook for my boys, and the ripping process keeps failing in an odd way.
I am able to rip a disc successfully, eject the next disc, and have the rip of the subsequent disc fail after ripping the first track with the message "Open drive failed. Drive is not opened." (see screenshot).
I am able to solve the issue by canceling the rip, ejecting the disc, and starting again. MC will then rip the disc it failed previously. I finish that rip, eject the disc, insert the next one, and I get the same fail after the first track, etc.
-
CD ripping is working better, but I seem to have encountered another issue. I am ripping a series of discs, Harry Potter audiobook for my boys, and the ripping process keeps failing in an odd way.
I am able to rip a disc successfully, eject the next disc, and have the rip of the subsequent disc fail after ripping the first track with the message "Open drive failed. Drive is not opened." (see screenshot).
I am able to solve the issue by canceling the rip, ejecting the disc, and starting again. MC will then rip the disc it failed previously. I finish that rip, eject the disc, insert the next one, and I get the same fail after the first track, etc.
I just saw that once yesterday as well. It's the sequence of detection on disc change. Will take a look at it when time allows.
-
I rip all my CDs on MC28 - when i upgrded to MC30 the ripping worked but I could not see the files outside of MC30 (sonos etc.) so have to use MC28