INTERACT FORUM
Mac => JRiver Media Center 33 for Mac => Topic started by: Dennis in FL on October 05, 2024, 08:19:37 am
-
I have two Macs, I was using a 2020 Intel iMac with a NAS server for the music files and it couldn't survive 24 hours without crashing. I also have a Mac Mini with an Apple M1 chip and tried it instead ( I saved a backup with the iMac and restored on the mini) and same thing.....it crashed sometime in the evening hours.
Looking for suggestions.
-
Update the NAS firmware.
-
Update the NAS firmware.
It is on auto update......and it is the latest (Synology Sept 11 Version: 7.2.2-72806 )
-
Likely a corrupted media file.
Check the MC log.
-
Well, I took a short break to evacuate due to Hurricane Milton.
No damage of any consequence !!!
So I started MC in a Mac server and also ran a client on an iMac.
They both crashed and the last log entries were about sharing plugins and DLNA stuff (if this is video, I set up TV only as a curiosity and I never use it - so I can remove the TV components )
I cut and pasted the very bottom of the log and I have no clue what it means.
Also attached the full logs of both macs (client labled as such- other file is mac mini server)
I took a peek at DLNA settings and changed both Audio and Video to ORIGINAL and am now testing this new setting to see if it crashes.
Client:
0015153: 123145545089024: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
0015154: 123145545089024: Sharing Plugins: VHTTPMessage::ParseBody: Start
0015154: 123145545089024: Sharing Plugins: VHTTPMessage::ParseBody: Reading 5274 bytes from message body
0015155: 123145545089024: Sharing Plugins: VHTTPMessage::ParseBody: Finish (1 ms)
0015155: 123145545089024: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 192.168.50.31: NOTIFY: http://192.168.50.15:52102/eventSub
0015155: 123145545089024: Playback: CPlayerZone::DLNADeviceSubscription_PropertyChanged: Start
0015155: 123145545089024: Playback: CPlayerZone::DLNADeviceSubscription_PropertyChanged: Transport state was 0 changing to 0
0015155: 123145545089024: Playback: CPlayerZone::DLNADeviceSubscription_PropertyChanged: Finish (0 ms)
0015155: 123145545089024: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
0015155: 123145545089024: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (1 ms)
0015155: 123145545089024: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: closesocket() closing 43
Server:
0015153: 123145545089024: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Start
0015154: 123145545089024: Sharing Plugins: VHTTPMessage::ParseBody: Start
0015154: 123145545089024: Sharing Plugins: VHTTPMessage::ParseBody: Reading 5274 bytes from message body
0015155: 123145545089024: Sharing Plugins: VHTTPMessage::ParseBody: Finish (1 ms)
0015155: 123145545089024: Sharing Plugins: CHTTPListenerWorker::HandleRequest: TCP: 192.168.50.31: NOTIFY: http://192.168.50.15:52102/eventSub
0015155: 123145545089024: Playback: CPlayerZone::DLNADeviceSubscription_PropertyChanged: Start
0015155: 123145545089024: Playback: CPlayerZone::DLNADeviceSubscription_PropertyChanged: Transport state was 0 changing to 0
0015155: 123145545089024: Playback: CPlayerZone::DLNADeviceSubscription_PropertyChanged: Finish (0 ms)
0015155: 123145545089024: Sharing Plugins: VHTTPMessage::Write: Wrote 0 bytes
0015155: 123145545089024: Sharing Plugins: CHTTPListenerWorker::HandleConnection: Finish (1 ms)
0015155: 123145545089024: General: CReferenceCountedSocket::Close: SOCKET_DEBUG: closesocket() closing 43
-
Was the power out?
Try powering all computers and network devices off, waiting a few minutes, then re-starting the network first, then other devices.
-
Was the power out?
Try powering all computers and network devices off, waiting a few minutes, then re-starting the network first, then other devices.
Yes post hurricane the power was off for days. I had everything on UPS battery and nice shutdowns before power loss.
But what I'm describing is a pre-hurricane problem, pre-power loss problem that continued after restoration of power
The probelm has been, everything seems OK and music plays correctly for a while. Then it crashes. When I use a client MC with a library from a server MC...they both crash.
However, my small changes to the DLNA settings seems to be working for a while now. I changed the output format to ORIGINAL and so far--no crash. In the past, it rarely lasted 8 hours doing nothing.
-
That might be a conversion problem on the server. A different codec might work.
-
The Apple crash report should be useful, when you get one next time copy and paste it here.
The logs aren't showing anything much out of the ordinary, however the client log appears to show you have 2 active network interfaces on the same lan, is that the case?
What DLNA devices do you have on the network?
What other DLNA capable programs are you running on either Mac?
-
>> The Apple crash report should be useful, when you get one next time copy and paste it here.
OK
>>The logs aren't showing anything much out of the ordinary, however the client log appears to show you have 2 active network interfaces on the same lan, is that the case?
I think that's the way my iMac reports using both WiFi and Ethernet --- each has a separate IP address. I have forgotten why I do that but there was some APP that required WiFi. I can probably just use ethernet.
>>What DLNA devices do you have on the network?
I have a WiiM Ultra preamp and an LG TV .... I never use the TV.
>>What other DLNA capable programs are you running on either Mac?
I have a Raspi 4 running Ropieee with DLNA turned off. I use it to feed Airplay into the WiiM
I have Tidal which uses Tidal Connect and I have QOBUZ which I'm not using now.
I think Plex has DLNA (not sure) but although I have the server running on the same machine as MC, I rarely use it.
JRiver MC lists only the WiiM and Sonos speakers in Playing now
-
>> The Apple crash report should be useful, when you get one next time copy and paste it here.
OK
>>The logs aren't showing anything much out of the ordinary, however the client log appears to show you have 2 active network interfaces on the same lan, is that the case?
I think that's the way my iMac reports using both WiFi and Ethernet --- each has a separate IP address. I have forgotten why I do that but there was some APP that required WiFi. I can probably just use ethernet.
>>What DLNA devices do you have on the network?
I have a WiiM Ultra preamp and an LG TV .... I never use the TV.
>>What other DLNA capable programs are you running on either Mac?
I have a Raspi 4 running Ropieee with DLNA turned off. I use it to feed Airplay into the WiiM
I have Tidal which uses Tidal Connect and I have QOBUZ which I'm not using now.
I think Plex has DLNA (not sure) but although I have the server running on the same machine as MC, I rarely use it.
JRiver MC lists only the WiiM and Sonos speakers in Playing now
Usually the only reason to have wifi and ethernet on at the same time is to use airdrop. My dev machine has that. It doesn't seem to affect the running MC adversely but it will likely be broadcasting SSDP on both interfaces.
Seeing the 1900 port socket in use makes me think that you have another DLNA program running on the Mac though that really shouldn't cause a crash.
-
MC on both Macs are both running perfectly now all morning. Before I changed the DLNA settings it would have crashed by now. I used to have ORIGINAL as I think DFF or DSF on audio when it was crashing.
Fingers crossed
-
MC crashed overnight. Both the server and the client. I force quit both and only the server produced an Apple crash report (attached with MC log).
Is this the old Time Machine Issue? I have both Macs on a early morning daily backup.
But the crash is not only in the evening. I have had crashes maybe an hour after beginning to play a song. Yesterday it survived many hours before crashing
-
Is this the old Time Machine Issue? I have both Macs on a early morning daily backup.
It may well be Time Machine or Spotlight as both of them are Notorious for using up a lot of Disk Space for no obvious reason.
-
MC crashed overnight. Both the server and the client. I force quit both and only the server produced an Apple crash report (attached with MC log).
Is this the old Time Machine Issue? I have both Macs on a early morning daily backup.
But the crash is not only in the evening. I have had crashes maybe an hour after beginning to play a song. Yesterday it survived many hours before crashing
Force quit?
So neither is actually "crashing". You are calling hanging a crash?
-
Yes….hanging…..
-
Yes….hanging…..
Probably something to do with sleep settings and network activity.
You could check your system preferences->energy saver settings.
-
Probably something to do with sleep settings and network activity.
You could check your system preferences->energy saver settings.
No...I'm running the JRiver server on a headless Mac Mini (M1 chip) and it has other 24/7 software running so I disabled any energy savers. And plus, it hangs during the day as well. I thought it had to do with the client server handshaking. I have a ASUS ZenWiFi AX (XT8) Router system and it is blazing fast and has no trouble sending 4K video from the NAS to my Apple TV.
Anyway, I just transferred the MC server to a Raspi 5 and played some music from the iMac client. It was working but had some significant dropouts - I guess the Pi doesn't have enough oomph. So I decided to go back to the MC server on the Mac Mini and when I clicked on the client's library choice for the mini they both hung. I'll attach the Apple crash report to this post.
-
No...I'm running the JRiver server on a headless Mac Mini (M1 chip) and it has other 24/7 software running so I disabled any energy savers. And plus, it hangs during the day as well. I thought it had to do with the client server handshaking. I have a ASUS ZenWiFi AX (XT8) Router system and it is blazing fast and has no trouble sending 4K video from the NAS to my Apple TV.
Anyway, I just transferred the MC server to a Raspi 5 and played some music from the iMac client. It was working but had some significant dropouts - I guess the Pi doesn't have enough oomph. So I decided to go back to the MC server on the Mac Mini and when I clicked on the client's library choice for the mini they both hung. I'll attach the Apple crash report to this post.
The crash report isn't useful when there is a force quit involved.
Are you running it in Media Server only mode when headless?
-
Not sure what you mean?
Do you mean is the MC the only software running? No
Or is there a setting in MC that should be turned on to make it a server only?
-
see screenshot attached
-
Maybe you said but are your files on a removable Drive?
-
A Raspberry Pi is fast enough for any audio. And most video.
-
Maybe you said but are your files on a removable Drive?
No...the audio files are on a NAS Synology server and the MC settings, logs, etc are on the Mac Mini internal SSD or the NAS server.
-
A Raspberry Pi is fast enough for any audio. And most video.
I know...that's why I thought there was something amiss with my DLNA settings or possibly with the communication of a MC server/client. I'll try the Raspi all alone without the client and see if I get dropouts.
-
The crash report isn't useful when there is a force quit involved.
Are you running it in Media Server only mode when headless?
Now it crashed when I was closing it --- no forced quit this time (report attached)
-
Not sure what you mean?
Do you mean is the MC the only software running? No
Or is there a setting in MC that should be turned on to make it a server only?
On window and Mac you can set MC to server only mode when starting (in settings under startup).
That will prevent any UI interaction (dialog boxes, etc).
-
I just saw that for the first time...thanks....
I just set it for server and am rebooting.
-
On window and Mac you can set MC to server only mode when starting (in settings under startup).
That will prevent any UI interaction (dialog boxes, etc).
I had high hopes. I set the MC for server on the Mac Mini and rebooted it. Sure enough, MC was running. And I ran played a couple of half hour symphonies from a iMac client without issue.
So I decided to let it sit there doing nothing and sure enough when I checked this morning it had hung and I needed to force quit.
This is getting frustrating. Are there any apps MC doesn't play nice with? I don't remember any of this happening with MC 32. I'm going to try running MC solo on the iMac and forgetting about the Mac Mini and server mode.
-
I ran MC solo on one Mac and it was doing fine all day yesterday but this morning it had hung. I suspect Time Machine interference.
I have a Raspi and a Windows machine......I'll try one of them while still using the NAS for the files tonight. I have other Mac Apps runing 24/7 with NAS files (like Emby) that don't hang.
This time was different, however. When I force quit MC, the Mac immediately blkew up and I had a black screen. I had to hit the power button.
I can't remember anything like this with MC 32.
-
On window and Mac you can set MC to server only mode when starting (in settings under startup).
That will prevent any UI interaction (dialog boxes, etc).
One of the things I love is the ability to save and restore a library across platforms.
I saved the library on my Mac and restored it on my Windows 11 machine
And then I imported the same NAS library used on the Mac and let MC run overnight
It survived. No hanging. No crashes. All is well.
Definitely a Mac issue.
I need the Mac to either be a client or a server. I can have the WIndows machine be a server with the Mac as a client (haven't tested that yet).
Years ago I had dropouts when the Mac was running Time Machine and all Macs do a backup overnight.
Any suggestions on tracking down the issue?
-
On window and Mac you can set MC to server only mode when starting (in settings under startup).
That will prevent any UI interaction (dialog boxes, etc).
I think I may have stumbled on something. This morning my Windows version was also hanging. But the attached screenshot is what was on monitor. I had accidentally included an SACD ISO file. I have been extracting DSF files from the ISOs and this one had slipped through the cracks.
Seems there's an endless loop there.
I'm going to double check if there are any more iso files and then rerun the Mac version to see if that's it.
-
It isn't just ISO....FLAC is also repeating
-
Last night I tested a Windows MC server with a Mac client and the Windows server was fine this morning and the Mac hung requiring a force quit. The strange repeating above of the iso and flac files also occurs with wav files.
-
Last night I tested a Windows MC server with a Mac client and the Windows server was fine this morning and the Mac hung requiring a force quit. The strange repeating above of the iso and flac files also occurs with wav files.
It should like your library has a loop of duplicate entries in it. Are you using the portable library function? You might have trouble with that and auto-import paths
-
It should like your library has a loop of duplicate entries in it. Are you using the portable library function? You might have trouble with that and auto-import paths
No...not using the portable library ....just regular old library. But I did save the library in a Mac and restore it in a Windows MC.
It is exclusively FLAC, ISO or WAV files. I've seen no repeats in DSF, MP3, ALAC, etc.
I suspect it is something in the restore of the library is buggy. I'm going to try a brand new Library on the same NAS files and see if they repeat.
-
OK...I created a brand new library and used the same NAS files as the library above with all the repeating entries.
And it was fine. The example I used is the repeating Ashkenazy Prelude. I attached a screenshot from both the Library reloaded on Windows from a Mac and a brand new library but using the same NAS file folders
I'm using some simple display rules like sorting based on artist and composition but nothing that should affect file type.
If I go back to the Mac with the original library (backed up and restored to windows) it does not repeat (also attached)
-
Yesterday I created a bare bones library on the Mac using the MC defaults but still using the NAS files.
This morning all was well and it is not duplicating the files as above.
So I suspect it is something with the customized views (almost all in Classical music album displaying) in the library that causes so many bugs.
I had been using that library on my mac as far back as MC 30 or 31 without issue.
I am thinking it may be prudent to start from scratch although that would be a major pain.
-
I started from scratch and everything has been working correctly until today - I had a crash.
-
I started from scratch and everything has been working correctly until today - I had a crash.
What were you doing when it crashed? Are you using media network at all?
-
No...I wasn't using MC at the time of the crash.
Interesting...after I restarted Media Center, all my classical music was missing. No files at all. But other genres were there....Pop, jazz, etc.
After trying running auto-import and just about everything else I could think of, I did a restore of my last backup and all my classical was back again.
Update: It crashed while I was typing this. This time it was playing music and I had just finished checking Customized View settings as I suspected MC doesn't like something there.
I didn't save the iMac report unfortunately. But I attach the log
And it just crashed again...this time I got the Mac crash report. Attached
-
I have two Macs, I was using a 2020 Intel iMac with a NAS server for the music files and it couldn't survive 24 hours without crashing. I also have a Mac Mini with an Apple M1 chip and tried it instead ( I saved a backup with the iMac and restored on the mini) and same thing.....it crashed sometime in the evening hours.
Looking for suggestions.
Version 33.41 has been running for almost a day now with no issues. Fingers crossed that it is a solution.
-
My last post above claimed victory but alas, the latest version is crashing again. I shouldn't say crashing. It is hanging. If I leave MC alone doing nothing it will hang in a few hours.
-
What happens if you use the mouse? Do you see a cursor? Can you click anywhere? Can you switch to another program?
-
Dennis if it's the mac mini that's having the problems and it's running Sequoia switch off every Apple AI Option you can find.
All the early rumours/reports I've seen tend to indicate that the AI Software is a memory hog/glutton and may be trying to use more memory than anything other than a Mac with a M4 chip can provide when other apps are running.
-
It isn't Apple Intellegence.
I have tested three macs - an old Intel 2020 iMac, an M1 mini and the M4 mini. They all hang. I also tested a Raspi 5 and a Windows 11 using the same MC NAS library from backup restore and they are OK.
-
It isn't Apple Intellegence.
I have tested three macs - an old Intel 2020 iMac, an M1 mini and the M4 mini. They all hang. I also tested a Raspi 5 and a Windows 11 using the same MC NAS library from backup restore and they are OK.
I've got a Sequoia machine that I'm going to dedicate to trying to reproduce this.
First step is duplicating the setup as close as possible. Please confirm or correct the following:
Your library is on the machine that MC is hanging on, the files associated with that library are on a NAS (assumption is that the NAS is SMBFS not NFS or any AppleFS).
You aren't running as a media client. The Mac machines have their own local libraries.
You aren't running in Media Server mode.
You energy settings match the attached picture
Your System firewall is on or off??
You don't have any additional firewalls installed.
-
Test without the NAS.
-
>>>>>
I've got a Sequoia machine that I'm going to dedicate to trying to reproduce this.
First step is duplicating the setup as close as possible. Please confirm or correct the following:
Your library is on the machine that MC is hanging on, the files associated with that library are on a NAS (assumption is that the NAS is SMBFS not NFS or any AppleFS). Yes..on a Synology NAS using the methods described here
https://youtu.be/Ana0zsjS3E8?si=6R5esn6hKGrw9h6j (https://youtu.be/Ana0zsjS3E8?si=6R5esn6hKGrw9h6j)
You aren't running as a media client. The Mac machines have their own local libraries. Yes
You aren't running in Media Server mode. Yes....actually I tried both ways....with a Mac server and a Mac remote....but now I have no server. I also tested a Raspi server and a Mac remote ---
You energy settings match the attached picture Yes
Your System firewall is on or off?? Inactive -- See pic
You don't have any additional firewalls installed. Correct
Also.....I can send you the MC library backup if needed. The history of that is about a month or so ago, I thought it was something in my library and I deleted it and started from scratch. And it did the same thing. I also have used the same NAS music library with Plex and it doesn't have issues. Note in the attached picture I have both WiFi and Ethernet. I haven't tried it with just ethernet, and maybe I will do that now.
-
Trying ethernet only is a good idea. The SSDP server binds to and runs on any connected interface.
Are you using SMB or APS in the NAS mount?
-
Trying ethernet only is a good idea. The SSDP server binds to and runs on any connected interface.
Are you using SMB or APS in the NAS mount?
SMB on the NAS
I also removed WiFi. Jim had asked for a test w/o NAS so I copied a smaller folder to an external drive on the Mac and deleted the NAS from the library and am running it now (no WiFi, no NAS).
-
What happens if you use the mouse? Do you see a cursor? Can you click anywhere? Can you switch to another program?
I get the whirlybird....and can't do anything. If I minimize MC then when it hangs, I can't restore to full screen when I click on the icon. Both cases need a force quit.
I can switch to another program.
-
You energy settings match the attached picture
Correction: I have restore after a power failure enabled
-
If you are going to test without the NAS don't mess around with trying to delete its entries from the library.
Just clear the library and start over with a local folder.
If you force quit MC while it's working (spinning ball) you will certainly end up with a corrupted MC database.
-
I must have forced quit a hundred times by now.....several times a day when it hangs.
How to find a corrupted file? I think I asked this before, but isn't there error trapping in the code to flag a bad file?
Can a sidecar file be the bad actor? I was experimenting with adding an on-line album review to the NOTES in the tags and the 3 or 4 paragraphs may have exceeded the allowable length....but I can't remember which album I did that.
I already set up MC w/o NAS by deleting the NAS file folder and inporting a small local folder - I'll let MC run overnight as it never makes it that long and if it hangs, I'll try a bare bones MC library after a library Clear.
-
It's fairly likely that the problem is at the hardware level.
-
If you are going to test without the NAS don't mess around with trying to delete its entries from the library.
Just clear the library and start over with a local folder.
If you force quit MC while it's working (spinning ball) you will certainly end up with a corrupted MC database.
I tested without the NAS. I have a local SSD on a Thunderbolt 4 port and I put a few GB of music on it. I had gone into MC Files and deleted (removed from Media Center) the NAS folder in its entirety and pointed to the local folder.
The MC log and the video of the forced quit are in a separate message to Bob
Also included is a crash report -- after the above, I cleared the Library and then inported the local music folder. Then MC crashed.
-
Dennis - try connecting that local SSD to one of the M4 Mac-Mini's front USB C ports instead of the Thunderbolt 4 port.
Those 3 ports on the back of a M4 Mini are all PD type ports so some devices connected to them can get hot.
When I first got my M4 Mini I plugged an extension dock, that provides some USB2 & 3 ports, into one of the ports one the back and at the end of the day discovered that whilst the M4 mini had stayed reasonably cool the expansion dock was very hot. it's now plugged into one of the front USBC ports and it now gets no hotter than it did when plugged into the M1 mini.
-
Dennis - try connecting that local SSD to one of the M4 Mac-Mini's front USB C ports instead of the Thunderbolt 4 port.
Those 3 ports on the back of a M4 Mini are all PD type ports so some devices connected to them can get hot.
When I first got my M4 Mini I plugged an extension dock, that provides some USB2 & 3 ports, into one of the ports one the back and at the end of the day discovered that whilst the M4 mini had stayed reasonably cool the expansion dock was very hot. it's now plugged into one of the front USBC ports and it now gets no hotter than it did when plugged into the M1 mini.
I have a Thunderbolt 4 external drive enclosure with a fan so it needs a TB4 port. I also have a USB hub plugged into one of the rear ports and it doesn't get hot.
-
It's fairly likely that the problem is at the hardware level.
What hardware do you suspect? Note that I have tested three separate Macs with and without Intel CPUs and they all hang. And Windows and Linux are fine (don't hang).
PS: I think it is something with Mac Sequoia. Sequoia came out in September and I started having problems back then (my post here is early October). The Sequoia update 15.1.1 came out in November so it isn't that.
But then others with Macs would also be having issues. This is a real puzzler.
As a test, I took one of my Macs and deleted everything I could find related to JRiver including old versions in the Mac OS library and reinstalled 33 and the key with no skins --- and am testing it now.
-
Your test above is with an external drive. What was the result of the test?
Limit the test library to ordinary FLAC or similar. It could be a problem with some little used format. Keep your test narrow.
And, as Bob said, if you're routinely forcing MC to close, that may leave a corrupt database. Let it run.
Network problem or security problem...
-
I have a Thunderbolt 4 external drive enclosure with a fan so it needs a TB4 port. I also have a USB hub plugged into one of the rear ports and it doesn't get hot.
Unplug the hub.
-
Unplug the hub.
That has nothing to do with it
-
Dennis - have you looked in the Apple Mac Forums to see if anybody else is experiencing similar problems with the M4 Mini?
My setup is a bit different to yours as I have the Mini with the M4 Pro chip in it and my albums/tracks are on a 4TB M2 disc that's connected to the mini via one of the T5 rear ports while the hub is plugged into one of the USB C front ports and the only problem I've had is remembering that the power on button is on the bottom of it.
-
Dennis - have you looked in the Apple Mac Forums to see if anybody else is experiencing similar problems with the M4 Mini?
My setup is a bit different to yours as I have the Mini with the M4 Pro chip in it and my albums/tracks are on a 4TB M2 disc that's connected to the mini via one of the T5 rear ports while the hub is plugged into one of the USB C front ports and the only problem I've had is remembering that the power on button is on the bottom of it.
I have tested 3 macs......An old 2020 Intel iMac hangs as well as the M1 and M4 (the M1 doesn't have any hub).
I think it has something to do with Sequoia.
-
I have tested 3 macs......An old 2020 Intel iMac hangs as well as the M1 and M4 (the M1 doesn't have any hub).
I think it has something to do with Sequoia.
On the Intel are you also running an external drive?
I ran a test overnight without issue (M1 Sequoia with similar as possible settings).
Try turning off media network in MC. I'm wondering if you have a broken device on your network.
-
On the Intel are you also running an external drive?
I ran a test overnight without issue (M1 Sequoia with similar as possible settings).
Try turning off media network in MC. I'm wondering if you have a broken device on your network.
The intel was using the NAS and it had a usb 3 ssd for photos…not audio. I replaced the Intel with the M4 mini but it was hanging the same way. I also have an M1 mini and an M2 air laptop. I haven’t tried the laptop yet.
On your Mac…can you enable a DLNA end point?
-
On the Intel are you also running an external drive?
I ran a test overnight without issue (M1 Sequoia with similar as possible settings).
Try turning off media network in MC. I'm wondering if you have a broken device on your network.
I thought perhaps the hidden Mac library files might have a corrupted file.....so thus:
I ran a test on a Mac M1 Mini by deleting all traces of JRiver and then installing a fresh Version 33.44 I copied 4 music files to the internal SSD and created a library with them and Media Network was OFF. It ran overnight without issue.
At the same time I had my "troubled" Library (NAS music files and network DLNA endpoint) on my Mac Mini M4 but first I also deleted all traces of JRiver and reinstalled a new copy - then restored the library. It hung during the night as usual.
I also installed MC 33.44 on my wife's Mac Book M2 Air (has nothing plugged into ports) and restored my MC library (NAS Music + Network DLNA) just now and am running as a test.
After the success of the Mac M1 Mini....I enabled Media Network just now and am running a test -- still with no NAS enabled.
Results after turkey
-
I ran a test on a Mac M1 Mini by deleting all traces of JRiver and then installing a fresh Version 33.44 I copied 4 music files to the internal SSD and created a library with them and Media Network was OFF. It ran overnight without issue.
After the success of the Mac M1 Mini....I enabled Media Network just now and am running a test -- still with no NAS enabled.
Well, the mac mini hung when I enabled Media Network and DLNA. I was still using a few local music files and not the NAS. But I had chosen the DLNA end point (WiiM Ultra).
On another Mac I was doing the same thing with two exceptions. 1) I was using the NAS and although I had Media Network enabled I had not chosen the DLNA endpoint ---- and this Mac lasted about 7 hours and it is still going. I just double clicked the DLNA and played some tunes. I suspect it will hang later.
I had yet another Mac ( a laptop) with Media Network checked the NAS files were in the library but the WiiM DLNA endpoint wasn't chosen. This MC was still running after a full day and the laptop has nothing plugged into the ports.
The laptop is WiFi and the rest are ethernet.
It's beginning to look like the culprit has something to do with DLNA and Macs or maybe MC and Macs. Maybe the WiiM but there is no issue with WiiM and Windows or Linux or other Apps using the WiiM with Sequoia.
-
Unplug the WiiM.
-
Unplug the WiiM.
I have a Raspberry Pi 4 with DLNA (via software Ropieee) and I am now testing using the RP4 instead of the WiiM DLNA as an endpoint.
Update --> It didn't hang, it crashed. So I guess that rules out the WiiM. I sent the log and crash report to Bob.
-
Dennis - in the last couple of weeks Apple have released 4 betas for the next version of Sequoia in shorter intervals between beta versions than normal, hopefully that urgency is an indication that Apple are in the process of correcting whatever is causing communicating via DLNA to misbehave and give problems.
-
It's not DLNA. I don't think Apple supports DLNA. It's probably their networking.
-
It's not DLNA. I don't think Apple supports DLNA. It's probably their networking.
Im not positive but I think this all started when Sequoia 15.0 came out in September.
-
But not generally Sequoia because I am running 15.1.1 on a M2 Mac Studio and don't have a hanging issue.
-
But not generally Sequoia because I am running 15.1.1 on a M2 Mac Studio and don't have a hanging issue.
Mine occurs after many hours…..do you keep MC running?
-
Mine occurs after many hours…..do you keep MC running?
I keep the MC server running by quitting out of MC (<File><Exit> or <Cmd><Q>).
There is no need to keep MC running when I am not doing anything with it. I exclusively play music using JRemote (except when I am testing something).
Just to test, I'll let it run over night and will report back here if it hangs.
-
I keep the MC server running by quitting out of MC (<File><Exit> or <Cmd><Q>).
There is no need to keep MC running when I am not doing anything with it. I exclusively play music using JRemote (except when I am testing something).
Just to test, I'll let it run over night and will report back here if it hangs.
Thanks.
I have the music files on a NAS but it doesn’t seem to matter.
-
It's not DLNA. I don't think Apple supports DLNA. It's probably their networking.
Today I was playing to my WiiM with MC via DLNA and after a piece finished, I was slow to find another piece and the WiiM clicked off the amp with the trigger. When I played some music, the VU meter was dancing but the amp was off.
I decided to try another player. I stopped MC and used Tidal's Mac APP and chose the WiiM. Immediately, I heard the WiiM trigger the amp but before I could play music, I got a Java error from Tidal:
Uncaught Exception:
Error: WebSocket is not open: readyState 0 (CONNECTING)
at WebSocket.send (/Applications/TIDAL.app/Contents/Resources/app.asar/node_modules/ws/lib/websocket.js:450:13)
at Object.send (/Applications/TIDAL.app/Contents/Resources/app.asar/app/main/tidalConnect/websocket.js:106:16)
at startSession (/Applications/TIDAL.app/Contents/Resources/app.asar/app/main/tidalConnect/sessionManager.js:79:24)
at Object.startOrResumeSession (/Applications/TIDAL.app/Contents/Resources/app.asar/app/main/tidalConnect/sessionManager.js:100:7)
at WebSocket.<anonymous> (/Applications/TIDAL.app/Contents/Resources/app.asar/app/main/tidalConnect/TidalConnectController.js:106:35)
at WebSocket.emit (node:events:519:28)
at WebSocket.setSocket (/Applications/TIDAL.app/Contents/Resources/app.asar/node_modules/ws/lib/websocket.js:251:10)
at ClientRequest.<anonymous> (/Applications/TIDAL.app/Contents/Resources/app.asar/node_modules/ws/lib/websocket.js:1012:15)
at ClientRequest.emit (node:events:519:28)
at TLSSocket.socketOnData (node:_http_client:580:11)
And then Tidal flashed an error that "Tidal can't find the internet device" or something to that effect....it didn't display long.
Then I couldn't select the WiiM using either Tidal Connect or Chromecast
I had to reboot the WiiM.
I'm going to send this to WiiM tech support although as mentioned above, I had troubles with another DLNA hardware and it is pointing to some Sequoia handshaking error.
Maybe I'll throw it at Apple as well.
If the Java error makes sense above - let me know.
Update: Many weeks ago, as an attempt to solve the hanging problems, I disabled WiFi on the Mac. I had both ethernet and WiFi enabled and since I couldn't remember why I had both enabled, I turned off one of them. Recently, I turned it back on and got the above errors. So I disabled WiFi again and the errors went away on Tidal. Most of the hanging issues with MC above were with WiFi disabled, so this was the Tidal player only.
-
Thanks.
I have the music files on a NAS but it doesn’t seem to matter.
My media are on a NAS as well (Synology DS1918+). They are all in a folder 'music' that is mounted on my machines via SMB. If MC loses the connection to the mounted media folder that could possibly lead to a hang but I haven't tested that.
After letting MC33 run over night there is no issue in my case. It works just fine. So there is likely something specific to your setup that is related to the hangs.
-
Are any of your JRiver devices using DLNA as end points?
-
No, I try to avoid DLNA because it won't do multichannel
-
No, I try to avoid DLNA because it won't do multichannel
I have no issues with Linux MC, Windows MC, or streamers other than DLNA.
Just Mac.
-
Dennis - in the last couple of weeks Apple have released 4 betas for the next version of Sequoia in shorter intervals between beta versions than normal, hopefully that urgency is an indication that Apple are in the process of correcting whatever is causing communicating via DLNA to misbehave and give problems.
Yes!!!
You were right!!!
MC and Sequoia 15.1 are not compatible with Media Network checked. I installed Sequoia 15.2 yesterday and everything works like it should for 24 hours now!!!!
MC seems a little snappier now, as well. But I don't see what the fix was in the release notes. https://developer.apple.com/documentation/macos-release-notes/macos-15_2-release-notes
A big thanks to Bob for tirelessly staying with me & looking for the bug.
-
I'm glad to hear that updating to Sequoia 15.2 has resulted in a "Return to Normal Service"
You are not the only one who wondered if the DLNA problem had been fixed because I also couldn't find any mention of it in the release notes; since it has I suppose we can write Apple failing to mention any OS fixes/corrections down to their habit of never mentioning OS fixes/corrections in an ordinary release.
But there is another thing about that 15.2 release that had me puzzled; Apple announced the release of the IOS version of Sequoia release 2 but kept very quite about the OS release. Which I found odd since 15.2 is the release that gives users in the other countries where English is the Official Language, the UK, Australia, Canada and New Zealand, access to Apple AI.
-
I'm glad to here that updating to Sequoia 15.2 has resulted in a "Return to Normal Service"
You are not the only one who wondered if the DLNA problem had been fixed because I also couldn't find any mention of it in the release notes; since it has I suppose we can write Apple failing to mention any OS fixes/corrections down to their habit of never mentioning OS fixes/corrections in an ordinary release.
Apple doesn't support DLNA so they wouldn't fix it.
It was probably a more fundamental network support problem.
-
Apple doesn't support DLNA so they wouldn't fix it.
It was probably a more fundamental network support problem.
Yes, probably something to do with sleep and socket connections. Explains why Time Machine was broken too.
-
Yes, probably something to do with sleep and socket connections. Explains why Time Machine was broken too.
And we had the dialog box crashes.
The only thing remotely close in the Sequoia 15.2 release notes is
Fixed: Views won’t accept dropped directories if UTType.directory or UTType.fileURL are not in the list of accepted content types for drop. (138158126)
There must be more fixes not listed.
-
As an aside the Mac Mini m4 is quite the performer
JRMark (version 33.0.44 64 bit): 11022
-
As an aside the Mac Mini m4 is quite the performer
JRMark (version 33.0.44 64 bit): 11022
Dennis that's only 2,000 below the 13024 score for my Mini with the M4 Pro chip and if you look in the Benchmark thread the highest score reported for an AMD Ryzen CPU was 9532 - https://yabb.jriver.com/interact/index.php/topic,54396.0.html (https://yabb.jriver.com/interact/index.php/topic,54396.0.html)
-
And we had the dialog box crashes.
The only thing remotely close in the Sequoia 15.2 release notes is
Fixed: Views won’t accept dropped directories if UTType.directory or UTType.fileURL are not in the list of accepted content types for drop. (138158126)
There must be more fixes not listed.
Just got [maybe] related behavior.
I was playing music to my WiiM and then I got involved with something and MC sat idle for maybe a half hour. The WiiM went to sleep and when I returned to play music again, MC gave me a playback error even though the WiiM DLNA arrow was green. I double clicked the WiiM again and got the below error. I closed and restarted MC and rebooted the WiiM and same thing. Then, I went over to another MAC and tried the same thing with that MC and it worked fine.
Whatever it is, I need to reboot the Mac !!!
-
Just got [maybe] related behavior.
I was playing music to my WiiM and then I got involved with something and MC sat idle for maybe a half hour. The WiiM went to sleep and when I returned to play music again, MC gave me a playback error even though the WiiM DLNA arrow was green. I double clicked the WiiM again and got the below error. I closed and restarted MC and rebooted the WiiM and same thing. Then, I went over to another MAC and tried the same thing with that MC and it worked fine.
Whatever it is, I need to reboot the Mac !!!
If that happens again, looks to see if the IP address is the same even though IIRC you set them to a fixed lease. Right click on the zone will show the address in the list .. Device Address
BTW the wiim I have doesn't appear to have that issue and as a side effect exposed a bug in JRemote for iOS that caused a crash which I fixed in the beta JRemote.
-
BTW the wiim I have doesn't appear to have that issue
I have the WiiM Ultra......they all seem to have their own quirks.