1 (edited by Quadrangulator 2025-02-02 01:44:33)

Topic: Bluesound Node Nano enabling ADI-2 Pro FS R BE B/T

My Bluesound Node Nano appears to be enabling my ADI 2's Bass / Treble when either manually skipping to the next track or when the next track begins playback on its own.

This happens with Tidal and Amazon Music HD in the BluOS Android app and the standalone Tidal Android app via Tidal Connect over SPDIF optical and USB.

This does not happen from Windows via USB or optical with either app.

Any ideas why this might be happening?

EDIT: Furthermore, the Bass / Treble Enable toggle does not seem to save with the preset (and does not mark the preset name as dirty (changed), though the gain, frequency, and q settings do, even Load with EQ enabled. I wonder if Enable toggle's lack of stickiness is the issue here.

2 (edited by KaiS 2025-02-02 15:29:21)

Re: Bluesound Node Nano enabling ADI-2 Pro FS R BE B/T

See next posting first.

This bevavior ask for a full factory reset of ADI-2:

While powering up, push and hold the VOL button (NOT the VOLUME dial) and Encoder 1 and Encoder 2, until you see the message: “Reset done“.
All user Setups and EQ Presets are deleted.
Take notes before, or store them through the Remote App, if you want to keep some.

3

Re: Bluesound Node Nano enabling ADI-2 Pro FS R BE B/T

This behaviour sounds more like an outdated firmware, as such issues had been fixed earlier. Note to OP: the change happens with sample rate changes.

Regards
Matthias Carstens
RME

4 (edited by Quadrangulator 2025-02-02 23:27:17)

Re: Bluesound Node Nano enabling ADI-2 Pro FS R BE B/T

Thanks for the replies, KaiS and MC.

However, neither suggestion worked. I've re-installed the firmware — I was on 267 already, which is the latest for my Hw Rev 6 unit — and also factory reset the device. However, the Bass / Treble still enables with certain tracks (I think it is either bit depth or sample rate change that triggers it, not sample rate change only).

As far as I can tell, this only happens when "Load with EQ" is enabled for the Bass / Treble shelves.

As for the hardware revision of my ADI-2 Pro FS R Black Edition, if mine is Rev 6, is this bug fixed in the latest firmware available only for Rev 7?

Additionally, What would be the difference in the hardware between Rev 6 and Rev 7? I purchased this ADI-2 brand new from a major retailer in the United States a couple of months and figured it was the latest version available.

Thanks!

EDIT: I looked at this thread about the differences between the various ADI-2 models...

https://forum.rme-audio.de/viewtopic.php?id=32506

... and I think have the ADI-2 Pro FS R BE released in 2020 because I have the Slow LD filter available. Does the latest revision of this have a newer FPGA, perhaps updated post AKM fire? Either way, would the latest revision still use the AKM 4493 chip?

5 (edited by ramses 2025-02-03 00:19:09)

Re: Bluesound Node Nano enabling ADI-2 Pro FS R BE B/T

If you see "ADI-2 Pro FS R BE" at the front of this unit, then you have this device.
It was shipped with the new MRC remote and has the AKM4493 converter with "SD LD" D/A filter.

https://www.dropbox.com/scl/fi/r7jsc6dji777m7wjukyyk/2025-02-03-ADI-2-Pro-FS-R-BE-How-to-recognize.jpg?rlkey=9qzdwk1ndisbuzyzcnper8u0n&st=fwr9p38y&dl=1

BR Ramses - UFX III, 12Mic, XTC, M-1620 Pro D, RayDAT, ADI-2 Pro FS R BE, X10SRi-F, E5-1680v4, Win10

6 (edited by Quadrangulator 2025-02-03 02:27:30)

Re: Bluesound Node Nano enabling ADI-2 Pro FS R BE B/T

Thanks, and the above is what I have. But I wonder why I'm unable to update my firmware beyond 267. Was there an updated version to this updated version?

7 (edited by ramses 2025-02-03 11:19:18)

Re: Bluesound Node Nano enabling ADI-2 Pro FS R BE B/T

Now I see what you mean, I was focused on model differences based on product name and features and thought there was only a misunderstanding, what product you have.

So, we both have ADI-2 Pro FS R BE, HW Rev 6, with the latest firmware - DSP v128 -
which you can see during power-on in the display.

BR Ramses - UFX III, 12Mic, XTC, M-1620 Pro D, RayDAT, ADI-2 Pro FS R BE, X10SRi-F, E5-1680v4, Win10

Re: Bluesound Node Nano enabling ADI-2 Pro FS R BE B/T

Thanks for clarifying, and yeah, it looks like we have the same ADI-2. I am also on firmware 267, DSP 128. But the firmware installer readme says "Hw Rev 7" has firmware for the FPGA up to version 412.

Is the sample rate change enabling B/T EQ issue I am experienceing fixed in firmware above 267 only?

If so, is it possible to have this fixed in a firmware for Hw Rev 6?

If fixing this in Hw Rev 6 is not possible, how would I know if I were purchasing an ADI-2 DAC FS R BE Hw Rev 7? Either way, what is the difference between Hw Rev 6 and 7?

9

Re: Bluesound Node Nano enabling ADI-2 Pro FS R BE B/T

This sounds more like a misunderstanding of what these options do. Last time we had this topic here was 2022.

If a reset (aka sample rate change) happens, the unit reloads all EQs  If Load B/T with EQ is active then it will correctly activate B/T.

If you want a different default state then simply save it as such, either without B/T or with them set to 0 dB (aka bypass).

Regards
Matthias Carstens
RME

10 (edited by Quadrangulator Yesterday 09:56:32)

Re: Bluesound Node Nano enabling ADI-2 Pro FS R BE B/T

Ahhh, I did not know the EQ reloaded on sample rate change. I assume that is required for the DSP to function correctly, otherwise the audio and DSP would be operating at different sample rates (probabaly not a good time).

For the B/T controls, I'll play around with the options and figure out what works best for my use case — now that I understand the EQ reloads with SR change, this makes sense.

I am, however, still curious about the Hw Rev 6 vs 7. Is there any practical difference between these versions of the ADI-2 Pro FS R BE?

11

Re: Bluesound Node Nano enabling ADI-2 Pro FS R BE B/T

Not at all.

Regards
Matthias Carstens
RME

12 (edited by KaiS Yesterday 14:49:26)

Re: Bluesound Node Nano enabling ADI-2 Pro FS R BE B/T

On my (1. Gen) Silverface ADI-2 Pro firmware V.122, and my ADI-2/4 Pro SE firmware V.35 I can‘t replicate this.

A sample rate change (44.1, 48, 96, 192 kHz tested) does not activate a switched off B/T, even with the option:

• EQ / EQ Enable/Presets / [current output] / Load B/T w. Preset: “ON“


When SR changes, the ON/OFF-state of EQ and Bass/Treble just stays as it was set by me.
Everything else wouldn’t make sense anyway.

13

Re: Bluesound Node Nano enabling ADI-2 Pro FS R BE B/T

Try the same by loading a saved EQ Preset that has 'Load with' and 'B/T' enabled, switch off B/T, change sample rate.

Regards
Matthias Carstens
RME

14 (edited by KaiS Yesterday 17:50:52)

Re: Bluesound Node Nano enabling ADI-2 Pro FS R BE B/T

MC wrote:

Try the same by loading a saved EQ Preset that has 'Load with' and 'B/T' enabled, switch off B/T, change sample rate.

You‘re right, now I can reproduce the bug.
Should be fixed IMO.

ADI-2 shouldn‘t “decide” on it’s own what DSP processing shall be active.
I just didn’t stumble across this, because I don’t use the EQ this way.

Re: Bluesound Node Nano enabling ADI-2 Pro FS R BE B/T

A bit of additional context...

My EQ was loaded with saved presets and B/T load with EQ was enabled when B/T would turn on after a sample rate change when B/T was disabled.

My use case is that I have unique EQ's for different headphones...

For example, I use the parametric bands use independant left and right channel settings to compensate for per-ear hearing loss and headphone driver differences while the bass and treble shelves I use for general headphone tuning.

Each headphone has a different B/T setting, but in general the bass is increased and treble decreased.

Sometimes I want the B/T enabled, particularly when listening to music (more bass, less treble). Other times I want the B/T disabled, particularly when playing games (less bass, more treble).

With this setup, I toggle the B/T setting on and off depending on the content. The sample rate change when streaming from a Bluesound Node or other source that changes sample rate based on source material obviously throws a monkey wrench into this scenario.

While not a deal breaker, I'd vertainly enjoy a fix in a future firmware update.