NAD M66 - finally someone makes a decent 2-channel preamp!

[Stix]

I wish this thing would do home theater pass through. Anyone know of a work around? Nad might implement it someday but they always seem to move at a snails pace.

 

[ex audiophile]

I for one would very much appreciate to learn of experiences with the M66.

I returned mine to my dealer. Cannot set initial volume, remote does not access any menus, loading a new Dirac filter requires a full power off/on reboot. In my room Dirac could not deal effectively with two subs (boomy) but to be fair, I am not expert enough with Dirac to tweak the results. In my experience the STR preamp is much easier to use, has menu access via remote, you can set the initial volume, and ARC is much simpler to use, and very effective in my room with two subs (2.2 stereo setup). The STR requires an external streamer and only has two sub outs but is less costly. For me the STR was much more appealing.

 

[Nocko!]

It arrived - and makes trouble. I want to control the M66 via TCP connection. With all NAD devices the control port is 23. Hopeless question: Does anybody know which port number I have to choose after the IP adress?

Needless to say that there is no documentation for this question - or am I blind?

 

[pogo]

See software & downloads here (CI API): Link

 

[Nocko!]

Thanks, but I know these documents. Unfortunately they are outdated. They all refer to port number 23 which works with my M17 but is closed at the M66...

 

[pogo]

Port 11000 is used for all BluOS player.
What are you planning to do?
Is the BluOS app not sufficient for you?

 

[Nocko!]

No, sorry. The BlueOS app is by far not sufficient. Better not to talk about BlueOS with me

I am trying to control the M66 with tcp/ip commands with an app called "Touchcontrol". You send commands like this "Main.Source=1" via network to the device you want to control. For that you must use the ip adress and the correct port number. For example, sending the command above to 192.xxx.xxx.xxx:23 to my M17 switches the M17 to source 1 - my satellite receiver. In the app I can control the satellite receiver and with the same app on the same screen the volume of the NAD. I don't use infrared controls or other apps.
I love the NAD M17 for it's wide (and easy to integrate) control functions but the M66 seems to be of another kind.

I've already used a port scanner and tried to control with serial (RS232 !) control but to no avail. Perhaps the M66 is blind and deaf.

 

[markrubin]

 

[Nocko!]

@markrubin:
Many, many thanks - I've already tried a few of them but nothing worked. I also get different information from NAD. In a first answer they told me that tcp/ip control won't work and that I am "lost" with BlueOS but a few minutes ago I got another answer that could help. We will see...

 

[Nocko!]

I know I promised something like a review here but for now there will be no news from me that are interesting for the majority of you. I am still struggling with the basics: NAD promised the option to control the M66 with TCP/IP or RS232 commands. Both doesn't work. At first NAD pointed me (correctly) to an RS232-Test app and the documents of the M12 in which the procedure for controlling the device in general is described. I told them friendly that I knew what to do and that the RS232 port seems dead and that port 23 of the http-protocol is closed. Then for four days nothing happened and now another guy from the NAD-"support" answered

"Unfortunately, at this time, this feature is not supported. However, rest assured that we will forward this request to our Quality Assurance Team and the BluOS Development Lab for their consideration as a future update..."

That is the default answer you get from the NAD support. I am really angry at this moment...

I don't think that my M66 is defective. But I think that a honest answer from the support is not too much to expect:
- is my M66 defective?
- is the behaviour on purpose and NAD promises features that are not there?
- or will there be an update and all is well?

I don't expect a fast solution within five days but I think a honest answer is the least a consumer can expect.

Meanwhile I have integrated the M66 in my setup and try something like a day to day use. There are a few bugs that are already described elsewhere:
- after loading Dirac measurements to the device you have to make a hard restart (power switch on the back) to get the M66 to show the correct filter names
- after a hard restart the M66 forgets a few of its settings, especially which screens are associated to the sources
- the display switches of after about 30 seconds instead of 60 seconds as stated in the manual. No problem at all but another point where I think: What are they are doing at NAD?

The remote is a joke, but a sad one:
- it can't even turn the device on or off but powers up my M17...
- one button to toggle through five Dirac filters and Dirac off...?
- a button to control the brightness of the "NAD" logo without any other function ? Shouldn't it control the display?
- you cannot change the input with the remote, just the presets.
- you cannot navigate through the menus using the remote. The cursor buttons are just for show. You can program these to control BluOS, if anyone interested in this...

BluOS is still a sad story of its own. Anyone who knows something like Roon or the Squeezeserver (Lyrion) will be horrified. I knew this before.

"Presets" doesn't make any sense at all:
A preset consists of
- a name
- a source
- and the option to use a defined (but not fixed!) volume setting.

