omnisphere instrument only playing midi channel 1

#Omnisphere instrument only playing midi channel 1 how to#

Kontakt, and with multiple mono-timbral plug-ins across multiple tracks/channels. Event Input 1.Ĭubase fully supports Scaler’s Multi-Voice output mode with both a single multi-timbral plug-in e.g. Kontakt, and Channel Output to correspond with the desired multi-timbral part (referred to by Studio One as Event Input) e.g. Then set each instrument track’s Instrument Output to your multi-timbral plug-in e.g. To use Scaler’s Multi-Voice output mode with multi-timbral plug-ins e.g NI Kontakt, you will need to create an instrument channel for each multi-timbral part, with each instrument channel’s MIDI input set to Scaler 2, and the appropriate MIDI channel. Be sure to use the VST2 or VST3 version of Scaler, as the AU plug-in format does not support multi-channel MIDI output. Just set each instrument’s MIDI input to Scaler and select the desired MIDI channel.

Studio One supports multi-channel MIDI routing from Scaler (with Multi-Voice Output mode activated) to multiple instrument tracks across multiple MIDI channels. This process is demonstrated in the following video by plug-in Boutique (not using Scaler):įor other alternatives and workarounds, see the workarounds section of this document below. Blue Cat's PatchWork - Fully Configurable Plug-Ins Chainer and Multi FX / Standalone Host or Plug-In One potential workaround is to use Blue Cat’s PatchWork, a paid plug-in which can itself host plug-ins with more intricate internal routing options, including multi-channel MIDI routing. Scaler’s Multi-Voice Output is not natively supported by Ableton Live, as per the following Ableton support article For more information, see the workarounds section of this document below. Routing Scaler’s MIDI output to multiple mono-timbral plug-ins across multiple MIDI channels is not supported due to the aforementioned AU plug-in format limitation. This being the case, the only way to use Scaler’s Multi-Voice Output mode in Logic is to use the ScalerControl MIDI effect as a plug-in in front of a single multi-timbral plug-in such as Native Instruments’ Kontakt, or Spectrasonics’ Omnisphere. The AU plug-in format which Logic uses exclusively does not support multi-channel MIDI output. Scaler 2.7 Multi-Voice Output Host Reference Document: ( Dropbox - Scaler Multi-Voice Output Host Reference Document.pdf - Simplify your life)

#Omnisphere instrument only playing midi channel 1 how to#

This is a picture of how many midi inputs I have routing to both VSTs in GP as well as back to midi outputs on physical keyboards for a rackspace I just completed last night.And attached is a support document with an overview of how to setup multi out on various DAWs with workarounds offered by some of our users. I’m attaching a picture that shows you what I mean.

Anything from the Kronos that I play live on the keyboard will ONLY come into GP on that one channel. The Kronos only ‘recognizes’ a single channel as the ‘live’ keyboard channel in combi mode, so I don’t really have a choice. I regularly do the same with just channel 1 from my Korg Kronos. I then simply ‘split’ and/or ‘layer’ by using multiple midi inputs in GP with selected key range and/or channel translations between the Fantom X and the various VSTs I have loaded into GP. I have a Roland Fantom X as my upper keyboard that at many times I simply use as a controller with 1 channel across the entire range. Remember that you can remap channel 1 to any other channel on an input in GP. Instead of this, it would be very easy to to simply use key ranges on multiple midi inputs on channel 1 only to distribute to your plugins accordingly. I’m trying to figure out why you need to manage different channels coming in from your master controller at all.