Well I havent heard any difference since updating the M33, but after reading this thread I can hear it![]()
Friend of mine had the same issue with Tidal connect today on his M32 ,Tidal worked trough Bluos but not Tidal Connect .Recently I had an update of both BluOS and Tidal. I use Tidal Connect (Samsung S22 Ultra, latest Android) but now I have issues on my M33:
- It connects via Tidal Connect, but when I select another album it gives a connection error ~80 % of the time.
- When it finally starts after a manual re-try it is always far in the first number.
- The time counter acts weird (updates every 5-10-15 seconds instead of realtime.
When I play Tidal via BluOS it works fine so probably Tidal. Wondering if more people have this and ideally a solution because I really do not like BluOS.
Tidal works flawless on my desktop PC.
And i have same problem,it seems like Tidal connect is bug on several system like wiim ectFriend of mine had the same issue with Tidal connect today on his M32 ,Tidal worked trough Bluos but not Tidal Connect .
Yes that is how it "should" be in the sense that this is the intended implementation. The two outs can be individually time and frequency adjusted with Dirac, but will play the same mono-signal. Which I think is the norm in bass management, at least in home audio.I have a question. The NAD M33 has R en L subwooferoutputs. But the subwoofers play in mono.. When I play a left test signal, my right subwoofer is playing also, and v.v. Is this how it should be?