Package Details: bitwig-studio 5.1.8-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, EvergreenTree)
Last Packager: smoothny
Votes: 114
Popularity: 2.03
First Submitted: 2016-03-28 16:43 (UTC)
Last Updated: 2024-04-25 16:08 (UTC)

Required by (62)

Sources (1)

Latest Comments

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

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 :-) https://www.bitwig.com/whats-new/

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 support@bitwig.com ?

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?