Package Details: bitwig-studio 4.3.4-1

Git Clone URL: (read-only, click to copy)
Package Base: bitwig-studio
Description: Digital audio workstation for music production, remixing and live performance
Upstream URL:
Keywords: audio daw multimedia music
Licenses: custom
Conflicts: bitwig-8-track, bitwig-studio-legacy
Provides: bitwig-studio
Submitter: stylemistake
Maintainer: stylemistake (smoothny, EvergreenTree)
Last Packager: EvergreenTree
Votes: 101
Popularity: 1.68
First Submitted: 2016-03-28 16:43 (UTC)
Last Updated: 2022-08-10 02:26 (UTC)

Latest Comments

EvergreenTree commented on 2022-05-11 22:19 (UTC)

I created a version of the bitwig-studio-beta PKGBUILD that works with the flatpak version of Bitwig studio 4.3 beta 1. It does require ostree as a make dependency to extract the files, but it seems to work fine. From what I've heard, they will be distributing more than just the flatpak in the future, so it probably won't be an issue anyway. Here is the PKGBUILD for reference:

alcomatt commented on 2022-05-11 22:12 (UTC)

from 4.3 Bitwig is moving away from debian packages and instead going the flatpak way, which is rather annoying. Do you think it will still be possible to package it for arch without being forced into the flatpak world of parallel(and duplicate) dependencies?

alcomatt commented on 2022-04-29 14:17 (UTC)

sha256 sums are good in the PKGBUILD and the source deb by Bitwig has not been modified. Please delete your yay/yaourt cache folder and try building package again. Something might have corrupted your deb file download.

kalimerox commented on 2022-04-29 14:01 (UTC) (edited on 2022-04-29 14:01 (UTC) by kalimerox)

I get

"" Found bitwig-studio-4.2.3.deb ==> Validating source files with sha256sums... bitwig-studio-4.2.3.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build bitwig-studio ""

when i try to upgrade on my manjaro machine...

1uk commented on 2022-02-17 20:13 (UTC) (edited on 2022-02-17 20:18 (UTC) by 1uk)

Works now! Added my user to the audio group. %jackd gives the same error message, but jack_control works and Qjackctl as well. Nice, thank you. Edit: But now, when I open pavucontrol I don't see bitwig as playback, and I don't hear any sound.

stylemistake commented on 2022-02-17 15:33 (UTC)

Refer to ArchWiki, you probably forgot to add yourself to the audio group and specify realtime limits/settings in sysctl.d. If you wish, you can also use jack-dbus which autostarts whenever the application requests it. Qjackctl is also a useful program.

1uk commented on 2022-02-17 15:15 (UTC) (edited on 2022-02-17 15:27 (UTC) by 1uk)

Hello, I installed it, and it works, but I can't start the audio engine. It says: "Unable to connect to jack server". I use pulseaudio and have pulseaudio-jack and jack2 installed. When I run jackd it just gives a info message to stdout. Can you help me? Should I switch to pipewire and deinstall pulse? <img alt="error message" src="" title="Unable to connect to jack server" />

when I run jackd:

jackdmp 1.9.20
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2021 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
jack_get_descriptor : dll
jack_get_descriptor returns null for ''
jack_get_descriptor : dll
jack_get_descriptor returns null for ''
jack_get_descriptor : dll
jack_get_descriptor returns null for ''
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns

