no UPNP after failed iRadio attempt :-(
Posted by: Lorenz on 18 August 2013
the issue of non-working iRadio has been discussed in length in this thread...
https://forums.naimaudio.com/to...rnet-radio-on-n172xs
Unfortunately - which is much much worse for me - switching to that nonworking iRadio disabled UPNP :-(((. UPNP behaves crazy after the switch. Toggles between servers/folders randomly with no playback available at all.
Powering NAIM devices down up again stops the voodoo and re-enables UPNP.
Same issue for me on a Unitiqute 24/192 and a NAC-N 172XS - both running 3.21 – no matter if connected via iOS app op IR remote (so no app issue).
As other have mentioned THIS faulty behavior in "the other" thread we should bring this up to NAIMs attention separately I guess...
Cheers, Lorenz
PS more than half a year delay, no seek2time on aac, no working iRadio, flawed UPNP - guess this is the rigourously 3.21 testing people talked about all the time...
Exactly the same thing happened to me. I turned the SuperUniti off and on and music was restored. Failure of iRadio really should not stop everything else.
And of course Apple, Microsoft, Google and Adobe never have any issues do they? And they're just tiny companies with miniscule resources available and no history of software development at all.
If it's troubling you that much Lorenz send a message to Naim support and ask if they'd be so kind as to double the cost of Naim streamers so they can hire more people to ensure that their products work with absolutely everything out there under all circumstances.
Or perhaps can we get things in perspective. Every computer in the world has glitches and power cycling as a 'fix' for an 'unresolved' issue is pandemic. Get over it people. Stick a CD on or some vinyl or try FM or DAB(+).
Andy
UPDATE: the issue does ONLY exist (in my case at least) when multiroom is enabled. if I switch multiroom off at either the Unitiqute 24/192 or the NAC-N 172XS switching between iRadio (which by it self does not work at the moment) and UPNP works. At least it does not trigger the devices into a state where only full power down and power up again resolves the issue. still very very annoying.
And of course Apple, Microsoft, Google and Adobe never have any issues do they? And they're just tiny companies with miniscule resources available and no history of software development at all.
If it's troubling you that much Lorenz send a message to Naim support and ask if they'd be so kind as to double the cost of Naim streamers so they can hire more people to ensure that their products work with absolutely everything out there under all circumstances.
Or perhaps can we get things in perspective. Every computer in the world has glitches and power cycling as a 'fix' for an 'unresolved' issue is pandemic. Get over it people. Stick a CD on or some vinyl or try FM or DAB(+).
Andy
Sorry but these issues are pretty poor from a software development perspective. It is fairly basic systems testing to test what happens if a service is not available - in this case the server that the Naim IR enabled devices link into is either not available or is having problems. One would expect there to be a timeout within the software and for the failure to connect to not affect anything else. Instead it would appear that it affects other parts of the system such as UPNP.
and this is not the only software issue - there is a new version of NStream coming because of interoperability problems with different firmware versions. Again this smacks of poor systems testing.
As for your comment about re-booting systems - not sure what software you use but both Mac OSX Mountain Lion and Windows 7 Pro x64 that I use - I cannot remember the last time I had to reboot them to resolve a problem.
UPDATE2: as NAIM corrected the faulty iRadio connection (see the other thread mentioned above) yesterday this problem disappereared as well. case closed.
And of course Apple, Microsoft, Google and Adobe never have any issues do they? And they're just tiny companies with miniscule resources available and no history of software development at all.
If it's troubling you that much Lorenz send a message to Naim support and ask if they'd be so kind as to double the cost of Naim streamers so they can hire more people to ensure that their products work with absolutely everything out there under all circumstances.
Or perhaps can we get things in perspective. Every computer in the world has glitches and power cycling as a 'fix' for an 'unresolved' issue is pandemic. Get over it people. Stick a CD on or some vinyl or try FM or DAB(+).
Andy
Sorry but these issues are pretty poor from a software development perspective. It is fairly basic systems testing to test what happens if a service is not available - in this case the server that the Naim IR enabled devices link into is either not available or is having problems. One would expect there to be a timeout within the software and for the failure to connect to not affect anything else. Instead it would appear that it affects other parts of the system such as UPNP.
and this is not the only software issue - there is a new version of NStream coming because of interoperability problems with different firmware versions. Again this smacks of poor systems testing.
As for your comment about re-booting systems - not sure what software you use but both Mac OSX Mountain Lion and Windows 7 Pro x64 that I use - I cannot remember the last time I had to reboot them to resolve a problem.
Agreed scillyisles. Spot on. Not sure why Andy feels heed needs to make excuses for naim's poor radio streaming track record. Don't get me wrong, I love the 320k iRadio streams on my naim gear... when it works. Which unfortunately is not very often. Frustrates me to no end that naim makes such good sounding gear but seems rather clueless on the software side and frequently releases buggy not ready for primetime software to the public.
And of course Apple, Microsoft, Google and Adobe never have any issues do they? And they're just tiny companies with miniscule resources available and no history of software development at all.
If it's troubling you that much Lorenz send a message to Naim support and ask if they'd be so kind as to double the cost of Naim streamers so they can hire more people to ensure that their products work with absolutely everything out there under all circumstances.
Or perhaps can we get things in perspective. Every computer in the world has glitches and power cycling as a 'fix' for an 'unresolved' issue is pandemic. Get over it people. Stick a CD on or some vinyl or try FM or DAB(+).
Andy
Sorry but these issues are pretty poor from a software development perspective. It is fairly basic systems testing to test what happens if a service is not available - in this case the server that the Naim IR enabled devices link into is either not available or is having problems. One would expect there to be a timeout within the software and for the failure to connect to not affect anything else. Instead it would appear that it affects other parts of the system such as UPNP.
and this is not the only software issue - there is a new version of NStream coming because of interoperability problems with different firmware versions. Again this smacks of poor systems testing.
As for your comment about re-booting systems - not sure what software you use but both Mac OSX Mountain Lion and Windows 7 Pro x64 that I use - I cannot remember the last time I had to reboot them to resolve a problem.
Agreed scillyisles. Spot on. Not sure why Andy feels heed needs to make excuses for naim's poor radio streaming track record. Don't get me wrong, I love the 320k iRadio streams on my naim gear... when it works. Which unfortunately is not very often. Frustrates me to no end that naim makes such good sounding gear but seems rather clueless on the software side and frequently releases buggy not ready for primetime software to the public.
When I was about a tenth of my current age, I used to wonder why, when I woke up in the morning, dying to use the bathroom, my equipment rigidly resisted being aimed appropriately. I presumed this was due to the high pressure causing a bloating of the pipes.....
Similarly, when I updated N-Stream and to 3.21 and then found that my Unitiqute was playing up, I was sure it was one/both updates causing the damage.
It turns out that my rigid equipment was the result of nocturnal dreams and that the radio-server coincidentally went down, playing havoc with iradio on all Naim equipment, regardless of age of update