To disable Google Cast you can factory default the NSS333 and then not enable it during the setup process, or use the API calls.
Have a look at thread ‘Disable google cast on ci 102’.
For anyone that’s OC, ‘Disabling Google Cast’ will get you there.
Note: this disables Spotify
What would be nice is if the guys at Naim give us some background as to why they’ve made changes to the FW and what they think the new FW brings to the listener?
At the moment I’m quite enjoying 3:11 and don’t want to go through withdrawal symptoms, when the time comes, without knowing what 3:12 is likely to bring.
Fair enough. Of course I only know so much G and I believe that being a champion for the 3.8 sound character shuts me out somewhat. But I do know that if the guys at HQ could have avoided the 3.10 debacle they would have. I have tons of respect for the guys working on this. Which brings us back to the “design or consequence” argument. MY feelings (not something that I have been told) are that it’s a consequence due to some part of the recent Stream Unlimited modules causing a challenge to sound quality. Commercial pressures and obligations mean that the guys in Salisbury have to work with what they are given. If Spotify ( purely an example) was causing an issue it has to stay. The Far East market wants ALL the features etc. Also the update train will not stop even if the best ever sounding FW was released. It’s a pickle isn’t it?
It will definitely will go better than last time. We are all prepared that FW can affect the sound - that smoothens a lot. Lots of us have arranged and adopted themselves (in different ways). I personally would like to have 3.8 (4.8) signature back in current FW releases, but I wait and see… (while enjoying 4.8 on NDS very much).
Thanks for the update, Cohen. New year it is then.
My theory is that whatever obstacles the naim developers were faced with due to the stream unlimited update, they have now had a long period of time to learn how to mitigate them. That, to me, bodes well for the next update.