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: 1.03
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 .. 7 8 9 10 11 12 13 14 15 16 Next › Last »

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/libx11-windowing-system.so: libbsd.so.0: cannot open shared object file: No such file or directory at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1937) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1855) at java.lang.Runtime.loadLibrary0(Runtime.java:870) at java.lang.System.loadLibrary(System.java:1122) 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(Class.java:264) 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 com.bitwig.flt.app.FloatMainApplication.DwW(SourceFile:2904) at com.bitwig.flt.app.FloatMainApplication.SPd(SourceFile:626) at bXZ.x3M(SourceFile:73) at com.bitwig.flt.app.FloatMainApplication.x3M(SourceFile:652) at bUu.ToV(SourceFile:1915) at bUu.vBx(SourceFile:142) at bUN.run(SourceFile:866) at bUu.RPa(SourceFile:1230) at com.bitwig.flt.app.aXX.RPa(SourceFile:1354) at bUu.vBx(SourceFile:1188) at bUu.WF(SourceFile:870) at com.bitwig.flt.app.FloatMainApplication.main(SourceFile:6278) 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=("https://downloads.bitwig.com/stable/1.2/bitwig-studio-${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.