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

[Greenplums]

They have moved the goal posts half way through the match and secretely changed the rules when the players complained. So we now have Add-ons with obviously more on the way and how many do you need before they introduce Bitwig Pro/Suite (Including all Add-ons). Buy that and you will get all future updates and add-ons for X per year. Then what? The introduction of something with another name? Sorry I am not buying into that. Fabulous DAW and one I could come back to but after this they will need to clean up their act before I do so.

[pdxindy]

I'm glad I hadn't settled 100% on Bitwig, I feel for those of you that did, the kowtowing must be rough.

That statement is the product of a slave-mind

[Echoes in the Attic]

All I really want is for Bitwig to have some kind of functionality like Ableton's M4L Capture Device to instantly recall global values (and maybe on a device level as well).

What is that exactly?

It's a device you can put anywhere that stores and recalls global snapshots of whatever devices you want (you can optionally include devices, track levels, send levels etc.). Kind of like Maschine's snapshot functionality. I don't think it should be a device in Bitwig, that's just how they had to do it with Max for Live. It should be part of the program, like with Maschine. Maybe I should have compared it to Maschine instead.

Sounds like a great idea for a $100 add-on requiring the latest version of Bitwig!

Oh no you didn't!

[Echoes in the Attic]

All I really want is for Bitwig to have some kind of functionality like Ableton's M4L Capture Device to instantly recall global values (and maybe on a device level as well).

What is that exactly?

It's a device you can put anywhere that stores and recalls global snapshots of whatever devices you want (you can optionally include devices, track levels, send levels etc.). Kind of like Maschine's snapshot functionality. I don't think it should be a device in Bitwig, that's just how they had to do it with Max for Live. It should be part of the program, like with Maschine. Maybe I should have compared it to Maschine instead.

Yeah, seems better suited to a project wide snapshot function...

I can already make snapshots in Bitwig for a device chain... but obviously not outside it

What's your method of doing snapshots for devices? I've done it with Freestyle because you can recall snapshots there (including midi out values), but haven't managed to do it with bitwig devices. I don't count duplicates with instrument selector at all if that's what you mean, since I want the snapshots to work whenever you trigger them, even after you've changed parameters.

[loungepanda]

There's a recurring pattern where users of this sub-forum make wild assumptions about what business model they imagine that BW will follow and then go apeshit when Bitwig decides to make a decision that deviates from that assumption.

Basically, go cry about it. Oh wait, you are. This thread is basically festivus.

[machinesworking]

I'm glad I hadn't settled 100% on Bitwig, I feel for those of you that did, the kowtowing must be rough.

That statement is the product of a slave-mind

You seriously cannot believe that. That's such obvious and weak minded projecting as to be worrying, are you OK?

You're bending over backwards to serve a company that doesn't care at all about you, not in the slightest. Any fool would have figured out the backlash from this, that at least half dozen people at Bitwig sat around and thought it was OK that they change the update plan mid stream says more than anyone who isn't just a toady to a brand should need to know.

Bitwig just made one of the worst moves I've ever seen any company ever make in terms of the user base, and here you are defending them. The kool aid is laced with cyanide, the emperor has no clothes, yet here you are calling other people sheeple. Reminds me of a certain MAGAtt that infested the USA.

Basically you've wrapped your identity in software, and the owners are yanking your chains, but to you everyone else isn't red pilled.

[pdxindy]

What's your method of doing snapshots for devices? I've done it with Freestyle because you can recall snapshots there (including midi out values), but haven't managed to do it with bitwig devices. I don't count duplicates with instrument selector at all if that's what you mean, since I want the snapshots to work whenever you trigger them, even after you've changed parameters.

I use a button modulator, activate the mod arrow and adjust parameters to taste. Add another button, use different settings. And so on. Then I make a preset page and add the snapshot buttons there.

Works pretty well, but they are not absolute values so if you change the default settings, it affects the saved states too.

[machinesworking]

Meanwhile, UVI just released probably their 6th significant update to Falcon.
They manage to somehow do this without gouging their user base.. weird huh?

[jonljacobi]

"Ultimately, I believe Bitwig will do the right thing, and they just made a stupid mistake here. Poor communication, not honoring existing agreements and expectations."

Don't treat companies as you would individuals or expect morals to apply. Especially if you work for them. They're eventually all about making money no matter how small and well-intentioned they start out.

If this costs the company money and customers, they will back off. If it makes them more money, they'll continue. As I said previously, if it offends you, show your displeasure with action, not words. If you're willing to accept it, then accept it. That's life.

My guess is that it will make them money, and they'll continue. Most people eventually fold and CFO's know that.

[pdxindy]

You seriously cannot believe that.

Your comments display your underlying thinking that your adolescent rebellion is somehow a form of freedom. It isn't. Then you mock others as slaves who aren't also engaging in childish grandstanding. You're the one who has wrapped yourself around Bitwig.

[gExpectations]

this thread is kinda funny to me. (1) id expect people to be mad for a couple of reasons, mainly (a) bitwig set the expectation that all releases are included when buying the upgrade plan (b) bitwig stands for innovative sound manipulation options so from that perspective spectral tools can be considered core. (2) at the end of the day its just an 80€ DLC, nothing about the potential of your music making with bitwig has changed. people are acting as if someone took their last potato and now they are starving. if you really are swapping daws because of a (probably unfair) marketing move, you are either a beginner or should value your own time more.

[Chameleonman]

It's more than just a lie, because people had invested their money... it's a scam. Bitweasels try to weasel out by changing the wording. They can call it unicorn it doesn't help.

[tempsperdu]

Bitwig users are unusual in that they had faith in the company enough to pay that company a year in advance for possible features. They now have no reason to do that, so why would they when this behaviour gives them every reason not to?
Did someone send Bitwig a copy of The Darwin Awards for inspiration?

[Echoes in the Attic]

What's your method of doing snapshots for devices? I've done it with Freestyle because you can recall snapshots there (including midi out values), but haven't managed to do it with bitwig devices. I don't count duplicates with instrument selector at all if that's what you mean, since I want the snapshots to work whenever you trigger them, even after you've changed parameters.

I use a button modulator, activate the mod arrow and adjust parameters to taste. Add another button, use different settings. And so on. Then I make a preset page and add the snapshot buttons there.

Works pretty well, but they are not absolute values so if you change the default settings, it affects the saved states too.

Ah yes, that's the problem. I'd want it as a way of snapping back to a default state (or one of several) after tweaking parameters. Doesn't work using modulators because they're relative, as you say.

[machinesworking]

You seriously cannot believe that.

Your comments display your underlying thinking that your adolescent rebellion is somehow a form of freedom. It isn't. Then you mock others as slaves who aren't also engaging in childish grandstanding. You're the one who has wrapped yourself around Bitwig.

When things turn into ad hominem entirely for your argument to have any traction at all, you've lost.

You haven't and can't make one good point about this change in the the update plan in favor of it, so you're resorting to petty arguments about which DAW has better features etc. then when that fails, you resort to just petty.