Sonarworks Ableton Plugin and Kick Drum in Ableton Live 10

Comments

3 comments

  • Avatar
    Chris

    Hey Tim,

    Thank you for the post!
    The difference in output is likely caused by differing correction being applied to each channel as the output characteristics would differ for each speaker.

    The listening spot feature might also impact your experience as it compensates for the loudness discrepancies between your speakers.
    It can be disabled in the bottom tab of the Reference 4 window whether it's Systemwide or the plug-in.

    0
    Comment actions Permalink
  • Avatar
    Thomas

    Hello,

    I just find out the same issue.

    I thought that the correction would not generate phase with mono material, so when SW enabled we don't listen things who are in mono.
    In my music some of things are mono and how can I trust my sound through SW when I'm designing a kick for example ?

    I want the best flat response of my room but SW enabled kicks loose power and body like a phase problem even if I select linear phase.

    Thomas

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

    Hi Thomas, 

     

    Thanks for the comment, our apologies for letting it hang for so long here! I'm sure you have already figured this out by now but let me explain still, just in case anyone else is wondering:

     

    The L-R output levels differ because we are offsetting them deliberately. The software also adjusts for the overall L-R level disbalance, not just the frequency response for each channel. So the software compensates by boosting one of the channels in order for the actual sound coming out of the speakers to be balanced! This functionality is operated with the Listening Spot feature and can be turned On/Off for any reason, whenever needed.

     

    I should mention that we have had serious issues this year with the Listening Spot functionality - it was not working exactly as expected on a couple of occasions. Several fixes have been put in place and all issues are definitively fixed with version 4.4.7 (v4.4.7.34 is currently available in Beta, see details and instructions here: Beta software releases).

    0
    Comment actions Permalink

Please sign in to leave a comment.