Bitwig

Echoes in the Attic · Fri Mar 28, 2014 11:14 pm

Ok I know you guys have focused a lot on your in-built devices but please keep your attention on VST workflow as well. Here's a list of issues where VST functionality should be improved:

-Turning of a plug-in does not disable the CPU. That really sours the bounce in place which is a great way to alleviate CPU use while keeping the source settings on the track.

-There appears to be no key command to hide/unhide plug-in windows. This is probably one of my most used key commands in other DAWs. Too much clicking to temporarily hide plug-ins to see the arrangement or clips and re-open them.

-Bitwig arrangement tool icons stay visible over the plug-in window. So depending on what's behind the different areas of plug-in window, the tool icons are actually changing as you move around the interface. It might be cross-hairs, maybe pencil etc. It's random though. Sometimes it's a pointer like it should be and sometimes the tools are showing for what's underneath.

-Mapping plug-in parameters has improved thanks to the "joker" parameter at the top. But, this doesnt always work (ex: OBXD does not show anything in the joker slot even though everything is automatable). And it can still be challenging if more than one parameter is linked, such as an XY pad or a knob that is also a menu (like in Zebra modulations). You only get one parameter showing in the top spot and the other(s) can still be very difficult to find because you may not know the name. Here is my suggestion: Have the ability to jump to the joker parameter in the list. Perhaps a right-click and "go to parameter", similar to "open containing folder" type command. At least there is a good chance of the parameter you're looking for being next to the one in the "joker" spot. But still a much faster workflow for mapping control pages and macros would be to just click to macro/control page rainbow slot and then tweak the plug-in parameter directly on the GUI. Ditch the dragging of control paramters. Just click and tweak, like mod sources and built-in parameters. Please.

-You can't tell which parameters have been mapped to the controller pages from looking at the parameter list. This gets confusing when trying to map out all parameters. Could you some visual indication that it has been assigned? Maybe even the colour dot that it's assigned to?

-Can't drag samples from clips/regions to VST Samplers like Kontakt, which you can do in other DAWs.

-Can’t rename parameters in control pages. Really need this for long parameter names. Especially since you only see the start of names. If you're going to cut off the names, cut the middle so you can see the end which is usually what distinguishes long names.

-Can’t access VSTs from the "+" menus.

-When loading bitwig presets that contain a plug-in, it would much better if they would load the way they were saved in the device. For example if the macro/preset window was open or if the plug-in window was open, these settings should be reloaded like that. I save all my VSTs as preset templates and really wish they'd open with the GUI open like plug-ins normally do.

