So as I’ve said it is likely that the major Streaming Unlimited Titanium update have messed things up (Naim streaming board) in some way which some claim they hear. And when you bypass this SU section with say Lindemann Bridge going into SPDIF (Digital IN) you bypass this section and go directly into the DSP onto the DAC. Dan have the possibility to evaluate this and we know others that have bypassed the streaming section have experienced more stable positive results. Look at the last row of the SU update below. I’m not sure what’s in the " NXP Audio Framework v3 4.0.0" which seems major. Anyone?
So what about the service updates?
This release contains important updates for Chromecast built-in 2.0, Spotify Connect, TIDAL Connect and the NXP Audio Framework. They’re not just about making StreamSDK better, but making it Titanium-solid, ensuring readiness for certifications. Let’s get into it!
Google Chromecast built-in 2.0
Now upgraded to version RC10 for an unparalleled casting experience.
USB audio Soundcard Input Support for Stream1955
Titanium now enables USB-audio soundcard input support for all Stream1955 music software builds. Simply use the USB Type-B port on your StreamKit1955 and select USB-audio in the StreamControl App for seamless playback convenience. Piece of cake!
Spotify Connect Update
Our Spotify Connect integration receives an upgrade to the latest eSDK, ensuring optimal compatibility and functionality for Spotify Connect users.
TIDAL Connect
TIDAL Connect now includes Hi-Res for TIDAL Max subscribers, providing audiophiles with an unmatched streaming experience.
NXP Audio Framework v3 4.0.0
Experience enhanced audio performance and stability with the latest iteration of the NXP Audio Framework version 3 4.0.0.
Major Codebase Rework for STM32 Host Controller
Witness a significant revamp with STM32 host controller; we’ve undertaken major codebase rework for improved efficiency and reliability.
And of course, there are the bugs…
At StreamUnlimited, we’re all about creating the best user experience. We continuously monitor and address any bugs or issues that arise, and that’s why our partners choose us.
Hi, the ethernet connection and WLAN connection goes to the NP800 network protocol module (‘Naim streaming card’ in the diagrams) That in turn connects to the digital board via LVDS along with other non network digital sources. The data is then switched, processed and adjusted by the SHARC DSP processor to be sent to either the digital audio output or the DAC i2s interface and then via the i2v stage to the streamer analogue audio output filter.
The firmware tuning that Naim sometimes undertake, takes place on the digital board and is associated with the ARM code ‘do nothing’ states.
This is exacly the same conclusion that I reached @drago regarding 3.10.1. I would roll_back to 3.8 in a heartbeat.
That is why I was very very cross indeed that Richard Dane prematurely closed down the ‘Unhappy Thread’.
Let’s be perfectly clear here. I am referring specifically to a 500 system with an ND555 at the front end.
I am very glad that folk with systems less revealing and sensitive are happy with 3.10.1. But please refrain from offering 500 system owners advice without having actally having experience of such a system sitting in your listening room. I have owned Naim systems since 1999, and held listening/red wine drinking sessions with senior Naim engineers in my own home. Over the years I hopefully picked up a few useful insights to what makes those Olive and Black boxes special.
As an aside; replacing the SL between 555 and 552 with Chord Music will dampen and calm the sound signature making it more organic. But personally that change proved detrimental with 3.8. I doubt it would solve the issues with 3.10.1…just cover them up in a warm blanket.
If you are interested please listen to She’s lost control by Joy Division from Substance on Qobuz Hi_Res. On 3.8 it was a aural joy, now it is ragged, sparkly and harsh. I can no longer tolerate the High Res track and have to revert to other versions.
Unfortunately after the experience with 3.10 I have lost faith in Naim. Thankfully when we downsized I moved to active speakers, so it should be fairly staightforward to flog on a few black boxes and head off in a new direction. However I am very sad about the not insignificant number of hours I spent honing the sound of my system over many years. A big shout out to drago Geko, Blackbird, Simon-in-Suffolk, Darkebear, GrahamH for their invaluable insights over the years and aplogies to anyone I have overlooked.
Best of luck to all ND555 Owners. For those of you who are not entirely happy, it is a significant expenditure that could have been preserved with the availablity of a relatively simple roll_back.
Sorry you were extremely cross when I closed the old thread. It was important to do so as it was to do with criticism of the old firmware that is now superseded by the latest release. Otherwise, everything gets very confusing for everyone trying to make head or tale of it. For the new firmware, a new thread is appropriate, and I see someone has started it already.
As for rollbacks, I will repeat once again here just for you, Naim cannot and will not roll back. For a few very good reasons; for one they are obligated by their streaming service partners (this will likely apply not just to Naim) not to do so. This is a lot to do with functionality, and when issues arise when customers are running older firmware, support becomes tricky and the first thing to check is that the FW is fully up to date, second is the app up to date. Get these two out of “synch” and things can get really clunky. Also bear in mind that with the last big FW release came a major new functionality - Naim Radio. This is a new in-house radio provider and should be a nice step up over the old Vtuner service. Maybe internet radio is not important to you, but if it is, then this is a very good reason not want to roll back.
The trouble is it’s dead easy for me to switch out the Shunyata to either BJC, Catsnake, C-stream, or stock stuff. With any changes I tend to try stepping back even with the SMPS and LPS’s I have.
I had a go this morning and as soon as I remove the Shunyata the loss of resolution, image width, timing and timbre is massive. And I mean massive!
I’d definitely like to have a play with some of the Ansuz stuff as I like their approach, and I think I’ve found a stockist not to far away from me, so might have a chat to them.
Thank you for this detailed explanation. I for one am very impressed with the update. Instead of critically listening to certain parts of of a song, I’m listening to the whole of the music. For me, I find it very satisfying.
Thanks Richard, appreciate the response. Apologies for getting bent out of shape over this issue. There are other things in life more important than hifi.
Wtf. I just updated my firmware and it sounds like i have new equipment listening to the jazz groove, not in a bad way. This is wholly unsettling. I have been listening to my system lately thinking it was a little flat or dry. Inwas actually thinking about downgrading the whole thing. Well thats off the table im a little concerned that naim can screw around with sound…
I really don’t believe the SR Sigma has any correlation with the sound signature issues we are experiencing. If anything the Sigma is revealing the perceived deficiencies of the FW updates.
As I offered on another thread; The SR Sigma provided the most significant upgrade to my streaming chain.
Richard, not knowing too much about the firmware issues, i was thinking about switching to a linn selekt or some other brand. For real, my system just didnt have the same juicy tactile sound that i bought it for. I wasnt sure if it was my speakers or where the lack of dimensionality was coming from. Maybe i just got fatigues with it. The update has cast almost all of those feelings aside. Naim needs to be alerted of this, based on the previous thread which i didnt pay much attention to- id guess they are aware. I hope they still care.
I don’t think people are listening critically. It’s just very annoying to listen to a nice part of a track where for instance the lead vocals sound harsh or lacking naturalness. It spoils the entire track.
It’s like eating a wonderful piece of cake and find in the middle some hair.
You will not be capable to retain only the delicious beginning.
I encountered that with the Farad ps on my ex Etheregen switch. 75% of the time the sound was excellent. But often, on certain instruments or parts of some tracks, the sound was a bit glassy and not comfortable to listen to.
I was unable to really relax. Each time I was fearing it will happen again at a certain moment.
If you press the clock symbol to the right where posts are counted and select “MUTE” the thread will go away and you will not be pinged. Same option is available all the way down on the thread page.
I understand, Richard, but from the point of view of those affected, that’s not good news (I am not among those). I was wondering if Naim couldn’t do what Apple is doing, namely allowing roll backs (they call it something else) for a limited period of time. Say, one month. Then, no more roll backs. And call it “pre-release”, so it’s not running awry of contractual agreements. Surely, it’s not good for Naim to have people unsure whether to ever upgrade in fear their systems would not be good enough for them after a FW update. That might lead to a prisoner dilemma kinda situation. Just a suggestion…
I really feel for you. That said, at the risk of sounding like a broken record, there are two things to keep in mind: (1) there is no fixed point/gold standard we have access to, (2) everything interacts. (1) is critical because for all you know the most lovely track in your favorite FW is actually not the sound that was recorded, which was too harsh because of the engineering/room acoustics. With every change in my system (and now FW) (and I have been a NAIM owner since June 1982), some tracks get better sounding, some worse. So, you don’t know what any track SHOULD sound like (except of course if you can compare to the live even). (2) is critical because your favorite cable MIGHT be the cause of the problem which the new FW release reveals OR not. And again you have no way of knowing. And it might be any other of the 20 variables at play (room acoustics, …). Now, the solution to me, as I think it’s not sustainable for FW updates to screw people’s sonic experience that much, is for NAIM to allow for a limited-time rollback and call the FW a “pre-release” for a month or so, on the Apple model (they don’t call it pre-release, though, as they don’t have contract with outside companies), as I have suggested to Roger. Hope to be helpful, even when I fail :).
Possibly a bit over my head, sorry! Just for my clarity, if I fire a download via ethernet from my hard-drive will it be influenced by say the Naim 3:10:0 firmware before it gets to the DAC or will it remain untouched?
