1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Solved +668dB spike from Massive X!!!!! (MASSIVEX-2304)

Discussion in 'MASSIVE + MASSIVE X' started by iLex, Sep 5, 2020.

Thread Status:
Not open for further replies.
  1. ChrisH1785

    ChrisH1785 New Member

    Messages:
    11
    Hi Jeremy,

    I’ve been having a break from producing. But intend to get up and running soon. Only way around the issue for me was to have a low pass filter over massive x, so when I hit play it wasn’t open. Have you updated Massive x since my last post? I will send my email address to you.
     
  2. EvilDragon

    EvilDragon Well-Known Member

    Messages:
    19,938
    There were no MX updates recently.
     
  3. Jeremy @ NI

    Jeremy @ NI Support Team NI Team

    Messages:
    1,339
    Hey Chris, no update for Massive X but we have a AU plugin beta version to test, you can send me your email address by direct message.
     
  4. berner

    berner New Member

    Messages:
    1
    Hi - I have just learnt of this horrifying potential issue with Logic and the white noise burst. My Mac is connected via optical to an old Yamaha AVR which is functioning as an integrated DAC and headphone amp. Would the AVR volume control cap the output of any high volume bursts? Or could the extreme volume of this white noise burst be conveyed by the digital signal? I also have at my disposal an old MiniDisc player with the AVLS feature - how have you integrated it into your signal chain in order to be able to rely on it as a hardware limiter?
     
  5. Jeremy @ NI

    Jeremy @ NI Support Team NI Team

    Messages:
    1,339
    Hey berner,
    Just so you know, we're working on a fix for this issue. If you want to try it out please send me a private message with the email address you use for NI.
     
  6. Toni Hintikka

    Toni Hintikka New Member

    Messages:
    1
    Same here. Horrible peak almost everytime I launch Massive X. Logic Pro as a DAW.
     
  7. EvilDragon

    EvilDragon Well-Known Member

    Messages:
    19,938
    MX 1.3.2 should fix this one, for good!
     
  8. iLex

    iLex NI Product Owner

    Messages:
    49
    Cool, thanks! I'm a little disappointed that I didn't get my Wacom support as a thanks for spending all that time sending files etc. :p
    No spikes, but I still can't use it.

    Then again Massive X is only, what, 2 years old now? Probably still in beta o_O:)
     
  9. Tobias @ NI

    Tobias @ NI NI Team NI Team

    Messages:
    8
    Hello everyone, we have just released Massive X 1.3.2. Please update to this version.

    A big thank you to everyone who has helped us to reproduce this one. It's been hard to catch. So, we highly appreciate your support!
     
    • Like Like x 2
  10. bsatorius

    bsatorius New Member

    Messages:
    1
    When the release email hit my inbox today, I had to create a forum account just to express my relief, and say thanks for this fix. Over the last year, I had to condition myself to turn down my headphones to zero anytime I add a new Massive X plugin to a track, which I do often (after finding this thread, I learned to put a limiter on master!). Thanks for calling this fix out in an email announcement. Much appreciated.
     
    • Like Like x 1
  11. Splicer

    Splicer New Member

    Messages:
    14
    That's... it? That's all there is after almost a year? Please tell me there's something more substantial around the corner.
     
  12. iLex

    iLex NI Product Owner

    Messages:
    49
    Is there any way we might see that Wacom support!? Anyone I can bribe? I make jokes about it, but it is the reason I don't use MX in any of my projects. How difficult is it? I have freeware that supports Wacom...
     
  13. chk071

    chk071 NI Product Owner

    Messages:
    180
    Patience, young padawan.
     
  14. EvilDragon

    EvilDragon Well-Known Member

    Messages:
    19,938
    Since the issue has been resolved, we can now close this discussion.
     
    • Like Like x 1
Thread Status:
Not open for further replies.