- No fxp/fxb loading (sometimes plug-ins depend on host's ability to load banks)

pdxindy · Post by **pdxindy** » Fri Mar 28, 2014 11:19 pm

I want to just click on the parameter in the gui. Lots of vst synths have cryptic names for stuff in the automation lists so the search function is hit or miss. They are not all going to change so Bitwig has to.

otherwise +1 to all points

urbangipsy · Post by **urbangipsy** » Fri Mar 28, 2014 11:25 pm

+ 1 for everything regarding VSTs..

Really feeling the software and it hurts me to see all the bugs inside, basic features missing. But like somebody already mentioned, it just makes you do music, so much inspiration inside. Biggest respect to come up with something like this boyz!

Orga · Post by **Orga** » Fri Mar 28, 2014 11:25 pm

+1 - especially plug-ins stealing commands and being able to access the VSTs from the '+' menu.

pdxindy, you can just click on the parameter you wish to automate and then open the automation panel and the selected parameter will be available.

pdxindy · Post by **pdxindy** » Fri Mar 28, 2014 11:29 pm

Orga wrote: pdxindy, you can just click on the parameter you wish to automate and then open the automation panel and the selected parameter will be available.

try assigning it to a macro... that is what I am talking about. It's a nightmare

Costa Rica · Post by **Costa Rica** » Fri Mar 28, 2014 11:32 pm

Who cares about VST? I suggest to concentrate on modular stuff. We haven't AU support either *giggles*

Echoes in the Attic · Post by **Echoes in the Attic** » Sat Mar 29, 2014 2:45 pm

The trick to pull up automation to find the plug-in parameter name doesn't even work all the time. Sometimes when I tweak a parameter it doesn't show there. Even when it does that's still a brutal workflow to finding the parameter as you have to then go and change windows and type it into the search field. Not well thought out.

beliefsystemrecords · Post by **beliefsystemrecords** » Sat Mar 29, 2014 3:00 pm

just tried ot find a cutoff on the arturia cs80 and gave up because the parameter names are so cryptic. tehre is no lp/hp/cutoff/filter or anythign i could associate with the function id liek to acess

nexttrack30 · Post by **nexttrack30** » Sat Mar 29, 2014 4:15 pm

totally agree.
especially parameter macro and device panel mapping.

i don't know it was to make device panel mapping happen but
search function is huuuuugh miss.

straight against work flow which bitwig emphasizes.
i really hope they can change it like automation way.
or ableton way is not bad either.

i'm afraid it will take looooooooooong time

i'll just pray it'd be easy

prime_id · Post by **prime_id** » Sat Mar 29, 2014 4:19 pm

+1
Very good points!

Blue-eyed Blonde Ape · Sat Mar 29, 2014 4:24 pm

Echoes in the Attic wrote: -Plug-in windows stay open when switching tracks. It should automatically close plug-in windows when switching track. Or at least have a setting.

-Plug-in windows steal all commands from Bitwig (transport, key commands etc.). So you actually have to click out to even start/stop playback with the spacebar. That's bonkers.

I like that it stays, would totally hate it, if it would flip around like in DP, always like to keep plugins GUI open until I close it myself.

Agree to last thing and it totally defeats QWERTY keyboard input purpose, yesterday tried to tweak Diva with QWERTY activated and it's totally useless because you have to click somewhere away from plugin's GUI so that QWERTY input would work, just f**** it! hahha what a heck is that, what's wrong with beta testers, it's like worst ever,

unless they said it but developers didn't listen to them, otherwise they are the worst ever beta testers in human kind existence, probably the only thing they did was staring numbed at buttons, that's it, come on how worse can one be of a beta tester than that, a beta tester who doesn't test anything ? hello we have here a plenty like that, obviously, my god.

Edit:
Would like to see ability to sort plugins by vendor, a must for me and so for many others, I believe.
Also browser search functionality doesn't work for shelled VSTs like Waves.

hoshino · Post by **hoshino** » Sat Mar 29, 2014 4:36 pm

Yes, as posted elsewhere, this is a major dealbreaker for me (in fact, I am not using Bitwig, but waiting for a fix) --

VST GUI is useless, can't change parameters at the same time as playing a MIDI note (at least on computer keyboard, which I do a lot, especially while on the move), which renders this whole software pretty useless for me, I work a lot with a certain plug ins and I like to tweak stuff on GUI real time. I mean, how the heck else do you match certain notes, progressions, chords with the sound and effects? A dedicated MIDI device? I don't want it, I keep it simple and portable where I can. Having to click on the main interface or close Plugins Gui just so I can hear sound is ridiculous to say the least

twilightborn · Post by **twilightborn** » Sat Mar 29, 2014 4:49 pm

+1 for the search not working with Waves Plugs.
Also sorting VST by kind/vendor would be a great feature

ElliottStanleyMusic · Post by **ElliottStanleyMusic** » Sat Mar 29, 2014 4:57 pm

I agree. It's also very unstable with third party plugins. I frequently get runtime errors and audio engine crashes with vsts.

Blue-eyed Blonde Ape · Sat Mar 29, 2014 5:15 pm

hoshino wrote: A dedicated MIDI device? I don't want it, I keep it simple and portable where I can. Having to click on the main interface or close Plugins Gui just so I can hear sound is ridiculous to say the least

Agreed, even if a midi keyboard is next to me I still keep it unplugged and use QWERTY instead, lol
Quick, simple, gets the job done, especially when just checking sounds and tweaking.

Bitwig

KVR Audio

List of VST issues in need of attention