Bitwig

mumpcake · Post by **mumpcake** » Sat Dec 08, 2018 4:29 pm

There are a few things in BWS that are common things that are implemented in a way that doesn't make sense to me and often are not in the manual.

1. Tap Tempo - I have to press CTRL key while clicking PLAY on the mouse. How does that make sense?

2. Remove item from collection. You have to right-click on the collection, Select "Set as Target Collection", and then un-star the plugin you want to remove. Wouldn't it make more sense to go to the collection, and be able to remove it with the delete key? Or at least have an option come up in the right-click context menu to remove the device from the collection?

brownerthanu · Post by **brownerthanu** » Sat Dec 08, 2018 6:23 pm

+1 for #2.

ilmai · Post by **ilmai** » Sat Dec 08, 2018 8:10 pm

1. Easier way to do tap tempo is to hold Ctrl and Alt, and tap Space.
2. +1

mumpcake · Post by **mumpcake** » Sat Dec 08, 2018 8:17 pm

ilmai wrote: ↑Sat Dec 08, 2018 8:10 pm 1. Easier way to do tap tempo is to hold Ctrl and Alt, and tap Space.

I'm not sure that is easier, but it's good to know as an alternative.

Yokai · Post by **Yokai** » Sun Dec 09, 2018 1:29 am

No simple "right-click on a MIDI clip > Export to MIDI" to save a single MIDI clip. Instead, you have to create an entirely new project and drag that clip over to the new project (so that the new project has only ONE MIDI clip in it) if you want to create a single, short *.mid file of just one 4-bar MIDI clip.
o.O

craigtumps · Post by **craigtumps** » Mon Dec 10, 2018 12:15 pm

Number 2 annoys me too.

JHernandez · Post by **JHernandez** » Mon Dec 10, 2018 3:32 pm

Seriously, the right hand browser. Why can't I keep the folders collapsed by default?

sth · Post by **sth** » Mon Dec 10, 2018 4:41 pm

Yokai wrote: ↑Sun Dec 09, 2018 1:29 am No simple "right-click on a MIDI clip > Export to MIDI" to save a single MIDI clip. Instead, you have to create an entirely new project and drag that clip over to the new project (so that the new project has only ONE MIDI clip in it) if you want to create a single, short *.mid file of just one 4-bar MIDI clip.
o.O

Can't you right click and Save Clip to Library, and not include the devices?

aMUSEd · Post by **aMUSEd** » Mon Dec 10, 2018 4:42 pm

craigtumps wrote: ↑Mon Dec 10, 2018 12:15 pm Number 2 annoys me too.

Yup it's daft, took me ages to figure out

Trancit · Post by **Trancit** » Mon Dec 10, 2018 4:52 pm

JHernandez wrote: ↑Mon Dec 10, 2018 3:32 pm Seriously, the right hand browser. Why can't I keep the folders collapsed by default?

Yes, there is no need for having the whole factory part uncollapsed everytime you open the samples tab... This bugs me too...

aMUSEd · Post by **aMUSEd** » Mon Dec 10, 2018 5:36 pm

What gets me is how easy it is to create device control panels, and yet how ludicrous it is that you can't import and export them - instead they get saved into a hidden folder and given unreadable names.

Yokai · Post by **Yokai** » Tue Dec 11, 2018 5:42 am

sth wrote: ↑Mon Dec 10, 2018 4:41 pm
Yokai wrote: ↑Sun Dec 09, 2018 1:29 am No simple "right-click on a MIDI clip > Export to MIDI" to save a single MIDI clip. Instead, you have to create an entirely new project and drag that clip over to the new project (so that the new project has only ONE MIDI clip in it) if you want to create a single, short *.mid file of just one 4-bar MIDI clip.
o.O
Can't you right click and Save Clip to Library, and not include the devices?

Then it becomes a .bwclip file that only Bitwig knows what to do with. Not a .mid file that is usable by other plugs and DAWs and software.

mholloway · Post by **mholloway** » Tue Dec 11, 2018 6:26 am

The collections system has been a complete joke since the program first launched.

It's like somebody sat down and said, "let's try to create an organizational system with the highest number of Required Clicks ever for completing a simple task!"

If a collection is selected, and you want to add something to it, you have to UN-select it first, because if it's selected, the thing you want to ADD to it isn't visible.... So you Unselect a Thing so that you can get to where you can add to the Same Thing you just unselected. GENIUS

Meanwhile in ableton I can just create a folder in my user library, call it whatever I want, and drag and drop anything and everything into it at any time, voila.

shadiradio · Post by **shadiradio** » Tue Dec 11, 2018 6:42 am

You can add & save custom keyboard sets through the settings UI, but you can't remove them without doing it through the file system. Bizarro. I thought it was only that way when it debuted because maybe that feature came in hot at the end before a patch, but it's been that way for a couple years now. It's so weird since they are just files, there could easily be a button next to the drop down to delete them from the UI, so it must be a conscious decision to not allow you to do it? This is so minor, but so strange!

escapednb · Post by **escapednb** » Tue Dec 11, 2018 9:03 am

I totally agree with those two points and i want to add some points which also fall into this category.
1. The timestretching. I know it's pretty much possible to do anything ableton does but i think the timestretch-workflow in bitwig is cumbersome and confusing.
2. Also the Fade/Autofade-feature is buggy as hell and still does many strange things.
3. There are still so many clicks appearing when cutting audio, using certain modulators and or sidechain. Nobody want's those even if you choose a hard curve like ramp etc...

i think many fixes for those problems are blocked by backward-compatibility but i still hope they get rid of them...

edit:
perfect timing

https://www.bitwig.com/en/18/bitwig-studio-2_5.html
some of those things seem to be adressed in 2.5

Bitwig

KVR Audio

Where Bitwig makes simple things hard...