Help. CPU overload in Ableton

Hi
I have an issue when I assign more than two midi buttons in osc/pilot to some parameters in Ableton I get a lot of cpu overload, which lags my Ableton and osc/pilot.
When I connect my iPad and use osc/pilot on it everything works well. But when I use Osc/pilot on my MacBook along with Ableton and assign more than two midi buttons everything lags so much and I get a lot of Cpu overload. I use MIDI Studio to connect osc/p and Ableton. Does anyone know how I can fix this.
Jpeg below with my current setup.
Please help because im a newbie and this really bums me out :frowning:

Thank you

Hello,
i m on Windows, so i sadly don’t know this “Midi studio”. And i never experienced CPU spikes, just by assigning more buttons. So i dont know if you have another sort of issue there, but let me give you little advice:
Here’s what i would do:

  • check the task manager /activity monitor, and analyze in detail what app is causing what CPU usage. Don’t forget to check GPU (Graphics) Usage!
  • check if Ableton and OSC Pilot are running on your dedicated graphics card or not. And then test, if the performance increases, when you force them to run on the dedicated graphics card.

For me, it was the behavior of the Windows Window-Manager, which cause lot of CPU and GPU usage and decreased my Ableton performance! (windows automatically loads such tasks, to handle multi-monitor setups, and i can’t do anything about it.)

Here’s a thread i created here, which was about performance in Windows 11

In my experience, OSCPilot adds +10% CPU to the system [in conjunction with the multi-window and graphics management! not on its own.] , and 20-50% of GPU, depending on the OS-driver-behavior, (multi window- management dependent), and depending on the graphicscard.

When i open three instances of OSC Pilot, my internal GPU of my laptop is overwhelmed, and i get severe lags. MIGHT be the case with one instance of OSC if you have a very bad laptop.

Although i could use OSC Pilot on the same machine, i decided to run it on my old PC, and connect both via USB-to-midi adapter (ESI MIDIMATE). This way i can load more VSTs into Ableton without dropouts :slight_smile:

1 Like

Looks like you accidentally created a MIDI feedback loop. In your current configuration, Ableton is sending data out to the bus and the bus is bringing it right back and so things will absolutely get very laggy. I would disable track AND remote output on “test port” bus 1 to end the loop.

BUS 1:

OSC/PILOT

OUTPUT
“test port for oscp” (Bus 1)

ABLETON LIVE

“test port for oscp” (Bus 1)
IN: TRACK SYNC REMOTE
OUT: TRACK SYNC REMOTE

if all you need is communication from OSC/PILOT to Ableton on your Mac, then you can stop there as this creates a one-way communication.

However, if you need parameter data from Ableton sent to OSC/PILOT, you should create a second iac bus for that.

BUS 2

ABLETON LIVE

“test port for oscp” (Bus 2)
IN: TRACK SYNC REMOTE
OUT: TRACK SYNC REMOTE

OSC/PILOT

INPUT
“test port for oscp” (Bus 2)

Also you don’t need to have [“test port for oscp” (Bus 1)] selected in your control surfaces.

1 Like

Thank you very much!

Wow that worked! Thank you very much! You are a lifesaver

Glad to know it worked!