[SOLVED] Wayland - Some inputs don't work in multiple u-he plugins

RELATED
PRODUCTS

Post

I recently switched to Wayland full-time after switching from Nvidia to AMD on a new build PC. Everything has been surprisingly solid, apart from one thing... Now, a bunch of inputs in u-he plugins don't work, in Bitwig (5.2.4).

Is this a known issue, and is it something that is likely to get resolved at some point in the non-too-distant future, by any chance?

Examples:

Repro 5
- Voices
- search presets

Diva
- search presets

Hive
- Voice mode
- Voices
- search presets
- numerous other

Bazille
- search presets

Thanks in advance :)
Last edited by virusav on Sat Nov 23, 2024 1:06 pm, edited 1 time in total.

Post

Hi, this is not a known issue, thanks for mentioning.
But I cannot say if our plugins are compatible to Wayland, this is nothing we ever tested so far.
That QA guy from planet u-he.

Post

Thanks tasmaniandevil for letting me know.

Hopefully Wayland testing will come into play at some point for u-he plugins. Quite a few modern distros are switching away from Xorg and adopting Wayland instead.

I've tried switching several times over the years from Xorg to Wayland, but it never felt quite ready and I had various issues that meant I switched back to Xorg. Since making the switch about 3 months ago, everything has been great and I can't see myself every going back. This u-he interface bug doesn't warrant switching back to either, but it does mean I can't use all my plugins to their full extent, at least not yet.

My fingers are crossed that this comes onto the devs radar sooner rather than later.

Thanks to all at u-he for the super awesome plugins, and MAHOOSIVE thanks for the Linux support to boot.

Post

virusav wrote: Tue Oct 01, 2024 6:39 pm I recently switched to Wayland full-time after switching from Nvidia to AMD on a new build PC. Everything has been surprisingly solid, apart from one thing... Now, a bunch of inputs in u-he plugins don't work, in Bitwig (5.2.4).

Is this a known issue, and is it something that is likely to get resolved at some point in the non-too-distant future, by any chance?

Examples:

Repro 5
- Voices
- search presets

Diva
- search presets

Hive
- Voice mode
- Voices
- search presets
- numerous other

Bazille
- search presets

Thanks in advance :)
Do you have XWayland installed on your computer? It is a 1:1 installation of Xorg, under the control of Wayland. Xorg compatibility is 100% supported by Linux, through Wayland with XWayland. What distro are you using? Check and confirm that you have XWayland installed. If you do, then the problem is not with Wayland.
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.:mad:
(Also: I'm Accused of lying about Linux—it boots, runs my pro audio workflow, stays stable, updates--though yearly dismissed as “niche”. Yet I'm the deluded one.)
:roll:

Post

I recently updated to latest Kubuntu, which switched to using Wayland as default, and I'm not seeing these issues on my end. Search and various dropdown menus in Hive and Diva seem to work fine. (REAPER + clap versions.)
Artist name Ben Enkindle. I (try to) make electronic music with Linux software.

Post

audiojunkie wrote: Thu Oct 03, 2024 4:51 pm Do you have XWayland installed on your computer? It is a 1:1 installation of Xorg, under the control of Wayland. Xorg compatibility is 100% supported by Linux, through Wayland with XWayland. What distro are you using? Check and confirm that you have XWayland installed. If you do, then the problem is not with Wayland.
Yeah, I have it installed. I just checked if Bitwig is using it and according `xlsclients -l` it is not.

I tried forcing Bitwig to use it with `env -u WAYLAND_DISPLAY bitwig-studio` and that didn't work either.

I'm running Arch (btw).

It's really weird, when I click UI components in the synth that don't work, then I can visibly see the "undo" button in the Bitwig interface click.

Post

elcalen wrote: Tue Oct 22, 2024 3:00 pm I recently updated to latest Kubuntu, which switched to using Wayland as default, and I'm not seeing these issues on my end. Search and various dropdown menus in Hive and Diva seem to work fine. (REAPER + clap versions.)
You're on KDE and I'm on Gnome, which could very well play a part in why you're not seeing the issue.

Post

Just checked the `engine.log` for Bitwig and I'm seeing the "MouseUp Without Tracking" event every time I click one of the UI elements that isn't working:

Code: Select all

tail -f .BitwigStudio/log/engine.log 
X11 ConfigureNotify
time since ViewMan started 87.00
first draw time since ViewMan started 193.39
Unhandled X11 event: 18
X11 ReparentNotify
X11 MapNotify
preset scan completed in 0.329 seconds.
MouseUp Without Tracking
[2024-11-4 19:28:13.274 BITWIG_ENGINE u-he Hive info] Closing plug-in undo history file
MouseUp Without Tracking

[2024-11-4 19:28:19.194 BITWIG_ENGINE u-he Hive info] Closing plug-in undo history file



