A few use cases off the top of my head:mholloway wrote:Would it be possible for someone to quickly, succinctly describe what the purpose and usefulness of these new MIDI Channel features are? As a 100% "in the box" guy, I don't really have any idea what is being upgraded / offered here with these, but I'm sure some hardware folks could explain it?
And, is there anything it offers the non-hardware user?
I'm psyched about Sampler and especially the two new modulators, but as for the MIDI stuff everybody's talking about, even after looking at the pictures with the stacks of Channels, I honestly don't know what the heck any of it does!
- Required to get proper usage out of multi-timbral VSTs like Falcon & Kontakt. You can load 4 separate instruments in one Kontakt instance for example, and then route 4 separate channels of MIDI into it to play each instrument with separate notes. This can all be done on a single Bitwig track now.
- Like antic mentioned above, you can now use the Bitwig instrument layer along with separated MIDI channels to have multiple instruments on the same track, playing different notes. A good example of this might be if you had two synths playing in harmony or counterpoint, now you can capture all that on a single track and keep your arrangement cleaner
- Some VST effects can be triggered by MIDI (e.g. Looperator by Sugar Bytes allows you to change preset via midi note input). Instead of having to create a separate track just to send notes to do that, you could now have one midi channel dedicated to actually playing your VST instrument, then another channel changing presets on Looperator
- A few cool standalone software tools (e.g. the incredible XronoMorph midi sequencer) send out multi-channel MIDI. It's currently a massive PITA to use with Bitwig as channel information isn't retained when you record a stream of MIDI from it. This will be remedied with 2.4.
I'm sure there's loads more use cases but those are the first that came to mind (for my workflow at least).