u/AudioThousand

I just ran a test in one of my projects where I have many instances of AmpliTube 5.

With VST3 instances, Ableton 12’s CPU meter was hovering around 57–58% when idle, whereas the exact same setup using VST2 instances was hovering around 15–17% when idle.

I also ran another test with 50 audio tracks and 50 instances of AmpliTube:
VST3: 80% when idle - 84% when playing (average)
VST2: 6% when idle - 80% when playing (average)

A third test with 50 audio tracks and 50 instances of H910 Harmonizer from Eventide:
VST3: 19% when idle - 20-24% when playing
VST2: 6% when idle - 20-24% when playing

And a fourth test with 50 audio tracks and 50 instances of Butch Vig Vocals (Stereo) from Waves:
VST3: 32% when idle - 33% when playing
VST2: 6% when idle - 36-38% when playing

What is going on here? I was under the impression that one of the main advantages of VST3 was the ability to “shut off” when not processing audio. If this is related to Ableton’s CPU meter—which apparently isn’t a true CPU meter—then why do the VST2 instances seem to shut off when not in use?

Can anyone shed some light on this?

System info:
Amplitube 5 v5.10.8
Ableton 12.3.6
Windows 10

I just ran a test in one of my projects where I have many instances of AmpliTube 5.

With VST3 instances, Ableton 12’s CPU meter was hovering around 57–58% when idle, whereas the exact same setup using VST2 instances was hovering around 15–17% when idle.

I also ran another test with 50 audio tracks and 50 instances of AmpliTube:
VST3: 80% when idle - 84% when playing (average)
VST2: 6% when idle - 80% when playing (average)

A third test with 50 audio tracks and 50 instances of H910 Harmonizer from Eventide:
VST3: 19% when idle - 20-24% when playing
VST2: 6% when idle - 20-24% when playing

And a fourth test with 50 audio tracks and 50 instances of Butch Vig Vocals (Stereo) from Waves:
VST3: 32% when idle - 33% when playing
VST2: 6% when idle - 36-38% when playing

What is going on here? I was under the impression that one of the main advantages of VST3 was the ability to “shut off” when not processing audio. If this is related to Ableton’s CPU meter—which apparently isn’t a true CPU meter—then why do the VST2 instances seem to shut off when not in use?

Can anyone shed some light on this?

System info:
Amplitube 5 v5.10.8
Ableton 12.3.6
Windows 10

I just ran a test in one of my projects where I have many instances of AmpliTube 5.

With VST3 instances, Ableton 12’s CPU meter was hovering around 57–58% when idle, whereas the exact same setup using VST2 instances was hovering around 15–17% when idle.

I also ran another test with 50 audio tracks and 50 instances of AmpliTube:
VST3: 80% when idle - 84% when playing (average)
VST2: 6% when idle - 80% when playing (average)

A third test with 50 audio tracks and 50 instances of H910 Harmonizer from Eventide:
VST3: 19% when idle - 20-24% when playing
VST2: 6% when idle - 20-24% when playing

And a fourth test with 50 audio tracks and 50 instances of Butch Vig Vocals (Stereo) from Waves:
VST3: 32% when idle - 33% when playing
VST2: 6% when idle - 36-38% when playing

What is going on here? I was under the impression that one of the main advantages of VST3 was the ability to “shut off” when not processing audio. If this is related to Ableton’s CPU meter—which apparently isn’t a true CPU meter—then why do the VST2 instances seem to shut off when not in use?

Can anyone shed some light on this?

System info:
Amplitube 5 v5.10.8
Ableton 12.3.6
Windows 10

I just ran a test in one of my projects where I have many instances of AmpliTube 5.

With VST3 instances, Ableton 12’s CPU meter was hovering around 57–58% when idle, whereas the exact same setup using VST2 instances was hovering around 15–17% when idle.

I also ran another test with 50 audio tracks and 50 instances of AmpliTube:
VST3: 80% when idle - 84% when playing (average)
VST2: 6% when idle - 80% when playing (average)

A third test with 50 audio tracks and 50 instances of H910 Harmonizer from Eventide:
VST3: 19% when idle - 20-24% when playing
VST2: 6% when idle - 20-24% when playing

And a fourth test with 50 audio tracks and 50 instances of Butch Vig Vocals (Stereo) from Waves:
VST3: 32% when idle - 33% when playing
VST2: 6% when idle - 36-38% when playing

What is going on here? I was under the impression that one of the main advantages of VST3 was the ability to “shut off” when not processing audio. If this is related to Ableton’s CPU meter—which apparently isn’t a true CPU meter—then why do the VST2 instances seem to shut off when not in use?

Can anyone shed some light on this?

System info:
Amplitube 5 v5.10.8
Ableton 12.3.6
Windows 10

I just ran a test in one of my projects where I have many instances of AmpliTube 5.

With VST3 instances, Ableton 12’s CPU meter was hovering around 57–58% when idle, whereas the exact same setup using VST2 instances was hovering around 15–17% when idle.

I also ran another test with 50 audio tracks and 50 instances of AmpliTube:
VST3: 80% when idle - 84% when playing (average)
VST2: 6% when idle - 80% when playing (average)