MouseUp Without Tracking
MouseUp Without Tracking
MouseUp Without Tracking
AM_View_WavetableSelector::listenerValueChanged 3 1065353216
NEXT FILE
relPath 
Wave path: '/home/keito/.u-he/Hive/Wavetables/Complex/Bright Excite.wav'
SampleFormat: IEEE Float
numChannels: 1
sampleRate: 44100
bitsPerSamples: 32
dataBlockSize: 4
numSamples: 163840 -> 80
wav import min -1.74974 max 1.51750
Mid Samples 1023-1027 -0.05046, -0.05077, -0.05314, -0.05357, -0.05278
success, but xWaveTableFile[ 0 ].Type != AM_SampleFileDescriptor::wavetable
MouseUp Without Tracking
[2024-11-4 19:28:33.474 BITWIG_ENGINE u-he Hive info] Closing plug-in undo history file
AM_View_WavetableSelector::listenerValueChanged 3 1065353216
NEXT FILE
relPath 
Wave path: '/home/keito/.u-he/Hive/Wavetables/Complex/Choice of Eight A.wav'
SampleFormat: IEEE Float
numChannels: 1
sampleRate: 44100
bitsPerSamples: 32
dataBlockSize: 4
numSamples: 16384 -> 8
wav import min -1.00000 max 1.00000
Mid Samples 1023-1027 0.35449, 0.35220, 0.34994, 0.34768, 0.34539
success, but xWaveTableFile[ 0 ].Type != AM_SampleFileDescriptor::wavetable
MouseUp Without Tracking
MouseUp Without Tracking
MouseUp Without Tracking
MouseUp Without Tracking
MouseUp Without Tracking
AM_View_WavetableSelector::listenerValueChanged 3 1065353216
NEXT FILE
relPath 
Wave path: '/home/keito/.u-he/Hive/Wavetables/Complex/Choice of Eight B.wav'
SampleFormat: IEEE Float
numChannels: 1
sampleRate: 44100
bitsPerSamples: 32
dataBlockSize: 4
numSamples: 16384 -> 8
wav import min -1.29367 max 1.46498
Mid Samples 1023-1027 -0.53716, -0.53501, -0.53716, -0.53501, -0.53716
success, but xWaveTableFile[ 0 ].Type != AM_SampleFileDescriptor::wavetable
MouseUp Without Tracking
MouseUp Without Tracking
MouseUp Without Tracking
MouseUp Without Tracking
MouseUp Without Tracking
MouseUp Without Tracking
AM_View_WavetableSelector::listenerValueChanged 3 1065353216
NEXT FILE
relPath 
Wave path: '/home/keito/.u-he/Hive/Wavetables/Complex/Disjointed.wav'
SampleFormat: PCM
numChannels: 1
sampleRate: 44100
bitsPerSamples: 16
dataBlockSize: 2
numSamples: 522240 -> 255
wav import min -0.49985 max 0.49999
Mid Samples 1023-1027 -0.00797, -0.00064, 0.00798, 0.01530, 0.02394
success, but xWaveTableFile[ 0 ].Type != AM_SampleFileDescriptor::wavetable
MouseUp Without Tracking
AM_RootView::mouseDown
MouseUp Without Tracking
AM_RootView::mouseDown
MouseUp Without Tracking
MouseUp Without Tracking
MouseUp Without Tracking
[2024-11-4 19:29:27.554 BITWIG_ENGINE u-he Hive info] Closing plug-in undo history file
MouseUp Without Tracking
MouseUp Without Tracking
MouseUp Without Tracking
MouseUp Without Tracking
beforeDelete (/home/jenkins/workspace/linux-plugins-pipeline/AM_View/AM_Cairo_View.cpp:48)
AM_ViewMan::beforeDelete()
killing ImageLoader thread
ImageLoader thread killed
AM_ViewMan::unregisterViewsPreferenceListeners


Post

Also, not sure where the "jenkins" user is coming from, unless it's some build pipeline used for the plugin, as that is not my username :D

Post

I've installed bitwig-studio via the AUR (as opposed to using the flatpak version, which I've had issues with in the past for things like VSTs).

It's also worth mentioning that when I launch Bitwig via the following command, then it shows a splash screen, which is not something that happens when launched without the prefix.

Code: Select all

GDK_BACKEND=x11 bitwig-studio
Even when launched with the prefix, the app is not listed in `xlsclients`.

Post

