CPU spikes to 100% after stopping playback from Pro Tools

Superior Drummer 3 Help
Viewing 5 replies - 1 through 5 (of 5 total)
  • Brad
    Participant

    You wouldn’t have any other plug-in inserted on the same track, a limiter for example?

    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)

    Mike Black
    Participant

    @Brad said:
    You wouldn’t have any other plug-in inserted on the same track, a limiter for example?  

    The track is clear, aside from the Superior Drummer plug. If I disable the plugin, the problem no longer occurs.

    Increasing the DAW buffer size helps, but it seems a bit buggy for it to have giant CPU spikes that only occur when hitting stop from the DAW vs the plugin window.

    Brad
    Participant

    I am using Pro Tools 2018.4, what version are you on? Not seeing this on my system. Have you changed any of the performance settings in SD3 (CPU Cores for example)?
    Is it a specific preset or kit, or is it happening consistently with any preset or kit. It’s an oddity that it only happens when stopping playback.

    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)

    Mike Black
    Participant

    @Brad said:
    I am using Pro Tools 2018.4, what version are you on? Not seeing this on my system. Have you changed any of the performance settings in SD3 (CPU Cores for example)?
    Is it a specific preset or kit, or is it happening consistently with any preset or kit. It’s an oddity that it only happens when stopping playback.  

    This is 2018.4. The audio is on a separate drive from the OS. It’s set to use one CPU. There are four available, but if I try to add more, the performance seems to go completely haywire so I leave it at 1. Don’t AAX plugs automatically get distributed across the CPUs by Pro Tools? I’ve never had a plugin that required you to specify how many CPUs to use. This seems like an odd thing to request from a user. I have it set to load the cache for the entire kit (24GB of RAM available) so it doesn’t spike whenever it loads a cymbal crash for the first time.

    I’ve tried different kits, including both SD3 and EZDrummer expansions. Some kits seem to spike a bit more than others, but they all have a big spike, and only when stopping playback from the DAW. I don’t have any issue using EZKeys, which is usually quite CPU efficient.

    For the most part, other plugins (mostly Waves) barely move the needle. The only other plugin that I struggle with is the Abbey Road Plates, which is a legendary CPU hog, but even that one doesn’t spike to 100 percent.

    John
    Moderator

    Hi,

    just leave the CPU setting at 1 in SD3, it’s the Default and the setting is there for users that want/need to be able to dictate this on their systems.

    How big is your Playback engine buffer size?
    Does it make a difference if you have another Track in the session, e.g. an Audio Track, and select it instead of having the SD3 Instrument Track selected?
    Which version number is displayed in the plugin interface?

    You aren’t seeing any CPU spikes in the standalone, right?
    I am able to run at least 2 instances of SD3 in sessions on my MacBook Pro 2,8GHz i7 in Pro Tools Ultimate 2018.4.
    I am running OS 10.13.5.
    What has been necessary on my system since a long time, regardless of which VI I am using, is that I need to turn the Turbo Boost off. With it on, the CPU spikes are terrible, again; this is with using any VI’s in a Session. Also Pro Tools only, since I can run other hosts with loads of VI’s and plugins with Turbo Boost on.

    There’s an app called Turbo Switcher, which has a free version and a Pro version, if you want to try this for yourself.

    BR,
    John

    John Rammelt - Toontrack
    Technical Advisor

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

No products in the cart.

×