Package Details: bitwig-studio 5.2.5-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: 113
Popularity: 0.039197
First Submitted: 2016-03-28 16:43 (UTC)
Last Updated: 2024-10-19 00:57 (UTC)

Required by (85)

Sources (1)

Latest Comments

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

Kallistisoft commented on 2023-12-07 08:34 (UTC)

Could you please add the bitwig beta package 'bitwig-studio-earlyaccess' to the list of conflicts. Thank you :)

Gimmeapill commented on 2023-09-16 07:24 (UTC)

Thanks for the quick updates. I also have a few pkgbuilds in dire need of an update as well :-)

Evergreen commented on 2023-09-16 01:12 (UTC)

Updated the provides list with the suggested changes. Thank you for the reminder and apologies for not getting to it sooner.

Gimmeapill commented on 2023-09-15 18:53 (UTC)

+1 for updating the provides array: provides=(clap-host vst-host vst3-host)

This is in line with the current packaging practices for audio software in Arch. Having only Bitwig and a few packaged vst plugins means that another host has to be installed to satisfy the *-host dependencies. Ex: https://archlinux.org/packages/extra/x86_64/dexed-vst3/

It is also not necessary anymore to have bitwig-studio listed: https://wiki.archlinux.org/title/Arch_package_guidelines#Package_relations

"Do not add $pkgname to PKGBUILD#provides, as it is always implicitly provided by the package."

AYANE-69 commented on 2023-07-31 12:37 (UTC) (edited on 2023-07-31 12:40 (UTC) by AYANE-69)

This package needs provides=( clap-host vst-host vst3-host ) to prevent installing clap and vst plugins from trying to forcibly install other hosts.

alcomatt commented on 2023-04-12 11:27 (UTC) (edited on 2023-04-12 11:43 (UTC) by alcomatt)

You could download the PKGBUILD file and edit it (and update the checksums) then use it to build a new package using makepkg. This is what I've done and it worked absolutely fine. I've used the bitwig-studio-beta PKGFILE though to have it installed side by side.

chrisco23 commented on 2023-04-11 22:41 (UTC)

I see today they've released 5.0 as beta, but their site provides only options "flatpak" and "ubuntu". Any good way to try 5.0 for us on Arch?

aur_duty commented on 2022-12-19 22:21 (UTC)

suggestion: add (plugin type)-host entries to the PKGBUILD provides=() array. Example: locally I edited the PKGBUILD adding 'clap-host' to provides=(). This allowed bitwig to satisfy a requirement of the pacman group clap-plugins.

Evergreen 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: https://gist.github.com/4Evergreen4/562d5ea590d9887b29f4960b1ad0dd24

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?

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