FL Studio’s Reset Plugins on Transport setting resets plug-ins when you start, stop, or move the song position marker. Image-Line specifically recommends disabling it when VST plug-ins cause significant glitching during start and stop events.
The setting exists for a reason. Some plug-ins keep internal states that affect what they produce from one moment to the next, so resetting them can make repeated playback more consistent. The price is extra work at exactly the moment you press play, stop, or jump somewhere else in the Playlist.
A project that runs smoothly once playback settles can therefore hitch at the transport without being generally overloaded. Treat the timing of the spike as evidence. If the CPU jumps only when transport state changes, test transport-related behavior before raising buffers, deleting effects, or rebuilding the whole session.
Do not assume the global switch must stay off forever. Disabling resets can allow state-dependent plug-ins to resume differently after you relocate playback, although Image-Line says those differences are unlikely to be significant in most cases. Listen for altered tails, envelopes, sequencers, random generators, and anything else whose output depends on its previous state.
One awkward plug-in does not have to dictate the setting for the entire project. FL Studio’s Wrapper includes the Reset plugin when FL Studio resets, letting you control reset behavior for an individual plug-in. This is the cleaner test when one instrument freezes, loses sound, or causes a CPU burst while the rest of the project behaves normally.
Start with the global setting off to confirm the diagnosis, then narrow the exception to the offending instance if your project benefits from resets elsewhere. A start-stop CPU spike that disappears immediately after this change is much stronger evidence than a vague improvement after several unrelated optimization tweaks.
The default compatibility mode uses a 2-millisecond fixed buffer when its two additional options remain off. It can introduce extra delay depending on your Audio Settings buffer, and Image-Line notes that the added delay is doubled for effect plug-ins. Use it on the specific offender rather than enabling compatibility options blindly across a project.
If the basic fixed-buffer option fails, Process maximum size buffers and Use maximum buffer size from host exist for narrower compatibility cases. Both can increase latency further, so they are escalation tools rather than routine performance settings. A plug-in that only needs the default mode should not inherit a heavier workaround.
Under bounded-latency real-time audio processing, transport actions still have to fit extra state and scheduling work inside a tiny real-time window. Compatibility buffering changes how that work reaches a plug-in, so a CPU spike at play or stop can be a timing problem even when steady playback is comfortable.
Watch the Plugin Performance Monitor during the same test. One plug-in jumping when transport changes gives you a concrete instance to inspect. Disable its reset behavior first, then try fixed-size buffers only if reset handling does not solve the fault.
Do not reach for Smart Disable as the first transport fix. Idle plug-in suspension with Smart Disable removes unnecessary processing after plug-ins become inactive, while Reset Plugins on Transport changes what happens when playback state changes. They solve different sources of CPU pressure.
If a transport glitch vanishes after you disable resets for one instance, leave the rest of the project alone. If the fault remains until fixed-size buffers are enabled, keep that compatibility setting on the offending plug-in only, because applying it broadly can add latency without fixing anything else.
The setting exists for a reason. Some plug-ins keep internal states that affect what they produce from one moment to the next, so resetting them can make repeated playback more consistent. The price is extra work at exactly the moment you press play, stop, or jump somewhere else in the Playlist.
A project that runs smoothly once playback settles can therefore hitch at the transport without being generally overloaded. Treat the timing of the spike as evidence. If the CPU jumps only when transport state changes, test transport-related behavior before raising buffers, deleting effects, or rebuilding the whole session.
Resetting every plug-in can make transport feel heavy
Open Audio Settings and find Reset Plugins on Transport in the Mixer section. Turning it off stops FL Studio from globally resetting plug-ins whenever transport functions are used, which can make starting, stopping, and moving the playhead faster and less glitchy with troublesome VSTs.Do not assume the global switch must stay off forever. Disabling resets can allow state-dependent plug-ins to resume differently after you relocate playback, although Image-Line says those differences are unlikely to be significant in most cases. Listen for altered tails, envelopes, sequencers, random generators, and anything else whose output depends on its previous state.
One awkward plug-in does not have to dictate the setting for the entire project. FL Studio’s Wrapper includes the Reset plugin when FL Studio resets, letting you control reset behavior for an individual plug-in. This is the cleaner test when one instrument freezes, loses sound, or causes a CPU burst while the rest of the project behaves normally.
Start with the global setting off to confirm the diagnosis, then narrow the exception to the offending instance if your project benefits from resets elsewhere. A start-stop CPU spike that disappears immediately after this change is much stronger evidence than a vague improvement after several unrelated optimization tweaks.
Fixed-size buffers solve a different transport problem
Some plug-ins misbehave because FL Studio normally sends them variable-sized chunks of audio data. The Wrapper’s Use fixed size buffers option changes that interaction and can fix timing errors, rendering glitches, crashes, or plug-in behavior that falls apart when playback starts or moves.The default compatibility mode uses a 2-millisecond fixed buffer when its two additional options remain off. It can introduce extra delay depending on your Audio Settings buffer, and Image-Line notes that the added delay is doubled for effect plug-ins. Use it on the specific offender rather than enabling compatibility options blindly across a project.
If the basic fixed-buffer option fails, Process maximum size buffers and Use maximum buffer size from host exist for narrower compatibility cases. Both can increase latency further, so they are escalation tools rather than routine performance settings. A plug-in that only needs the default mode should not inherit a heavier workaround.
Under bounded-latency real-time audio processing, transport actions still have to fit extra state and scheduling work inside a tiny real-time window. Compatibility buffering changes how that work reaches a plug-in, so a CPU spike at play or stop can be a timing problem even when steady playback is comfortable.
Transport tests should isolate one failure at a time
Loop a section that normally plays cleanly, then stop and restart it several times from the same position. Next, move the song position marker while playback is running. If the glitch follows those actions rather than the musical density, you have separated a transport problem from an ordinary high-load passage.Watch the Plugin Performance Monitor during the same test. One plug-in jumping when transport changes gives you a concrete instance to inspect. Disable its reset behavior first, then try fixed-size buffers only if reset handling does not solve the fault.
Do not reach for Smart Disable as the first transport fix. Idle plug-in suspension with Smart Disable removes unnecessary processing after plug-ins become inactive, while Reset Plugins on Transport changes what happens when playback state changes. They solve different sources of CPU pressure.
If a transport glitch vanishes after you disable resets for one instance, leave the rest of the project alone. If the fault remains until fixed-size buffers are enabled, keep that compatibility setting on the offending plug-in only, because applying it broadly can add latency without fixing anything else.
