Comments

13 comments

  • Avatar
    Antonio Serralvo Neto

    I struggled with that for days... I found out that it was being caused by two factors:

     

    1 - One of my cables was phase inverted, and it was causing some sort of a shock in the readings.

    2 - The relation between volume/Microphone gain was not balanced. You should adjust the volume to the speakers so it really sounds conversation level. Only THEN you adjust the gain to match the desired level.

    I hope it works!

    0
    Comment actions Permalink
  • Avatar
    Antonio Serralvo Neto

    And, always reserve a set of 30 minutes or so to calibrate your system. Do it in a hurry will do you any good whatsoever. It takes time and it is worthy every moment!

    0
    Comment actions Permalink
  • Avatar
    Joosa Kurvinen (Edited )

    I am also having this issue and can't seem to figure it out. Left speaker is measured fine, but with the right speaker I always get "Mono signal detected". The signal is clearly stereo, as far as I know there isn't any cross-feed between the channels, the monitors have rather equal volume as far as my ears can tell, and I even measured that they are in the same phase (slightly less sure about the subwoofer). Maybe my gain settings are somehow wrong and measuring just 1-2cm away from the speaker as it says makes it spike too high, even though the gain check shows it's all good? Other than that I have no idea what to try anymore..

     

    Edit: Finally figured it out. There's something wrong with my Adam Sub 8 and it's indeed causing some crosstalk between the stereo channels. No idea how to fix that, but the issue identified by Reference was indeed real.

    0
    Comment actions Permalink
  • Avatar
    Guy Harwood

    @Joosa

     

    did you ever figure out what the problem was with your Adam Sub 8?  

     

    I have the same 'mono signal detected' issue and am running an Adam Sub 8.

    0
    Comment actions Permalink
  • Avatar
    Juan Gonzalvez

    Same thing here, "phase inverted cable" or something like this. I replaced the audio cable, now it's fine, it works out.

    0
    Comment actions Permalink
  • Avatar
    Joosa Kurvinen (Edited )

    Yeah might have been just a bad cable for me too, I don't remember anymore if I tried switching that. What I did was to by an external cross-over. https://www.thomann.de/gb/behringer_cx2310_v2.htm Wasn't that expensive and maybe it's also otherwise higher quality and has more options. The number of cables going everywhere behind my desk is now awful though. :D

    0
    Comment actions Permalink
  • Avatar
    Guy Harwood

    i tried different XLR cables and a different interface but i kept getting the 'mono signal detected'

    eventually i tried using the RCA inputs on my subwoofer instead of the XLRs, which worked.

    Sub is going for a repair soon.

    0
    Comment actions Permalink
  • Avatar
    Axel Fischer

    hi guys,

    i have the same problem:
    using an adam sub 8 and the adam a7x as satellites.

    my routing is:
    original sonarworks microphone -> uad apollo twin x duo -> adam 8 sub -> adam a7x

    i always get that mono error message when i measure the right speaker (although its definetely a stereo signal). i tried different cables and also switched the phase of the sub without any success.
    i can do a measurement without the sub connected, but i guess the measurement won‘t make sense in that case, when i re-connect the sub after doing the measurement?!

    Do you have any more ideas how to fix that mono error problem with the 2.1 adam setup??

    Thanks for any help!!

    0
    Comment actions Permalink
  • Avatar
    Kārlis Stenders (Edited )

    Hi Axel, 

     

    I've checked your support ticket thread, and it seems there was never a conclusive resolution. Did you manage to complete the measurements?

    1
    Comment actions Permalink
  • Avatar
    Axel Fischer

    Hi Karlis,

    thanks for coming back to me.

    Unfortunately i couldn`t fix this and i haven`t got a conclusive resolution yet.
    Do you have an idea, how to handle this problem?

    Axel

    0
    Comment actions Permalink
  • Avatar
    Kārlis Stenders (Edited )

    Hi Axel,

     

    Difficult to tell, we will have to dig deeper and investigate. I have created a support request for us to have a closer look.

    0
    Comment actions Permalink
  • Avatar
    Guy Harwood

    i got around the issue by having my subwoofer repaired.

    one of the channels was bleeding into the other.

    0
    Comment actions Permalink
  • Avatar
    Kārlis Stenders

    Hi Guy, 

     

    Thanks for chipping in! Yes, that can be an issue potentially. Could also be a panning setting in the interface control software - even a slight panning shift, and one channel bleeding into the other one can cause this error.

    0
    Comment actions Permalink

Please sign in to leave a comment.