Massive X should clear its internal buffers when it receives a stop message from the DAW

abnegative · November 2022

If the plugin doesn't flush its buffers when it receives a stop message from the host, any tail audio will be incorrectly included in a render, unless the user waits for the tail to stop every time.

Massive X should clear its internal buffers when it receives a stop message.

Please do this on any stop message, regardless of whether the host was playing.

Interestingly, Kontakt 7 does not have this issue. Maybe this implies different internal dev teams that maybe should work together?

Nico_NI · November 2022

Thanks for flagging this @abnegative. I'll forward this to the Massive X team.

Nico_NI · November 2022

Our team tried to reproduce what you explained to no avail. Would you have any more details or a screen recording that we could look into?

abnegative · November 2022

https://community.native-instruments.com/discussion/comment/39359#Comment_39359

I'll make a video now. Thanks for the quick response!

abnegative · November 2022

@Nico_NI

https://www.youtube.com/watch?v=numTE5EW9rI

abnegative · November 2022

In case this is helpful, here is more information as requested by Synapse Audio Software:

https://www.youtube.com/watch?v=osppgnEzeDI

https://forum.synapse-audio.com/viewtopic.php?f=1&t=13287&start=0

abnegative · February 2023

Any updates on this? I would imagine the fix is trivial.

abnegative · February 2023

Synapse Audio has resolved this issue for DUNE 3.

When I asked them what the fix was they said "the plugin is simply fully reset when turned off (as opposed to just sending All Notes Off)."

@Nico_NI Hopefully you can forward this information to the team.

abnegative · February 2023

A quote from Image-Line describing what FL Studio does when the transport stop is pressed while playback is stopped:

"It deactivates and reactivates the plugin, and sends the MIDI pitch bend range to synths.

If the plugin is deactivated, it should flush the delay buffers, but not all plugins do that."

Massive X is one such plugin that doesn't do that.

While I'm at it, I think most would agree that presets should be selectable with a single click.

Massive X is such an amazing synth so I'm eager to see it perfected.

abnegative · May 2023

the calls that are supposed to cause plugins to flush buffers are as follows.

VST3: setProcessing(false)

VST2: effStopProcess

CLAP: reset()

LV2: deactivate()

source: https://forum.cockos.com/showpost.php?p=2678928&postcount=15

Massive X should clear its internal buffers when it receives a stop message from the DAW

Comments

Categories