Bitwig drove me crazy today
Added 2024-09-04 18:22:32 +0000 UTCIn this video, I talk about some of the issues I’ve been running into with Bitwig Studio, specifically when it comes to importing and working with seamlessly looping audio files. Bitwig often makes unwanted changes to files when I import them, like shifting the start point or adding stretch modes that cause artifacts when the tempo changes. It’s frustrating because these things happen automatically, and the solutions are often hidden or unclear. My goal is to point these issues out, hopefully get them fixed, and start a conversation about how to make the workflow easier for everyone.
Key points:
I'm highlighting Bitwig's bugs to help get them fixed.
I ran into issues with audio imports, like Bitwig offsetting wave files and enabling unwanted stretch modes.
Changing the project BPM introduces artifacts due to Bitwig's default stretch mode.
There’s a hidden solution where holding down control lets me import files in raw mode, but it’s not well communicated.
I feel the process is too complicated and think Bitwig could improve the user experience by making these options clearer.
Comments
Artifactwig
Chris
2024-09-07 15:29:25 +0000 UTCBeen having the very same issues. I’m at the point now where I’m seriously considering Cubase 13 which is half price until the 25th (£100 more than the bitwig annual subscription). Really like Bitwig even though it’s missing some basic audio/midi devices. Cubase is pulling me closer and yes all DAW’s have their issues as we all know but after 40yrs Steinberg has been through most of these issues already. Really don’t want to be switching daws like I’m Carl Cox with 5 decks. I suppose 2 isn’t too bad 🤦♂️
THE R
2024-09-05 20:17:33 +0000 UTC
