Clicking FX button to open chain in Reaper 6.78 causes application to stop responding when all 4 different plugins are loaded, one on each track

[skylarbattles]

I heard great things about these reverb so I downloaded!

I always load up newly downloaded plugins to test if everything is working.

Unfortunately when one instance of each reverb is loaded on a separate track in Reaper, clicking the fx button on any one track causes Reaper to stop responding and it never responds forcing the user to force quit. I'm on a Silicon Mac and Ventura 13.2 not the newest 13.3

Thanks! :)

[michaelwillis]

@skylarbattles Which version of dragonfly reverb did you download? The reason I am is because I just barely released version 3.2.9 today, but I think it's giving me problems in my DAW, so if you tried that one, please give 3.2.8 a try and let me know how it goes.

[michaelwillis]

In fact, I just deleted the 3.2.9 release... I might kick out another release soon if I can verify that the recent changes aren't causing the bug that I experienced in my DAW.

[falkTX]

@michaelwillis what bug are you seeing?

[michaelwillis]

@falkTX Last night Ardour gave me an explosion of sound while I was working on a session with sfizz and dragonfly reverb. It's possible that it was a big in sfizz, because was editing the SFZ files and I have previously experienced my DAW crashing when sfizz tries to live reload files upon edit.

The burst of noise happened repeatedly, each time I tried reloading my DAW session. This happened right after I switched to dragonfly reverb 3.2.9, so that's why I'm considering that the reverb plugins might be at fault.

[michaelwillis]

...and of course this morning I have not reproduced the bug, so I still have no idea what caused it.

[skylarbattles]

I'll double check but I think it's the newest version. I check if the regression fixes it. Thanks!