Bitwig VS Ableton

[sl1914]

...
For me, personally, this is always the best approach, and try as I have to 'like' bitwig's 'collections' and 'stars', I have always found it very slow and cumbersome. Which I've also felt about other daws that similarly abstract the concept of folder organization (e.g. Maschine's 'tagging' system...ughhhhhhh).

The great thing about tagging (and IMO Bitwig collections are pretty much another word for tagging) is that one file can belong to more than one category. I like to organize VSTs according to folders named after companies that make them. But inside those folders I can use tagging/collections to find different kinds of VSTs easily.

[pdxindy]

What you need to do is right-click on a collection and "choose as a target collection". Then, the stars you assign to the right side will define what is part of your collection and what isn't.

I don't use that function (choose as target collection) other than for favorites... I create a collection, multi-select what I want and drag them into the collection - done - no need to use stars at all for collections.

[syntonica]

In the short time that I spent demoing Bitwig, the biggest snnoyance was so much mousing around just to find tiny, fiddly targets. If I try it again, it will be with the express purpose of learning and/or setting keyboard shortcuts.

The browser was huge and confusing and I never cottoned on to it. I really disliked that it kept offering VST3s when there were perfectly good VST2 versions installed. The horse may be dead, but I'm going to beat it until there's nothing left.

[xbitz]

I vastly prefer working that way then dealing with the abstracted 'collection' concept where you have to 'target' a collection then click stars on items.

You don't have to target a collection and click stars...

Seems like Bitwig could use a better browser tutorial cause lots of people posting don't know how to use the browser.

Actually, the way how the star system works in Bitwig got me really confused. Only understood it a few days ago. It's not exactly intuitive to be fair.

Just the fact that it looks like a star, but in reality it's an assignment system to any chosen collection. What you need to do is right-click on a collection and "choose as a target collection". Then, the stars you assign to the right side will define what is part of your collection and what isn't. You can apply this to the default "Favorites" of course, too - in that case it does behave like favorites. (Just pointing this out, maybe it helps other to un-confuse themselfes, too).

with smart ones can skip the 'choose...' part using "in_collection=Favorites category=Reverb device_type=audio" for ex.



the marked reverb will go to the right smart collection instantly, removing also needs one click only

[slackhead]

Anyone confused by the Bitwig browser should check out Baphometrix's video on the subject. It's very long, as is their way, but lot's of good info and tips. This helped me a lot.


This one is good too:

[xbitz]

^^^ he has created an unofficial docs too https://docs.google.com/document/d/1XRd ... cztr5f5fqn probably can be parsed faster

[SLiC]

The browser was huge and confusing and I never cottoned on to it. I really disliked that it kept offering VST3s when there were perfectly good VST2 versions installed. The horse may be dead, but I'm going to beat it until there's nothing left.

The browser can be customised down to small and simple, just right click and deselect the columns.
You can set to see VST 3 over VST2 etc in preferences, personally I have it selected to only show VST3 when available, this and hide duplicates makes it easier to find what I want. I cant see any reason to use a VST 2 version if a VST 3 exists, is there any?

[perpetual3]

I vastly prefer working that way then dealing with the abstracted 'collection' concept where you have to 'target' a collection then click stars on items.

You don't have to target a collection and click stars...

Seems like Bitwig could use a better browser tutorial cause lots of people posting don't know how to use the browser.

Yup, agreed.

[perpetual3]

The browser was huge and confusing and I never cottoned on to it. I really disliked that it kept offering VST3s when there were perfectly good VST2 versions installed. The horse may be dead, but I'm going to beat it until there's nothing left.

The browser can be customised down to small and simple, just right click and deselect the columns.
You can set to see VST 3 over VST2 etc in preferences, personally I have it selected to only show VST3 when available, this and hide duplicates makes it easier to find what I want. I cant see any reason to use a VST 2 version if a VST 3 exists, is there any?

Softube plugins. If you turn off or deactivate a Softube vst3 or turn off the audio engine using a vst3 on Mac and then reactivate or turn on, the plugin reinitializes itself and the patch is lost.

[SLiC]

The browser was huge and confusing and I never cottoned on to it. I really disliked that it kept offering VST3s when there were perfectly good VST2 versions installed. The horse may be dead, but I'm going to beat it until there's nothing left.

The browser can be customised down to small and simple, just right click and deselect the columns.
You can set to see VST 3 over VST2 etc in preferences, personally I have it selected to only show VST3 when available, this and hide duplicates makes it easier to find what I want. I cant see any reason to use a VST 2 version if a VST 3 exists, is there any?

Softube plugins. If you turn off or deactivate a Softube vst3 or turn off the audio engine using a vst3 on Mac and then reactivate or turn on, the plugin reinitializes itself and the patch is lost.

Ah, OK- I am on PC, never had an issue with any VST3...sounds like a Softube Bug. As I understand things VST3 only has advantages and efficiencies over VST 2 (assuming the VST3 is working properly!)

[syntonica]

As I understand things VST3 only has advantages and efficiencies over VST 2 (assuming the VST3 is working properly!)

Not really either. MIDI-wise, VST2 is far superior. It's why SB finally had to kill VST2 to get VST3 adoption to happen after some 20 years.

[SLiC]

As I understand things VST3 only has advantages and efficiencies over VST 2 (assuming the VST3 is working properly!)

Not really either. MIDI-wise, VST2 is far superior. It's why SB finally had to kill VST2 to get VST3 adoption to happen after some 20 years.

How so? (genuinely curious), I mean VST 3 is happening like it or not anyway, but most of what I have read is favourable (although I cant say I have personably noticed any advantages, unlike CLAP)

[pdxindy]

The browser was huge and confusing and I never cottoned on to it. I really disliked that it kept offering VST3s when there were perfectly good VST2 versions installed. The horse may be dead, but I'm going to beat it until there's nothing left.

You can make it simple and only show the plugins and devices you want.

[dellboy]

It's the users choice to hide most of the stuff if one wants.

I want the browser to be in its fully closed compact state when I select a new project,but it always opens up in its entirety, and requires lots of scrolling and clicking. I can make it the way I want by clicking on the "browser file area" at the top of the browser window and selecting the folder to the far right, but there seems no way to make that the default. It always reverts back to the fully open state when the DAW boots up.

[pdxindy]

It's the users choice to hide most of the stuff if one wants.

I want the browser to be in its fully closed compact state when I select a new project,but it always opens up in its entirety, and requires lots of scrolling and clicking. I can make it the way I want by clicking on the "browser file area" at the top of the browser window and selecting the folder to the far right, but there seems no way to make that the default. It always reverts back to the fully open state when the DAW boots up.

Yes, it would be useful if there was a save configuration as default option for the side browser

Make a new project, configure the browser how you want. Save that as a template. In the Dashboard under Settings -> Behavior select "Use a template for new Projects". Select the saved template. Now the browser should be how you want when you open a new project.