FL user turned Bitwig user here, I've had nothing but a great time with Bitwig, although Bitwig has it's own issues, and one of them pointed out in this thread is just that it's not 'ready' to replace a lot if 'replacing' were a selling point. There's things missing with default plugins (a strong point: a vocoder), there's a lack of Rewire support if you roll that way (JACK seems to be able to do something like Rewire, but I haven't looked into it,
until then here's this), and a kind of useful yet disappointing set of default sounds.
As for the positives and what made me move, PDC, plugin sandboxing (FL has plugin sandboxing I think, but it just didn't seem to work for me majority of the time? There'd be points where FL would have a plugin crash and it'd tell me that a plugin crashed, but majority of the time, if a plugin crashes, it all crashes..), the ability to have multiple projects 'open' (I say 'open' because you can only have the audio engine on for one which makes sense), the audio engine startup process generally just being faster than loading up a project in FL, audio events and how incredibly easy and fast it is to play with them compared to FL, and it's composition view being so flexible. I haven't bothered looking at Open Controller API yet. There's more coming along the way for Bitwig like Network Syncing and Modular Device Programming too, so I feel Bitwig will have a strong future ahead of itself.
I still like to use FL on the side though, FL is still
always useful, including for it's piano roll, which is forever.
