I’ve just started using redux and my chosen DAW just happens to be “reaper” (Arch Linux / CachyOS, renoise has been working fine on this system).
I was getting almost random lockups, but it appears to be when I click to open the VST UI when the default is the full editor view. If I open the VST UI and it’s just the keyboard I can generally open the full editor, although it might have crashed at that point sometime.
Setting “run as separate / dedicated process” stops reaper from completely locking up, but then I get no more sound and no UI on that VST instance until the DAW is restarted.
Does anyone know if this is a reaper or redux thing? or more hopefully any other config that might work around this? Other than remembering to always collapse the full UI. Which yeah I kinda keep forgetting to do …
Can’t reproduce this here on Ubuntu with Wayland / Gnome:
It is crashing when you open the plugin like shown above? Which Desktop are you using? Do you have a NVIDIA card maybe? Recently there was a similar issue, but affecting Renoise.
Yes, exactly that, if I close the window in that layout and re-open that vst instance it’ll hang/lockup and eventually open the without the UI (and without the vst working anymore). I’m on wayland/KDE. But similar enough that I think there must be small change I can make to fix it!
can you choose a plasma x11 session before log in?
I installed plasma-x11-session package to re-enable the X11 option on login and selected that on login but I still get the problem.
When I get the problem I do get this output if I run reaper from a terminal which might be a clue:
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 42 (X_SetInputFocus)
Serial number of failed request: 5156
Current serial number in output stream: 5157
Renoise Redux LOG> Closing log file…
corrupted double-linked list
is there something like
System Settings → Window Management → Window Behavior → Focus
Click to focus?
Yes KDE has that setting. I think that’s the general desktop environment setting that controls when you click a window it becomes focus - as opposed to say the window becoming focus when you just hover the mouse over it, or whatever the other 5 options do! Do you think a different option there might affect the behaviour of opening the vst gui?
if it is set to click to focus most likely not.
Well I seem to have resolved this … for now.
I deleted (well renamed) ~\.config/REAPER i.e. I deleted ALL my reaper config and the problem has gone away. Of course I could now accidentally re-create this scenario, I just have to hope I can identify which configuration change causes this if it happens again.
