Selecting some midi inputs but not all?

Official support for: bitwig.com
Post Reply New Topic
RELATED
PRODUCTS

Post

I am used to working in an environment where I can choose exactly which midi controllers go to any given track.
As far as I can see, in Bitwig it seems we must choose between ONE midi input or ALL midi inputs.
Is this true, or am I missing something?

Post

LarsDaniel wrote: Thu Feb 02, 2023 8:29 am I am used to working in an environment where I can choose exactly which midi controllers go to any given track.
As far as I can see, in Bitwig it seems we must choose between ONE midi input or ALL midi inputs.
Is this true, or am I missing something?
Yes, you cannot select 2 midi controllers for a track... it is 1 or all. You can work around it with 2 tracks.

Post

LarsDaniel wrote: Thu Feb 02, 2023 8:29 am I am used to working in an environment where I can choose exactly which midi controllers go to any given track.
As far as I can see, in Bitwig it seems we must choose between ONE midi input or ALL midi inputs.
Is this true, or am I missing something?
Yes you are missing something. You are right as Input ONE or ALL.

But if you choose ALL, just put a "Channel Filter" Device as first device in your chain. There you can chose none to 16 channels, that can be listened to.
01_temp.jpg
You do not have the required permissions to view the files attached to this post.

Post

pdxindy wrote: Thu Feb 02, 2023 3:16 pm
LarsDaniel wrote: Thu Feb 02, 2023 8:29 am I am used to working in an environment where I can choose exactly which midi controllers go to any given track.
As far as I can see, in Bitwig it seems we must choose between ONE midi input or ALL midi inputs.
Is this true, or am I missing something?
Yes, you cannot select 2 midi controllers for a track... it is 1 or all. You can work around it with 2 tracks.
Thanks, but not a workaround in my case.
The thing is, in my performance-setup I have three controllers: Launchpad Pro Mk3, normal midi keyboard, Linnstrument.
My ideal setup is that every midi track is receiving both Launchpad and keys, so both can be used at any time for convenience. The Linnstrument on the other hand only goes to one specific track so I can play that at any time (no matter what track is active.)
(This was so simple in AUM on iPad. I think a midi input/output matrix should be a part of any DAW.)

But it seems that there is a workaround: To put a channel filter on every midi track and filter out the eight Linnstrument channels.

Post

OdoSendaidokai wrote: Thu Feb 02, 2023 3:23 pm
LarsDaniel wrote: Thu Feb 02, 2023 8:29 am I am used to working in an environment where I can choose exactly which midi controllers go to any given track.
As far as I can see, in Bitwig it seems we must choose between ONE midi input or ALL midi inputs.
Is this true, or am I missing something?
Yes you are missing something. You are right as Input ONE or ALL.

But if you choose ALL, just put a "Channel Filter" Device as first device in your chain. There you can chose none to 16 channels, that can be listened to.

01_temp.jpg
Thanks. Yes, channel filters on my midi tracks will be the solution.

Post

LarsDaniel wrote: Fri Feb 03, 2023 12:57 pm
Thanks, but not a workaround in my case.
The thing is, in my performance-setup I have three controllers: Launchpad Pro Mk3, normal midi keyboard, Linnstrument.
My ideal setup is that every midi track is receiving both Launchpad and keys, so both can be used at any time for convenience. The Linnstrument on the other hand only goes to one specific track so I can play that at any time (no matter what track is active.)
(This was so simple in AUM on iPad. I think a midi input/output matrix should be a part of any DAW.)

But it seems that there is a workaround: To put a channel filter on every midi track and filter out the eight Linnstrument channels.
Yeah, Channel Filter will work...

And for anyone who is trying to have 2 specific controllers on a track and Channel Filter wont work for them, one could also have Controller #1 as input to some tracks. Add an extra track which has Controller #2 as input and put Note Receivers on the Controller #1 tracks so they also receive from Controller #2

Post

I do this:
Setup multiple instrument tracks with their inputs set to the controllers you want to receive from.
set the inputs to always be monitoring (the little speaker should be yellow)
Create another track that will be the receiver for these tracks.
Put note receivers into a Note FX Layer.
Set those note receivers to receive from the instrument racks.
Then you can select that track as your midi input to any track you want to play on.
snap-2023-02-09_201720.png
Then when you want to receive midi from that combo...
snap-2023-02-09_201818.png
Save that as a template and you'll be set. If you need to add this to old projects you can always keep the setup open in a deactivated project and copy and paste the tracks into your active project.


I tend to put all my midi tracks in a group and hide it to the side of my projects. Makes it easy to find.

This is also my goto for midi routing. If i'm using a stack of midi controllers I configure them all in one place, so if I need to swap one out for another its all handled at that single point rather than all the channels that need to receive the input.

I hope that makes sense. With note & midi channel filters its possible to do serious midi magic in Bitwig. This type of flexibility just isn't available in a lot of other systems I've used. It took me a bit of time to see this but Bitwig did a great job with this implementation.
You do not have the required permissions to view the files attached to this post.
----------------------------------------------------------------------
/CTRL → http://slashctrl.io
Music & mixes → http://soundcloud.com/kirkwoodwest

Post

Thanks! Some interesing ideas.👍🏻

Post

And if enough people demand that note receiver not only receive from other tracks, but also from Midi inputs directly, then we could even add Midi which isn‘t prepared with a script…

Post Reply

Return to “Bitwig”