Usage: jackdmp [ --no-realtime OR -r ]
               [ --realtime OR -R [ --realtime-priority OR -P priority ] ]
      (the two previous arguments are mutually exclusive. The default is --realtime)
               [ --name OR -n server-name ]
               [ --timeout OR -t client-timeout-in-msecs ]
               [ --loopback OR -L loopback-port-number ]
               [ --port-max OR -p maximum-number-of-ports]
               [ --slave-backend OR -X slave-backend-name ]
               [ --internal-client OR -I internal-client-name ]
               [ --internal-session-file OR -C internal-session-file ]
               [ --verbose OR -v ]
               [ --clocksource OR -c [ h(pet) | s(ystem) ]
               [ --autoconnect OR -a <modechar>]
                 where <modechar> is one of:
                   ' ' - Don't restrict self connect requests (default)
                   'E' - Fail self connect requests to external ports only
                   'e' - Ignore self connect requests to external ports only
                   'A' - Fail all self connect requests
                   'a' - Ignore all self connect requests
               [ --replace-registry ]
               [ --silent OR -s ]
               [ --sync OR -S ]
               [ --temporary OR -T ]
               [ --version OR -V ]
         -d master-backend-name [ ... master-backend args ... ]
       jackdmp -d master-backend-name --help
             to display options for each master backend

alcomatt commented on 2022-01-13 21:41 (UTC)

4.1.3 released with workaround for nVidia driver fixes.

jarkko commented on 2021-12-30 22:11 (UTC)

Just to remark: the latest NVIDIA driver works with Bitwig Studio, if GNOME on Wayland is used.

alcomatt commented on 2021-12-13 22:00 (UTC) (edited on 2021-12-14 21:50 (UTC) by alcomatt)

Today Bitwig started crashing on start, taking X with itself. X session crashes silently and respawns. Most likely caused by some recent arch updates, but cannot seem to figure out which ones. Nothing conclusive in the logs.

It turned out to be nvidia driver update v 495.46

Specifically, this is listed in release notes Known Issues section:

 Known Issues

Interaction with pthreads
Single-threaded applications that use dlopen() to load NVIDIA's libGL library, and then use dlopen() to load any other library that is linked against libpthread will crash in libGL. This does not happen in NVIDIA's new ELF TLS OpenGL libraries (see Chapter 5, Listing of Installed Components for a description of the ELF TLS OpenGL libraries). Possible workarounds for this problem are:

Load the library that is linked with libpthread before loading libGL.

Link the application with libpthread.

Bitwig Nvidia Users be aware, downgrading nvidia driver to v495.44 resolves issue.

phunni commented on 2021-11-18 15:18 (UTC)

Not sure if this is to do with my setup, the package or a bug in bitwig, but bitwig is crashing almost straight away. I get the option to log in, to choose demo, I choose demo, I get a window telling me to click on the dashboard button. I can't click on anything and then, after a few moments, it crashes. No error message - even if I run it from cli.

settyness commented on 2021-11-08 19:37 (UTC)

That's really neat if you use flatpak.

abique commented on 2021-11-07 07:18 (UTC) (edited on 2021-11-07 07:19 (UTC) by abique)

On flatpak there is a 3.3 branch, a stable, early-access and beta branch. Once 4.1 is out there will be a 4.0 branch as stable and early-access will point to 4.1.

You can point them to flatpak for early-access and beta.

flatpak install --branch=beta com.bitwig.BitwigStudio

flatpak run --branch=beta com.bitwig.BitwigStudio

settyness commented on 2021-11-07 01:37 (UTC)

I really wish there was a way to keep people from flagging pre-release versions and/or differentiating between the two. Unfortunately, the only thing I can think of is establishing a pre-release branch, and I don't think that will stop people from flagging, and it's too much overhead.

00zerozero commented on 2021-08-07 11:15 (UTC) (edited on 2021-08-07 11:17 (UTC) by 00zerozero)

Works fine now, first download had an error, after running yay again it worked.

almet commented on 2021-07-14 16:51 (UTC) (edited on 2021-07-14 16:52 (UTC) by almet)

It's working for me (installed with yay this morning). Thanks a lot stylemistake.

Serum commented on 2021-07-14 15:45 (UTC)

I can't download this. I've updated my mirrors but the download speed is straight up zero bytes/second. Anyone else having this issue?

stylemistake commented on 2021-07-13 19:54 (UTC)

Updated PKGBUILD, if anything doesn't work or new dependencies must be added, let me know.

almet commented on 2021-07-13 18:25 (UTC)

Yes! Bitwig 4 is finally out there :-)

I'm not sure how I should proceed to install it. Any ideas?

crimsondeath commented on 2021-07-09 16:42 (UTC)

Hey, I'm on 3.1.3, im kinda new to linux, and im using Manjaro xfce. I've managed to use debtap to convert the .deb. Bitwig is running on my machine.

In windows, my track pad was able to navigate along the XY axis freely however now I have to hold down CTRL and Shift to move exclusively along the X or Y axis. Does anyone have a solution to this? Many Thanks!

abique commented on 2021-05-11 16:28 (UTC)

@stylemistake, yes that could work, but early-access is not beta either. I think the correct solution is to have those three channels: beta/early-access/stable and a good set of scripts to make the maintenance easier.

stylemistake commented on 2021-05-11 16:24 (UTC)

Well, perhaps we can reuse the beta package for this?

dgmulf commented on 2021-05-11 16:20 (UTC)

@abique Yes, Bitwig is aware of the issue, and a fix is coming in the next release.

@stylemistake The problem with that approach is that users of AUR helpers like yay who want a strictly stable experience need to manually hold back upgrades for prerelease versions.