Noticed that java apps might not always play nicely with Wayland
(https://discourse.ubuntu.com/t/environm ... kers/12750)
$_JAVA_AWT_WM_NONREPARENTING

Many Java apps (such as Intellij) don’t support Wayland natively and break on most XWayland implementations (and other non-reparenting window managers). This often results in blank screens. To make them work, set _JAVA_AWT_WM_NONREPARENTING=1. I consider this a toolkit bug, but it seems unlikely to be fixed.
Had a play around with various launch prefixes, e.g.

Code: Select all

_JAVA_AWT_WM_NONREPARENTING=1 XDG_SESSION_TYPE=x11 WAYLAND_DEBUG=1 GDK_BACKEND=x11 bitwig-studio 
[2024-11-4 22:48:1.294 info] About to start the following process:  /opt/bitwig-studio/bin/show-splash-gtk /opt/bitwig-studio/resources/splash-bitwig-studio.png
[2024-11-4 22:48:1.294 info] Child process launched with PID 78400
[2024-11-4 22:48:1.294 info] Backing up log file "/home/keito/.BitwigStudio/log/BitwigStudio.log" to "/home/keito/.BitwigStudio/log/BitwigStudio-previous-run.log"
[2024-11-4 22:48:1.295 info] About to start the following process:  /opt/bitwig-studio/bin/BitwigStudio -cp /opt/bitwig-studio/bin/bitwig.jar:/opt/bitwig-studio/lib/cp:/opt/bitwig-studio/bin/libs.jar -Dorg.sqlite.lib.path=/opt/bitwig-studio/lib/bitwig-studio -XX:+UseZGC -XX:+ZGenerational -Xms300m -Xmx3g -Djava.io.tmpdir=/tmp/bitwig-keito -DinstallationRoot=/opt/bitwig-studio -DsplashPid=78400 -Djava.awt.headless=true -XX:ErrorFile=/home/keito/.BitwigStudio/bitwig-studio-jvm-crash.log com.bitwig.flt.app.BitwigStudioMain
Then noticed the process that is launched:

Code: Select all

/opt/bitwig-studio/bin/BitwigStudio -cp /opt/bitwig-studio/bin/bitwig.jar:/opt/bitwig-studio/lib/cp:/opt/bitwig-studio/bin/libs.jar -Dorg.sqlite.lib.path=/opt/bitwig-studio/lib/bitwig-studio -XX:+UseZGC -XX:+ZGenerational -Xms300m -Xmx3g -Djava.io.tmpdir=/tmp/bitwig-keito -DinstallationRoot=/opt/bitwig-studio -DsplashPid=78400 -Djava.awt.headless=true -XX:ErrorFile=/home/keito/.BitwigStudio/bitwig-studio-jvm-crash.log com.bitwig.flt.app.BitwigStudioMain
Wondered if that was somehow not adhering to Xwayland.
Last edited by virusav on Mon Nov 04, 2024 10:52 pm, edited 1 time in total.

Post

elcalen wrote: Tue Oct 22, 2024 3:00 pm I recently updated to latest Kubuntu, which switched to using Wayland as default, and I'm not seeing these issues on my end.
Are you using the deb package, or the flatpak? What does the launch process look like if you start it via a terminal? e.g.

Code: Select all

/opt/bitwig-studio/bin/BitwigStudio -cp /opt/bitwig-studio/bin/bitwig.jar:/opt/bitwig-studio/lib/cp:/opt/bitwig-studio/bin/libs.jar -Dorg.sqlite.lib.path=/opt/bitwig-studio/lib/bitwig-studio -XX:+UseZGC -XX:+ZGenerational -Xms300m -Xmx3g -Djava.io.tmpdir=/tmp/bitwig-keito -DinstallationRoot=/opt/bitwig-studio -DsplashPid=78400 -Djava.awt.headless=true -XX:ErrorFile=/home/keito/.BitwigStudio/bitwig-studio-jvm-crash.log com.bitwig.flt.app.BitwigStudioMain
EDIT: Ignore me, just re-read and you're using Reaper.
Last edited by virusav on Mon Nov 04, 2024 11:00 pm, edited 1 time in total.

Post

Also, are you using a HiDPI screen with any scaling?

Post

virusav wrote: Mon Nov 04, 2024 10:59 pm Also, are you using a HiDPI screen with any scaling?
I'm on 1080p, no scaling, for what it's worth.

And yeah, I'm on KDE—that could of course be a factor. Though Gnome has been using Wayland as default for longer than KDE has, so I feel like if many people were having issues with it, we would have had more reports?

And I was recently playing around with the trial version of Bitwig as well, and noticed no obvious problems. BUT I can't remember for certain if I accessed any of the specific features you were having issues with. Unfortunately I no longer have Bitwig installed, so I can't test it now.
Artist name Ben Enkindle. I (try to) make electronic music with Linux software.

Post

FWIW I chatted to Bitwig regarding the captured logs to see if this is an issue they need to fix their end, but they responded saying that the problem exists within the u-he plugin. Hopefully, as more users transition to wayland, this will become an issue that warrants some attention from the devs.

Post Reply

Return to “u-he Linux support”