What drives you crazy in Bitwig?

[pdxindy]

Not being able to hide plugins from the browser (for instance when you have both the VST2 and the VST3 version of a plugin installed).

Make a collection of the plugins you want visible... then select the collection and save that as the default display. Problem solved

Sorry, you are confusing "workaround" with "solution".

You said you wanted to be able to select which plugins show when you open the popup browser. I showed you how. Set it up once, and then every time the popup opens, you will see only the plugins you selected. Exactly what you said you wanted.

But you're right, I was confused. I thought you wanted a solution when you obviously don't.

[starflakeprj]

To me it isn't a solution, since I need to "show all" every time I want to add more plugins to the collection. To me it is a solution first when it works as I would like.

[MegaPixel]

Ok, so let's for say you have the example1.vst3, and example1.dll (VST2) installed on you computer. In Bitwig Example.vst3 doesn't work well, so you need to use Example.dll instead. But since Example.vst3 works well in Studio One, you rather use VST3 there. In Bitwig you both the VST2 and the VST3 file will show, but in Studio One you can hide Example.dll so you will only have one plugin with the name Example showing.

How do you solve this?

In bit wig you can either set options to pref vst3 over vst2 and it will hide them or show everything and make folders and add what you want to them for quick access & categorization.

However when I'm in FLStudio there is a scan option for plugins, you can tick to enable and disable the ones you want. So if I know the VST3 works well in FLStudio I will untick the VST2 and so on.

The alternative is, you install all your vst files in custom folders then you duplicate that folder and call it something else and delete the vst dll files from that one and tell the other DAW to use that folder instead of the original installed one.

[starflakeprj]

Ok, so let's for say you have the example1.vst3, and example1.dll (VST2) installed on you computer. In Bitwig Example.vst3 doesn't work well, so you need to use Example.dll instead. But since Example.vst3 works well in Studio One, you rather use VST3 there. In Bitwig you both the VST2 and the VST3 file will show, but in Studio One you can hide Example.dll so you will only have one plugin with the name Example showing.

How do you solve this?

In bit wig you can either set options to pref vst3 over vst2 and it will hide them or show everything and make folders and add what you want to them for quick access & categorization.

However when I'm in FLStudio there is a scan option for plugins, you can tick to enable and disable the ones you want. So if I know the VST3 works well in FLStudio I will untick the VST2 and so on.

The alternative is, you install all your vst files in custom folders then you duplicate that folder and call it something else and delete the vst dll files from that one and tell the other DAW to use that folder instead of the original installed one.

Yes, but this is global and cannot be done individually per plugin. I have a total of 1400 plugins installed (VST2 and VST3). Lots of duplicates, but I guess around 800 unique ones. In Studio One I can easily hide the plugin (VST2 or VST3) that I want to be hidden. Everything else is to me a workaround. I'm very picky sometimes, especially when I'm comparing to something that works exactly as I would like it to.

[MegaPixel]

Yes, but this is global and cannot be done individually per plugin. I have a total of 1400 plugins installed (VST2 and VST3). Lots of duplicates, but I guess around 800 unique ones. In Studio One I can easily hide the plugin (VST2 or VST3) that I want to be hidden. Everything else is to me a workaround. I'm very picky sometimes, especially when I'm comparing to something that works exactly as I would like it to.

Dual booting system...
1 DAW on each OS you can boot up into, which install files on different drives or locations... Or multiple computers with a KVM.

Other than that, its all just workarounds or you got to make do with what each of your DAWs can do.

[starflakeprj]

Yes, but this is global and cannot be done individually per plugin. I have a total of 1400 plugins installed (VST2 and VST3). Lots of duplicates, but I guess around 800 unique ones. In Studio One I can easily hide the plugin (VST2 or VST3) that I want to be hidden. Everything else is to me a workaround. I'm very picky sometimes, especially when I'm comparing to something that works exactly as I would like it to.

Dual booting system...
1 DAW on each OS you can boot up into, which install files on different drives or locations... Or multiple computers with a KVM.

Other than that, its all just workarounds or you got to make do with what each of your DAWs can do.

Well, the question was what drives me crazy in Bitwig, right? This drives me crazy, and something I have requested for years.

[MegaPixel]

Well, the question was what drives me crazy in Bitwig, right? This drives me crazy, and something I have requested for years.

Same for me with the browser on the right, I select a sample or midi clip and the thing moves or scrolls to a different location as it can't handle how many there are (same issue with scanning turned off in settings).

And it's piano roll editor, which does the job, but far from capable of doing what many other DAWs can do. I even made a micro website for them to demo how it could be made better lol... Maybe in version 12.11.4... I've been asking them for a better piano roll for years.

But in BitWig when I'm searching for something I either type it in and use the filters or use the folders that I created. And FLStudio I just untick the ones I don't want to see on the plugin scan menu.

[pdxindy]

Well, the question was what drives me crazy in Bitwig, right? This drives me crazy, and something I have requested for years.

