Using Scaler2 within a Bitwig Instrument Track (Kontakt Rack) for multiple MIDI channels

Apologies if this is a repeat of a previous issue - I tried to scan for it using keywords but did not find a match so here goes…

I am using Bitwig and have multiple MIDI tracks feeding into an instrument track which has the following plugins in sequence - Scaler2, Kontakt, Raum

The problem is that Scaler2 will remap all MIDI to channel 1 by default which doesn’t really help if you have a multiple instrument rack using specific MIDI channels per instrument. Bitwig will map the MIDI tracks to whatever I choose and if I don’t have Scaler2 in the plugin chain for the instrument track then each MIDI channel goes through to it’s respective instrument in the Kontakt rack. But if I have Scaler2 in the plugin chain before Kontakt then every incoming MIDI is remapped to channel 1 (by default). Basically there’s no ability for Scaler2 to pass through notes as the original MIDI channel mapping as far as I can see. Is this correct?

It’s a bit of a pain because I like to have Scaler2 in the plugin chain to try out various permutations but that won’t work if I am passing through the chain more than one MIDI channel. It would be helpful if Scaler2 would at least simply pass through the channel notes that it is not set to monitor so that they are not interferred with but it doesn’t - it remaps them. Any chance of changing this or is there a workaround?

Many thanks in advance for constructive/positive suggestions.

If you’re using Bitwig, you could try an Instrument Layer with two layers. One with Scaler on it and another empty layer that will pass the midi through.

Hi Ben,

Thanks for the reply. I’ve tried that out and yes technically that does work in that the midi goes in parallel to all the layers. Problem is, the aim of having Scaler2 in the plugin chain is so that one can experiment and see how things sound. By putting Scaler2 onto a seperate layer the output of Scaler2 is no longer passed through to the Kontakt rack so it’s a bit of a non event really. Perhaps it could go down as a feature request for Scaler2 to pass through any MIDI channel that’s not it’s currently selected one to ‘monitor’.

Thanks anyway.

Tbh, I NEVER have Scaler on the same track as any other instrument. It’s much better to use the routing options to reference the Scaler tracks output, so that it can be modified before it hits the instruments, eg changing the channel with a Channel Map. With Bitwig you’re really spoilt for choice with routing.:+1:t2: