Seven amazing deals,
this weekend only!
*

[button class="color-white" href="/weekend-deals/"]

EZD2 Distortion when triggering multiple drum sounds

EZdrummer Help
Viewing 5 replies - 1 through 5 (of 5 total)
  • Brad
    Participant

    Sorry, I’m going to ask some things you probably have looked into, but here goes…..

    What are your buffer settings that are giving quick throughput and do you have zero-latency switched on in S1?

    Have you brought up the performance monitor in S1 and checked “Show Devices” does it show that EZD is overloading the processor?

    Does this happen when you are using EZD as the only plug-in within a session or does it start to distort with the addition of other plugins?


    EZdrummer version: 2.2.1
    Operating system: macOS Big Sur (11)

    Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
    DAW: Studio One Pro (always up to date)
    DTX Express III (Extreme triggers), Nektar LX88
    OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
    Presonus Quantum, Faderport & Faderport 8
    Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
    2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

    1

    Thanked by: Rob Taylor
    Rob Taylor
    Participant

    Hi Brad and thanks for replying.

    I was going to say… “I’m not using any other plugins at all in any of these testing processes” and, yes, low latency monitoring is enabled even though I don’t believe it should be needed with just one plug in but I’ve been sort of trying everything and this didn’t see to hurt.

    But when I popped into my empty song template just now to consider your questions, I found I did have a bunch of effects like reverb, compression and EQ as well as EZKeys available and active on empty tracks. I’ve disabled them all now and it seems like it may have reduced the frequency of occurrences a small bit, they continue to persist

    Keep in mind, since the issue is repeatable in the stand alone application, I’ve sort of shifted my attention to EZD2 itself as opposed to S1 as I’m assuming S1 settings are irrelevant to how the stand alone behaves and issue appears identical across USB and MIDI triggered instances.

    That said, here are some more S1 settings I’ve applied:

    Dropout Protection: Max / Process Block Size 2048 samples / Process Precision 64Bit / Use Native vs Hardware is greyed out and unavailable

    Monitoring latencies for instruments are as follows: Standard – 69ms/6632 samples    Low latency 3.21ms / 308 samples

    Buffering at 64 appears to produce optimal latency/quality result aside from described issue

    Windows Task Manager monitoring shows CPU usage maxing out about 27% during heavy use while S1 tells a different story…

    CPU usage indicator hovering around 50% with random spikes to 100% during zero use of EZD2 while heavy use takes it right up to 100% / red indicator on

    Please feel free to ask anything else that might help nail things down. Thanks again

     

    Brad
    Participant

    The Studio One performance monitor will display a breakdown of device CPU usage by plug-in. When you play quickly, what does the CPU for EZD show?

    I know it may sound unmusical, but could you try drumming really fast using the EZKeys plug-in and see if the same issue happens? (Just an experiment)

    If you set the buffer/block size to 128, does the problem go away completely?

    Does it make a difference as to which EZD EZX/Kit/preset you have loaded?

    In the Universal Control interface, is the block size 64 as well? Trying to get my head around setting the block size in the driver and application (EZD or S1) the Quantum TB driver I believe doesn’t have that option)


    EZdrummer version: 2.2.1
    Operating system: macOS Big Sur (11)

    Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
    DAW: Studio One Pro (always up to date)
    DTX Express III (Extreme triggers), Nektar LX88
    OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
    Presonus Quantum, Faderport & Faderport 8
    Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
    2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

    1

    Thanked by: Rob Taylor
    Rob Taylor
    Participant

    Hey Brad, thanks for hanging in here with me!!

    FYI, for now at least, I’ve kind of given up on the stand alone app as it falls apart at 128 and only sounds good at 256 which creates far too much latency to be useful. All testing moving forward will be within S1 unless otherwise specified.

    When you play quickly, what does the CPU for EZD show? – 22 – 25 before playing then up to a peak of about 38 at maximum input when distortions begin to apear

    … try drumming really fast using the EZKeys plug-in and see if the same issue happens? About 30 before playing then up as high as 41 during max input but, interestingly, no distortion of sound whatsoever

    If you set the buffer/block size to 128, does the problem go away completely?  Within S1, 128 still seems to be low enough latency to be playable but, yes, at maximum playing speed, some distortion continues to appear. Switched to 256 and WOW!!! All distortion events seem to have vanished and still no latency!!

    Does it make a difference as to which EZD EZX/Kit/preset you have loaded? Yes, it did seem as though the more complex kits resulted in more distortion than the basic ones

    In the Universal Control interface, is the block size 64 as well? The block size in Universal Control matches up with whatever I set within S1 options. They seem to link automatically. Not sure if that answers your question.

    I believe there are 2 things I was doing ‘wrong’ before that this process has helped me discover and resolve. One was toggling the low latency monitoring within S1 which was previously not toggled a few days back. The other is this one just now. That being that I never imagined 256 would provide low enough latency to be playable so didn’t bother trying after toggling low latency monitoring.

    So, BAM! The DAW plug-in side of things is solved! I suppose I can live without the stand alone app but would like to resolve that too if possible.

     

    Either way, thank you so very much for helping me reach this place. Very excited about my set up now as it is incredibly fun to play these great sounding kits with my TD-17!!

    Brad
    Participant

    Excellent, glad you got it to the point where you can enjoy creating music! As far as the standalone app, might worth while playing around with the block size in Universal Control and the buffer size in the app itself and see if you can reach a happy place. But for now…. play on!


    EZdrummer version: 2.2.1
    Operating system: macOS Big Sur (11)

    Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
    DAW: Studio One Pro (always up to date)
    DTX Express III (Extreme triggers), Nektar LX88
    OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
    Presonus Quantum, Faderport & Faderport 8
    Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
    2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

Viewing 5 replies - 1 through 5 (of 5 total)

No products in the cart.

×