iPad Mini 2 won't play from Nucleus but iPhone 14 does (ref#VC6Y3Q)

What best describes your playback issue?

· Music doesn't start when I press "Play"

What type of Zone is affected by this problem?

· *Directly-connected Zones* are affected.

Does the issue affect all file formats?

· The issue affects *multiple/all* file formats.

Does the issue happen with local library music, streaming service music, or both?

· *Only streaming* music is affected.

Please select the streaming service(s) with which you're encountering playback problems.

· Qobuz

Have you tried logging out and back in again to your streaming service in Roon Settings?

· Logging out and back in had no impact, the issue remains

What are the make and model of the affected audio device(s) and the connection type?

· Roon Nucleus to PS Audio Directstream DAC Mk 2

Describe the issue

My ipad mini 2 running ios 12.5.8 won’t play from my Roon Nucleus but will from my iPhone 14

Describe your network setup

Wireless from ipad to Nucleus. Everything else is wired.

Roon works on my old iPad, albeit with an older version. Try removing Roon from your iPad and then reinstalling the app.

Thanks. I will try that. I’m also wondering if the problem may be compatibility of old iPad and Qobuz.

Hi @kenneth.goetz,

Thank you for your post.

Can you please clarify whether you’re playing to the iPad as a Zone (the iPad system output or speakers) or simply using the iPad to control playback on the PS Audio Zone?

Logs show two corresponding events:

First, the session between the iPad Remote and the Nucleus goes stale because of a network change event. The Remote reconnects to the server.

Around the same time, the PS Audio also loses contact with the Nucleus because of a network change event. RoonServer and RAAT need to reinitiate a session with this Zone.

03/09 19:56:43 [Local 03/09 13:56:43] Trace: [raatserver] [RaatServer localhost @ 192.168.1.132:9200] lost client connection. Retrying(0)
03/09 19:56:43 [Local 03/09 13:56:43] Trace: [raatserver] [RaatServer localhost @ 192.168.1.132:9200] connecting (attempt 1)
03/09 19:56:43 [Local 03/09 13:56:43] Trace: [raatserver] [RaatServer localhost @ 192.168.1.132:9200] connected
03/09 ...
03/09 19:56:44 [Local 03/09 13:56:44] Trace: [raat_ll/client] [PS Audio Extended Resolution US] OnDisconnected: BeginRead read count is 0, socketerror is: Success
03/09 19:56:44 [Local 03/09 13:56:44] Trace: [raatserver] [PS Audio Extended Resolution US] lost client connection. Retrying(1)
03/09 19:56:44 [Local 03/09 13:56:44] Info: [raatserver] [PS Audio Extended Resolution US] connecting (attempt 1)
03/09 19:56:44 [Local 03/09 13:56:44] Info: [transport] destroyed zone DSD was playing? False
03/09 19:56:44 [Local 03/09 13:56:44] Trace: [zone DSD] Suspend
03/09 19:56:44 [Local 03/09 13:56:44] Trace: [raat_ll/client] [Nucleus HDMI B] OnDisconnected: BeginRead read count is 0, socketerror is: Success
03/09 19:56:44 [Local 03/09 13:56:44] Trace: [raat_ll/client] [Nucleus HDMI A] OnDisconnected: BeginRead read count is 0, socketerror is: Success
03/09 19:56:44 [Local 03/09 13:56:44] Warn: [raat_ll/client] [PS Audio Extended Resolution US] failed to connect(0) Connection reset by peer

Playback is queued and prepared to begin on both the iPad speakers and the PS Audio when this occurs. Only the PS Audio is actively playing. From the user interface, this would have the effect of the PS Audio Zone visibly disappearing as you attempt to begin playback to the Zone while controlling from the iPad.

This would ultimately be a question of the network connection between the Nucleus and the PS Audio Directstream itself, since the iPad isn’t involved in audio transport.

Do you have a mesh network or any managed switches in this setup? We can advise a few settings recommendations to prevent these dropouts from recurring.

Hi @kenneth.goetz,

We haven’t seen a response yet so we wanted to ensure you’d had a chance to review the post above. Please let us know if we can provide further assistance. Thank you!

Thanks - I got it working

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.