My guess is Bitwig is not planning to implement what you want any time soon as they have already implemented their solution. Unfortunately for you, you are unhappy with their approach to plugin organization.

[starflakeprj]

Well, the question was what drives me crazy in Bitwig, right? This drives me crazy, and something I have requested for years.

My guess is Bitwig is not planning to implement what you want any time soon as they have already implemented their solution. Unfortunately for you, you are unhappy with their approach to plugin organization.

But on the other hand, it's pretty much the only thing I'm unhappy with.

[starflakeprj]

Well, the question was what drives me crazy in Bitwig, right? This drives me crazy, and something I have requested for years.

Same for me with the browser on the right, I select a sample or midi clip and the thing moves or scrolls to a different location as it can't handle how many there are (same issue with scanning turned off in settings).

And it's piano roll editor, which does the job, but far from capable of doing what many other DAWs can do. I even made a micro website for them to demo how it could be made better lol... Maybe in version 12.11.4... I've been asking them for a better piano roll for years.

But in BitWig when I'm searching for something I either type it in and use the filters or use the folders that I created. And FLStudio I just untick the ones I don't want to see on the plugin scan menu.

Every DAW has it's pros and cons I guess. Most you can live with, as long as they are not ruining your inspiration or workflow. Workflow wise, Studio One is no.1 to me, but it's also a very streamlined DAW, old-school if you will. It's not the DAW I use if I want to be creative outside the box, or experimental. For that Bitwig is the no.1. And if I just want to have fun, being partly creative, partly experimental, but also partly streamlined, I'll use Reason.

I also own FL Studio, but we are not very good friends, Reaper, but Reaper is my most boring DAW (except from Maschine of course), Waveform, but it's way to immature and Renoise, which makes me nostalgic, but I still haven't managed to make anything in it.

[pdxindy]

Well, the question was what drives me crazy in Bitwig, right? This drives me crazy, and something I have requested for years.

My guess is Bitwig is not planning to implement what you want any time soon as they have already implemented their solution. Unfortunately for you, you are unhappy with their approach to plugin organization.

But on the other hand, it's pretty much the only thing I'm unhappy with.

The one thing that drives me crazy is recording a clip of say 4 bars and I stop it at 4.0.1 and it quantizes to 5.

[starflakeprj]

Well, the question was what drives me crazy in Bitwig, right? This drives me crazy, and something I have requested for years.

My guess is Bitwig is not planning to implement what you want any time soon as they have already implemented their solution. Unfortunately for you, you are unhappy with their approach to plugin organization.

But on the other hand, it's pretty much the only thing I'm unhappy with.

The one thing that drives me crazy is recording a clip of say 4 bars and I stop it at 4.0.1 and it quantizes to 5.

I never use Bitwig (or any other DAW) for recording, so this is nothing I have encountered. But I can imagine it being quite annoying for some people.

[MegaPixel]

Every DAW has it's pros and cons I guess. Most you can live with, as long as they are not ruining your inspiration or workflow. Workflow wise, Studio One is no.1 to me, but it's also a very streamlined DAW, old-school if you will. It's not the DAW I use if I want to be creative outside the box, or experimental. For that Bitwig is the no.1. And if I just want to have fun, being partly creative, partly experimental, but also partly streamlined, I'll use Reason.

I also own FL Studio, but we are not very good friends, Reaper, but Reaper is my most boring DAW (except from Maschine of course), Waveform, but it's way to immature and Renoise, which makes me nostalgic, but I still haven't managed to make anything in it.

For me it would be:

Bitwig - quick, modular, get things down fast, has it's issues but nothing that's making me turn away from it (mind you the piano roll comes close to doing that)

FLStudio - I started of with it, got into it quite a lot but when you do you find so many issues. And still using patterns drop down, cringe... Some things are YES and some things are oh WTF. It's marmite.... But that piano roll, you gota love it.

Studio One - I gave the free edition or was a trial a run, and I couldn't quite get into it. Mind you I didn't give it much of a chance. But I did like the piano roll in it. Really missed bitwigs modularity though. I will be giving it another go when I got more time on my hands to dig into it.

Cubase - I really didn't like that... Chord suggestion was nice though but never really used it.

Ableton - I didn't like it, just went against my grain... 10% ooo nice, 90% no...

Reason, Reaper, Renoise & Maschine - Never tried.

But speaking of Renoise, I used to do a lot with Octamed back at the dawn of time with it, very familiar with the workflow, but go back to it?

[lokanchung]

They broke shift to disable snap with automation handles.... I wrote them about this along with a suggestion about using ctrl to lock axis. Seems like every major update they break a few things. I wonder how this thing happens....

[antic604]

No vertical zoom in the midi editor?

There is vertical zoom in the midi editor

You got the crazy inverted zoom and scroll feature with middle mouse down and drag feature.... And the invisible drag area to the left of the virtual keyboard which up and down goes up and down and left and right scales.

Or use Ctrl+Alt+MW like a normal person