Search Criteria
Package Details: bitwig-studio 4.2.3-1
Package Actions
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: | bitwig-studio |
Submitter: | stylemistake |
Maintainer: | stylemistake (smoothny, EvergreenTree) |
Last Packager: | EvergreenTree |
Votes: | 98 |
Popularity: | 0.49 |
First Submitted: | 2016-03-28 16:43 (UTC) |
Last Updated: | 2022-04-20 01:29 (UTC) |
Dependencies (7)
- libbsd (libbsd-git)
- xcb-util-wm
- xdg-utils (mimi-git, busking-git, xdg-utils-git, linopen, xdg-utils-mimeo, xdg-utils-handlr, xdg-utils-slock, mimi-bachoseven-git, xdg-utils-symlink-fix, mimejs-git)
- alsa-lib (alsa-lib-git, alsa-lib-minimal-git, alsa-lib-x205ta) (optional)
- ffmpeg (ffmpeg-v4l2-request-git, ffmpeg-nox-git, ffmpeg-svt-vp9-git, ffmpeg-vp9-timestamp, ffmpeg-cuda, ffmpeg-ndi, ffmpeg-intel-full-git, ffmpeg-vulkan, ffmpeg-yt-dlp-bin, ffmpeg-headless, ffmpeg-amd-full-git, ffmpeg-amd-full, ffmpeg-full, ffmpeg-decklink, ffmpeg-libfdk_aac, ffmpeg-mmal, ffmpeg-nocuda, ffmpeg-shinobi, ffmpeg-obs, ffmpeg-full-git, ffmpeg-git) (optional) – MP3 support
- jack (jack-git, jack2-git, pipewire-common-jack-git, pipewire-full-jack-git, pipewire-jack-git, jack2, pipewire-jack) (optional)
- oss (oss-nonfree, oss-git) (optional)
Latest Comments
EvergreenTree 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 requireostree
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/562d5ea590d9887b29f4960b1ad0dd24alcomatt 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?
alcomatt commented on 2022-04-29 14:17 (UTC)
sha256 sums are good in the PKGBUILD and the source deb by Bitwig has not been modified. Please delete your yay/yaourt cache folder and try building package again. Something might have corrupted your deb file download.
kalimerox commented on 2022-04-29 14:01 (UTC) (edited on 2022-04-29 14:01 (UTC) by kalimerox)
I get
"" Found bitwig-studio-4.2.3.deb ==> Validating source files with sha256sums... bitwig-studio-4.2.3.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build bitwig-studio ""
when i try to upgrade on my manjaro machine...
1uk commented on 2022-02-17 20:13 (UTC) (edited on 2022-02-17 20:18 (UTC) by 1uk)
Works now! Added my user to the audio group.
%jackd
gives the same error message, butjack_control
works and Qjackctl as well. Nice, thank you. Edit: But now, when I open pavucontrol I don't see bitwig as playback, and I don't hear any sound.stylemistake commented on 2022-02-17 15:33 (UTC)
Refer to ArchWiki, you probably forgot to add yourself to the audio group and specify realtime limits/settings in sysctl.d. If you wish, you can also use jack-dbus which autostarts whenever the application requests it. Qjackctl is also a useful program.
1uk commented on 2022-02-17 15:15 (UTC) (edited on 2022-02-17 15:27 (UTC) by 1uk)
Hello, I installed it, and it works, but I can't start the audio engine. It says: "Unable to connect to jack server". I use pulseaudio and have pulseaudio-jack and jack2 installed. When I run jackd it just gives a info message to stdout. Can you help me? Should I switch to pipewire and deinstall pulse? <img alt="error message" src="https://imgur.com/ToNLR7c.png" title="Unable to connect to jack server" />
when I run jackd:
alcomatt commented on 2022-01-13 21:41 (UTC)
4.1.3 released with workaround for nVidia driver fixes. https://downloads-eu.bitwig.com/stable/4.1.3/Release-Notes-4.1.3.html
jarkko commented on 2021-12-30 22:11 (UTC)
Just to remark: the latest NVIDIA driver works with Bitwig Studio, if GNOME on Wayland is used.
alcomatt commented on 2021-12-13 22:00 (UTC) (edited on 2021-12-14 21:50 (UTC) by alcomatt)
Today Bitwig started crashing on start, taking X with itself. X session crashes silently and respawns. Most likely caused by some recent arch updates, but cannot seem to figure out which ones. Nothing conclusive in the logs.
It turned out to be nvidia driver update v 495.46
Specifically, this is listed in release notes Known Issues section:
Bitwig Nvidia Users be aware, downgrading nvidia driver to v495.44 resolves issue.
phunni commented on 2021-11-18 15:18 (UTC)
Not sure if this is to do with my setup, the package or a bug in bitwig, but bitwig is crashing almost straight away. I get the option to log in, to choose demo, I choose demo, I get a window telling me to click on the dashboard button. I can't click on anything and then, after a few moments, it crashes. No error message - even if I run it from cli.
settyness commented on 2021-11-08 19:37 (UTC)
That's really neat if you use flatpak.
abique commented on 2021-11-07 07:18 (UTC) (edited on 2021-11-07 07:19 (UTC) by abique)
On flatpak there is a 3.3 branch, a stable, early-access and beta branch. Once 4.1 is out there will be a 4.0 branch as stable and early-access will point to 4.1.
You can point them to flatpak for early-access and beta.
flatpak install --branch=beta com.bitwig.BitwigStudio
flatpak run --branch=beta com.bitwig.BitwigStudio
settyness commented on 2021-11-07 01:37 (UTC)
I really wish there was a way to keep people from flagging pre-release versions and/or differentiating between the two. Unfortunately, the only thing I can think of is establishing a pre-release branch, and I don't think that will stop people from flagging, and it's too much overhead.
00zerozero commented on 2021-08-07 11:15 (UTC) (edited on 2021-08-07 11:17 (UTC) by 00zerozero)
Works fine now, first download had an error, after running yay again it worked.
almet commented on 2021-07-14 16:51 (UTC) (edited on 2021-07-14 16:52 (UTC) by almet)
It's working for me (installed with yay this morning). Thanks a lot stylemistake.
Serum commented on 2021-07-14 15:45 (UTC)
I can't download this. I've updated my mirrors but the download speed is straight up zero bytes/second. Anyone else having this issue?
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
?abique commented on 2021-04-01 14:20 (UTC)
Yes the installer was replaced for a hotfix. Anyway, 3.3.7 is out.
Philotomy commented on 2021-03-30 17:50 (UTC)
The 3.3.6 sha256 checksum seems to be invalid.
settyness commented on 2021-02-09 01:54 (UTC)
3.3.2 wasn't a stable release, nor is it in the changelogs. But I guess this is Arch Linux, so when in Rome...
marcinn commented on 2020-11-26 19:47 (UTC)
Apologies... I haven't noticed that pkg is up to date.
jgjot-singh commented on 2020-11-26 19:33 (UTC)
YESSSS!
Yo I got love for front line workers and a, butbAUR package maintainers are my real heroes.
jgjot-singh commented on 2020-11-26 19:33 (UTC)
YESSSS!
Yo I got love for front line workers and a, butbAUR package maintainers are my real heroes.
marcinn commented on 2020-11-26 19:18 (UTC)
Hi. v3.3 is available.
stylemistake commented on 2020-10-25 14:16 (UTC)
Yeah, you can do just that. We will release 3.3 once it gets out of beta.
jgjot-singh commented on 2020-10-19 17:09 (UTC)
Hi, Bitwig 3.3 .deb file is up on Bitwig website now, though it still says beta.
If I just modified the relevant parameters in this PKGBUILD to point to that file, will it install 3.3?
stylemistake commented on 2019-12-24 08:03 (UTC)
I have removed zenity from dependencies, since it doesn't seem to be used anywhere and debian package no longer requires it.
bluhue commented on 2019-07-16 05:33 (UTC)
Ah! So sorry, I had the previous version still there. Thought
git clean -ffd .
would've removed it.stylemistake commented on 2019-07-15 17:50 (UTC)
Before you clean it, check if any of the files have changed. Maybe it's not just a repackage (if contents are changing, and not just timestamps).
stylemistake commented on 2019-07-15 17:47 (UTC) (edited on 2019-07-15 17:48 (UTC) by stylemistake)
Hmm, sha256sum of a freshly downloaded package is unchanged. Clean the cache, perhaps? This is really weird, tho.
bluhue commented on 2019-07-15 17:38 (UTC)
I think they've repackaged it again.
stylemistake commented on 2019-07-14 19:45 (UTC)
Apparently they silently repackaged it. Fixed the checksum, also using sha256 now, because why not.
klingt.net commented on 2019-07-12 16:20 (UTC)
The package's m5sum is not valid anymore:
sean commented on 2018-06-10 21:02 (UTC)
It seems to work so long as an audio backend is installed at some point. It also fails relatively gracefully if a backend is missing.
For example, I've installed the gnome-desktop group, which depends on PulseAudio and ALSA. To install this package, I downloaded a snapshot and moved jack to optdepends, built it, and added it to IgnorePkg. Both the PulseAudio and ALSA backends work, though I had to make a simple change to my PulseAudio configuration.
stylemistake commented on 2018-06-10 05:54 (UTC) (edited on 2018-06-10 06:00 (UTC) by stylemistake)
It is possible, but we need to make sure it works without jack libs.
P.S. Zenity also seems like an unnecessary dependency, never seen it using it.
sean commented on 2018-06-10 05:48 (UTC)
Is it possible to move the dependency on the jack group to optdepends? I know many people prefer to use Jack with DAWs, but it isn't required by Bitwig Studio. Sometimes I actually prefer not to install it.
prg commented on 2018-05-03 13:27 (UTC)
flac/mp3 issues have been resolved in 2.3.3 for me
prg commented on 2018-04-27 15:15 (UTC)
Just had a conversation with one of the bitwig devs - sounds like they are aware of this issue (they are running into this with Ubuntu 18.04) and plan to fix it in a 2.3.x point release. Could potentially be related to ffprobe
Workaround for the time being would be to decode mp3/flac/whatever to WAV before you import
mateba commented on 2018-04-27 14:30 (UTC)
Obviously, the avprobe symlink trick doesn't work either.
mateba commented on 2018-04-27 14:25 (UTC)
My guess is that it's related to gstreamer: I use git to keep track of my bitwig projects and by looking at the logs I can tell that MP3 worked on the 14th of March, that is after ffmpeg 3.4.2-2 but before gstreamer 1.14. This is one of the packages i've been playing with recently and we can see that there are gstreamer libraries in /opt/bitwig-studio. That could explain why not everybody is experiencing the issue. That's quite a random guess, still. Anyone can confirm that it works without gstreamer ?
prg commented on 2018-04-27 14:04 (UTC) (edited on 2018-04-27 15:15 (UTC) by prg)
Got a response from BitWig; looks like they aren't interesting in fixing it... :/
Hello [prg]
this must be something specific to Arch Linux, on Ubuntu it works just fine. Unfortunately we can't maintain official support for all the different distros out there and therefore had to decide on one we use to test and more or less guarantee that it works. Therefor we currently can't say what exactly the reason is, that drag and drop does not seem to work using Arch Linux and Bitwig Studio.
Best regards, Bitwig Technical Support Team
<hr>prg commented on 2018-04-25 20:13 (UTC)
I'm also experiencing mikeza's issue. I've emailed BitWig through their support contact form but would love to hear any if anyone comes with a resolution here. ffmpeg 3.4.2-2 installed; don't remember having this problem with old versions
mateba commented on 2018-04-20 21:00 (UTC)
@mikeza Same here, did you find a solution ?
It's not related to ffmpeg since I'm sure MP3 & FLAC worked at least until mid-march and latest ffmpeg build-date is feb. I also tried to downgrade BW with no luck.
mikeza commented on 2018-04-04 19:15 (UTC) (edited on 2018-04-05 22:44 (UTC) by mikeza)
@stylemistake Yes, I have ffmpeg 1:3.4.2-2
Edit: I've also installed and tested ffmpeg-git and ffmpeg-compat-54
Legacy Bitwig worked fine.
stylemistake commented on 2018-04-04 00:29 (UTC)
@mikeza Have you installed "ffmpeg", which is an optional dependency?
mikeza commented on 2018-04-03 22:48 (UTC) (edited on 2018-04-03 22:49 (UTC) by mikeza)
Encountering problems trying to import/play MP3 and FLAC files. WAV works fine. All other features are working great.
[2018-04-03 17:38:19 float-document-master error] Error loading file /home/mz/media/music/mp3/100s/IVRY/03 F Around.mp3: com.bitwig.base.io.ivA: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Could not read audio file metadata
Edits: shortened error message
stylemistake commented on 2017-12-11 16:03 (UTC) (edited on 2018-03-06 17:59 (UTC) by stylemistake)
@bsorahan > Hoping that "pacman -Syu" wouldn't put me back in demo mode!
Due to their new licensing policy, you get updates for 1 year after purchase, and this cycle is different depending on when you purchased it. So when you decide not to continue paying for the next year, just lock yourself into specific PKGBUILD version, and that's it.
bsorahan commented on 2017-12-11 03:47 (UTC)
I've used this to install bitwig and it works fabulously (after installing jack2), so I'm thinking about buying a license. I was curious about what would happen when bitwig 3 comes out: hoping that "pacman -Syu" wouldn't put me back in demo mode! It looks like we should maybe expect a major version upgrade to require a different package or some other sort of manual intervention? Thanks for making this package!
blk commented on 2017-10-29 13:48 (UTC) (edited on 2017-10-29 13:48 (UTC) by blk)
jonathon commented on 2017-03-03 15:37 (UTC)
liam1895 commented on 2017-03-02 06:52 (UTC)
stylemistake commented on 2017-03-01 01:01 (UTC)
jonathon commented on 2017-03-01 00:02 (UTC)
interferon commented on 2017-03-01 00:01 (UTC)
vxf6 commented on 2017-02-28 22:21 (UTC)
stylemistake commented on 2016-12-09 12:27 (UTC)
vxf6 commented on 2016-11-13 20:21 (UTC)
stylemistake commented on 2016-11-13 20:01 (UTC) (edited on 2016-11-15 00:12 (UTC) by stylemistake)
nvllsvm commented on 2016-11-13 18:44 (UTC)
vxf6 commented on 2016-11-13 15:09 (UTC)
alcomatt commented on 2016-11-11 21:56 (UTC)
abique commented on 2016-03-28 15:40 (UTC) (edited on 2016-04-13 08:42 (UTC) by abique)
rvega commented on 2016-03-28 15:18 (UTC)
vxf6 commented on 2016-03-23 00:24 (UTC)
stylemistake commented on 2016-03-22 19:42 (UTC) (edited on 2016-03-22 19:43 (UTC) by stylemistake)
vxf6 commented on 2016-03-22 18:28 (UTC)
stylemistake commented on 2016-02-20 21:30 (UTC)
eikakot commented on 2015-12-20 12:51 (UTC)
eoli3n commented on 2015-11-29 12:10 (UTC) (edited on 2015-11-29 12:12 (UTC) by eoli3n)
eoli3n commented on 2015-11-27 19:39 (UTC)
itsizzy commented on 2015-11-04 10:05 (UTC)
net147 commented on 2015-11-04 00:48 (UTC)
archxyz commented on 2015-10-12 13:14 (UTC)
itsizzy commented on 2015-10-12 07:22 (UTC)
archxyz commented on 2015-10-11 09:01 (UTC) (edited on 2015-10-11 09:02 (UTC) by archxyz)
itsizzy commented on 2015-10-07 07:45 (UTC)
abique commented on 2015-10-06 20:46 (UTC)
Joermungand commented on 2015-10-06 06:45 (UTC)
YottaSecond commented on 2015-10-01 23:52 (UTC)
cprussin commented on 2015-10-01 18:17 (UTC)
eoli3n commented on 2015-09-22 13:30 (UTC)
eoli3n commented on 2015-09-22 12:35 (UTC)
Joermungand commented on 2015-09-17 06:30 (UTC)
odensc commented on 2015-09-15 23:42 (UTC)
anarch.linux commented on 2015-08-23 07:25 (UTC)
KenjiTakahashi commented on 2015-08-07 01:37 (UTC)
ricus commented on 2015-07-08 14:59 (UTC)
leolweb commented on 2015-05-24 21:09 (UTC)
crepererum commented on 2014-12-03 21:39 (UTC)
Zeben commented on 2014-11-20 20:15 (UTC)
abique commented on 2014-06-05 19:09 (UTC)
commented on 2014-05-26 09:09 (UTC)
itsizzy commented on 2014-05-26 06:18 (UTC)
commented on 2014-05-24 09:42 (UTC)
itsizzy commented on 2014-05-06 15:50 (UTC)
schef commented on 2014-05-06 15:20 (UTC)
itsizzy commented on 2014-05-02 08:10 (UTC)
commented on 2014-04-24 10:02 (UTC)
itsizzy commented on 2014-04-01 10:47 (UTC)
m0rph commented on 2014-04-01 06:42 (UTC)
Joermungand commented on 2014-04-01 04:27 (UTC)
m0rph commented on 2014-03-31 19:14 (UTC)
commented on 2014-03-31 12:48 (UTC)
itsizzy commented on 2014-03-31 12:46 (UTC)
m0rph commented on 2014-03-31 12:29 (UTC)
commented on 2014-03-31 09:56 (UTC)
m0rph commented on 2014-03-31 09:54 (UTC)
itsizzy commented on 2014-03-31 09:45 (UTC)
commented on 2014-03-31 09:27 (UTC)
AsavarTzeth commented on 2014-03-31 09:23 (UTC)
itsizzy commented on 2014-03-30 16:00 (UTC)
mynis01 commented on 2014-03-30 12:45 (UTC)
m0rph commented on 2014-03-29 06:43 (UTC)
myrnehr commented on 2014-03-26 17:55 (UTC)
itsizzy commented on 2014-03-26 17:22 (UTC)
myrnehr commented on 2014-03-26 16:56 (UTC)
myrnehr commented on 2014-03-26 16:45 (UTC)