Nova's Chromecast built-in no longer being detected
Posted by: Alley Cat on 27 June 2018
This is weird as I've never had issues until today.
The Nova is being detected by the Qobuz app for Airplay playback, but no longer for Chromecast output.
I've restarted the iPhone and the Nova (unpowered) as well as the router.
I think there's a new Naim app out today but I've not downloaded as I can't see that would make a difference.
I can't remember if I used to be disable Chromecast in the Input settings of the app, but there's no option for that now.
Very weird, the only thing that fixed it was reverting to older firmware (not even a factory restore worked).
AC,
Another data point... after reading your post I decided to log into the Tidal web-player using the Chrome browser on my PC running Windows 10. After connecting and logging into my Tidal account I tried to cast the Tidal stream to my Nova. The Nova is not showing up in the list of available Chromecast devices. I've used Chrome browser to cast audio from concert simulcasts in the past. Something seems to have changed. I recently updated the Nova to 2.6.1.
Gregg
GOlson posted:AC,
Another data point... after reading your post I decided to log into the Tidal web-player using the Chrome browser on my PC running Windows 10. After connecting and logging into my Tidal account I tried to cast the Tidal stream to my Nova. The Nova is not showing up in the list of available Chromecast devices. I've used Chrome browser to cast audio from concert simulcasts in the past. Something seems to have changed. I recently updated the Nova to 2.6.1.
Gregg
I'm not sure what happened as I was successfully using the Nova via Chromecast using both pre 2.3, 2.3, 2.3.1, 2.6 and 2.6.1.
I seem to recall someone else saying they'd had to get Naim to reinstate Chromecast as some glitch had removed their Chromecast 'licence' from Google's database.
As reverting to 2.3 fixed things, I suspect it isn'y anything specific to 2.6.1 as it's been out for a couple of weeks.
I tried on a couple of iPhones but the Qobuz app just did not see the Chromecast functionality apart from once when it seemed to try to connect but didn't - I wonder if some odd verification happens with Google's servers - I hope not, or at least not often, as this would mean you'd need always on internet (even though we generally do).
GOlson posted:AC,
Another data point... after reading your post I decided to log into the Tidal web-player using the Chrome browser on my PC running Windows 10. After connecting and logging into my Tidal account I tried to cast the Tidal stream to my Nova. The Nova is not showing up in the list of available Chromecast devices. I've used Chrome browser to cast audio from concert simulcasts in the past. Something seems to have changed. I recently updated the Nova to 2.6.1.
Gregg
I don't use Chrome and from memory (I may be wrong) casting from Chrome is more of a faff on a Mac.
I just wonder could Tidal have done something to prevent casting from the Chrome app - as illogical as it sounds they might have done so? I know certain apps and websites often on iOS prevent the user from using Airplay to send content (mainly video) to AppleTVs, and this can be controlled by tags in web page code.
No... the casting from Google Chrome browser is independent of the web-app loaded. The casting functionality is driven from the browser menu level.. has nothing to do with the web page you have loaded. You can always just go to the settings icon (a '...' in the menu bar) and select the cast option. A small window then presents that allows you to select the cast destination. The Nova has always available for selection in the past... not present at this moment. I'll try going back to 2.3 this evening and see if anything changes.
FYI,
Just did a second system reset and now Chrome browser is seeing the Nova as a chromecast device as expected. Strange.....
Gregg
Thanks, this is very odd as I've had the Nova for maybe 8-9 months and not seen this before.