abique commented on 2021-05-11 10:13 (UTC)

The concept is that there are two channels: stable and early-access.

The very same builds gets marked as stable once it has been out for some time and no serious regression did hit the support inbox.

I think the best it to make an other package: bitwig-studio-early-access

stylemistake commented on 2021-05-11 10:03 (UTC) (edited on 2021-05-11 10:07 (UTC) by stylemistake)

I would prefer this AUR entry to be a single, continuous source of package versions, because it is always possible to check them out from git. We could prefix these pre-release versions as: 3.3.8.pre-1, just to provide a better clarity for end users. Thoughts?

abique commented on 2021-05-11 06:40 (UTC) (edited on 2021-05-11 06:41 (UTC) by abique)

On flatpak there are two branches: stable -> 3.3.7 and early-access -> 3.3.8

@dgmulf did you report your issue to ?

dgmulf commented on 2021-05-11 01:08 (UTC) (edited on 2021-05-11 01:09 (UTC) by dgmulf)

3.3.8 is considered a "pre-release", and has a project-breaking bug on my system (the Amount control in the ADSR modulator no longer functions). Should there be a separate package for pre-release versions, e.g. bitwig-prerelease?

abique commented on 2021-04-01 14:20 (UTC)

Yes the installer was replaced for a hotfix. Anyway, 3.3.7 is out.

Philotomy commented on 2021-03-30 17:50 (UTC)

The 3.3.6 sha256 checksum seems to be invalid.

settyness commented on 2021-02-09 01:54 (UTC)

3.3.2 wasn't a stable release, nor is it in the changelogs. But I guess this is Arch Linux, so when in Rome...

marcinn commented on 2020-11-26 19:47 (UTC)

Apologies... I haven't noticed that pkg is up to date.

jgjot-singh commented on 2020-11-26 19:33 (UTC)


Yo I got love for front line workers and a, butbAUR package maintainers are my real heroes.

jgjot-singh commented on 2020-11-26 19:33 (UTC)


Yo I got love for front line workers and a, butbAUR package maintainers are my real heroes.

marcinn commented on 2020-11-26 19:18 (UTC)

Hi. v3.3 is available.

stylemistake commented on 2020-10-25 14:16 (UTC)

Yeah, you can do just that. We will release 3.3 once it gets out of beta.

jgjot-singh commented on 2020-10-19 17:09 (UTC)

Hi, Bitwig 3.3 .deb file is up on Bitwig website now, though it still says beta.

If I just modified the relevant parameters in this PKGBUILD to point to that file, will it install 3.3?

stylemistake commented on 2019-12-24 08:03 (UTC)

I have removed zenity from dependencies, since it doesn't seem to be used anywhere and debian package no longer requires it.

bluhue commented on 2019-07-16 05:33 (UTC)

Ah! So sorry, I had the previous version still there. Thought git clean -ffd . would've removed it.

stylemistake commented on 2019-07-15 17:50 (UTC)

Before you clean it, check if any of the files have changed. Maybe it's not just a repackage (if contents are changing, and not just timestamps).

stylemistake commented on 2019-07-15 17:47 (UTC) (edited on 2019-07-15 17:48 (UTC) by stylemistake)

Hmm, sha256sum of a freshly downloaded package is unchanged. Clean the cache, perhaps? This is really weird, tho.

bluhue commented on 2019-07-15 17:38 (UTC)

I think they've repackaged it again.

$ sha256sum bitwig-studio-3.0.deb
57860bc11496e738aad7d3e022f3721e6b9e30b401488b97672564e8aef929d0  bitwig-studio-3.0.deb
$ grep sha256 PKGBUILD

stylemistake commented on 2019-07-14 19:45 (UTC)

Apparently they silently repackaged it. Fixed the checksum, also using sha256 now, because why not. commented on 2019-07-12 16:20 (UTC)

The package's m5sum is not valid anymore:

==> Making package: bitwig-studio 3.0.0-1 (Fri 12 Jul 2019 06:18:13 PM CEST)
==> Retrieving sources...
  -> Downloading bitwig-studio-3.0.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   154  100   154    0     0   1149      0 --:--:-- --:--:-- --:--:--  1140
100  190M  100  190M    0     0  5408k      0  0:00:36  0:00:36 --:--:-- 5857k
==> Validating source files with md5sums...
    bitwig-studio-3.0.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
Error downloading sources: bitwig-studio

sean commented on 2018-06-10 21:02 (UTC)

It seems to work so long as an audio backend is installed at some point. It also fails relatively gracefully if a backend is missing.

