Flush buffers on DAW Stop

[abnegative]

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.

DUNE 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.

[Kriminal]

Which host?

[abnegative]

Which host?

Reaper and FL Studio

[Kriminal]

By tails I assume you mean long release on notes or fx such as reverb?

They should continue till they come to a natural end, unless you press double stop/panic, AFAIK. (Especially when rendering)

[abnegative]

By tails I assume you mean long release on notes or fx such as reverb?

They should continue till they come to a natural end, unless you press double stop/panic, AFAIK. (Especially when rendering)

Yup that's what I mean by tails.

I just tried what you described in Reaper, FL Studio, and Reason. Double pressing Stop did not kill the tail.
Can you confirm the behavior you expect? Can you elaborate on "double stop/panic"?

[Kriminal]

Double clicking stop on the transport controls in host, or pressing the 'home' key on keyboard.

This may be host specific, but I'm sure it's a common method.

[abnegative]

Double clicking stop on the transport controls in host, or pressing the 'home' key on keyboard.

This may be host specific, but I'm sure it's a common method.

I can confirm this method is used in FL Studio (not so much double clicking stop, but pressing stop while playback is already stopped).
With that said, double clicking stop killed the tail in another plugin (Diva), but did not do so for DUNE. DUNE did appear to have received some message, as I noticed the MIDI input light blink. However, it seems to either ignore the message or mishandle it (I could hear a sample dropout, but the tail continues).

[abnegative]

After using a Midi Monitor in FL Studio, I see that the messages sent on double stop were irrelevant (It just reset pitch on each channel).
I know there is some message the host sends to the plugin when playback is stopped. When the plugin receives this message, it should kill all sound. Omnisphere and Diva do this successfully.

[abnegative]

I've raised this issue with other vendors. Native Instruments appears to be investigating:
https://community.native-instruments.co ... om-the-daw

Here is a demonstration of the issue:
https://www.youtube.com/watch?v=numTE5EW9rI

[Kriminal]

Hopefully a dev will turn up and have a look...or explain why it behaves that way (its fine here, so can't help anymore)

[abnegative]

Thanks for checking it out Kriminal

[Richard]

I'm not sure what you mean exactly, there is different forms of "stop". For instance, hitting stop on the transport bar, MIDI All notes off / all Sounds off messages, or something format-specific (e.g. VST2-specific). The latter two are also host dependent, i.e. some hosts may never send certain messages or in different situations.

Like Kriminal wrote, in Orion it would be double-click Stop or pressing the Home key, which acts as a Reset message & sends an All Notes Off message to all plug-ins.

[abnegative]

I'm not sure what you mean exactly, there is different forms of "stop". For instance, hitting stop on the transport bar, MIDI All notes off / all Sounds off messages, or something format-specific (e.g. VST2-specific). The latter two are also host dependent, i.e. some hosts may never send certain messages or in different situations.

Like Kriminal wrote, in Orion it would be double-click Stop or pressing the Home key, which acts as a Reset message & sends an All Notes Off message to all plug-ins.

Have you had a chance to watch the video demonstration? If so, does it make the issue clear?

[Richard]

Have you had a chance to watch the video demonstration? If so, does it make the issue clear?

Not quite. For what purpose exactly do you need this? Completely resetting the audio on just a transport stop message seems wrong ihmo. I'm pretty sure most users would object to that, and it is also guaranteed to cause issues at least for some applications.

[abnegative]

Have you had a chance to watch the video demonstration? If so, does it make the issue clear?

Not quite. For what purpose exactly do you need this? Completely resetting the audio on just a transport stop message seems wrong ihmo. I'm pretty sure most users would object to that, and it is also guaranteed to cause issues at least for some applications.

I figured it would be easier to show you than tell you. Please see this video explanation:

https://youtu.be/osppgnEzeDI