Chromatic Producer I

Answered

Sonos goes haywire when using a recordplayer with sa port

26 replies
453 views

I used to have my Sonos Amp connected to my Pro-ject turntable (debut III with preamp). I moved my Amp away and recently also got a Sonos Port. I connected my turntable to the port and want to use it as an input for the record player.

But the audio keeps dropping, at some point my system goes total haywire. Most Sonos devices totally drop out and are missing from the system and after a while come back. Today it even when they came back claimed two S2 products (Ikea speakers) where incompatible with S2 and after a few more minutes they did show up normally again.

This is my setup:

Pro-ject recordplayer line into Sonos Port

Sonos Amp

Sonos Arc + Sub + 2 Sonos Ones SL

2 Sonos Ikea speakers

Sonos One

Sonos Play:1

Sonos Roam

Sonos Boost

The port is NOT connected to any receiver and just functioning as a line in for the turntable.

I try and play the line in on the Arc, Play:1 and/or Amp. Lots of drops of the sound until it all goes haywire.

When it goes haywire it seems like mostly the products who use the Boost disappear. I know my One is on the wifi network directly and so is the Port. The odd thing is my Arc also disappears and that one is wired.

Any tips or ideas what I can do?

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

Ken_GriffithsAnswer

Does your router have separate SSID’s for its 2.4Ghz and 5Ghz WiFi bands? If so, perhaps shift the Roam onto the 5Ghz band and then remove your routers 2.4Ghz WiFi credentials (if applicable) from your Sonos App network settings, leaving just the 5Ghz band in place. Also…

Set the routers 2.4Ghz WiFi band to channel 1, 6 or 11 and set the channel-width to 20MHz only.
Set the Boost so that it is at least one metre (or more) away from the router.
Set the SonosNet channel in the Sonos App so it is at least 5 channels away from the chosen router channel.

What I think may also prove helpful in this instance, is to reserve/fix all the Sonos IP addresses in your routers DHCP servers reservation table, so that on system-reboot the Sonos products will always get assigned their existing IP address.

See if those few suggestions resolve your system issues.

Show previous replies

jgatie

So the label actual means its using the Boost / SonosNet? Christ that is some unclear labeling. Glad I didn’t turn it off just to try :)

Oh I’ve not said so yet, but thank you for all the help so far.

No, the label means its Wi-Fi radio is turned on/off. The most confusion happens when someone hardwires a Beam/Arc/Amp, connects it to surrounds or a Sub, then turns off Wi-Fi because it’s wired to Ethernet. They forget that it has to connect to the Sub and surrounds via Wi-Fi.

ratty

If I understand correctly, despite all devices having “Enable Wifi” turned on (checkmark), they aren’t using the Wifi but the SonosNet signal?

@ratty will love that comment, as he has argued for a long time about the labelling in the Sonos App in relation to the devices WiFi adapters..

Quite. The “Disable WiFi” turns off the “WiFi” hardware (Sonos use off-the-shelf chipsets), but since in this instance it can only apply to SonosNet (or a home theatre’s 5GHz satellites connection) it’s infuriatingly misleading. Leave it enabled.

Airgetlam

Yes. Unfortunately. It’s what many of us have been railing against since that feature was included in the controller.

It really means “turn off all radio signals” which included SonosNet and Wifi, as well as the capability for sound bars to connect to Subs and surround devices.

I’d be a fan of removing it altogether, but I do recognize there are (very few) instances, mostly in professional installations, where it makes sense. But it’s so poorly labeled that we have this issue over and over in the forums, where people think they’re doing the right thing, based on the label, but turns out they’re not.

Bruce

ratty

I’d be a fan of removing it altogether

And go back to http://x.x.x.x:1400/wifictrl ? Bring it on. Worked perfectly, without all the “unable to disable” controller protestations.

Airgetlam

Heh. Your memory is infinitely better/longer/sharper than mine, sir. I tend to live in the moment, for better or (more likely) worse.

Bruce

jgatie

And go back to http://x.x.x.x:1400/wifictrl ? Bring it on. Worked perfectly, without all the “unable to disable” controller protestations.

Ahh the good old days, where we’d report the mention of that command and it would magically *poof* off the board.

Ken_Griffiths

So the label actual means its using the Boost / SonosNet? Christ that is some unclear labeling. Glad I didn’t turn it off just to try :)

Oh I’ve not said so yet, but thank you for all the help so far.

ha ha .. you certainly wouldn’t be the first to have switched off the WiFi adapter and wondered why things were not working. It mostly happens when folk cable a Beam/Arc etc; to a router and then switch off the adapter thinking it’s not needed, when in fact it’s needed for the wireless surround speakers/Sub to work - oddly they don’t realise their surrounds stopped working until a few days later and then wonder if their devices have a fault?

Anyhow, if you want to go onto try some of the things suggested here earlier, then you should (hopefully) find your issues will go away and things should begin to settle - reserving the IP addresses will help too.. and keeping your SonosNet channel at least 5 channels away from the router’s 2.4Ghz band will also help.

edit: I need to type faster (beaten again with my reply here) .. ha ha

ratty

So the label actual means its using the Boost / SonosNet? Christ that is some unclear labeling. Glad I didn’t turn it off just to try :)

Oh I’ve not said so yet, but thank you for all the help so far.

ha ha .. you certainly wouldn’t be the first to have switched off the WiFi adapter and wondered why things were not working. It mostly happens when folk cable a Beam/Arc etc; to a router and then switch off the adapter thinking it’s not needed, when in fact it’s needed for the wireless surround speakers/Sub to work - oddly they don’t realised their surrounds stopped working until a few days later and then wonder if their devices have a fault🤔?

It’s worse than that. If WiFi credentials are in the system -- e.g. for Move/Roam -- the satellites would connect to WiFi in the absence of the HT master’s 5GHz signal. Owing to latency variations they will sometimes work, sometimes not.

ratty

And go back to http://x.x.x.x:1400/wifictrl ? Bring it on. Worked perfectly, without all the “unable to disable” controller protestations.

Ahh the good old days, where we’d report the mention of that command and it would magically *poof* off the board.

That might have been me, wearing my old mod hat. After https://bsteiner.info/articles/disabling-sonos-wifi then why bother?

jgatie

That might have been me, wearing my old mod hat. After https://bsteiner.info/articles/disabling-sonos-wifi then why bother?

“We can’t tell you, but Google is your friend.”

Show more replies

Sign up

Login to the community