Element crashes when using oversampling feature.

[Oortseam]

Element crashes in Reaper when using oversampling at any node with audio inputs.

To Reproduce

• Load Element as a VST plugin into Reaper.

• Load any VST plugin into Element.

• Connect input and output pins.

• Set oversample parameter other then '1x' at this VST node

• Save, close and reopen Reaper project or simply unload and reload Element

• Crash happens (or some distorted sound from Element first and then crash)

• OS:Windows10.0.18362.30 (Win10 RS6 [1903] May 2019 Update)

• host Reaper x64 v6.23

That's the most obvious issue but there are more wrong things with oversampling. Such as distorted pitch shifted sound instead of crash when reloading oversampled VSTi nodes with no audio inputs or sudden crashes with no reload at all.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[mfisher31]

I wasn't able to reproduce this on my end. Is it still happening on your machine?

[Oortseam]

Hello!
Yes. It's still happening on my two machines. What can I try to investigate to help you (or myself :) ) with this issue?

[Oortseam]

Hello!
Downloaded v 0.46.3 yesterday (with a hope of something changed with oversampling crash). Unfortunately the issue is still here which disappoints me so much.
What information (or some kind of testing) is needed from me to solve this problem?

PS: The same thing with standalone version. After you set OS parameter in some module to something higher then 1, save the session and close Element, it's impossible to startup Element once again, since it tries to open the last saved session and crashes immediately.

[mfisher31]

I'm really not sure, except send a crash report if you get one from windows. I cannot reproduce in either the plugin or standalone.