Bitwig 5 is up

[SLiC]

I have spent a few hours with it tonight now and didn’t run in to any issues either (I wasn5 particularly looking, just made a track…as for the new browser I pretty much just start trying and a few letters in what I am looking for pops up….same way I used the old browser!

[pdxindy]

I have spent a few hours with it tonight now and didn’t run in to any issues either (I wasn5 particularly looking, just made a track…as for the new browser I pretty much just start trying and a few letters in what I am looking for pops up….same way I used the old browser!

Yes, typing a few letters works the same... that is great when you know the specific device you want. However, there is other new functionality that makes it faster when you don't know the name of what you want... for example with samples.

Make a bunch of collections with samples in them. I sort names with numbers first. One name of one of the collections might be "4.1 Cymbals" Now I can type 4.1 and hit tab and it opens that collection.

It is much faster than before to get out of the default filter. So my default for empty instrument tracks is a set of my most common devices/plugins. But in this case, I want to add a specific sample to a Sampler. I type the first few numbers like above and hit tab and that takes me to a specific samples collection. When you hit tab it clears the letters you typed and leaves the cursor in the search field ready to type something else to further sort the collection. They did a great job on it!

[Jac459]

saying you don't care about modulations as a bitwig user is like saying you don't like meat in a barbecue party... blasphemy....

It's because I'm a musician not a producer. I care more about composition than modulation. I'll leave modulation for the kids to play with.

It is factually unrealistic to hope that a software as complex as Bitwig (or any DAW) will work straight out of the box with your computer, your midi setup, your VSTs, your audio card without beta.

I have been a private Alpha and Beta tester for several DAWs. I know how the whole thing works....or at least the way it should work.

Sure, no software is 100% bug free even after extensive private testing but no developer I know of just expects their user base to do all the beta testing for them and then pay them for the privilege of doing it (well maybe IK Multimedia is an exception but then they don't have a paid update plan where the users are expected to pay then work for free as beta testers)

But there should not be any major zero hour bugs getting past the private testing and left for the user base to discover mere minutes after installing the public beta. Yes it happens, but no it shouldn't.

Their New Browser is a buggy mess and they're calling Beta 8 a release candidate.

The performance of Bitwig (the company) is amateurish in my opinion and that opinion is based on decades of experience.

I realize that opinion triggers the fan base but it is what it is.....

Yes I can't do anything about your opinion, and that's alright...
You lost 99% of your credibility saying that modulation is not for musicians anyway.

Let's agree to disagree my friend, we live in different worlds...

[simmo75]

Jac459, you come across as the definition of fanboy, reign it in a bit buddy, lol!

[ollie77]

People are aware that they don't have to use the beta releases, right? I have to ask because I feel like the dumbest dude around for not being able to figure this out.

[Jac459]

Jac459, you come across as the definition of fanboy, reign it in a bit buddy, lol!

Well, if fanboy is trying to defend the work of others then let it be.

And again, I don't pretend to convince everybody...

My point is... I don't support calling the work of others "amateurish" lightly. To me it is an extremely violent assertion and I don't accept it.
I am pretty sure if somebody post his/her music here, and I am calling it "amateurish", everybody will jump at my neck as being impolite.
In the same place/forum, it seems normal to pee on the work of editors without any decent explanations... I don't support that.

And then you will tell me, it is different, you paid the product so you own them and you can say whatever shit you want. I disagree. It is like when an asshole is treating waitress like poo because he feels he/she is the client. I always standup against that... I just can't accept it...

Anyway, I am not trying to chase all the Karens in the world... I have better things to do.

[Jac459]

People are aware that they don't have to use the beta releases, right? I have to ask because I feel like the dumbest dude around for not being able to figure this out.

Of course not, nobody is saying that. But then, int the other hand, I am sure you are also less surprised if there is a bug in the beta than if you are on a "stable" version.

Most of the time, if you want an easy life, don't go to beta. If you have a very specific setup and you want to be sure the beta works for you, backup your initial version and try the beta so you can report bugs if you have and then be sure that your setup will properly work on the stable release. Same if - like me - you prefer to take the (controlled) risk and try the new features directly.

[simmo75]

Jac459, you come across as the definition of fanboy, reign it in a bit buddy, lol!

Well, if fanboy is trying to defend the work of others then let it be.

And again, I don't pretend to convince everybody...

My point is... I don't support calling the work of others "amateurish" lightly. To me it is an extremely violent assertion and I don't accept it.
I am pretty sure if somebody post his/her music here, and I am calling it "amateurish", everybody will jump at my neck as being impolite.
In the same place/forum, it seems normal to pee on the work of editors without any decent explanations... I don't support that.

And then you will tell me, it is different, you paid the product so you own them and you can say whatever shit you want. I disagree. It is like when an asshole is treating waitress like poo because he feels he/she is the client. I always standup against that... I just can't accept it...

Anyway, I am not trying to chase all the Karens in the world... I have better things to do.

You f**king what mate?
What a pathetic little rant!
I never once mentioned amateurish, I think you have the wrong person…

[Jac459]

You f**king what mate?
What a pathetic little rant!
I never once mentioned amateurish, I think you have the wrong person…

Well, it doesn't seem you follow the discussion you are into my friend.
You reacted to a comment I made about Teksonik. So I am explaining you about the comment of Teksonik, did you even read it? Not everything is about you...
Actually if you remembered what we discussed about one page ago, I clearly mentioned I respect your opinion...

Of course, that's not the case of your latest comments .

[BobDog]

People are aware that they don't have to use the beta releases, right? I have to ask because I feel like the dumbest dude around for not being able to figure this out.

I can guarantee you are not the dumbest dude around here

[moxxi]

Classic KVR discussion...

[Trancit]

The browser isn´t any bug free at all...

Just 2 quick examples:
1. For VST2/3/Clap plugins if you click on the parent folder it shows just VST2 even it counts all...
Not before I choose the lower folder (why there have to be 2 levels anyway???) it shows the others too...

Browser 1.jpg

.
2. I have "insert in empty instrument track" set to show all plugins (without any presets) according to the procedure provided by the support...
If I now change the filter to the note fx, it shows just presets...no devices and there is no way in this tab to change this...
Clicking on "Everything" shows then just samples and presets until I click on the "devices" tag there...
After having done so I can now click on the blue NoteFX collection and choose devices...

PopUp.jpg

.
This new browser is nothing but a huge PITA for me... it does all the time completely unexpected stuff and I spend endless time hunting around clicking here clicking there to find a way until it decided to show me what it should have done on the first click...

[SLiC]

I must admit I am firmly in the ‘of all the things that needed updating the browser wasn’t one of them’ camp…it looks prettier but I was more than happy with the old one.

That said, I dont have any real issue with the new one…it works for me exactly like the old in how I use it (text search and collections) so I haven’t even noticed the issues like above…to me it was all just a lot of wasted effort as Bitwig already had the best browser….so many other things could have benefited from the development time. It maybe be however this may be part of something bigger, an underlying structure change for maybe network sharing or commercial packs, who knows.

[Jac459]

The browser isn´t any bug free at all...

Just 2 quick examples:
1. For VST2/3/Clap plugins if you click on the parent folder it shows just VST2 even it counts all...
Not before I choose the lower folder (why there have to be 2 levels anyway???) it shows the others too... Silly design???... Bug??? ...Don´t know but stupid and annoying...
Browser 1.jpg
.
2. I have "insert in empty instrument track" set to show all plugins (without any presets) according to the procedure provided by the support...
If I now change the filter to the note fx, it shows just presets...no devices and there is no way in this tab to change this...
Clicking on "Everything" shows then just samples and presets until I click on the "devices" tag there...
After having done so I can now click on the blue NoteFX collection and choose devices...
PopUp.jpg
.
This new browser is nothing but a huge PITA for me... it does all the time completely unexpected stuff and I spend endless time hunting around clicking here clicking there to find a way until it decided to show me what it should have done on the first click...

I don´t know what they had in mind how it is supposed to work but for me they couldn´t have failed more... this is the worst case I could have ever imagined...

Did you send an email to the beta support?

[Jac459]

I must admit I am firmly in the ‘of all the things that needed updating the browser wasn’t one of them’ camp…it looks prettier but I was more than happy with the old one.

That said, I dont have any real issue with the new one…it works for me exactly like the old in how I use it (text search and collections) so I haven’t even noticed the issues like above…to me it was all just a lot of wasted effort as Bitwig already had the best browser….so many other things could have benefited from the development time. It maybe be however this may be part of something bigger, an underlying structure change for maybe network sharing or commercial packs, who knows.

Yes I agree with you.
And I think you are right on the "an underlying structure change for maybe network sharing or commercial packs". Clearly the browser makes it more natural and enticing to use their sound packs. Maybe in the future they will try to sell sound packs externally (outside the upgrade plan). Clearly creating devices outside of the upgrade plan was a big fail so proposing sound/sample packs would maybe be better accepted. I guess they are still trying to get a second revenue stream so that's not impossible.