No signal from subwoofer out

Answered

Comments

6 comments

  • Official comment
    Avatar
    Sam R.

    You'll get more voltage out of the M10's PRE OUTs if you'd like to run those out to your Subwoofer instead. 

    In the meantime I will pass this forward as feedback to the engineering team.

    Regards,
    Sam R.

    Comment actions Permalink
  • Avatar
    Bruce

    This has been my issue for months, both with the M10 and now the M33. The manual for the M33 spec states 1.1vrms max for the subwoofer output. The pre outs are listed at 3.75vrms max. This is a huge difference, and it is obviously intentional as it is stated clearly in the device's manual. I wish Lenbrook would explain why it chose the limit the sub's output.

    If you use the pre outs for the sub you will lose bass management, and you will be sending full range to your speakers. You will also have to control the crossover by the dial on the sub. Additionally, I don't know how this will affect running Dirac room correction.

    Unlike the Node/Powernode 2i, the subwoofer output is NOT active on the M10/M33 when "no subwoofer" is chosen. 

    Perhaps Sam R. can offer an explanation?

    0
    Comment actions Permalink
  • Avatar
    Tony W. - Product Support Manager

    Hi Bruce

    Your issue is better handled by NAD SUpport directly - please contact them at support@nadelectronics.com

     

    0
    Comment actions Permalink
  • Avatar
    Ron Sjoerds

    For me the "workaround" is the best solution. My KC62 has standby problems on LFE connection (see also elsewhere in this forum on LFE issues with other subs). Once the KC62 goes into standby (while listening but apparently sensing no input) it hardly comes out of it, even when playing the same song (Angel /MA ON > other song with less low frq STANDBY > back to Angel then it stays in STANDBY) Connection via pre-amp and "no sub" in settings, crossover 80hz on KC62 works flawless, no more standby problems. And about losing "bass mgmt" ... all bass mgmt on M10 is the crossover, which is now handled on sub itself. And all frquencies are send to the loudspeakers (LS50 meta's) anyway (as I understood from other replies from NAD engineers in this forum).

    My M10 has other problems, but this one I could handle :-)

    0
    Comment actions Permalink
  • Avatar
    Bruce

    "And all frquencies are send to the loudspeakers (LS50 meta's) anyway (as I understood from other replies from NAD engineers in this forum)"

    That is not the case when using the M10/33 subout and adjusting the crossover in the BluOS app. Your mains will receive the frequencies above your chosen crossover point, say 80Hz, and direct the frequencies below 80Hz to your sub. I am not aware of what the db/octave crossover slope that the software uses.

    When using the pre outs and controlling the crossover at the sub, the mains receive a full range signal from the pre outs. I also use the pre outs and blend the lower frequencies, volume and crossover at the sub.

    BTW, I received a text response from Bob Moran (NAD customer support) about the low level sub out. He said that 1.1vrms output "meets BluOS specs."

    I explained that my Powernode Gen 1, Powernode 2i, and Node 2i have no sub output issues, only the M10/33; and that the low sub output is well documented on AV forums, he said he would forward it to engineering.

    I have another issue as well. My M33 screen intermittently boots up to ghosting and lines around the edges of the screen, even after following Bob's instructions to upgrade firmware again and send an activity log showing the upgrade was successful. He said they were aware of this problem but have no solution currently.

    0
    Comment actions Permalink
  • Avatar
    Ron Sjoerds

    Hello Bruce

    [I have another issue as well. My M33 screen intermittently boots up to ghosting and lines around the edges of the screen, even after following Bob's instructions to upgrade firmware again and send an activity log showing the upgrade was successful. He said they were aware of this problem but have no solution currently.]

    Welcome to the world of the greyish screens. I got this problem with two different M10's right from the start when I bought the first one 1,5 year ago. Annoying, and only to be restored by a power cycle. At least once a week. Firmware issue, never solved. Never put it via a remote control in standby helps a little bit and makes it happen less often.

    0
    Comment actions Permalink

Please sign in to leave a comment.