License model no way !!!

Official support for: bitwig.com
Locked New Topic
RELATED
PRODUCTS

Post

LOL, this gets morr comical by the day. Now the rich kids or adults with a job get to look down on those who complain about the price. Classism much? Have you thought for a second that maybe some users are from third world countries which make a great effort to pay a license? Why you like to put down and make fun of poorer people? Does it make you feel big and powerful? So sad.

It really amazes me the extend at which people try to play mind games to convince themselves they are not being ripped off.

The value of the license in the second hand market is the best true indicator of BW value. I suspect BW won't have much if they stick to the current model.
dedication to flying

Post

rod_zero wrote:LOL, this gets morr comical by the day. Now the rich kids or adults with a job get to look down on those who complain about the price. Classism much? Have you thought for a second that maybe some users are from third world countries which make a great effort to pay a license? Why you like to put down and make fun of poorer people? Does it make you feel big and powerful? So sad.

It really amazes me the extend at which people try to play mind games to convince themselves they are not being ripped off.

The value of the license in the second hand market is the best true indicator of BW value. I suspect BW won't have much if they stick to the current model.
It is funny, but it's the same old story with these debates... I do find the mind games fascinating. I mean it's one thing to say burn your money on a subscription (I could afford to but I wont) but it's another thing to use the cheap argument in the license debate... it's a pretty amazing mental leap.

Post

humanbeingbeing wrote:
Coockie1176ln wrote: So yeah its just a feeling ppl are baised on not facts
Uhhh no. You're delusional. Just you keep repeating that to yourself, then maybe it'll be true.
Youre not logical.
Go to Changelog by selecting latest version off bitwig from you account, open searchbar on your browser, type in "Regression"

This is my results for how many regression there are fixed, 12 fixed regression
3.png
Here is result for all "FIXED"which is 437 fixed bugs.
1.png
Now for improved we got 86 improvements
2.png
How is That 2 steps back for each fix? Guess the numbers show whom are delusional off us. Good luck at cram school.
You do not have the required permissions to view the files attached to this post.

Post

Coockie1176ln wrote:
humanbeingbeing wrote:
Coockie1176ln wrote: So yeah its just a feeling ppl are baised on not facts
Uhhh no. You're delusional. Just you keep repeating that to yourself, then maybe it'll be true.
Youre not logical.
Go to Changelog by selecting latest version off bitwig from you account, open searchbar on your browser, type in "Regression"

This is my results for how many regression there are fixed, 12 fixed regression
3.png
Here is result for all "FIXED"which is 437 fixed bugs.
1.png
Now for improved we got 86 improvements
2.png
How is That 2 steps back for each fix? Guess the numbers show whom are delusional off us. Good luck at cram school.


Hahahahahahahaha. You don't get it. ... and omg, what side of the argument are you on!! I guess I imagined all those bugs after all ;)

Post

"Some" People keep saying that for each fix there are 2 regressions. You said people don´t make that up. But i came up with proof if you didn't get what i said from start then its you who don't get it. I'm on my side thanks neither bitwig or those against bitwig.

Post

Coockie1176ln wrote:"Some" People keep saying that for each fix there are 2 regressions. You said people don´t make that up. But i came up with proof if you didn't get what i said from start then its you whom don't get it. I'm on my side thanks neither bitwig or those against bitwig.
You found 12 fixed regressions. They were not imagined. Semantics over 1 steps forward 2 steps back does not make your original statement correct. Those people did not mean 2 regressions for each fix, they were talking about those regressions. There was no personal bias, but I'm glad you were able to go an see that for yourself.

...also for anyone else trying to float this idea that Bitwig 1.0 was a smooth bug free experience- get a grip.
Last edited by humanbeingbeing on Mon Jan 16, 2017 5:11 pm, edited 1 time in total.

Post

humanbeingbeing wrote:
Coockie1176ln wrote:"Some" People keep saying that for each fix there are 2 regressions. You said people don´t make that up. But i came up with proof if you didn't get what i said from start then its you whom don't get it. I'm on my side thanks neither bitwig or those against bitwig.
You found 12 fixed regressions. They were not imagined. Semantics over 1 steps forward 2 steps back does not make your original statement correct. There was no personal bias, but I'm glad you were able to go an see that for yourself.

...also for anyone else trying to float this idea that Bitwig 1.0 was a smooth bug free experience- get a grip.
I wrote that its not correct that people say "For every fix bitwig goes back 2 steps"
437 fixes only 12 of those where regressions. I only implied that others have said the mentioned about every fix and thats its false that each fix moves bitwig back 2 steps

also i hate bugs i have never thought bitwig was bugfixed, man ive been so annoyed, now i sit on s1 atm and man discovering bugs there as well :dog:

Post

Coockie1176ln wrote:
humanbeingbeing wrote:
Coockie1176ln wrote:"Some" People keep saying that for each fix there are 2 regressions. You said people don´t make that up. But i came up with proof if you didn't get what i said from start then its you whom don't get it. I'm on my side thanks neither bitwig or those against bitwig.
You found 12 fixed regressions. They were not imagined. Semantics over 1 steps forward 2 steps back does not make your original statement correct. There was no personal bias, but I'm glad you were able to go an see that for yourself.

