Search Criteria
Package Details: bitwig-studio-earlyaccess 6.1b6-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/bitwig-studio-earlyaccess.git (read-only, click to copy) |
|---|---|
| Package Base: | bitwig-studio-earlyaccess |
| Description: | Digital audio workstation for music production, remixing and live performance - early access version |
| Upstream URL: | https://www.bitwig.com/ |
| Keywords: | audio bitwig daw multimedia music |
| Licenses: | custom |
| Conflicts: | bitwig-8-track, bitwig-studio, bitwig-studio-legacy |
| Provides: | clap-host, vst-host, vst3-host |
| Submitter: | taraen |
| Maintainer: | taraen (stylemistake) |
| Last Packager: | taraen |
| Votes: | 10 |
| Popularity: | 0.005409 |
| First Submitted: | 2021-10-04 19:12 (UTC) |
| Last Updated: | 2026-08-16 15:04 (UTC) |
Dependencies (7)
- libbsd (libbsd-gitAUR)
- xcb-util-wm
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, openerAUR, mimejs-gitAUR, xdg-utils-mimeoAUR, xdg-utils-gitAUR)
- alsa-lib (optional)
- ffmpeg (ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-ffplayoutAUR, ffmpeg-cudaAUR, ffmpeg-whisper-gitAUR, ffmpeg-cuda-fullAUR, librempeg-gitAUR, ffmpeg-gitAUR, ffmpeg-decklinkAUR, ffmpeg-fullAUR, ffmpeg-full-gitAUR, ffmpeg-headlessAUR, ffmpeg-whisperAUR, ffmpeg-obsAUR, ffmpeg-full-llvmAUR, ffmpeg-libfdk_aacAUR, ffmpeg-amd-fullAUR, ffmpeg-amd-full-gitAUR) (optional) – MP3 support
- jackAUR (jack2-gitAUR, pipewire-jack-gitAUR, pipewire-full-jack-gitAUR, pipewire-jack-ldacAUR, jack2, pipewire-jack) (optional)
- ossAUR (oss-nonfreeAUR, oss-gitAUR) (optional)
Required by (118)
- a-sid (requires vst3-host) (optional)
- adt (requires clap-host) (optional)
- adt (requires vst3-host) (optional)
- aida-x-git (requires vst3-host)
- aida-x-git (requires vst-host)
- aida-x-git (requires clap-host)
- airwindows-consolidated-git (requires clap-host) (optional)
- airwindows-consolidated-git (requires vst3-host) (optional)
- amsynth-git (requires vst-host) (optional)
- cabbage-bin (requires vst-host) (optional)
- cabbage-bin (requires vst3-host) (optional)
- cardinal-data-git (requires vst-host) (optional)
- cardinal-data-git (requires vst3-host) (optional)
- cardinal-git (requires vst-host) (optional)
- cardinal-git (requires vst3-host) (optional)
- cardinal-vst-git (requires vst-host)
- cardinal-vst3-git (requires vst3-host)
- carla-git (requires vst-host) (optional)
- cchorus (requires clap-host) (optional)
- cchorus (requires vst-host) (optional)
- Show 98 more...
Latest Comments
1 2 Next › Last »
taraen commented on 2026-08-16 15:15 (UTC)
@UltraBlack I've gone ahead and reworked the script with variables (_basever and _betaver are now used to make up the version string, and are used later in the script to download the correct file and name it accordingly.) You might want to cleanbuild. Happy producing!
taraen commented on 2026-08-16 14:56 (UTC)
@UltraBlack thanks for the heads up. I actually had a look at the code and you're partially correct. It does actually download the correct file (6.1%20Beta%206) but idiosyncratically saves/renames the downloaded file under the wrong beta version's filename from the preceding (bitwig-studio-6.1-beta-6.deb::). Thankfully the script doesn't really care what the filename is, it just unpacks whatever is downloaded by the source= line, and so far this has worked flawlessly as it does download the current beta version always. This is a little bit confusing but I verified that with the current script, it does download and install beta version 6 despite temporarily fetching and saving the file as "beta 1" - it is actually Beta 6 renamed to Beta 1. Regardless, I've changed this to make it less confusing and thank you again for reporting.
UltraBlack commented on 2026-08-16 12:08 (UTC)
Hey there! Just a heads up: It seems like the makefile still downloads into the beta-1 file, meaning that the installer won't download or use the new version if the previous version has been downloaded already, even though the package version is now beta-6.
fluffy-dragons commented on 2025-11-01 15:58 (UTC)
beta 5 came out yesterday, happy late halloween
taraen commented on 2025-08-27 10:22 (UTC) (edited on 2025-08-27 10:40 (UTC) by taraen)
Shoot! I checked an hour ago and there wasn't anything yet. Haha. Edit: it's live.
z3n commented on 2025-08-27 10:21 (UTC)
beta of 6 just got released
stfefane commented on 2025-01-01 20:34 (UTC)
Hi, you can find a patch to update to 5.3b3 here : https://gist.github.com/stfufane/bcb88d0390d485dc3813cc6a93e892b5
Thanks !
taraen commented on 2022-05-30 16:06 (UTC)
@ex3l1io0 No problem. I would try this myself, but the VST of VCV seems to be paid... I'd suggest you ask around the VCV community / support forum for troubleshooting tips. Maybe the plugin has a log file somewhere that could give a hint why this happens. I can only speak of the couple VSTs I use (U-he, gvst) are working fine with this package. Just for reference I'm running Manjaro unstable branch, gnome desktop on wayland. Also using Pulseaudio+JACK (no pipewire for audio at all) The standalone VCV from the AUR installs and runs fine, but I'm guessing you're talking about the VST plugin.
ex3l1io0 commented on 2022-05-30 15:10 (UTC)
@Taraen Ok thanks, do you know if there is a way to compare which libraries are used with the Flatpak and the .deb version? I'm also using the individually sandboxing within Bitwig, but VCV Rack keeps crashing.
taraen commented on 2022-05-30 14:43 (UTC)
@ex3l1io0 I did not write this script (stylemistake did, I only changed a few lines to pull the newer versions of Bitwig) but as far as I can tell, all it does is extract the contents of the Ubuntu/Debian .deb version of Bitwig, and installs it into arch system directories. The script doesn't really modify anything about Bitwig. The main difference between this package and Flatpak is, that the Flatpak version is running sandboxed with bundled libraries, whereas the AUR packages all make use of native arch system libraries. My suggestion for you is to go to the Bitwig settings, go to the tab "Plug-ins", and move the "Plug-in Hosting Mode" setting further to the right. Personally I use "Individually" because I have 32 gigs of ram to mess with, so your mileage may vary.
1 2 Next › Last »