Bitwig 5 is buggy af. New browser is useless and using windows explorer is faster now to add vsts, which says a lot. V4 is great despite major bugs that have their work arounds, going to see where v5 leads, which seems is led by the same team that took awful and illegal decision to make updates a subsribe model despite the eula.

 

What would you like to see in v6?

 

Their take on rest of the DAW, what they done so far is amazing, it's not like I'm missing something or that breaks my thing, I was happy when they added fades in V2 and from that point it was enough for me, but I was thinking the same before Bitwig and than realized it can get easier if you actually embrace the other way of doing things. They seem to nail some of the stuff, so I ditch my old way of working. Dunno, piano roll could get some love, whole MIDI aspect, selecting group of notes defined by criteria (like by position, pitch, octave, pattern and etc), audio editing too, cutting on zero crossing and all the fun stuff, it's working, but it's fairly basic, sometimes it can take little time, but it's price to pay. Inserting same plugins on multiple selected channel, it's not that common that I do this, but there was times when I wanted to insert Tool or VU meter at the end of every channel and the only way was to go one by one, some folks probably have template ready for that kind of workflow, but still it would be nice one.

 

Yes, yes, yes, agree, agree.
Bitwig could make a gigantic leap by doing just a few good tweaks at the BASIC level of what a DAW is supposed to be.
Problem seems to be: Too many people see Bitwig as their sandbox playground for some modular synthesis. Which is fine, have fun!
But to all modular-loving people i can just say: congratulation to this upgrade, it's for you and for you only, so be grateful, but don't forget, that there are also people who have good reason to be disappointed in this upgrade, and are now waiting for Bitwig 6. If you want an overview of just SOME of the reasons of why there's disappointment, have a look at some of the existing feature requests. Although i might add that my personal priorities are different than the Top-ranking of this feature request list. I think a better piano roll, better midi editing, better audio editing, audio quantization, audio overdub, and fixing visibility issues of the playhead/grid are the absolute top requests.
https://bitwish.top/c/features/5

 

Last edited: Apr 13, 2023

Applying processing just on selected parts would actually be more than welcome, think Logic and Cubase recently got that, can see the benefits, maybe I just want something different on one part of the audio clip, some quick audio restoration or different EQ or effect, whatever, that thing could really speed things up.

 

I agree with almost all of your points.

I have to disagree with you on this one. Yes, what got me interested in Bitwig in the first place was the modular aspect of it, but I use it as my main DAW for everything, and I hardly touch the Grid. However, their modulators are just amazing and I'm happy for this new update. You don't need to be in a modular mindset to incorporate them in your workflow. Whatever I may be doing, there's always more than a 50% chance that using the modulators will add movement and life to the sound.

 

You are right, when I was re-watching promo videos realized there's actually huge potential I'm disregarding and all that can benefit me too, that's the thing I like about Bitwig, always improve my workflow in many ways, great stuff.

 

It's on beta 2, bugs are expected

 

This new global mod system can be used in interesting ways. You just got to watch some videos or put your imagination to use.

 

Bitwig is changing versions too fast they could have improved V4 much more. This is a sign that maybe they're not satisfied with their product, they want to introduce a new payment mechanism, or its a -desesperate- marketing move, anyway this fast changes could lead to bad decisions. I stand with Bitwig for the workflow more than the modular things, if the UI experience is damaged I will remain in V4. Since V5 is still in beta its too early to say anything lets hope that evolves well.

 

It's in BETA, what do you expect? If it was a finished product it wouldn't be a beta. If you're experiencing bugs just send them a report like anyone else, you're beta testing.

 

I’ve really wanted to try Bitwig for years but I love my Push 2. Has anyone created some kind of compatibility script or anything to be able to fully use a Pushwith Bitwig? With similar workflows, I’d imagine it’s feasible for someone clued up on it? I know Richie Hawtin loves using his Push in production and when live, and has recently moved from Ableton to Bitwig.

 

Yup : https://www.mossgrabers.de/Software/Bitwig/Bitwig.html

Don't have a push, but his Launchpad Pro script for Bitwig was way better than Novation's original script for Live.

 

Changes in Bitwig Studio 5, Beta 3
IMPROVEMENTS

• Browser: The ordering of search results has been improved, with direct name matches coming first, then consistently sorting other results by kind (device, preset, etc.)
• Templates are now listed in side-browser, and are available via a Templates source (under All Sources > by Kind)

FIXES

• Collections weren't showing (or accepting new) VSTs [32044]
• Fixed crash when switching a Polymer module that is targeted by a project-level modulator [31812]
• Some large projects could crash the audio engine when loading [31352]
• Users can't save project after deleting modulator in project device [32043]
• Segments Grid/Polymer module & modulator: Fixed inconsistencies in release behavior in bipolar mode, etc.
• "Add automation lane" context menu entry was missing for project-level modulators [32054]
• Fixed crash when copying modulators at the track- or project-level [32018] [32021]
• Fixed crash when choosing template to use as default template, or when using the New from Template… action [32003] [32053]
• Dropdown choosers on remote control pages were not displaying the selected value [32046]
• Transfer Grid module: Would sometimes not allow other modules to come near it
• Longer sound package names were not centered in browsers [31921]
• Slice in Place dialog buttons looked broken [32045]
• Track inspectors were too wide in non-English localizations
• u-he CLAP plug-ins: Fixed a crash when using right-click to Init
• Windows CLAP plug-ins: Were sometimes not reloading
• VST2: Several plug-ins now work again in version 5 [32042]
• Nektar controller extensions: were often crashing instantly [32009]

 

I run live 11, but i have to admit that when i tried bitwig 4.4 there were alot of elements that kind of persuadded me to perhaps switch over.
But the truth is that switching over for me is a no no, until bitwig incorporates a few more features regarding workflow im staying with live11
I think the best of both worlds is the key here!
"I mean i use both btwg and live, shame you cant use btwg within live as a plugin"
Theres alot of things in its favour, personally i think it was total crap when first released, but now its a Powerhouse!!
As i understand it , bitwg was created by some ex ableton employee,s So i find myself asking why certain aspects of it are kind of strange and unintuative!! For me thats the problem, Its beutiful to look at and all fancy icons n stuff, and although its an epic daw, i personally think it still lacks the intrinsic nature of live ,Its A serious contender but for me its a litte weird in certain areas.....

 

hi jynx. would you mind sharing some more thoughts about bitwig's workflow and why you preferred live?

 

ditto. also, those who managed to master BT workflow, please counter. I would love to come to terms with intuitive use of BT, but there are those little things which ruin the flow for me.
My main complaint is that it is much less predictible in switching panels. It might be a matter of coming to terms with it once and for all with similar key combinations but I simply can't make it. Nothing near as easy as switching from cubase to live 6 (!)

 

That's fair and a subjective thing, I for once can't stand using Live, I tried for a good while and it's just weird and not intuitive, weird shortcuts and bizarre workflow (and this is coming from someone that released music made in 5 different DAWs). Opposite to what you might be thinking I find it really sad because I love their stock plugins and M4L devices.

 

You must be new to Bitwig? Their licensing model demands (not promised) fast updates. The update pace has significantly slowed down this year, to some people's dissatisfaction. I was beginning to wonder WTH myself but now it makes sense. This update must of been a lot of work. Usually we get 3-4 updates a year + bug fixes. This is normal for Bitwig.

Also the ver numbers, just there for categorization and marketing. They don't mean very much in Bitwig's world. Just a number.