For example, I've installed the gnome-desktop group, which depends on PulseAudio and ALSA. To install this package, I downloaded a snapshot and moved jack to optdepends, built it, and added it to IgnorePkg. Both the PulseAudio and ALSA backends work, though I had to make a simple change to my PulseAudio configuration.

stylemistake commented on 2018-06-10 05:54 (UTC) (edited on 2018-06-10 06:00 (UTC) by stylemistake)

It is possible, but we need to make sure it works without jack libs.

P.S. Zenity also seems like an unnecessary dependency, never seen it using it.

sean commented on 2018-06-10 05:48 (UTC)

Is it possible to move the dependency on the jack group to optdepends? I know many people prefer to use Jack with DAWs, but it isn't required by Bitwig Studio. Sometimes I actually prefer not to install it.

prg commented on 2018-05-03 13:27 (UTC)

flac/mp3 issues have been resolved in 2.3.3 for me

prg commented on 2018-04-27 15:15 (UTC)

Just had a conversation with one of the bitwig devs - sounds like they are aware of this issue (they are running into this with Ubuntu 18.04) and plan to fix it in a 2.3.x point release. Could potentially be related to ffprobe

Workaround for the time being would be to decode mp3/flac/whatever to WAV before you import

mateba commented on 2018-04-27 14:30 (UTC)

Obviously, the avprobe symlink trick doesn't work either.

mateba commented on 2018-04-27 14:25 (UTC)

My guess is that it's related to gstreamer: I use git to keep track of my bitwig projects and by looking at the logs I can tell that MP3 worked on the 14th of March, that is after ffmpeg 3.4.2-2 but before gstreamer 1.14. This is one of the packages i've been playing with recently and we can see that there are gstreamer libraries in /opt/bitwig-studio. That could explain why not everybody is experiencing the issue. That's quite a random guess, still. Anyone can confirm that it works without gstreamer ?

prg commented on 2018-04-27 14:04 (UTC) (edited on 2018-04-27 15:15 (UTC) by prg)

Got a response from BitWig; looks like they aren't interesting in fixing it... :/

Hello [prg]

this must be something specific to Arch Linux, on Ubuntu it works just fine. Unfortunately we can't maintain official support for all the different distros out there and therefore had to decide on one we use to test and more or less guarantee that it works. Therefor we currently can't say what exactly the reason is, that drag and drop does not seem to work using Arch Linux and Bitwig Studio.

Best regards, Bitwig Technical Support Team


prg commented on 2018-04-25 20:13 (UTC)

I'm also experiencing mikeza's issue. I've emailed BitWig through their support contact form but would love to hear any if anyone comes with a resolution here. ffmpeg 3.4.2-2 installed; don't remember having this problem with old versions

mateba commented on 2018-04-20 21:00 (UTC)

@mikeza Same here, did you find a solution ?

It's not related to ffmpeg since I'm sure MP3 & FLAC worked at least until mid-march and latest ffmpeg build-date is feb. I also tried to downgrade BW with no luck.

mikeza commented on 2018-04-04 19:15 (UTC) (edited on 2018-04-05 22:44 (UTC) by mikeza)

@stylemistake Yes, I have ffmpeg 1:3.4.2-2

Edit: I've also installed and tested ffmpeg-git and ffmpeg-compat-54

Legacy Bitwig worked fine.

stylemistake commented on 2018-04-04 00:29 (UTC)

@mikeza Have you installed "ffmpeg", which is an optional dependency?

mikeza commented on 2018-04-03 22:48 (UTC) (edited on 2018-04-03 22:49 (UTC) by mikeza)

Encountering problems trying to import/play MP3 and FLAC files. WAV works fine. All other features are working great.

[2018-04-03 17:38:19 float-document-master error] Error loading file /home/mz/media/music/mp3/100s/IVRY/03 F Around.mp3: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Could not read audio file metadata

Edits: shortened error message

stylemistake commented on 2017-12-11 16:03 (UTC) (edited on 2018-03-06 17:59 (UTC) by stylemistake)

@bsorahan > Hoping that "pacman -Syu" wouldn't put me back in demo mode!

Due to their new licensing policy, you get updates for 1 year after purchase, and this cycle is different depending on when you purchased it. So when you decide not to continue paying for the next year, just lock yourself into specific PKGBUILD version, and that's it.

bsorahan commented on 2017-12-11 03:47 (UTC)

