Dropouts during scene changes when specific instruments are triggered for the first time.

Sasha-TP · 2025-02-12T22:03:46+00:00

There was an error rendering this rich post.

I have the problem with the Maschine software that when a project is reloaded and certain VSTs and internal instruments are triggered for the first time, there are short dropouts and CPU spikes. As I said, it only happens the first time the respective instrument is played, after that everything runs stable.

The problem occurs, for example, with the following instruments, depending on the preset used:

internal machine drum synths
various Kontakt Play Series instruments
Massive X
Arturia Pigments
UHE Hive

It is definitely due to the maschine software and it makes no difference whether I use it standalone or as a VST3 plugin.
Does anyone have any idea if this is a bug?

Find more posts tagged with

Maschine MK3

Maschine 3 SW

Accepted answers

All comments

Kubrak

I had this if I had unsuffitient amount of RAM. RAM image has been swapped to disc and loading it back has caused the dropout or first few notes of instrument have not been played…

Andy Wt

This very annoying bug is also present in M+: Maschine Plus: Drop outs when changing scenes (MAS-29716)

Questions about whether this bug will ever be fixed are ignored.

Sasha-TP

Hey, thank you very much for your answers. I also suspect that it is a bug in the machine software. I have a Windows PC with a Ryzen 7 8840U processor and 32 GB RAM. When a large project is running, the CPU only reaches 30 - 40 percent utilization and the RAM still has enough reserves. I don't think it really has anything to do with the scene change itself in Maschine. The problem only occurs when the instruments or VST are triggered for the first time. After that everything is great. Unfortunately, this happens every time a new project is loaded.

I have also tried all the tweaks I know (power management, unnecessary services etc.) to improve the performance of Windows. Before you ask, yes, I have also switched off Windows Defender, which is the problem with dropouts on Windows computers in 99 percent of cases. Unfortunately, none of this was successful.

Sasha-TP

Guys I found the culprit that causes dropouts and glitches in Maschine. It's the internal reverb plugin of Maschine (not the legacy one but the newer one).

Since I've had problems with the internal reverb before (there were dropouts when two reverb plugins were connected in series and when the source stopped playing there was a CPU overload after a few seconds), I thought I'd remove all Maschine internal reverbs from the project as a test.

And what can I say, it works, no more dropouts.
The Maschine internal reverb plugin definitely has a bug. I can only recommend everyone to stop using it and switch to alternatives.
I hope I could help everyone who has the same problem.

Best regards to all.

Andy Wt

Great if removing Reverb solved the issue for you. Seems that in case of M+ presence of Reverb doesnt matter. I've tried project with dropouts which contains only several instances of Metaverb and Legacy reverb. At least removing all Metaverb instances, saving and rebooting doesnt change anything - dropouts are still present.

Sasha-TP

It's a shame that the solution doesn't work with the plus machine. But that's exactly the problem with the Plus in standalone mode. I also had constant problems with crashes and dropouts, so I now only use the Plus as a controller. I simply strapped a Windows tablet underneath and customized Windows a little with autostart of the Maschine software and control for closing and opening programs via the tablet buttons. It works perfectly, I can now use all the VSTs available, have enough power, a built-in battery and Ableton now also runs on the Maschine 😉 A Maschine Plus Plus, so to speak. I can only recommend it.

LostInFoundation

Well…at this point I would recommend NOT buying a M+ but a cheaper MK3… ☺️

olafmol

Dropouts when switching scenes also happen on Maschine software with MK3, unfortunately. I guess it has something to do with caching as it only happens on the first time when new sounds are triggered after switching a scene. It's an old problem, already from Maschine 2.x software, and it seems it's very hard for NI to fix for whatever reason.

Quick links

Unanswered questions