A third test with 50 audio tracks and 50 instances of H910 Harmonizer from Eventide:
VST3: 19% when idle - 20-24% when playing
VST2: 6% when idle - 20-24% when playing

And a fourth test with 50 audio tracks and 50 instances of Butch Vig Vocals (Stereo) from Waves:
VST3: 32% when idle - 33% when playing
VST2: 6% when idle - 36-38% when playing

What is going on here? I was under the impression that one of the main advantages of VST3 was the ability to “shut off” when not processing audio. If this is related to Ableton’s CPU meter—which apparently isn’t a true CPU meter—then why do the VST2 instances seem to shut off when not in use?

Can anyone shed some light on this?

System info:
Amplitube 5 v5.10.8
Ableton 12.3.6
Windows 10

I just ran a test in one of my projects where I have many instances of AmpliTube 5.

With VST3 instances, Ableton 12’s CPU meter was hovering around 57–58% when idle, whereas the exact same setup using VST2 instances was hovering around 15–17% when idle.

I also ran another test with 50 audio tracks and 50 instances of AmpliTube:
VST3: 80% when idle - 84% when playing (average)
VST2: 6% when idle - 80% when playing (average)

A third test with 50 audio tracks and 50 instances of H910 Harmonizer from Eventide:
VST3: 19% when idle - 20-24% when playing
VST2: 6% when idle - 20-24% when playing

And a fourth test with 50 audio tracks and 50 instances of Butch Vig Vocals (Stereo) from Waves:
VST3: 32% when idle - 33% when playing
VST2: 6% when idle - 36-38% when playing

What is going on here? I was under the impression that one of the main advantages of VST3 was the ability to “shut off” when not processing audio. If this is related to Ableton’s CPU meter—which apparently isn’t a true CPU meter—then why do the VST2 instances seem to shut off when not in use?

Can anyone shed some light on this?

System info:
Amplitube 5 v5.10.8
Ableton 12.3.6
Windows 10

I just ran a test in one of my projects where I have many instances of AmpliTube 5.

With VST3 instances, Ableton 12’s CPU meter was hovering around 57–58% when idle, whereas the exact same setup using VST2 instances was hovering around 15–17% when idle.

I also ran another test with 50 audio tracks and 50 instances of AmpliTube:
VST3: 80% when idle - 84% when playing (average)
VST2: 6% when idle - 80% when playing (average)

A third test with 50 audio tracks and 50 instances of H910 Harmonizer from Eventide:
VST3: 19% when idle - 20-24% when playing
VST2: 6% when idle - 20-24% when playing

And a fourth test with 50 audio tracks and 50 instances of Butch Vig Vocals (Stereo) from Waves:
VST3: 32% when idle - 33% when playing
VST2: 6% when idle - 36-38% when playing

What is going on here? I was under the impression that one of the main advantages of VST3 was the ability to “shut off” when not processing audio. If this is related to Ableton’s CPU meter—which apparently isn’t a true CPU meter—then why do the VST2 instances seem to shut off when not in use?

Can anyone shed some light on this?

System info:
Amplitube 5 v5.10.8
Ableton 12.3.6
Windows 10

Hi!

I’m experiencing rather slow loading and closing times with projects in Ableton, and I feel like I’ve tried everything.

I currently have a session that takes 2:30 minutes to load and 3:35 minutes to close—consistently. It does contain a fair number of VSTs and plugins (Keyscape, SD3, Amplitube), but this seems to be a general issue across all my sessions.

I’ve tried the following without any improvements – Create Analysis File is ON:

• Freezing VST-heavy tracks
• Removing the VSTs used in the project from their VST folder – one at a time.
• Migrating the project to a new folder to reduce the number of media files
• Removing large folders in “Places”
• Deleting unused track lanes
• Deleting unused "Media Files"
• Decreasing the buffer size
• Removing return tracks
• Disabling custom VST-folders and moving all to system folders
• Removing VST2 duplicates (when VST3 version is available)

Here are my specs:

• OS: Windows 10
• CPU: Intel Core i7 13700K / 3.4 GHz / 16 Cores (8-P & 8-E)
• RAM: Corsair Vengeance DDR5-5200 BK C40 DC - 64GB
• SSD 1 (OS, plugins and Ableton): Kingston SSD KC3000 1024GB M.2
• SSD 2 (Recording/projects): Kingston SSD KC3000 1024GB M.2
• SSD 3 (VSTs/libraries): Kingston SSD KC3000 2048GB M.2
• PSU: Corsair RM750x White v2 (2018
• CPU cooler: Noctua NH-D15
• Motherboard: ASUS Prime Z690-P DDR5

I’ve also spent a lot of time experimenting with optimization (Hyper-Threading, C-states, Turbo Boost, ParkControl, adjusting CPU priority/affinity in Task Manager with audiodg.exe, Ableton 12, Ableton Index, AbletonAudioCpl, Process Lasso, prioritizing background services instead of programs, etc.).

When I load the session in Safe Mode, it takes 12 seconds to open and 5 seconds to close. However, as mentioned above, I’ve already tried removing one VST at a time to identify a potential outlier, but without any significant change to the actual time it takes to open/close the session – the slow loading/closing time remains.

Does anyone have any advice on the matter?