In many ways the 272 is the best thing in my life and in others it’s a major pain in the arse …
Almost daily basis the app doesn’t recognise it , meaning a full reset , I’ve read various post and still nonethe wiser , it’s Ethernet cabled in , I’m guessing it could be the virgin modem … what’s my next step chaps ?
Please can you describe your whole network setup and where cables run to/from etc, including any switches you have?
Also is this a new problem, or has it always been an issue?
Useful to add control point info as well as version numbers for both app, control point and streamer.
The “latest’ is not a version number!
When app can’t find device try connecting to the 272 website using http://(ip address) from browser on same phone/tablet as app.
The ip address you need can be found via 272 front screen/setup/factory settings/system status/IP
For example
I had the same problems and in the end decided to buy a new streamer unit, because the 272 is a 1st gen streamer and also cannot handle the highres files using the Naim app.
Anyway, with the new streaming bridge (connected to the dac/preamp of the 272) I still had some connection problems. Therefore I altered some settings in the router and switch, i.e. QoS and related solutions (using chatGPT). This was already better. I also disabled the battery saving option of my smartphone which can interfere with the network.
I guess that most 272 users face problems when using a (quit) dense network in a dynamic household environment. The best is to isolate the audio as much as possible.
Woodford,
Since I “upgraded” my 272 to firmware 4.9, the player has become much less reliable.
I now experience frequent crashes which require a hard switch off-on reboot. Most of my MP3 files now result in crashes.
Did you upgrade to 4.9, and if so, did the problem start after the upgrade?
The problems actually started with 4.8, not fixed with 4.9, and they were mentioned a few times: the player simply gets “stuck” if I try to change too rapidly from one song to another, requiring a hard restart. By too rapidly I mean I have to let one song play for a few seconds before moving to another, or if I scroll (move forward or backward) within one song to only do it once and let it start playing from that point, before touching the scroll bar again.
This happens both when playing from the local NAS, as well as Tidal. I posted somewhere before that I explicitly tested this between 4.7 and 4.8 , and the problem never occurred on 4.7.
I don’t play mp3s, on the extremely rare occasions when I do, I can’t scroll within the file, I don’t get that bar active at all, but no crashes.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.