What drives you crazy in Bitwig?

Official support for: bitwig.com
Post Reply New Topic
RELATED
PRODUCTS

Post

No vertical zoom in the midi editor?

Post

excuse me please wrote: Sat Jul 17, 2021 2:31 pm No vertical zoom in the midi editor?
There is vertical zoom in the midi editor

Post

pdxindy wrote: Sat Jul 17, 2021 3:39 pm
excuse me please wrote: Sat Jul 17, 2021 2:31 pm 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.
Web Developer by day, DAW tinkerer by night...

Post

Hehe yes. Completely forgot about the drag area. I was scrolling up and down through 3 octaves for a while 🙃

Post

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).
Mac Mini M4 Pro | 14 Cores (10P/4E) | 48GB RAM | Studio One | Reason | Bitwig Studio | Logic Pro | FL Studio | Cubase Pro | Waveform | Reaper | Renoise | ~1000 VSTs/AUs | ~350 REs

Post

starflakeprj wrote: Sat Jul 17, 2021 7:13 pm 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).
Can you not just physically delete the `.vst` or `.vst3` file that you don't want to appear., or if you're feeling cautious, move it to a safe place.
Bitwig 6.0.8 + Akai MIDIMix + Launchpad X + MF Twister
ExpressiveE Osmose Keyboard + Universal Audio Apollo Twin X
Mac Mini M1 16GB/4TB + macOS 26.5 Tahoe

Post

carlca wrote: Sat Jul 17, 2021 7:17 pm
starflakeprj wrote: Sat Jul 17, 2021 7:13 pm 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).
Can you not just physically delete the `.vst` or `.vst3` file that you don't want to appear., or if you're feeling cautious, move it to a safe place.
This means I need to have different directories where I store different plugins since I use multiple DAWs. So it's not a valid solution.
Mac Mini M4 Pro | 14 Cores (10P/4E) | 48GB RAM | Studio One | Reason | Bitwig Studio | Logic Pro | FL Studio | Cubase Pro | Waveform | Reaper | Renoise | ~1000 VSTs/AUs | ~350 REs

Post

starflakeprj wrote: Sat Jul 17, 2021 7:29 pm
carlca wrote: Sat Jul 17, 2021 7:17 pm
starflakeprj wrote: Sat Jul 17, 2021 7:13 pm 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).
Can you not just physically delete the `.vst` or `.vst3` file that you don't want to appear., or if you're feeling cautious, move it to a safe place.
This means I need to have different directories where I store different plugins since I use multiple DAWs. So it's not a valid solution.
If you turn off pref vst3 only over vst2, or could be hide vst2 when vst3 available, it will show both, I think there are options for 32 and 64 bit also. Then you get options in the instrument browser for 32bit, 64bit etc... I got a load of vst 3 plugins which crash a lot so I mostly stick with vst2 64, but some just say 64bit. I keep all the vst installs on another drive (if the installers give me the option to):
  • vsts/vst/32 (for those that dont tell me if they are v1,2 or 3) (is there a vst1?)
  • vst/vst/64 (for those that dont tell me if they are v1,2 or 3) (is there a vst1?)
  • vst/vst2/32
  • vst/vst2/64
  • vst/vst3/32 (for the few that allow you to choose where to install the vst3 plugin)
  • vst/vst3/64 (for the few that allow you to choose where to install the vst3 plugin)
Web Developer by day, DAW tinkerer by night...

Post

At the moment is the fact that some users can import whole Ableton project while others can't.
It looks like there are issues with missing files especially Audio/Sample clips.

No one seems to have a clue either.
Drive you crazy? Definately :wink:
ABEFLGMOPPRRST :phones:

Post

starflakeprj wrote: Sat Jul 17, 2021 7:29 pm
carlca wrote: Sat Jul 17, 2021 7:17 pm
starflakeprj wrote: Sat Jul 17, 2021 7:13 pm 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).
Can you not just physically delete the `.vst` or `.vst3` file that you don't want to appear., or if you're feeling cautious, move it to a safe place.
This means I need to have different directories where I store different plugins since I use multiple DAWs. So it's not a valid solution.
I use multiple DAWs on macOS. I still have just the single .vst folder and the single .vst3 folder.

Does anyone else have multiple plugin folders for different DAWs?
Bitwig 6.0.8 + Akai MIDIMix + Launchpad X + MF Twister
ExpressiveE Osmose Keyboard + Universal Audio Apollo Twin X
Mac Mini M1 16GB/4TB + macOS 26.5 Tahoe

Post

starflakeprj wrote: Sat Jul 17, 2021 7:13 pm 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

Post

carlca wrote: Sat Jul 17, 2021 8:31 pm
starflakeprj wrote: Sat Jul 17, 2021 7:29 pm
carlca wrote: Sat Jul 17, 2021 7:17 pm
starflakeprj wrote: Sat Jul 17, 2021 7:13 pm 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).
Can you not just physically delete the `.vst` or `.vst3` file that you don't want to appear., or if you're feeling cautious, move it to a safe place.
This means I need to have different directories where I store different plugins since I use multiple DAWs. So it's not a valid solution.
I use multiple DAWs on macOS. I still have just the single .vst folder and the single .vst3 folder.

Does anyone else have multiple plugin folders for different DAWs?
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?
Mac Mini M4 Pro | 14 Cores (10P/4E) | 48GB RAM | Studio One | Reason | Bitwig Studio | Logic Pro | FL Studio | Cubase Pro | Waveform | Reaper | Renoise | ~1000 VSTs/AUs | ~350 REs

Post

pdxindy wrote: Sat Jul 17, 2021 9:00 pm
starflakeprj wrote: Sat Jul 17, 2021 7:13 pm 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".
Mac Mini M4 Pro | 14 Cores (10P/4E) | 48GB RAM | Studio One | Reason | Bitwig Studio | Logic Pro | FL Studio | Cubase Pro | Waveform | Reaper | Renoise | ~1000 VSTs/AUs | ~350 REs

Post

liquidsound wrote: Sat Jul 17, 2021 8:18 pm At the moment is the fact that some users can import whole Ableton project while others can't.
It looks like there are issues with missing files especially Audio/Sample clips.

No one seems to have a clue either.
Drive you crazy? Definately :wink:
I think I solved the problem. :phones:
ABEFLGMOPPRRST :phones:

Post

What drives me crazy is how great of a one-handed workflow it would be with a pen if they would just leave the radial menu open. This forced two-handed crap is no good. And would be such an easy fix. Could be a long press to leave it open. Or just leave it open until a tool has been selected (if using select tool). Click outside to close. Why make us hold and use a second finger...

Post Reply

Return to “Bitwig”