I've used this to install bitwig and it works fabulously (after installing jack2), so I'm thinking about buying a license. I was curious about what would happen when bitwig 3 comes out: hoping that "pacman -Syu" wouldn't put me back in demo mode! It looks like we should maybe expect a major version upgrade to require a different package or some other sort of manual intervention? Thanks for making this package!

blk commented on 2017-10-29 13:48 (UTC) (edited on 2017-10-29 13:48 (UTC) by blk)

@liam1895 - "loading jack package: jack_get_version_string" - I had the same issue and fixed it with `sudo pacman -S jack2`. `jack_get_version_string` seems to be present only in Jack2 (

jonathon commented on 2017-03-03 15:37 (UTC)

It's working OK for me on two installs with jack2 (plus cadence-git).

liam1895 commented on 2017-03-02 06:52 (UTC)

Is there a missing package? When installing and trying to use jack audio in bitwig interface I keep getting the error "error loading jack package: jack_get_version_string"

stylemistake commented on 2017-03-01 01:01 (UTC)

Created bitwig-studio-legacy for those who are unhappy with licensing model of 2.0.

jonathon commented on 2017-03-01 00:02 (UTC)

Given the new licensing model would a bitwig-studio-legacy (or similar) package for 1.3.15 be a useful thing?

interferon commented on 2017-03-01 00:01 (UTC)

Greetings, I think that there should be two different packages for Bitwig 1.3 and Bitwig 2.0, since those with a license for Bitwig 1.3 who did not buy the upgrade can only use the demo version of Bitwig 2, so they will likely not want to upgrade.

vxf6 commented on 2017-02-28 22:21 (UTC)

Thanks for pushing the package for Bitwig 2.0 so quickly!

stylemistake commented on 2016-12-09 12:27 (UTC)

Created an automated script for incrementing this package version. Tell me if something breaks.

vxf6 commented on 2016-11-13 20:21 (UTC)

Nah don't sweat it, thanks for maintaining the package.

stylemistake commented on 2016-11-13 20:01 (UTC) (edited on 2016-11-15 00:12 (UTC) by stylemistake)

I rushed pushing a new version without actually checking if it builds. Fixed md5sums.

nvllsvm commented on 2016-11-13 18:44 (UTC)

The hash included in 1.3.14-1 is incorrect. The hash for 1.3.13 was mistakenly used instead.

vxf6 commented on 2016-11-13 15:09 (UTC)

==> Validating source files with md5sums... bitwig-studio-1.3.14.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! Getting this error when trying to update using cower, I just updated to 1.3.13 a few days ago without any issue. Any pointers? Thanks.

alcomatt commented on 2016-11-11 21:56 (UTC)

New version is out today. Just saying :)

abique commented on 2016-03-28 15:40 (UTC) (edited on 2016-04-13 08:42 (UTC) by abique)

Thank you for renaming the package! :)

rvega commented on 2016-03-28 15:18 (UTC)

When launching from the command line using the provided launcher, MP3 support is fine but if you launch from the .desktop file, PATH is not set so MP3 support does not work.

vxf6 commented on 2016-03-23 00:24 (UTC)

@stylemistake Great thanks, I also thought it was a certificate issue on their end.

stylemistake commented on 2016-03-22 19:42 (UTC) (edited on 2016-03-22 19:43 (UTC) by stylemistake)

@chilango, you can temporarily solve SSL cert problem by adding the following line to PKGBUILD: DLAGENTS=('https::/usr/bin/curl --insecure -o %o %u') However this error message is not our problem. Most probably it's an outdated root CA certificate causing the problem.

vxf6 commented on 2016-03-22 18:28 (UTC)

I'm getting a "curl: (60) SSL certificate problem: unable to get local issuer certificate" error (verified with curl -v). I'm kind of new around here, could I for example set the source from the PKGBUILD file manually to the a .deb file that I download manually?

stylemistake commented on 2016-02-20 21:30 (UTC)

Small update: symlinks to 'avconv' are no longer needed, they are provided transparently by the latest PKGBUILD.

eikakot commented on 2015-12-20 12:51 (UTC)

To get mp3 working using ffmpeg instead of avconv which is no longer available in AUR just make a couple symlinks as root: ln -s /usr/bin/ffmpeg /usr/bin/avconv ln -s /usr/bin/ffprobe /usr/bin/avprobe

eoli3n commented on 2015-11-29 12:10 (UTC) (edited on 2015-11-29 12:12 (UTC) by eoli3n)

hm, ffmpeg is installed -> extra/ffmpeg [installed] but no mp3 working :/ edit : i mean add a mp3 to an audio track and sampling it, not exporting as mp3 1.3.4 is out thx a lot to mkzero for provinding that package ;)

