CPU Bug in slapper 3.0.19

Slapper Slapper - Bug Reports
#1

Hi, there is some sort of CPU usage bug with slapper.
We are running apple silion (non rosetta), and the newest version of protools (2024…10.2).
We are working across multiple OSX, im running Ventura 13.7. Not sure what my collegues are running, but we have the same issue.

Its hard to explain, but easy to demonstrate.

We are running large sessions for post production, and the System usage seems to be fine, when suddenly you see a huge spike in usage, for then to have the meters settle at a much higher usage than before it happens.

I have gone trough all the plugins we use to narrow down the problem, and it seems to be Slapper at fault. And i have a feeling that the Dynamic Plugin Processing stops working (no evidence for that)

If i make a new protools session where i send pink noise to 100 channels of slappers the meter spikes, but if i dont send any audio the System usage behaves in a strange way, where it does produce the same “odd” behaviour that i can see in the larger session.

  • Joakim
#2

can you send me your example session and a recipe to recreate it?
I was gong to suggest that the “TAPE MODE” setting is very CPU intensive, but only while the delay values are being changed - the rest of the time that mode is no different.

#3

Here is a test protools session and a screenrecording.

Im not sure what to make of it, but it behaves different than other plugins, where if no audio is going to the channels, the cpu usage wont go down. But if you disable any send gong to the channel (even without audio going trough) it will go down.

Ive just multiplied the channels by 100 to make things more visible