License model no way !!!

[Coockie1176ln]

One thing fl studio is best at.. its start up time! I wish all daws was as fast! Studio one is slow if u think bitwig is slow try s1! Also its even slower if u have scan vst om start up for obvious reason but slow start up bitwig is moderate could be faster like fl

[humanbeingbeing]

it's not about infinite or not. It's about undo on 3rd party vst right? Well, most tuff i use has that integrated anyway.

of course you right i'ts not about infinite,,,i hope they fix cntrl z / cmd z option for 3rd party vst before 2.0 upgrade
(maschine for example in evry daw is a nightmare if you want "undo" ,it only work from his panel menu or from hardware)

Everybody mail em about it xD get their asses to work !!!

Would be a fine idea, but people have already done this, they will say this is not on the top list of features, where as modulators supposedly are...

IMO it's a crucial workflow feature, in modern apps not just in music production, but any circa 2010 productivity app has undo and redo for every process, it's important so that you can develop a muscle memory for commands and that everything works as predicted... I remember this problem, it was extremely jarring expecting it to work like Ableton and having to work around it.

[humanbeingbeing]

it's not about infinite or not. It's about undo on 3rd party vst right? Well, most tuff i use has that integrated anyway.

of course you right i'ts not about infinite,,,i hope they fix cntrl z / cmd z option for 3rd party vst before 2.0 upgrade
(maschine for example in evry daw is a nightmare if you want "undo" ,it only work from his panel menu or from hardware)

Everybody mail em about it xD get their asses to work !!!

Would be a fine idea, but people have already done this, they will say this is not on the top list of features, where as modulators supposedly are...

IMO it's a crucial workflow feature, in modern apps not just in music production, but any circa 2010 productivity app has undo and redo for every process, it's important so that you can develop a muscle memory for commands and that everything works as predicted... I remember this problem, it was extremely jarring expecting it to work like Ableton and having to work around it.

[humanbeingbeing]

this board is so weird how it sometimes posts twice and apparently can't delete posts...

[BlackStarMuzic]

they want annual money for update ok,new company policy,for someone is cool for other no
..but in 3 years they don't fixed "VST UNDO" so if i have bitwig 1 and don't update to 2 i stay with a daw doesn't able to undo an operation in a vst?
amazing!

That's still an issue!? wow, it's worse than I thought, that is good test for 2.0 then, if they have vst3 support and no vst undo that's a bad sign, fingers crossed.

studio one doesnt have that either still been out longer then bitwig

So for me thats a downvote for Bitwig AND a downvote for Studio One. I can use Ableton or another app that supports it.

Does ableton really support that? I have ableton and has never once worked for me though I stopped using it before 9.7 so did it come with/after that?

Yes it does really support that. Just did a sanity check with 9.7.1.

Awesome well good to know. I guess I'll have to open it an play around haha

[ezelkow1]

There has always been confusion how live does undo, due to them limiting the number of vst parameters you can automate. Obviously a daw can only undo vst parameters it knows about, so you either have to modify the options.txt file to automap all exposed vst params (this had a 128 max, not sure if that has changed), or go through and populate each one yourself that you want to be able to undo/automate (or just hit the configure button on the vst and leave it on while you use it so it autopopulates)

At least that used to be the reason for the confusion unless something has changed

[humanbeingbeing]

There has always been confusion how live does undo, due to them limiting the number of vst parameters you can automate. Obviously a daw can only undo vst parameters it knows about, so you either have to modify the options.txt file to automap all exposed vst params (this had a 128 max, not sure if that has changed), or go through and populate each one yourself that you want to be able to undo/automate (or just hit the configure button on the vst and leave it on while you use it so it autopopulates)

At least that used to be the reason for the confusion unless something has changed

You dont have to do any of that... it just works.

[BlackStarMuzic]

There has always been confusion how live does undo, due to them limiting the number of vst parameters you can automate. Obviously a daw can only undo vst parameters it knows about, so you either have to modify the options.txt file to automap all exposed vst params (this had a 128 max, not sure if that has changed), or go through and populate each one yourself that you want to be able to undo/automate (or just hit the configure button on the vst and leave it on while you use it so it autopopulates)

At least that used to be the reason for the confusion unless something has changed

Interesting more that I did not know. haha but that makes sense!

[ezelkow1]

well good to know, that used to be how it worked ~5 years ago, so like I said, unless something has changed, which apparently it has. I do vaguely remember something with the live 9 release about have more vst params available

[Cyoon]

i like the photoshop (now also cubase) way. Like having a history with clear description of the action etc.

[stamp]

well good to know, that used to be how it worked ~5 years ago, so like I said, unless something has changed, which apparently it has. I do vaguely remember something with the live 9 release about have more vst params available

Nothing changed with Live 9. There's still the 128 parameter limit.

[humanbeingbeing]

well good to know, that used to be how it worked ~5 years ago, so like I said, unless something has changed, which apparently it has. I do vaguely remember something with the live 9 release about have more vst params available

This feature has been working since before 2012. The 128 parameter issue is the number of exposed parameters which is a plugin specific issue, sometimes internal parameters are not exposed to the DAW and if they're not exposed, they can be undone, it's not really much of an issue to be fair.

[Coockie1176ln]

well good to know, that used to be how it worked ~5 years ago, so like I said, unless something has changed, which apparently it has. I do vaguely remember something with the live 9 release about have more vst params available

This feature has been working since before 2012. The 128 parameter issue is the number of exposed parameters which is a plugin specific issue, sometimes internal parameters are not exposed to the DAW and if they're not exposed, they can be undone, it's not really much of an issue to be fair.

something similear issue with A.N.A in bitwig! Anyone with ana try get last moved parameter registered by bitwig. Sonic academys fault i belive also they are so bad are to respond on customers issue.

[StrZlee]

i understand and like that new model... 13,25/month for a great innovative software,... look back what they created the last years, a really outstanding daw with many blazing features and great support.

guys don't troll around, invest in the future of bitwig! i will do... (and i think it's time to print a new pile of fanboy stickers ;D )

[mikey1point0]

I was following Bitwig before it was Bitwig. When it was released finally I was extremely happy and went all in. When I heard about (version 2) I was super excited, when I read the new payment policy it freaked me out.

I'm now looking at other options simply because of having to pay for 12 months of updates.

What exactly does that mean (12 months of updates)? It would put my mind at rest if someone could definitively tell me that BUGs will be patched regardless of where i'm at in my subscription cycle. Only then will I be happy to comply.

Simply using the last working version is not looking after those who have to save a little harder to own a DAW. This actually makes me sad. I spent time telling others about how great bitwig is and now I can't.

Not being able to use a DAW when a bad patch is added in the last month / day of my subscription leaving me unable to use it does not make me feel safe or happy, it is this that will now stop me from telling others to buy. I will instead caution potential buyers and tell them to wait and see what happens over the next year once version 2 is out. (True story)

I really hope I have misunderstood, I really do. If bug fixes are free but features are paid then I will be happy to get V2.