Bitwig

incendy · Post by **incendy** » Tue May 09, 2017 4:33 pm

Just fix the multiple midi channel issue interfacing with VST's and I will be pretty happy. And once the Midi Channels are working correctly would also love a Midi Transformer feature similar to Logic, unless it already exists, then please tell me how to use it : ).

macmuse · Post by **macmuse** » Thu May 11, 2017 12:57 pm

M.L.M. wrote:My Top Feature is Browser Midi Playback Preview with activated Synth, like in Studio One

+1

xonetacular · Post by **xonetacular** » Fri May 12, 2017 6:51 pm

I want little VU meters on the track audio input menu like ableton has so you can see which inputs are active when selecting from a big list of them.

Fleer · Post by **Fleer** » Sat May 13, 2017 4:02 am

As even this month's CM review points out: AU compatibility is essential.

Cyoon · Post by **Cyoon** » Sat May 13, 2017 4:11 am

whats the point about au compatibility? All major plugins are available as vst as well and since BWS it is a crossplatform software it makes more sense to support something crossplatform.

pdxindy · Post by **pdxindy** » Sat May 13, 2017 4:16 am

Fleer wrote:As even this month's CM review points out: AU compatibility is essential.

Why?

Rappo Clappo · Post by **Rappo Clappo** » Sat May 13, 2017 7:05 am

Oh, I thought reason was essential.

Cyoon · Post by **Cyoon** » Sat May 13, 2017 7:23 am

Rappo Clappo wrote:Oh, I thought reason was essential.

you mean rewire reason into bitwig? What can you do in reason, what you cannot do in bitwig?

Rappo Clappo · Post by **Rappo Clappo** » Sat May 13, 2017 8:35 am

@.maki

Dunno, I don't have Reason. However, now you have mentioned it; I am interested in Essentials with VST support, just to learn more about routing. Bitwig is kind of abstract with the implemented nested device chain. I find it difficult to get a grasp on it.

Fleer · Post by **Fleer** » Sun May 14, 2017 2:43 am

pdxindy wrote:
Fleer wrote:As even this month's CM review points out: AU compatibility is essential.
Why?

Ease of use. Some plugins are only AU.
And I use Apple MainStage.

pdxindy · Post by **pdxindy** » Sun May 14, 2017 4:08 am

Fleer wrote:
pdxindy wrote:
Fleer wrote:As even this month's CM review points out: AU compatibility is essential.
Why?
Ease of use. Some plugins are only AU.

Sure you want that... but it does not seem essential. There are plenty of VST plugins to use. A number of DAW's do not support all plugin formats

SLiC · Post by **SLiC** » Sun May 14, 2017 10:24 am

pdxindy wrote:
Fleer wrote:As even this month's CM review points out: AU compatibility is essential.
Why?

Yeh, definitely not essential....maybe useful to a very small number of users who use an AU plug in that doesn't have a VST, but that is a very small list....

Now comping, that's essential

Fleer · Post by **Fleer** » Mon May 15, 2017 2:38 am

Still, lack of AU compatibility is the only criticism highlighted by this month's CM magazine review of Bitwig 2.0, apart from the lack of new instruments. And CM does reach a lot of potential Bitwig customers. No mention of comping, though.
Hell, just imagine being without Sinevibes (http://www.sinevib.es)

Cyoon · Post by **Cyoon** » Mon May 15, 2017 9:15 am

If that is the only thing CM is able to come up with, it is pretty great, since anybody involved in working with plugins simply knows it is not relevant to have au support anymore.

So they do not have something else to moan about or simply do not want to harm Bitwig and just enjoy 2.0 like everybody else, both would be cool basically.

Fleer · Post by **Fleer** » Tue May 16, 2017 1:36 am

Would love AU compatibility so that I can do everything with Bitwig and MainStage.

Bitwig

KVR Audio

Your TOP 5 feature requests for Bitwig