Ethernet as an Input?

[Dennis from Venice]

I just saw on the Ultra Input that one of the choices is "Ethernet." What is that? Was that always there?

I am having troubles with DLNA and would love to have some other way of streaming.

 

[slartibartfast]

I just saw on the Ultra Input that one of the choices is "Ethernet." What is that? Was that always there?

I am having troubles with DLNA and would love to have some other way of streaming.

It only appears when your Ultra is connected via Ethernet instead of WiFi. It covers streaming from services, Squeezelite etc.

 

[Wiimer]

I just saw on the Ultra Input that one of the choices is "Ethernet." What is that? Was that always there?

I am having troubles with DLNA and would love to have some other way of streaming.

When a LAN cable is connected to the Ultra, its input changes from WI-FI to Ethernet.

 

[Wiimer]

I was late...

 

[Dennis from Venice]

I use JRiver Media Center on a Mac with Ultra as the endpoint via DLNA and I get daily hangs in the JRiver software. Together with JRiver's Mac coder, I've been trying to debug the source. If I use the Mac's internal speakers instead of the Ultra, it doesn't hang. So now, I'm trying another DLNA endpoint as the tech thinks it is something about the Ultra. I'm not so sure as when I use the Windows 11 or Linux versions of JRiver, it doesn't hang. So it's a Mac/JRiver/Ultra/DLNA puzzle. If I can somehow stream JRiver directly to the Ultra via ethernet and other than DLNA, that would be the cat's meow.

 

[Burnside]

Have you tried different ways of delivering the audio to your ultra from JRiver? I infer from what you say that you are using JRiver interface to “play to” the Ultra. If JRiver is also configured as a DLNA server, can you access it under Home Media Share in the WiiM Home app and play tracks from there? To extend that a little, can you similarly use BubbleUPnp on Android or mconnect on iOS to access the JRiver server and play to the Ultra without issues? Or using JRemote? While the alternatives may not be your client of choice, it might help narrow down where the issue might be.

Edit: have WiiM shed any light on why the ultra is failing?

 

[Dennis from Venice]

Right now, I have a Raspberry Pi 4 set up as a DLNA endpoint using Ropieee. The Raspi has an Allo "hat" which outputs optical to the Ultra.

So I'm playing music round-a-bout via the Opt In instead of the Ultra DLNA. Just started and won't know for a while as the hangs occur after sitting idle for hours.

I would love to try something other than DLNA but there isn't any. My next test will be to bypass the Ultra and run JRiver directly from the Mac to a DAC via USB from the Mac.

I got this from the on-line JRiver Media Center troubleshooting section on why MC hangs:

" ... With multi-threaded applications like MC this usually means that two competing threads are both waiting on the same resouce, and stuck in an endless loop. Nothing ever really "goes wrong" (as far as the application can tell), but it gets stuck.
"

 

[simbun]

In another post you said that the hang occurs on multiple macs, have they all been upgraded to Sequoia? I know Sequoia caused some issues with MinimServer but I think that was network access related.

I don't see how an endpoint can cause such a hang, all it's doing is pulling a file over http (in addition to some eventing if JRiver is also the control point). Using an external control point e.g. WHA, will simplify that interaction further.

 

[Dennis from Venice]

In another post you said that the hang occurs on multiple macs, have they all been upgraded to Sequoia? I know Sequoia caused some issues with MinimServer but I think that was network access related.

I don't see how an endpoint can cause such a hang, all it's doing is pulling a file over http (in addition to some eventing if JRiver is also the control point). Using an external control point e.g. WHA, will simplify that interaction further.

Yes...all Macs have Sequoia. One was an older Intel Mac. I have three others. An M1 mini, M2 laptop, and M4 mini. I have also had no issues with other players (Roon, Plex) not using DLNA (with RAAT and Plexamp) as well as non-Macs using DLNA.

 

[simbun]

Yes...all Macs have Sequoia. One was an older Intel Mac. I have three others. An M1 mini, M2 laptop, and M4 mini. I have also had no issues with other players (Roon, Plex) not using DLNA (with RAAT and Plexamp) as well as non-Macs using DLNA.

Were you running JRiver on the macs before Sequoia, and were they experiencing the same issue?

 

[Dennis from Venice]

Were you running JRiver on the macs before Sequoia, and were they experiencing the same issue?

This is new. I've had JRiver for may years without this issue, but JRiver also had a new version release. I went back and tried last year's JRIver version and it too hung.

I also tried sending audio to a DLNA endpoint I had on a Raspberry Pi and it crashed the Mac JRiver - thus I can safely say the WiiM is not the issue.

But I haven't convinced myself that the JRiver software isn't the issue. I'm waiting for the next Sequoia update duee soon.

 

[Dennis from Venice]

Were you running JRiver on the macs before Sequoia, and were they experiencing the same issue?

Interesting.

Today I was playing to my WiiM with JRiver Media Center 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 instead of rebooting WiiM. 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 from Tidal 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: The above error repeated even after a reboot of the Mac and the WiiM Ultra. I had both Ethernet and WiFi enabled on my Mac and when I shut off the WiFi everything worked again. I can't remember why I had both active - there was a reason for it. But for a month now I had ethernet only and recently enabled both and got the errors.