...also for anyone else trying to float this idea that Bitwig 1.0 was a smooth bug free experience- get a grip.
I wrote that its not correct that people say "For every fix bitwig goes back 2 steps"
437 fixes only 12 of those where regressions. I only implied that others have said the mentioned about every fix and thats its false that each fix moves bitwig back 2 steps

also i hate bugs i have never thought bitwig was bugfixed, man ive been so annoyed, now i sit on s1 atm and man discovering bugs there as well :dog:
They did not mean 2 steps back for EVERY fix... they were talking about those regressions.... but yes ok, very technically semantically speaking there wasn't 2 steps back for every fix...

... some developers here have pointed out that Bitwig follows standard development practices, one of those standard practices is regression testing.

Post

humanbeingbeing wrote:
Coockie1176ln wrote:
humanbeingbeing wrote:
Coockie1176ln wrote:"Some" People keep saying that for each fix there are 2 regressions. You said people don´t make that up. But i came up with proof if you didn't get what i said from start then its you whom don't get it. I'm on my side thanks neither bitwig or those against bitwig.
You found 12 fixed regressions. They were not imagined. Semantics over 1 steps forward 2 steps back does not make your original statement correct. There was no personal bias, but I'm glad you were able to go an see that for yourself.

...also for anyone else trying to float this idea that Bitwig 1.0 was a smooth bug free experience- get a grip.
I wrote that its not correct that people say "For every fix bitwig goes back 2 steps"
437 fixes only 12 of those where regressions. I only implied that others have said the mentioned about every fix and thats its false that each fix moves bitwig back 2 steps

also i hate bugs i have never thought bitwig was bugfixed, man ive been so annoyed, now i sit on s1 atm and man discovering bugs there as well :dog:
They did not mean 2 steps back for EVERY fix... they were talking about those regressions.... but yes ok, very technically semantically speaking there wasn't 2 steps back for every fix...
That's what i meant, ofc i know they literately didn't mean it but people kept taking what others said when they just felt disappointed and themselves say its true etc. They were talking with their feelings and it kinda to me sounded wrong, i just felt the need to get it out right so people don't think that each fix causes a regression that it happens so often. Thats causes just bad rumors. that bitwig have had its share of bugs thats true. that people are pissed about the new model thats true.

Post

Coockie1176ln wrote:
humanbeingbeing wrote:
Coockie1176ln wrote:
humanbeingbeing wrote:
Coockie1176ln wrote:"Some" People keep saying that for each fix there are 2 regressions. You said people don´t make that up. But i came up with proof if you didn't get what i said from start then its you whom don't get it. I'm on my side thanks neither bitwig or those against bitwig.
You found 12 fixed regressions. They were not imagined. Semantics over 1 steps forward 2 steps back does not make your original statement correct. There was no personal bias, but I'm glad you were able to go an see that for yourself.

...also for anyone else trying to float this idea that Bitwig 1.0 was a smooth bug free experience- get a grip.
I wrote that its not correct that people say "For every fix bitwig goes back 2 steps"
437 fixes only 12 of those where regressions. I only implied that others have said the mentioned about every fix and thats its false that each fix moves bitwig back 2 steps

also i hate bugs i have never thought bitwig was bugfixed, man ive been so annoyed, now i sit on s1 atm and man discovering bugs there as well :dog:
They did not mean 2 steps back for EVERY fix... they were talking about those regressions.... but yes ok, very technically semantically speaking there wasn't 2 steps back for every fix...
That's what i meant, ofc i know they literately didn't mean it but people kept taking what others said when they just felt disappointed and themselves say its true etc. They were talking with their feelings and it kinda to me sounded wrong, i just felt the need to get it out right so people don't think that each fix causes a regression that it happens so often. Thats causes just bad rumors. that bitwig have had its share of bugs thats true. that people are pissed about the new model thats true.
Fair enough but the regressions were serious and common, enough to register a bad experience in people's feelings... it's absolutely true that humans are derivative and we copy what we read but of course regressions were not a figment of the imagination... and as they were real I have to give people the benefit of the doubt, if they say they experienced those regressions they probably did and I have to assume they did, it's counterproductive to suggest otherwise.

Post

also I want to say something about this word 'biased'... this isn't a debate where I want to be right... bugs are incredibly inconvenient for me, I do not want to be right about bugs, I dont want bugs, I am not unfairly prejudiced against Bitwig... I bought it, I want it to work.. I would love to be able to delete Ableton.
Last edited by humanbeingbeing on Mon Jan 16, 2017 11:31 pm, edited 1 time in total.

Post

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!

Post

panox80 wrote: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.

Post

in 1.3.15 still don't work

Post

humanbeingbeing wrote:
panox80 wrote: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

Locked

Return to “Bitwig”