[Fixed in 4.4] Weird bug: latest "Spectral Suite" update not included in upgrade plan

[JsinOwl]

2. There will always be company shills, they say something like 30% of people are authoritarians. They will supplicate themselves to the boss, they have no ability to have a real opinion of their own, they will defend draconian or bad actions from above always choosing to side with authority over the "little people".

Bitwig are the 'little people', so cruelly attacked for a mere error of judgement. This is my opinion.

People can behave politely. This is my opinion.

Bitwig should have included this package in then upgrade plan. This is my opinion. (which I politely emailed them about last week)

I'm not sure why I'm bothering, but....

People would not be reacting this way if it were a mere error in judgement. Breaching contract with hundreds if not thousands of users is not a "mere error in judgement". Stop downplaying what what they did. And stop exaggerating the statements of upset users. If someone uses hyperbole, and you take it literally, that's your issue, not theirs. "Politeness" does not engender change. That's why when governments do crappy things, people protest. They don't send polite letters and ask to talk about it over a cup of tea.

[Hink]

do you think perhaps that Bitwig learned something about their customer base and their passion for the product and what Bitwig has done for them in the past?

[PatrickW]

I was on FL Studio for 10+ years and switched to Bitwig studio a year ago. I could never go back. It takes less clicks to do almost everything in Bitwig. So much more window management in FL Studio. You have to manually route every individual instrument to a playlist lane in FL, whereas in Bitwig that's the default. Once you get to end-game FL use, you'll have 20 patcher windows all over the place instead of signal flow management neatly tethered to the instrument channel. Have fun managing that. To create an MSEG or ADSR in FL Studio for instance, you have to open a patcher, create an ADSR, enable signal outs from the ADSR, enable signal ins on a plugin, and then manually wire it into the plugin. You have to be high to use FL over Bitwig, for real.

Thank you for the input !
I will take this information into my FL Studio/Bitwig adventure !
As said, I'm keeping both and I'm quite sure that both have their advantages.
I will find out in the next months.
Who knows, maybe I'm completely wrong in my assumptions.
But working on my first FL Studio project after 13 years, it's working out pretty nice ...
The main difference I notice is that you have to be very organized in FL Studio to keep things clear.
But that's not a problem with my way of working ...
And if I compare the piano roll in Bitwig to the one in FL Studio, well ...

What I like about Bitwig is the connection with my modular system.
I have no idea yet how that works in FL Studio or if that even works with that DAW.
So, as said, at this moment, I keep both.
But if the Bitwig management would have been smart from day one, this discussion would not have happened at all.