Poor or Lack of Bit Depth / Sampling Rate / Bit Rate on NAD M10 (V2)
Beantwortet
Hi all, I bought a NAD M10 V2 recently and wonder if the same issues below are present on other NAD or BluOS devices.
This NAD (running the latest BluOS 3.20.28 as of this writing) has a beautiful touchscreen but its most essential "Album/Track info" screen has a few odd limitations.
At first glance, it's nice to have all the following display options available:
- Source (Detailed)
- Source (Simplified)
- Album, Text and VU
- Album and Text
- Album Only
- Analog VU Meter
- Digital VU Meter
- Text Only
When only after buying the device and setup the source, then I realize the following issues that are not documented anywhere on the BluOS support pages, NAD manuals, or online reviews:
1. Only the "Source (Detailed)" selection, which is only one out of eight options actually shows track info. See attached example: 
2. But this "Source (Detailed)" display option does not show bit depth or bit rate when playing MQA.
3. There is another "Now Playing" screen which shows more track info. But the first issue is, it can only be activated by a tap on the screen, after which it just "times-out" after a few seconds, and turns into one of the eight options listed above.
4. The second issue is that even this "Now Playing" screen also lacks bit depth, bit rate and sampling rate info. I have attached a screenshot here which shows potentially where this information can go. 
Overall, it seems either BluOS is very limited or NAD designed this poorly. If you look at competitive (and in some case, cheaper) products like Wiim and Volumio, they don't have these issues.
I look forward to feedback from other users who are more experienced with BluOS.
-
@Matt S - Bluesound Product Manager
Are my issues posted above for NAD M10 V2 related to the "app overhaul" that you mentioned in this thread?
If yes, thanks for acknowledging community feedback and working to improve the interface. I can't wait to see your results!
1 -
@Seppi Evans, thanks for the information, I have sent NAD an email with the above details.
I hope they reply!
0 -
As advised, I contacted NAD about the above issues.
Thumbs up for their tech support for being very polite. 👍
However, they don't have an explanation why the issues exist and also can't promise whether they will enhance future firmwares to address this issue.
So basically it's a non-answer answer.
To all future NAD M10 or M10 V2 potential owners, you can make your choice whether this is acceptable to you.
For me, I wish I hadn't bought the NAD M10 V2, now that I know these limitations that were not documented anywhere before.
1 -
Update: Since I posted my last comment, after upgrading to BluOS 4.02, the lack of bit rate and bit depth issue has become worse.
Now, it won't even show up when playing Roon in the "Detailed" screen.
What's going on, BlueOS and NAD teams?
0 -
I am considering buying the NAD M10 V2 or the CA EVO 150. Has this issue been addressed now on the NAD or is still present? I assume no.
I know it sounds, and probably is, minor but when you are paying £2,000 and comparing different units some details like that adds to the equation. Is not so much about lack of the feature, is also about appetite to add it.
0 -
By. “appetite” if you mean the lack of demand then yes it’s entirely possible not enough people are buying M10 V2 to warrant paying for engineers time to add features.
but NAD needs to keep in mind that these posts that are ranked high google searches are also turning off future buyers.
These lack of initiative or confirmation from NAD to commit and add basic features that any audiophile would want may create a vicious cycle that’s not good for anyone.
0 -
By lack of appetite I meant the lack interest from NAD to implement this. But for sure it depends if its a popular request or not. That part I cant comment, if its only me and you that want this or others, and what is their market share on this type of product.
Unfortunately with ALL products (GoPro for action video recording, DJI for drones, Stages for Smart Bike Cycling, UniFi for networking) I have interest and own there is a long list of fundamental feature requests/enhancements (with very strong demand from many) and most of these dont get implemented, so it does seem to be the norm :-( . It feels like they create a product and only focus on bug fixing.
0 -
I received today my NAD M10 v2, to my positive surprise I noticed that in the Source (Detailed) screen is showing the format name (e.g. FLAC, MP3 etc.) the bit depth and the Sampling Rate. My unit is running BluOS 4.2.6.
What would be a nice addition and more effective is to have the same exact details in all the screens that the Albut/Text is showing rather than just the Source detailed screen only. I already sent an email to NAD asking for this.
0 -
Hi all.
As already mentioned by Seppi Evans, the right thing to do is to send a request directly to NAD Support: support@nadelectronics.com
They will review and prioritize accordingly.
0 -
I just checked BluOS 4.2.6 on my NAD M10 V2, the bit depth/rate info still does not show when using Roon Ready, which is what I use almost exclusively.
Maybe it shows when using Amazon or TuneIn, but I don't use both of these services. I actually just tested Spotify, it doesn't show bit depth/rate either.
0 -
Just checked with both Spotify and Tidal, on Spotify does not show anything as you say, not an issue for me as I mostly use AM Unlimited and that works fine. However I also checked with Tidal as I am on a Free Trial Period with the HiFiPlus package and there you can see the details, similar to AM.
0 -
Spotify is usually 320 but often reports as VBR (variable bit rate).
0 -
@Tony W. I can understand why BluOS doesn't bother to show Spotify's bit rate and bit depth, but Roon is audiophile-level service. For an audiophile-level device like M10 V2, it is not acceptable to omit this information when using Roon.
Will this be fixed? I asked because in previous versions of BluOS, bit rate and bit rate are being displayed by M10 V2.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
13 Kommentare