eoli3n commented on 2015-11-27 19:39 (UTC)

No azerty keyboard layout support :/ default editing tools set to 12345, which does not exist on azerty keyboard. mp3 doesnt work inside bitwig, i tried to install libav but no package with that name exists, is somebody know how to make it work ? pacman -Qs libav prints me extra/ffmpeg [installed], extra/gst-libav, extra/libavc1394 [installed], community/ffmpeg-compat, community/ffms2,

itsizzy commented on 2015-11-04 10:05 (UTC)

@net147: This is just a warning, so no real problem there. But it stems from the "Bitwig Modular.svg" - which has a whitespace in it's name. This is not the first time the Bitwig guys messed that up. If you find time, please report this to their support. Fixing this upstream is the only real solution, until then you could hack around this by renaming the file to use an underscore or dash instead of a white space character.

net147 commented on 2015-11-04 00:48 (UTC)

Installing this package causes the following command to fail: sudo gtk-update-icon-cache -q -t -f /usr/share/icons/hicolor with the error: gtk-update-icon-cache: The generated cache was invalid.

archxyz commented on 2015-10-12 13:14 (UTC)

@mkzero You are right. It appears to be a dependency and works after installing it. Thanks! :)

itsizzy commented on 2015-10-12 07:22 (UTC)

archxyz: can you try that again after installing "libbsd"? My best guess would be, that this is a dependency...

archxyz commented on 2015-10-11 09:01 (UTC) (edited on 2015-10-11 09:02 (UTC) by archxyz)

I can't start Bitwig 1.2. The messages it throws are JRE Path: //opt/bitwig-studio/lib/jre Could not de-obfuscate stack trace: /home/USER/.BitwigStudio/b0xxxxxxxxxxxxxxx0c-Linux-release.txt not found. Could not de-obfuscate stack trace: /home/USER/.BitwigStudio/b0xxxxxxxxxxxxxxx0c-Linux-release.txt not found. java.lang.UnsatisfiedLinkError: /opt/bitwig-studio/lib/bitwig-studio/ cannot open shared object file: No such file or directory at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0( at java.lang.ClassLoader.loadLibrary( at java.lang.Runtime.loadLibrary0( at java.lang.System.loadLibrary( at Mdn.vBx(SourceFile:186) at com.bitwig.x11_windowing_system.X11WindowingSystem.vBx(SourceFile:20) at com.bitwig.x11_windowing_system.X11WindowingSystem.<clinit>(SourceFile:14) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName( at com.bitwig.windowing_system.mK.RPa(SourceFile:151) at com.bitwig.windowing_system.mK.<clinit>(SourceFile:42) at com.bitwig.flt.prefs.fIi.Ekf(SourceFile:93) at com.bitwig.flt.prefs.fIi.Wzr(SourceFile:52) at com.bitwig.flt.prefs.fIi.vBx(SourceFile:27) at at at bXZ.x3M(SourceFile:73) at at bUu.ToV(SourceFile:1915) at bUu.vBx(SourceFile:142) at at bUu.RPa(SourceFile:1230) at at bUu.vBx(SourceFile:1188) at bUu.WF(SourceFile:870) at I changed b0xxxxxxx0c and the user name. Otherwise it is same. Does anyone have the same problem?

itsizzy commented on 2015-10-07 07:45 (UTC)

abique: please use the bitwig-studio-demo-rc package to report out-of-date rc packages, not the stable one...

abique commented on 2015-10-06 20:46 (UTC)

version 1.3RC!!!

Joermungand commented on 2015-10-06 06:45 (UTC)

Version 1.2.0 brings back ‘gtk-update-icon-cache’ issues. This time, the culprits are /usr/share/icons/hicolor/48x48/apps/Bitwig Modular.png and /usr/share/icons/hicolor/scalable/apps/Bitwig Modular.svg

YottaSecond commented on 2015-10-01 23:52 (UTC)

In case it helps anyone, I just installed 1.2.0 by modifying these three lines in the PKGBUILD: pkgver=1.2.0 source=("${pkgver}.deb") md5('0d74f1b6ec6eecc4dbcbb3ab09ae2768')

cprussin commented on 2015-10-01 18:17 (UTC)

@eolien, I've had that problem since bitwig came out and I contacted bitwig support regarding it. Apparently the problem definitely comes from the Java framework, but we were unable to find a good solution. I will update this thread if we end up finding something that works.

eoli3n commented on 2015-09-22 13:30 (UTC)

