Why you left Bitwig?

[Reefius]

https://m.youtube.com/channel/UCuzDmHD4 ... 7GA/videos

I can't watch his video's, they're just plain boring. He makes videos of over an hour for stuff that can be explained in 10 minutes, always saying the same things like 20 times over and over again.
Worst tutorials ever.

[excuse me please]

PS About the trial, I'm on a tab, so I didn't notice, but it seems rather suspicious.

About the tuts, I haven't updated Bitwig yet, I try to watch some though.

[antic604]

@Reefius

Lol now I notice; that whole darn Goa tutorial is in Cubase!
Mixed two channels up:

https://m.youtube.com/channel/UCuzDmHD4 ... 7GA/videos

3rd time's the charm?

[excuse me please]

@antic604

Ok, thanks!

[Trancit]

And how the hell does he have 297 days of trial remaining in Phase plant? Looks like he's using some kind of trial extender because the official trial period is 10 days

You should be careful with this kind of suspicion just you don´t know the reason for that...

There is no "trial extender" for kilohearts products...
Dash Glitch is a quite known youtuber for psy trance production and I would simply guess kilohearts gave him a 1 year trial version for reviewing and using in his vids...

[Hanz Meyzer]

Well, you can always travel back in time... Right?

[rod_zero]

I haven't left Bitwig but I'm starting to realize that the DAW is overhyped with too little to show for the hype. On top of a subscription like update model that I don't care what anyone here says is a subscriptions model in everything but name. They might as well just start charging $10 bucks a month at this point.

That is what really turned me off about the DAW. I really like it, I can even put up with some of the what I think are critical missing features but having to pay for them to fix the crappy macOS performance because my sub ran out is total crap imo. I don't care about The Grid. I want meat and potatoes features and they also need to fix some of the odd design decisions they've made early on that make absolutely no sense imo. Controller support is awful. I like DrivenByMoss but I don't want to be beholden to the whims of some dude doing it in his spare time. He seems to be mostly interested in PUSH2 and that's pretty much it.

If Bitwig doesn't do something this year in-terms of updates I'm moving elsewhere. I re-upped for one more year (I've had the code for a few months but haven't applied it yet). I genuinely like the DAW it has a lot potential, it's had potential since version 1, now it's time to actually execute. There are too many options right now in the market to put up with mediocre products.

I remember how many pointed out how impractical will be to give maintenance updates to users stock in in between big updates once their update "plan" had run out. I remember the bitwig employees that post here promised no one will be left behind if an OS broke something.

[spacepluk]

I bought Bitwig because I thought it was the only viable DAW for linux, and that was important for me at the time.

I upgraded 3 or 4 times and then I decided that I don’t like the pricing scheme and now I’m back to Reason/Cubase.

[tooneba]

- When adding a new track while playback is running, the TD-3 (which runs its own built-in sequencer) suddenly goes out of sync and it stays out of sync until I stop and restart playback.

Similar thing happens in Live when adding latency plugin while playing. It won’t compensated until I click stop button. Is it intend behavior?

[Echoes in the Attic]

- The 8 Macro knobs on each device only seem to be mappable to 1 parameter at a time. I had to insert a separate Macro modulator to be able to map multiple parameters to the same knob.

The things you are calling macros aren't macros. They are direct plugin parameters and are a way to order those parameters and group them into pages for remote control using devices. Like how you can change the orders of plugin parameters in Ableton except that in Bitwig you can actually leave some blank and also repeat parameters on multiple pages.

For macros that control multiple parameters (actual macros), you have as many as you want. You can add 4 at a time to a modulator slot if you want, or just one. And yes in order to add macro modulators, you have to add them. That's how it works when you have as many as you want of something.

[rodanmusic]

For the following 5 reasons:
1. The terrible and hard to use piano roll (imo).
2. The bad retina GUI performance that wasn't getting fixed.
3. Studio one was too well thought out for me to keep waiting for Bitwig to work.
4. I didn't use the clip launcher nearly as much as i thought I would.
5. It was costly to upgrade when they hadn't released any features i really cared about for several releases.

Once they fix 1 & 2 I will probably start using it again along side Studio One.

[antic604]

I remember how many pointed out how impractical will be to give maintenance updates to users stock in in between big updates once their update "plan" had run out. I remember the bitwig employees that post here promised no one will be left behind if an OS broke something.

You mean like Live 9.x users on OSX Catalina?

[apoclypse]

https://m.youtube.com/channel/UCuzDmHD4 ... 7GA/videos

I can't watch his video's, they're just plain boring. He makes videos of over an hour for stuff that can be explained in 10 minutes, always saying the same things like 20 times over and over again.
Worst tutorials ever.

Yeah. I knew you were talking about Baphometrix before I even clicked on the link. Completely agree. Just long ass videos with no real point to them.

[apoclypse]

I remember how many pointed out how impractical will be to give maintenance updates to users stock in in between big updates once their update "plan" had run out. I remember the bitwig employees that post here promised no one will be left behind if an OS broke something.

You mean like Live 9.x users on OSX Catalina?

That's different. I would expect that Live 9 would stop working because it used an old backend (I think was still using Carbon as a bootstrap for Live) while version 10 uses Qt. So I can understand that Live doesn't work on Catalina.

Bitwig has no such issues. They just don't bother to back port any fixes to older versions of Bitwig. So even if you don't want to upgrade if you want fixes that actually make the application usable you have to pay.

[antic604]

That's different. I would expect that Live 9 would stop working because it used an old backend (I think was still using Carbon as a bootstrap for Live) while version 10 uses Qt. So I can understand that Live doesn't work on Catalina.

Oh, so it's a double standard? Right

But even disregarding your convenient Carbon vs. Qt argument, have they been backporting 9.x fixes to 8.x and earlier. No.

Bitwig has no such issues. They just don't bother to back port any fixes to older versions of Bitwig. So even if you don't want to upgrade if you want fixes that actually make the application usable you have to pay.

How many DAWs you can list that update previous version(s)? I was sure there's none, until someone (you?) said that it was the case with Cubase which I'm really doubtful - I had a look at their patch history and updates end within 6-9 months after release and they've annual release cycle.