Plus 1
Hi @jstewart01
re: patches
There are two ways to make a streamer:
-
The quick way - take a reference design using latest tech, grab the “main line” code, customise it a bit, pop it in a box, certify it then sell it. Do very few software updates to it then 2 years later discontinue it and repeat around the same process. Expect all customers of old product to sell it and buy a new one.
-
The Naim way - we support long term platforms that last for well beyond the normal life of tech consumer electronics. On the software side we have to ensure that the code base has backwards compatibility, support older CPU’s (this can be tough), plus in a fast moving business often the mainline code is more about quantity, rather than quality. We have tons of bug fixes that other manufacturers don’t have, as we want the platform to be right, not just be a race to bash out the next wizz-bang tech product. We also have quite a bit of “magic sauce” as well that makes our solution far superior to the reference platform, from better audio clocking, audio buffering, different protocols to interface to the DSP etc.
Overall, Naim are in the Streaming game for the long-term, and hence we have to avoid cutting corners and doing throw away tech that gets you quick to market, but makes the customer suffer buying into a dead-end solution.
Best
Steve
This is the most reassuring thing to me. Too many play this game especially in the lower price brackets. I feel I will be able to use my Atom for many years to come.
With digital becoming such an important part of Naim. Wouldn’t it be time to move sourcing and rely on 3rd part partnerships and take more control? I assume this will continue to be an issue if nothing is changed. Obviously others do it “better”. Outsourcing is often a fast short term solution IMO and the more you get in-house the more control of it all.
Looks like they already have some degree of control, based on the number of Naim-specific “patches” in the software. Outsourcing is often times a balance, between what you get (more control, etc) and what you lose (additional investment, more people, management time and attention, need to attract talent, etc).
If control is critical to the health of the Naim platform, they should evaluate whether they have the talent to (transition/acquire/build from grounds up) and run all the bits in-house. Doing this will take effort and investment, will likely take a year or more, during which other development, features, etc will be affected.
Hi @Blackbird
In an ideal world it would be nice. But in practice often you end up reinventing the wheel + the large tech companies like Google, Apple, Amazon, Spotify etc. don’t want to be supporting and certifying lots of different platforms nowadays. They’re all focusing of that a few system integrator (SI’s) do the work and then lots of big manufacturers all benefit from a known code base. The art is to work with that SI and create something special and bring something to the relationship. In Naim’s case we’re a pretty strong software house and a lot of key features run on the Naim platform before others get it as we have the skill to debug things when the going gets tough. Many others are driven by project managers who tick a box of a wanted feature and expect it delivered, with no idea on how it works.
Best wishes
Steve
Thanks Steve - makes all sense and is the absolute right long-term strategy imho (coming from SW industry myself). But also please do not forget and put last your customers’ requirements and desires for state-of-the-art and leading UX, useability, ‘se.y’ F&Fs, plugnplay and compatibility! Naim still lacks respective quality in their SW - and in HW more and more as well, unfortunately. Compete with the best in these fields (such as apple) but not with 3rd party suppliers constraints! Naim customers are willing to pay premium prices for best in class performance - but not for regular crashes and bugs of their 555….
Hey Clare - did you get an ETA wrt this?
App updates are with Apple/Google for review; TIDAL Connect firmware update is in listening phase - that’s final phase before release…
If it pass that phase yes
It stays in the listening phase until it’s ready for release. Only when sound quality is signed off does it leave the building…
App update is available in NL… Hope the sound quality is signed off soon!
Yes, more on App update here:
Cheeky monday morning bump - are we looking for a release this week potentially? I’ve no clue how long it stays with Mr Listener… Got my fingers crossed though - a week of WFH!
I’ve got a meeting with the software team later this morning - will report back!
Still some more listening to do; if that goes well, we’re looking at launch by the weekend…
OK, so the golden ears at Naim are not 100% happy with the firmware update yet, so some tweaks to do before we release.
Incredibly frustrating, I appreciate, but i’m sure we’d all prefer a firmware that has the optimum performance, not just functionality.
I’ll continue to keep you all updated.
Thanks Clare, appreciate the update. I am naive as to what is involved with implementing this sort of update but am intrigued nonetheless. I would have thought it involved software changes so that Tidal Connect ‘works’, ie, more an operational update so that the unit can receive the file from Tidal, rather than anything that influences sound quality as such. Are you saying that Naim can tweak the update in certain ways so as to bring a certain SQ with it? I may be misunderstanding what you are saying so am curious to clarify.
Software code is a complex series of interactions; you don’t just ‘plug in’ the TIDAL Connect bit (wish it was that simple). Any changes can affect the whole, including sound quality. Therefore the final stage of every software release is ensuring everything sounds as it should, and making adjustments if it doesn’t.
It would be fascinating to get a “peek” into this listening part of the process. Essentially, a bunch of experts are “auditioning” the new release - we may be able to get some good tips for when we replace/upgrade gear.