List of VST issues in need of attention

[Regnas]

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!..

VST GUI is useless, can't change parameters at the same time as playing a MIDI note (at least on computer keyboard...

Wow, this is an unacceptable behaviour.

Please someone tell the Bitwig team to not release the 1.0.4 update without fixing this thing.

Unbelievable...

[dolomick]

+1 for all these logical VST issue requests

[julioelgenio]

Noooo, keep the multiple windows of VST, let it be an option, I like having BitWig on one screen and dragging the VSTs onto the second screen.

[marvotron]

VST GUI is useless, can't change parameters at the same time as playing a MIDI note (at least on computer keyboard...

To actually solve this issue to everyone's satisfaction isn't easy when you consider plugins like Reaktor where you often have to do text input in the plugin window. Its something that didn't work properly in Live for quite some time and doesn't work properly in other hosts (e.g. Studio One).

Ideally they'll find out how to implement the same solution as Live whereby the plugin window only gets keyboard inputs when a textfield is focused in the plugin.

Currently Studio One has the opposite issue where all keyboard input goes to the host and you cant type anything into a plugin, which makes Reaktor almost useless in Studio One (for my purposes).

Other hosts have different behaviour which arent 100% consistent.

[hoshino]

Oh I know its not perfect and there will be plug ins that won't want to cooperate, but considering competition, I haven't had any issues in Live with this so far and good or bad, but it has just become a huge part of my so called workflow, so if bitwig wants to win fresh devotees, they simply need to fix this. And I know I am not the only one wanting to stick to qwerty. There's a large crowd relying on software rather than hardware now and am I mistaken in saying that bitwigs dom said that bitwig would be especially suited to ppl who work primarily with software goodies? Qwerty really does get the job done quick while making patches and so forth or working with arps, checking octave ranges on the fly, matching note combinations or structures with the sound or in working with sidechaining comps, gates of filters, working with rhythmic delays, quick note changes and so forth. I'm sure I don't have to explain, especially while one is on the road etc.

[contrast]

but it has just become a huge part of my so called workflow, so if bitwig wants to win fresh devotees, they simply need to fix this.

Read what you wrote again. "If bitwig wants to gain customers, they need to make the program work exactly how I want it to." That's nonsense, of course.

I mean I am not saying don't make your feature request, but it's awfully presumptuous to assume that everything you want is automatically the right way for it to work.

For me at least, it is much more important that text input work in the plugin so I can enter patch names and so on, and I use a controller to enter notes, start/stop, and so on. So I would be disappointed if they broke that. Of course I think it would be best if they could come up with some solution that works for everyone.

[hoshino]

No, that is not what I meant. My point is if they want to gain customers, they need to work on simple features such as this vst gui thing that is mostly a given in absolute majority of daws. Yes, yes you will bring rewire on the table and tell me it is the same thing and simply their choice that we have to adapt to our work and you are correct as well.
Let's not mix up two things- certain pecularities of bitwig vs serious flaws. For example, I find the piano roll a complete fluke so far- the super annoying cross instead of reg pointer, pencil that takes god knows what to delete a note (amiwrong?) And so on so forth which are peculiarities and my opinion only, you might love the piano roll for example so that's good and therefore kinda my own issue, which I am willing to try to get used to. Another example is the vst gui that has to be manually exited, again, pretty darn annoying, but I am totally willing to adapt and as you could see , there were even ppl who liked it!
Do u see what I am saying? Peculiarities, which all daws have vs serious flaws.

[Tronam]

In the past much has been said about the VST SDK's poor documentation. I don't know if this is still true, but isn't it extremely challenging to implement VST host support flawlessly because developers on both sides have been creating custom solutions and workarounds over the years for all sorts of plugin/host/OS issues? It seems like most DAWs just have to fix as they go until plugin support becomes more and more reliable.

[Echoes in the Attic]

Arggh. So much clicking to open and close plug-in windows! Even if you need to temporarily open another program, the plug-in window stays on top of that. Even just a finder window will open underneath the plug-in window of Bitwig!

Also, and this is a BIG ONE, you can't drag samples from anywhere in Bitwig (browser or arrangement!) to VST Samplers like Kontakt, which you can do in other DAWs.

The number of workflow killers is just too much with VSTs I think.

[Echoes in the Attic]

Added a couple more that came up.

Turning off plug-in doesn't disable the CPU.
Plus-in settings get lost and they can't load after you save your project to a new location.

Bitwig, you needed beta testers that used VSTs.

[virtualmark]

+1 to all the OPs points. I just cannot believe that there was even a beta test phase, some things are in such a bad state.

[pdxindy]

Both Kirnu Cream and Numerology VST fail in Bitwig...

[TristanMendoza]

i agree with the automation stuff, i tried automating FM8 but that wasn't impossible and i used to find my self looking for VSTs when i would add them from the inspector but i got over it..id like to see that as a feature but i don't think it'd happen because its one thing to do it with native stuff but its probably something else to do it with 3rd party stuff

[Andrei Marchenko]

+1 for Topic Starter

[LawrenceF]

-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.

FWIW, I can confirm this with Guitar Rig.

Bypassing the GR module in the BWS docker doesn't actually stop the audio stream from playing through the GR plugin, it (apparently) only bypasses that part of the stream in that module for the audio channel. Audio still streams through GR during bypass, you can still see the metering on it's UI. Must be parallel / split streams.

Maybe that's why it's named "Device On" and not "Bypass", because it doesn't actually bypass the plugin processing, but just bypasses the device in the chain so you don't hear the plugin processing. Dunno.

For clarity, at lest in this particular case, I can go to the GR UI itself and just power it off with it's own power button and stop that processing.