So there is no point it presets. But you have to use them, if you want to use the IR remote control (might be wrong here...?)

Presets should have options for:
- different display modes (on/off, with or without details etc.)
- a fixed volume
- Dirac slot / Dirac on/off
- DDH on/off
- Trigger control
and so on.

By the way: The trigger switches off when the M66 enters network standby mode. That's ok, but there should be an option to configure this. I don't want my classic A/B amps to power down every 15 minutes.
The input triggers are not mentioned in the manual or the menus. Don't know what to do with them. Automatic Source selection was an idea. But this won't work.

Soundwise I still have to investigate. I am not sure but perhaps there are a few "digital glitches" with some records so there is some work for me to do.

I've used the classic Dirac for years and DLBC seems very, very good in my setup. This is the reason why I am still fighting with the M66. There are no alternatives.

Any questions or should I shut up?
Nocko!

 

[pogo]

you cannot change the input with the remote

Function can be assigned via IR Learning.

 

[Nocko!]

Function can be assigned via IR Learning.

Hello Pogo,
sorry, don't draw conclusions from one to the other. IR Learning or "IR Trigger" can only learn Presets and three predefined inputs (HDMI, Optical and one of the analog inputs). But: Perhaps I am too dump. I was searching for useful features within the webinterface and the app. Don't know where to search anymore...
The M66 seems - from a friendly point of view - not ready.
Anybody knows where to download older firmware to install via the USB port?

 

[pogo]

IR Learning or "IR Trigger" can only learn Presets and three predefined inputs (HDMI, Optical and one of the analog inputs).

Input source up/down would still be useful here. NAD can certainly add this. You could also sacrifice presets for the most important inputs.
Switching inputs should work with your HTRM2.

 

[Nocko!]

Switching sources should work with your HTRM2.

Unfortunately even this doesn't work but I have to admit, that I don't care about the IR remote at all. This is just a warning for others who think of the M66 as a real "all-in-one" device. It is not. But perhaps I am too demanding...

 

[Nocko!]

@markrubin and the others who already own a M66:

When activating "analog direct" for the XLR inputs there is still a bandwith-limited signal for my subwoofers and Dirac still works. Is Dirac working analog nowadays?

I don't need the "analog direct" option for my setup. But the more I try the more I ask myself if there is anything I should believe in as far as NAD is concerned...

 

[ao2419]

Can someone answer a question about latency? I use the same setup for streaming/listening as DJ/production work, so latency is important. I read analog direct removes all processing. Does analog direct remove the 50 ms delay in BluOS? Essentially, when you drop a needle on a record, do you hear sound immediately? I also read some of the earlier replies that implied analog direct turns the sub output off? Or does it just turn off DLBC and default to a set crossover?

 

[Descartes]

I also think an objective review would be appreciated; doesn't need to include measurements, but a thoughtful review of functionality would be great!

Amir, Gene or Erin would be great to review

 

[Hephaestus]

Can someone answer a question about latency? I use the same setup for streaming/listening as DJ/production work, so latency is important. I read analog direct removes all processing. Does analog direct remove the 50 ms delay in BluOS? Essentially, when you drop a needle on a record, do you hear sound immediately? I also read some of the earlier replies that implied analog direct turns the sub output off? Or does it just turn off DLBC and default to a set crossover?

Analog direct can be applied only to analog inputs of the device, those are: Phono MM&MC, Line 1&2 and Balanced. It cannot be applied to BluOS for obvious reasons, however Dirac can be disabled. It would be interesting to see what is the minimum latency of digital inputs when Dirac is disabled. In general I would advice against to use this sort of equipment in a scenario where minimal latency is critical.

Needle contact on the record surface can be heard immediately when Analog direct mode is engaged. (I have about 4ms latency in my Genelecs though)
I do not have subs currently but I recall NAD rep to mention that sub outs default to crossover settings selected from the device menu when analog direct is selected.
This quote is from NAD M66 FAQ:

"Activating Analog Direct routes the selected input through a purely analog signal path, bypassing all digital conversion and BluOS processing.

Note: Analog Direct mode is available only for Analog sources on M66."

Amir, Gene or Erin would be great to review

Definitely! At this moment Hi-fi News has a review with measurements in their July issue. It is currently behind paywall only. Digital subscription trial can be had for a low cost.

 

[Kal Rubinson]

I do not have subs currently but I recall NAD rep to mention that sub outs default to crossover settings selected from the device menu when analog direct is selected.

That seems to be the case.

 

[pogo]

According the block diagram inside the M66, there is no path to the subwoofers in analog direct Mode.