Flush buffers on DAW Stop

[Richard]

Thank you abnegative for taking the time to make this video! Excellent explanation, no more questions

We'll look for the message Reaper sends exactly so we can realize a full stop. Note this may only work using VST2 plugins. After quickly testing this in Reaper it seemed like all VST3 plugins would render the tail.

[abnegative]

Thank you abnegative for taking the time to make this video! Excellent explanation, no more questions

We'll look for the message Reaper sends exactly so we can realize a full stop. Note this may only work using VST2 plugins. After quickly testing this in Reaper it seemed like all VST3 plugins would render the tail.

No problem! Thank you for looking into this. There are a ton of threads in the Reaper forums regarding this issue with various plugins, so I'm sure this will save a lot of people a lot of time.

I can confirm that this applies to both VST2 and VST3. In my testing, Omnisphere VST3i responds correctly to a reset message. I'm not very familiar with the VST standard, but perhaps this is some message from the host that is optional for the plugin to handle (just speculating here). Anyway, I'm happy to perform any more testing and provide any data needed to help get to a resolution.

[abnegative]

Any luck with this?

I just noticed that the issue does not appear to be present in the VST3i version of DUNE 3. I've been intentionally using the VST2 version because it reports the preset name.

[Teksonik]

I use multiple instances of DUNE 3 in almost every one of my FL Studio projects and I don't have any issues with render. Perhaps I just don't understand what you're reporting.

Have you tried this render setting "cut remainder"?

D3 020523-1.png

[abnegative]

Teksonik, this is independent of the DAW used. In order to experience the issue, you must render while the tail is still audible.

Here's an explanation:
https://www.youtube.com/watch?v=osppgnEzeDI

[Teksonik]

Ask yourself why no one else has reported this issue in all the years that DUNE 3 has been released. This would appear to be a rare use case issue.

Anyway I never have to render except on final render of the song and I use cut remainder so it doesn't affect me but good luck I hope they fix your problem.

[abnegative]

I asked myself. I concluded I am a rare case individual. I can do things most can't.

There are applications for on-the-fly rendering. Here is one such example:
https://www.youtube.com/watch?v=uRkAkz-ImUo

[Teksonik]

II can do things most can't.

Or you're doing things most don't have to.....

Burning MIDI to Audio doesn't make any sense whatsoever to me and like I said you're the only one reporting this "probelm" so.......

But anyway good luck maybe Synapse fix it for you.

[abnegative]

II can do things most can't.

Or you're doing things most don't have to.....

Burning MIDI to Audio doesn't make any sense whatsoever to me and like I said you're the only one reporting this "probelm" so.......

But anyway good luck maybe Synapse fix it for you.

"to me" are the operative words. One day it'll click.

[Teksonik]

One day it'll click.

Yes one day it will click why you're the only one with this "problem". The rest of us know how to use our DAWs and DUNE 3 properly.

Here let me give you a hint in Reaper:

Reaper 020623.png

Then delete remainder. Simple.

[Richard]

Yes it is simple, if you need it all the time however, it would be an extra step to perform.

Anyway this will come with the next maintenance update, so closing this thread