Tried this, didn't work :

eoli3n commented on 2015-09-22 12:35 (UTC)

With i3, when i start bitwig on a workspace, switch to another workspace and come back the bitwig's one, app seems frozen. Mouse's cursor still change in different interface's parts, but nothing happen when i click. Any idea ?

Joermungand commented on 2015-09-17 06:30 (UTC)

The icon paths and names have been fixed in the deb file. The whole ‘Install icons’ section should be removed from the PKGBUILD, as it’s no longer needed and it is what triggers the error.

odensc commented on 2015-09-15 23:42 (UTC)

Getting the following error: install: cannot stat ‘/tmp/pacaurtmp-oden/bitwig-studio-demo/pkg/bitwig-studio-demo/usr/share/icons/gnome/48x48/apps/Bitwig Studio.png’: No such file or directory

anarch.linux commented on 2015-08-23 07:25 (UTC)

the problem with icon file is the whitespace in its name. after renaming icon to e.g. Bitwig-Studio.png gtk-update-icon-cache succeeds again.

KenjiTakahashi commented on 2015-08-07 01:37 (UTC)

There is something wrong with the icon file, it causes `gtk-update-icon-cache` to fail with `The generated cache was invalid`.

ricus commented on 2015-07-08 14:59 (UTC)

@mkzero, it might be a good idea to call this package bitwig-studio instead of bitwig-studio-demo, since the program acts like a demo without a license, or full-featured otherwise. They also don't make different versions on the download page at

leolweb commented on 2015-05-24 21:09 (UTC)

There's an error into PKGBUILD file, in the 1.1.8 release package bitwig-studio.png was renamed as Bitwig Studio.png

crepererum commented on 2014-12-03 21:39 (UTC)

Regarding MIDI: Use the following script in combination with the right jackd midi routing:

Zeben commented on 2014-11-20 20:15 (UTC)

Bump. Bitwig 1.1 is out. For those who want to get it right now - edit pkgbuild: -- md5sums=('b28c2246c637cea744ffb1ba88c6f1f0') ++ md5sums=('bf06da1d9e1026ba9dd2eeec9ecfc58e') -- pkgver=1.0.15 ++ pkgver=1.1 Regards.

abique commented on 2014-06-05 19:09 (UTC)

mkzero, why don't you call this bitwig-studio?

commented on 2014-05-26 09:09 (UTC)

mkzero: I'll try that, thanks. I'll post here any solution I found, just in case ;)

itsizzy commented on 2014-05-26 06:18 (UTC)

earn: Maybe have a look at .. Or you could contact their support via that online form on their website.

commented on 2014-05-24 09:42 (UTC)

mkzero: still, the MIDI is not working for me :/ In or Out, Bitwig just does'nt see MIDI output nor gets MIDI input notes or message. Do you have where I might look, as the forums look a little bit crowded, in a bad way.

itsizzy commented on 2014-05-06 15:50 (UTC)

schef: Updated. But please use the out-of-date function the AUR provides the next time, that sends notifications, too. I try to update the package as fast as I can(usually only a few hours) and I at least need to test the build before uploading it.. ;)

schef commented on 2014-05-06 15:20 (UTC)

1.0.8 is out md5sum 0ab2bd87eca1a199fc1f61db8fe59941

itsizzy commented on 2014-05-02 08:10 (UTC)

earn: MIDI should work just fine. I've had problems with one of my devices but those where fixed in the latest RC version(there's an AUR package for that, too). Maybe try that one. If it doesn't help you can ask on the KVRaudio forum for Bitwig, one or two of the Bitwig devs seem to be there now and then and even some Arch Linux users as it seems.

commented on 2014-04-24 10:02 (UTC)

I can't use ay MIDI Ouput, they are not listed in Bitwig Preferences. Known bug ?

itsizzy commented on 2014-04-01 10:47 (UTC)

There is a know bug when importing MP3s because bitwig uses avlib but tries to probe MP3s with ffprobe. As a workaround you need avlib installed and a symlink from avprobe to ffprobe. One of the Bitwig guys posted on the KVR forum that has been reported already and it should be fixed in the future. I will also add the avlib as an optional dependency later today or maybe tomorrow, as they already announced Bitwig 1.0.5.

m0rph commented on 2014-04-01 06:42 (UTC)

I hurried and make PKGBUILD for an unofficial version 1.0.4, which was subsequently updated, so md5sums is changed.

Joermungand commented on 2014-04-01 04:27 (UTC)


