asked Jul 20 '16 at 11:49 by salicional (21)

edited Jul 20 '16 at 11:51

1
1

Please Let Us Have Full Midi Channel Routing Support.

Midi Channel Routing in Bitwig Studio (BS version 1.3.11) is very deficient.

Unless I am missing something, the only way a multitimbral synth such as Omnisphere, and the Sampler Kontakt 5.5+ can be used by in Bitwig loading an instance of (say) Ominisphere in an instrument track - but, because it isn't possible to send out Midi Data to each channel of Omnisphere in BS, multitimbral multi channel function isn't possible.

Why is it, that a sophisticated piece of Software like Bitwig Studio, cannot provide users with this very basic midi channel output routing, that which is available to users of Studio One, Cubase, Logic, and, after a fashion Live ?

When I purchased Bitwig Studio, I had assumed that I could rout midi just as I have been in Cubase and Live.

Please Let Us Have Full Midi Channel Routing Support.

You are missing something: each track can be routed directly to the instrument in another track on a specific channel. You can see it demonstrated in this video: https://www.youtube.com/watch?v=xQ3vXoIoZvg&list=PLupECr895XZKHpuO2biNuJJ9Tnyu-U4aZ

link

answered Jul 23 '16 at 11:19 by Curtailer (41)

Thank you for taking the time to help me with this. Very much appreciated.

I viewed the video you sent but the details were too small on my screen for me to extract any information from it.

Just to be clear though, we are talking about midi routing are we not? Audio routing to separate instrument outputs I am OK with.

link

answered Jul 23 '16 at 12:48 by salicional (21)

edited Jul 23 '16 at 12:50

From what I understand - You would like to be able to route MIDI data to a specific channel within a single instance of Kontakt/Omnisphere or sampler.

Easy... Create an instrument track with an instance of your sampler on it. Setup your MIDI CC's within your sampler (unique MIDI channel for every timbre/expression/instrument within your sampler.

Create as many Instrument tracks as per your setup in the sampler (these will be blank without any plugins).

Switch to the mixer. On each of the blank instrument tracks you need to allocate them to the MIDI channels setup in your sampler. You can do this by clicking on the output (above fader, usually says "master". After clicking on there go to "notes to tracks"->Plug-In's->Select your sampler.

You'll now see an option next to the output selector to change the MIDI channel. Allocate each blank instrument track accordingly and bobs your uncle.

That being said... Expression mapping would provide a more comprehensive approach to this type of workflow (have recently requested it here: https://answers.bitwig.com/questions/7629/fr-workflow)

link

answered Jul 23 '16 at 15:02 by pauriniw (97)

@salicional, yes, we are talking about MIDI routing. Pauriniw described it perfectly. You can route MIDI tracks' output directly to a plugin using the method he/she described. Now, if there only was a way to map MPE MIDI to Omnisphere/Kontakt I'd be happier myself.

link

answered Jul 23 '16 at 17:42 by Curtailer (41)

BOB'S your uncle indeed - how did you know :)

Thanks indeed for your clear and concise instruction. Whilst Bigwig hasn't provided the most intuitive workflow in this regard, it gets the job done and I am thankful for that.

I am so used to being able to set the midi output per track/channel in the track instance in the Arranger in other Daws, Bitwig unhappily chose to hide it away ! Even Live has better midi output function than Bitwig.

Thank you.

link

answered Jul 24 '16 at 13:27 by salicional (21)

Errr, you can set MIDI output in the arranger... in the inspector. The inspector shows channel config at the bottom of the inspector in relation to the currently selected track :)

Expression maps and per-note expression in Cubase along with VST3 is MIDI routing heaven ;) Bitwig has already partially implemented this idea although it doesn't make much sense given that it lacks VST3 support however at such an early stage Bitwig is super promising.

link

answered Jul 27 '16 at 15:22 by pauriniw (97)

edited Jul 27 '16 at 15:23

Once again you have saved me from self-destruct !

I had been reading the printed manual that came with BS but after wading through it twice and not getting the information I needed, gave up. But not now :) Thanks to you, I am able to move on to the next mystery to unravel !

Yes I agree, Cubase has a wonderful Midi implementation. But then, Steinberg have been doing this since the early days of Midi. After Steinberg were publishing Pro16 & Pro 24 Midi pattern-based sequencer for the Atari ST, I was sequencing with C-Lab's Creator and Notator; also pattern-based, on Atari ST. Emagic took over development, and I was using the newly labled Notator Logic ( Atari and PC) until 2003 when a buy-out by Apple shook the World of sequencing. Apple dropped production for the PC in favour of their own, and I was forced to jump ship - but not to a Mac. I purchased a license for Cubase. If it wasn't for Apple, I'd still be with Logic ... hey ho; but we move on :)

With Thanks,

Mike.

link

answered Jul 29 '16 at 10:12 by salicional (21)

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×213
×12

Asked: Jul 20 '16 at 11:49

Seen: 2,389 times

Last updated: Jul 29 '16 at 10:12