Package Details: bitwig-studio 5.2.7-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: 114
Popularity: 0.50
First Submitted: 2016-03-28 16:43 (UTC)
Last Updated: 2024-11-22 04:50 (UTC)

Required by (85)

Sources (1)

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 16 Next › Last »

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.