Home Creators Posts Import Register Favorites Logout

Poll

Which Bitwig version are you on?

  • BLEEDING EDGE / BETA / 4.2 55
  • still 4.1 12
  • below 4 0
  • 2022-03-10
  • 67 votes
{'title': 'Which Bitwig version are you on?', 'choices': [{'text': 'BLEEDING EDGE / BETA / 4.2', 'votes': 55}, {'text': 'still 4.1', 'votes': 12}, {'text': 'below 4', 'votes': 0}], 'closes_at': None, 'created_at': datetime.datetime(2022, 3, 10, 14, 50, 44, tzinfo=datetime.timezone.utc), 'description': None, 'allow_multiple': False, 'total_votes': 67}

Content

important for future presets here on patreon. Its maybe not nice to be always bleeding edge for everyone.

Comments

George Napier

I have found their betas to be really quite solid.

Skadi

Mostly using the bleeding edge version. However, some beta releases ran into a java heap error which prevented Bitwig from starting (workaround was to use an older launcher .exe which works. The installed beta version was able to launch with it.)

Stijn

my license expired, waiting for a next major release to renew. So stuck on 4.1.6 for now :)

Scott Garman

I dislike the churn of keeping up to date when beta releases have multiple versions coming out frequently, so I stick with the latest stable release. Happy to hear that 4.2 is now stable as of today and I plan to update to that tonight.

Koz Myk

v4.1.6 until just now I HAD tried the Betas for 4.2 but they were upsetting my interface drivers for my other programs so I removed them.

Alexandre Enkerli

Been having pretty decent experiences during beta periods. Rather stable and the new features have been really fun to explore. In this case, 4.2 is an important release, for me. I hear some users who are less interested in the Note Grid. To me, it’s pretty major. Your tutorial on pitchtracking was close to a revelation. (I had been hoping for a dedicated pitchtracking module, finding the zero-crossing one to be subpar. And outputting the full pitch contour to the pianoroll is exactly the thing I’m not getting from plugins, including Melodyne. Plain MIDI doesn’t cut it.) While testing a BWS beta, I do keep the stable version around and I occasionally go back to it, either to compare or to find a workaround for a bug. In the latest episode of SonicTalk, there was a short exchange about BWS being the one DAW with a quick development cycle. Dominic Hawken was mentioning the lack of technological debt, compared to other DAWs. To me, it remains impressive. Like this beta period lasted for just a few weeks with bugs fixed quickly. Did anyone compile a timeline of BWS development cycles, with dates? Been referring to old release notes and it’s quite interesting.

Daniel McShane

4.1 here until 4.2 is out of beta. Please keep doing presets for 4.2!

Troy Outtram

Latest beta - downloading it when it comes out each time and reading the notes to see what’s changed. I’d love more instructions on how to use some of the new features from Bitwig as they obviously would have these for the internal Bitwig Dev/Test team. I work in large scale software dev projects in the FSI industry and it’s refreshing to see regular updates and less red tape haha

Stefan Sauer

Still 4.1.X, but brought the license extension already. So feel free to make presets for 4.2

Jumpstar

5.0 alpha :-) - :D :D

Jumpstar

that was a joke. i'm on this 4.2 now, and very nice it is

Fabrizio Sciarra

Well, in general I tend to jump on beta too, because I want to try to support Bitwig development. When I have an important project ongoing, I keep a backup made with previous stable version, just in case. Oh.... Linux, just to mention... My 2c.