m0rph commented on 2014-03-31 19:14 (UTC)

As I promised, here's my PKGBUILD for full version It is substantially the same as bitwig-studio-demo PKGBUILD, but without unneeded deb2targz.

commented on 2014-03-31 12:48 (UTC)

"And for music creation on Linux pretty much *the* game changer everyone has been waiting for" About time ^^

itsizzy commented on 2014-03-31 12:46 (UTC)

earn: I can second m0rph's opinion - there are a few bugs, in my case especially when using MIDI-controllers. These bugs where not present when using the Windows version of Bitwig on the same hardware, so maybe I have to reconfigure something.. But coming from many years of Windows+Ableton with crashes, not beeing able to plug HW whithout restarting, poor performance when adding instrument tracks, etc. (the list of problem goes on quite a bit) I have to say from what I've seen Bitwig is pretty stable and for music creation on Linux pretty much *the* game changer everyone has been waiting for.

m0rph commented on 2014-03-31 12:29 (UTC)

earn: It's pretty stable and usable for me, but of course it has some bugs. I am not a professional composer/musician, it's just my hobby, so my opinion may not be objective.

commented on 2014-03-31 09:56 (UTC)

m0rph : how is it working so far ? Stable ?

m0rph commented on 2014-03-31 09:54 (UTC)

mynis01 I'm also have full version and I've made PKGBUILD for it. I will paste it somewhere when I will be at home.

itsizzy commented on 2014-03-31 09:45 (UTC)

earn: AsavarTzeth: You are of course right, it should say 'jack' instead of 'jack2'. The jack2 package provides jack(or at least it should provide it), so everybody on the jack side would be fine. I've also tried ALSA but found no way of getting sound out of Bitwig without jack - at least with the 3 test systems I have.

commented on 2014-03-31 09:27 (UTC)

You can, just remove the 2 from jack2. It works fine this way, let's see what the maintainer thinks about it.

AsavarTzeth commented on 2014-03-31 09:23 (UTC)

I don't know what the official dependencies say, but shouldn't jack2 be set as optional? As the devs say: "JACK and ALSA? We currently support both, but recommend you use JACK." I interpret this as you can go with plain ALSA with or without pulse. JACK2 is not required for it to work, although you should seriously consider using it. This is critical to me since gstreamer defaults to jack and not jack2. I also use audacity and mplayer, which both use jack. Point being I cannot upgrade now because of conflicts.

itsizzy commented on 2014-03-30 16:00 (UTC)

mynis: To my knowledge you can do that, but i'm not sure if you have to put 'file://' in front of the path. The easiest way would probably be to just put the PKGBUILD in the same directory as the deb-file and run makepkg - it should see the file and use it instead of downloading it again.

mynis01 commented on 2014-03-30 12:45 (UTC)

I have the full version of bitwig and I'm trying to figure out the best way to install it in arch. At first I was going to try to just use the dpkg from the AUR, but then I stumbled accross this package and thought maybe it would be better to just use your pkgbuild. So, in order to make it search my local filesystem for the package instead of downloading it over the web, would I just change the line "source=("${pkgver}.deb")" to "source=("/location/in/filesystem/bitwig-studio-1.0.3.deb")"?

m0rph commented on 2014-03-29 06:43 (UTC)

There is a list of dependeces inside deb package. I think we can map most of these package names to ArchLinux package names. libcairo2, libxcb-icccm4, libxcb1, libxcb-randr0, libx11-xcb1, libxkbfile1, libxcursor1, libstdc++6, libc6, libgcc1, libpixman-1-0, libfontconfig1, libfreetype6, libpng12-0, libxcb-shm0, libxcb-render0, libx11-6, zlib1g, libxau6, libxdmcp6, libxfixes3, libexpat1, libxrender1, libx11-6, zlib1g, libjack-jackd2-0, xdg-utils, libav-tools, zenity

myrnehr commented on 2014-03-26 17:55 (UTC)

mkzero: cool, will do.

itsizzy commented on 2014-03-26 17:22 (UTC)

myrnehr: Thank you. I added the depend. I'm still trying to figure out all dependencies though, so if you find any other packages needed a clean, working version feel free to comment or open an issue on Github.

myrnehr commented on 2014-03-26 16:56 (UTC)

Also, UI dropdowns cause segfaults for me?

myrnehr commented on 2014-03-26 16:45 (UTC)

Add "xcb-util-wm" as a dep, as you get "java.lang.UnsatisfiedLinkError: /opt/bitwig-studio/bin/ cannot open shared object file: No such file or directory" without it.