Package Details: bitwig-studio 5.3.9-1

Git Clone URL: https://aur.archlinux.org/bitwig-studio.git (read-only, click to copy)
Package Base: bitwig-studio
Description: Digital audio workstation for music production, remixing and live performance
Upstream URL: https://www.bitwig.com/
Keywords: audio daw multimedia music
Licenses: custom
Conflicts: bitwig-8-track, bitwig-studio-legacy
Provides: clap-host, vst-host, vst3-host
Submitter: stylemistake
Maintainer: stylemistake (smoothny, Evergreen)
Last Packager: Evergreen
Votes: 120
Popularity: 1.51
First Submitted: 2016-03-28 16:43 (UTC)
Last Updated: 2025-06-03 03:24 (UTC)

Required by (111)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 19 Next › Last »

stan79 commented on 2025-05-11 11:11 (UTC) (edited on 2025-05-11 16:56 (UTC) by stan79)

Hello. Yesterday Bitwig was working fine. Today, when I try to launch it, it fails with the message: "Child process with PID xxxx exited with error code: 3". I checked .BitwigStudio and found a log file with this crash info: 

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fac05579b23, pid=1613, tid=1717
#
# JRE version: OpenJDK Runtime Environment (21.0.6+7) (build 21.0.6+7-Ubuntu-122.04.1)
# Java VM: OpenJDK 64-Bit Server VM (21.0.6+7-Ubuntu-122.04.1, mixed mode,tiered,compressed class ptrs, z gc, linux-amd64)
# Problematic frame:
# C  [libnvidia-glcore.so.570.144+0xd79b23]

I also use Hyprland with uwsm, which was updated too. Here's what I’ve tried so far: Downgraded both the kernel and nvidia-open to known working versions — no luck. Downgraded uwsm — no effect. Bitwig works if I force it to use OpenGL instead of Vulkan. Anyone else seeing this? Any tips on what might have changed between versions or how to debug further?

auralon commented on 2025-03-08 17:35 (UTC)

For anyone experiencing the same issue as I mentioned below, it was a simple file permissions issue. Solved here

With the resolution being: find ~/.u-he -type f -iname "*dialog*" -exec chmod 755 {} \;

TheEgg commented on 2024-11-06 17:42 (UTC)

Same thing for me auralon, except I didn't notice anything not working with the x11 backend (although I'm not a big plugin user). Nice to have the splash screen back again. I just installed and ran the flatpak from bitwig.com and I get the splash screen with that.

auralon commented on 2024-11-04 22:28 (UTC)

Posting here to see if anyone else is having issues with this package on Wayland? Bitwig doesn't seem to be playing nicely with Xwayland.

When I launch it with a prefix GDK_BACKEND=x11 bitwig-studio then I get a splash screen, which doesn't show otherwise, but some plugins fail to have UI components that are interactable.

Checking the engine.log shows that the following events are occuring:

Unhandled X11 event: 18
X11 ReparentNotify
X11 MapNotify
preset scan completed in 0.329 seconds.
MouseUp Without Tracking

Onyx0452 commented on 2024-07-25 18:48 (UTC)

Not sure how to pass this through to maintainers, but apply the following diff to the PKGBUILD to update to 5.2: https://pastebin.com/tVJUiwQC

IRVNG commented on 2024-05-17 05:57 (UTC)

Updating my last comment, Bitwig support sent me this after I told them that on Windows there's an option to let the plugins adjust to the screen's dpi: "on Windows, this option we are offering in the settings is provided directly by the operating system and on macOS it is not even necessary as an option as macOS takes care of it completely automatically. On Linux, however, it is a very complicated situation depending on which desktop environments and window servers are being used." I responded saying that Linux is indeed complicated. I'm grateful that these people are investing their efforts into making the software work with Linux.

IRVNG commented on 2024-05-13 17:58 (UTC) (edited on 2024-05-13 17:59 (UTC) by IRVNG)

Is anyone using Bitwig with a HiDPI screen and found that some plugins don't scale correctly and look tiny? And if so has anyone found a fix? Bitwig Support told me: "If VST plugins don't contain their own scaling features, they get shown based on the scaling of your operating system and you have to change it there", but my system's scaling is also set correctly so I don't know how to fix this issue.

alcomatt commented on 2024-05-02 07:08 (UTC)

5.1.8 was always a bit off, it appeared before 5.1.8 was officially released and would not run after install. It probably was never updated since initial release. You can go to your ~/.cache/yay/bitwig-studio folder, edit PKGBUILD file to correct the checksum and then issue makepkg to get your shiny 5.1.8 you can then install using pacman -U <pkgfilename>

TheEgg commented on 2024-05-02 07:04 (UTC) (edited on 2024-05-02 07:08 (UTC) by TheEgg)

Is the sha256sum incorrect for 5.1.8? I'm getting validity check errors with paru (although it installs with yay).

« First ‹ Previous 1 2 3 4 5 6 7 8 .. 19 Next › Last »