Bitwig

TristanMendoza · Post by **TristanMendoza** » Mon Jan 18, 2016 5:55 pm

If you guys wanna follow me on Instagram and Twitter, thats where Ill be posting the updates and pics of course.
Its faster than the forums!
My Insta and Twitter are both @SentrikMusic.

anp27 · Post by **anp27** » Mon Jan 18, 2016 6:12 pm

thetechnobear wrote:flexible midi routing, i think would be almost embarrassing to announce,

This is what I mean when I say 'flexible midi routing':

thetechnobear wrote:given most peoples response would be... what you cant do that already?

My response would be, "No, we currently do not have flexible MIDI routing in Bitwig".

thetechnobear · Post by **thetechnobear** » Mon Jan 18, 2016 8:01 pm

anp27 wrote:
thetechnobear wrote:flexible midi routing, i think would be almost embarrassing to announce,
This is what I mean when I say 'flexible midi routing':
....

thetechnobear wrote:given most peoples response would be... what you cant do that already?
My response would be, "No, we currently do not have flexible MIDI routing in Bitwig".

I know what you mean, and I can do it in I think every other daw e.g. Logic, Cubase, Reason....
yet, in bitwig we have to create 16 controller devices to do it - a hack for a feature found on all other daws...
and one that has been requested to be changed since pretty much day 1 of BWS release 1.0.

Echoes in the Attic wrote: I'd like to see a setting to adjust for synths with max pitch bends of other than +/- 48 notes. I'm finding most tend to be 24, or even 12 max. Kind of makes separate note pitch control useless if it doesn't bend the right amount.

You can do this now with within the controller API via

Code: Select all

setUseExpressiveMidi(boolean useExpressiveMidi, int baseChannel, int pitchBendRange)

so if you had your own controller script, you could use this.

the idea with MPE, is that the host/controller would inform the VST of the pitchbend range to use... but thats not going to help with non-mpe enable vsts.

toby · Post by **toby** » Mon Jan 18, 2016 8:49 pm

I hope they show an update (maybe some 1.5 features or even 2.0)

I do not mind waiting a bit for the update like last time if it has as many great additions as the 1.1 update did

anp27 · Post by **anp27** » Tue Jan 19, 2016 12:23 am

thetechnobear wrote:I know what you mean, and I can do it in I think every other daw e.g. Logic, Cubase, Reason....
yet, in bitwig we have to create 16 controller devices to do it - a hack for a feature found on all other daws...
and one that has been requested to be changed since pretty much day 1 of BWS release 1.0.

Yeah, exactly. It's a hack.

kev2525 · Post by **kev2525** » Tue Jan 19, 2016 9:52 am

TristanMendoza wrote:If you guys wanna follow me on Instagram and Twitter, thats where Ill be posting the updates and pics of course.
Its faster than the forums!
My Insta and Twitter are both @SentrikMusic.

When are you going to NAMM? I want the inside track on Bitwig!

PS - I searched the directory and I noted that Ableton are not there this year.

TristanMendoza · Post by **TristanMendoza** » Wed Jan 20, 2016 12:54 am

kev2525 wrote:
TristanMendoza wrote:If you guys wanna follow me on Instagram and Twitter, thats where Ill be posting the updates and pics of course.
Its faster than the forums!
My Insta and Twitter are both @SentrikMusic.
When are you going to NAMM? I want the inside track on Bitwig!

PS - I searched the directory and I noted that Ableton are not there this year.

I fly out Thursday at 3-4 AM

blouaap · Post by **blouaap** » Wed Jan 20, 2016 2:41 pm

Not always sure why there is still complaints about MIDI routing. There is countless ways to do the routing and they aren't even hacks.
Here is three different ways of routing (Ok one might be the same as other, but you get the idea):

xbitz · Post by **xbitz** » Wed Jan 20, 2016 3:22 pm

AFAIK the problem not the in but the out, u can't route back the out of the multi-instrument to the same track as from the MIDI notes come or if the multi-instrument generates notes to different MIDI channels then it can't be routed to different tracks in BWS

anp27 · Post by **anp27** » Wed Jan 20, 2016 6:29 pm

xbitz wrote:AFAIK the problem not the in but the out, u can't route back the out of the multi-instrument to the same track as from the MIDI notes come or if the multi-instrument generates notes to different MIDI channels then it can't be routed to different tracks in BWS

Exactly what xbitz said.

UncleMarty · Post by **UncleMarty** » Wed Jan 20, 2016 6:51 pm

I'll have what he's having.

blouaap · Post by **blouaap** » Wed Jan 20, 2016 9:38 pm

@xbitz
Give me an example scenario of what you might want. I would like to try to see if I can do it. I have never had any problems with routing midi as of yet. I just want to see what I might be missing.

xbitz · Post by **xbitz** » Wed Jan 20, 2016 10:01 pm

I don't either(this is I've written AFAIK), but for http://www.kvraudio.com/forum/viewtopic ... 9&t=455116 for example

blouaap · Post by **blouaap** » Wed Jan 20, 2016 10:09 pm

xbitz wrote:I don't either(this is I've written AFAIK), but for http://www.kvraudio.com/forum/viewtopic ... 9&t=455116 for example

Ah okay, I see your problem immediately. Like kontakt has multi audio out, there should be something similar but for MIDI out per channel. Jee, I cannot even begin to think how to do that internally, I only know a workaround via OSX IA, but nothing in Bitwig will be able to. Note Receiver should seriously have a channel chooser. And using input in a channel simply does absolutely nothing.

anp27 · Post by **anp27** » Thu Jan 21, 2016 12:48 am

blouaap wrote:Note Receiver should seriously have a channel chooser.

Exactly what I think too.

Bitwig

KVR Audio

NAMM is here, Bitwig announcement predictions were all wrong!