I’m not sure of this. Streaming 96/24 multiroom from the NDX2 to the Nova and the Nova reports 96/24 as well. It might of course just be picking that up from the feed but I would hope that it reflects what it is actually playing. No way of telling what the Qb is playing but must be lower.
Multiroom is still in my app, but it no longer works after the update between my Qb2s. I can see the other Qb. I can activate it. The other Qb even lights up and the volume moves up and down with the master multiroom volume. But nothing streams. I reinstalled the app and updated the Qbs but no joy.
Thanks. How to do it with the app is clear, I use that daily. But there one explicitly selects the master which initiates the session and you choose the clients.
But in this scenario, using a single button, from the client, how does it then know it should use the Nova as a master and not another device that’s playing?
Not much help to you, but I just tested it and it works fine between my Qb2’s.
Going back to the original question, any more thoughts as to how to restore multiroom to the app for the NDX2? Strange that it is only that one that does not work. Else time to contact Naim support but I was hoping to avoid bothering them as I suspect they are getting a lot of requests at the moment.
Have you rebooted the NDX2 by unplugging it? If so, and it doesn’t fix it, try a factory reset.
If Nova is master, whatever other streamer(s) is/are doing, by way of their own streaming, if they are selected in the app (or on a screen if available), the client streamer(s) will respond to the latest command. In the case of any client it will join the multiroom hosted by (if this is your example) the Nova.
If the client is subsequently then commanded to stream on its own (a different source), the client will drop out of multiroom. No action needs to be taken via the app (or screen) in relation to the Nova.
Apart from the odd hiccup reported here and elsewhere, in a stable network, multiroom works well.
Bear in mind that only the master (if it is capable) will stream at the highest level of quality, the clients receive a lesser quality. This used to be covered on Naim’s website, alas the link that @robert_h posted a while ago on a different thread has been lost. He may be along to comment on the exact downscaling that occurs to client, while the master is unaffected.
1 Like
Thank you.
Unplugging: Yes, I have tried that - I switched off the XPS overnight which I assume should be the same thing.
Reboot: I will try that and report back.
Follow the advice from HH re unplugging. At the same time, turn off your control point completely.
Once the NDX2 is back on your network, then and only then switch on your control point.
If you do a factory reset you will loose your settings, like presets / favourites.
Not clear if its multiroom missing on app or NDX2 not finding other ‘rooms’, eg your Nova?
If the Nova finds multiroom, will it add NDX2 as client?
If not, before doing factory reset, it might be worth powering off everything, including control point and finally router. Restart router after ten minutes, wait further ten minutes then one at a time, re-power streamers and finally power up control point, which iiuc is an Android phone. In iOS there is a reset network setting for phones, if there is something similar, you could consider that. Can’t be more specific on Android, Apple here!
I’m fairly certain a lower resolution is used in the client streams….in fact, Mp3 even sticks in my memory….
I tried having a search around where I’d read about this, but cannot now find…it may have been in the ‘old’ previous version of the Uniti guides on the Naim website, I can’t remember…
Obviously, if you send out separate streams from something like the Core, that is capable of sending multiple streams at different, and HiDef, resolutions…but that’s not Multiroom/Party Mode as such….
Perhaps Client devices in a Multiroom session display the resolution of the Master they are receiving the feed from, but I have a feeling they downsample internally….I may be wrong.
I really can’t remember the details now, but I’m fairly certain only the ‘master’ device plays at the original resolution, whatever that is…As I’ve said, this is similar to Apple’s Airplay.
The ND555 White paper, last page of Specs, indicates ASRC 320k & 16/44 for PartyMode…
SC
Agree SC, I did a search and also found the ND555 white paper, but there used to be a clear description of how clients streamed against the master. Another useful reference lost on the website revamp.
I wasn’t sure it was as low as Mp3 but that may well be the case.
1 Like
Hi, I recall that 1st gen streamers send MP3 to multiroom clients.
That I can understand.
Just doesn’t seem to be clear what the current streamers are sending out and any clients are using….Going from the ND555 white paper, it would seem to suggest 16/44 WAV is the max….
SC
It’s missing on the app. No problem running it from the remote. Equally the Nova finds the NDX2 both from its remote and from the app.
I have tried the full switch everything off and then back on. But I think I will give it another go. I’m not worried about losing the presets on a factory reset but losing all the tracks and albums in favourites would be more than a little tedious (not worried about losing radio favourites).
I think that’s between green screen streamers and also with gen 1 muso/Qbs, but isn’t the case for new platform products, so Atom/Nova etc, NDX2 etc, NC. Not sure about gen2 muso/Qb.
If it’s missing from the app that may suggest the control point is the issue and it may require the reset on the phone. If Nova finds NDX2 then as you will have likely realised it is unlikely to be the NDX2.
Where are these favourites originating from, streaming service like Tidal or Qobuz or from locally stored music? If from T or Q, then these will be still be available.
One other thought, before doing a full reset. Can you utilise another Android phone from someone you know? Install the app will only take a mo and will determine if it is your control point. Doesn’t have the be the same model initially, just an Android device. Be interesting to know, if you can arrange short use, as to whether that gets you closer to what is happening.
It is also worth posting your exact Android device, version number and confirm the exact Naim app version number you are running. If you are lucky enough to find someone reading this thread has the same or very similar, it may be useful. Iiuc Android devices are quite wide and varied, so unless someone else has your device, the issue may have occurred elsewhere.
I’m not sure I understand your explanation.
Perhaps it’s easier with a concrete scenario:
- I have a Nova playing iRadio
- I have a Mu-so playing Tidal
Now on my Qb I want to do multi-room, how do I select which device it should join? Or, assuming it can’t be selected, since there’s only one button, which device does it join? The Nova or the Mu-so?
I also suspect the app rather than the NDX2. I have already tried a reinstallation but I will see if I can persuade my wife to let me play with her phone 
and see how that goes. Then try a phone reset.
Favourites are mainly Qobuz and a few from the Core so, if Qobuz stays, a reset is a viable option but I will try to solve the app first.
Android phone is a Pixel 7, Android 14 (Build AP2A.240905.003). App version is 7.1 (1109500). NDX2 version is 3.10.0 (5598).
Many thanks for your help and suggestions.
All multiroom ops starts with the master - so in your example and using the app, if you wish for the Qb to join iRadio playing on Nova, in the Nova ‘room’ or ‘device’, in other words click on Nova in the app and the at the bottom of the screen for Nova, click the playing line and on the next screen near to the volume, on rhs will be the multiroom box. Simply click Qb and it will join.
The same applies for Qb to be added to Muso streaming Tidal - repeat as above, this time using the Muso ‘device’ and add Qb as described.
When sometime later, you want the Qb to do something else or simply wish to place it in standby, you can do this directly with the unit or via the app using Qb ‘device’; no need to go to the Nova ‘device’.