Hi,
Does anybody uses Rack 2 Pro in Bitwig (4.1.6) on Arch based Linux distro?
On Manjaro, I have an issue that it’s easy to reproduce : just load the vst on a track, close the plugin window, then reopen it and it will crash.
That being said, the standalone version is working fine.
Yes, I had the same thing and another person on reddit had the same issue. I reported it and spent a while trying to get it solved but I eventually moved to KDE Neon because it works there. I would love for this to get fixed so I can go back to arch.
Please report it to support.
I already did, and they told me today that they didn’t try to reproduce it on Arch yet… Hope they will investigate more on this.
I have some Windows plugin that I run through Yabridge, is it working fine on KDE Neon ? Why did you choose it ?
I used Neon for a few years because it provides up to date desktop environment but stable base, generally works really well. I’ve got loads of plugins running in yabridge, no problems.
It’s quite annoying that they haven’t tried to reproduce it, I reported it just before Christmas. I’m glad that it’s not just me because it’s obviously a wider issue affecting others. Hopefully they can reproduce it soon.
The team is looking into it. I just can’t reproduce here as I’m not on a Linux machine. Sorry for any confusion.
Hi, I just want to inform you that this issue is still there in the V2.1 preview. Also tested on Bitwig 4.2 Beta 1, same behaviour.
I can confirm the same.
I can’t reproduce this - it all works for me. I’m using Arch Linux (up to date as of today), Bitwig 4.1.6, and Rack 2.1.0, freshly installed with only Core and Fundamental installed.
I wonder whether the problem is with one of your Rack plugins? What happens if you move all the plugins out of ~/.Rack2/plugins and try again?
If you have a ~/.Rack2/template-plugin.vcv, try moving that aside too…?
I currently have arch on a timeshift snapshot which I restored to test the new update and then reverted when it wasn’t working (I’ve had to change distro to be able to use Rack vst) but previously I tested it with a new user and in a manjaro live usb and had the same problem in both (I didn’t log into rack or bitwig so it would have been just with built in/fundamental modules with no template).
For me at least it is a problem limited to only bitwig, it works in renoise, reaper, bespokesynth.
The issue is rather frustrating because it doesn’t seem to register as a crash in the Rack log although if I start Rack standalone after the crash in bitwig it says that it crashed and asks to clear the patch.
I guess you probably have this info on the issue tracker already but I found some stuff in the journal when it happens:
Jan 24 17:22:29 hyperion kernel: BitwigPlug:sh0[17360]: segfault at 6899 ip 00007f708cdf8a2d sp 00007f701cee5988 error 4 in libRack.so[7f708c686000+b85000]
Jan 24 17:22:29 hyperion kernel: Code: af ff 48 83 f8 88 77 a1 c7 83 44 68 00 00 01 00 00 00 e9 7b ff ff ff 66 0f 1f 44 00 00 48 85 ff 74 5b 55 48 89 fd 48 83 ec 28 <48> 8b 87 58 68 00 00 f3 0f 6f 87 48 68 00 00 0f 29 44 24 08 48 89
Jan 24 17:22:29 hyperion systemd[1]: Started Process Core Dump (PID 17378/UID 0).
Jan 24 17:22:29 hyperion systemd-coredump[17379]: [?] Process 17300 (BitwigPluginHos) of user 1000 dumped core.
Module linux-vdso.so.1 with build-id 55f19b5e03a88be11e86025133bff8f8cb6bcaf3
Stack trace of thread 17360:
#0 0x00007f708cdf8a2d n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64
Jan 24 17:22:29 hyperion systemd[1]: systemd-coredump@5-17378-0.service: Deactivated successfully.
Jan 24 17:23:02 hyperion kernel: BitwigPlug:sh0[17445]: segfault at 6899 ip 00007fb40b935a2d sp 00007fb3a7f94988 error 4 in libRack.so[7fb40b1c3000+b85000]
Jan 24 17:23:02 hyperion kernel: Code: af ff 48 83 f8 88 77 a1 c7 83 44 68 00 00 01 00 00 00 e9 7b ff ff ff 66 0f 1f 44 00 00 48 85 ff 74 5b 55 48 89 fd 48 83 ec 28 <48> 8b 87 58 68 00 00 f3 0f 6f 87 48 68 00 00 0f 29 44 24 08 48 89
Jan 24 17:23:02 hyperion systemd[1]: Started Process Core Dump (PID 17463/UID 0).
Jan 24 17:23:02 hyperion systemd-coredump[17464]: [?] Process 17393 (BitwigPluginHos) of user 1000 dumped core.
Module linux-vdso.so.1 with build-id 55f19b5e03a88be11e86025133bff8f8cb6bcaf3
Stack trace of thread 17445:
#0 0x00007fb40b935a2d n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64
Jan 24 17:23:02 hyperion systemd[1]: systemd-coredump@6-17463-0.service: Deactivated successfully.
Doesn’t look very useful from what I can tell but if there are some tests we can do which will provide a meaningful output then I’d be happy to timeshift back to Arch.
Thanks for you help. Unfortunately, I already tried with no success.
May I ask you what’s your setup ? Are you using Jack, Yabridge, … ?
No sure if this wsill make any difference, but have you tried changing the Plug-in Hosting setting in Bitwig to host VCV individually?
Yes I also tried every different sandboxing options, with no difference.
I’ve tried with ALSA and PulseAudio, and both work fine.
I’m running Arch in a VMWare VM and it’s pretty flaky, so I wouldn’t base any decisions on my setup. But I can open, close, and re-open the Rack VST window in Bitwig without any problems.
@TroubledMind: You’re sadly right that that log isn’t very helpful. I think I’d need to reproduce the crash to get any further with it.
I did some test in a Virtual Box too. I tried EndeavourOS (also Arch based) and it worked. Then I tried again with another version of Manjaro and the problem remains. As @Richie had success with Arch, I’m pretty sure it’s related to Manjaro. So I think I will move to EOS. Thank you for your help !
Damn, before installing I tested in live usb (EOS) and the problem happened again ! Wtf !? It’s working in the VirtualBox but not with the Live USB. This is black magic, it’s driving me crazy. @TroubledMind May I ask you to test with a VirtualBox too, just to check if you’re experiencing the same behaviour ?
I have Arch so it’s definitely not just a manjaro problem. For me the vst was working in Arch and then sometime just before Christmas it stopped working. I have a laptop with manjaro on it and it worked there when it had initially stopped working on Arch but then stopped working there too. The last time I fired up the manjaro laptop (when the last Rack update was released) it was working again so I restored my timeshift snapshot of Arch and still wasn’t working.
I’ll see what I can do with virtualbox, haven’t use it before.
Ok, managed to get Endeavour installed in virtualbox and Rack doesn’t work inside Bitwig.
It’s working for me in VirtualBox but it’s also very very flaky, it would not be usable. @Richie would it be possible for you to test in a more stable environment than VirtualBox ? Like a live USB or on an installed system ? Because it’s difficult to confirm that the bug can’t be reproduced in such an unstable environment.
I noticed that it’s working when you activate the 3D acceleration in the Virtualbox settings:
Can you confirm the same ?
Yes, it works for me with that enabled too.
