Hi Folks.
This should not be considered as tutorial, just an example of my workflow. Instead of going back and forth from BIAB to DAW when laying out arrangement, I do a rough sketch in BIAB to hear how particular set of RT's sound together with NI or other synths.

There probably is a way to program keyswitches for NI... I didn't look closely yet, as I am still finalizing everything in DAW, but for rough sketching this works for me. If you have any questions, please ask here, as I do not monitor youtube comments.

Cool Cool Cool.

If you are changing chords and need to re-generate the midi chord track instead of having the keyswitches on the same track you can put the keyswitches on another track and re-route that track to Kontakt track. If you set Kontakt to Omni midi input it will work with whatever channel the keyswitch track is on.

"If you set Kontakt to Omni"
Good workaround if you don't have any other midi going on, otherwise Kontakt will pickup all the midi in the project.

Another workaround would be creating a Chord Track on any other track, not specified in Preferences>Chord output and use piano roll to add key switches. The downside of course it will not pickup new changes in chord sheet.

On Omni it will only pick up all other midi on other tracks if it is Default Synth or you Re-route the other tracks to it.
If you load VstSynthFont into a track it will only play that midi from that track no mater what channel the midi is on as it is Omni.

OOOOOOH, my brain hurts.
Well done Misha.

Musocity,
That could work, in some cases, if you don't have multiple plugins set up. But then again, it would be tricky to transplant it to DAW together with chord track and make it work inside DAW, not conflicting with other MIDI items.

What would be nice if there was a simple mechanism to do Key Switches as they seem to dominate workflows of VSTis.
I think the "easiest" way from a user perspective would be to set a custom range for key switches in options when generating new Chord Track. So generations or chord changes do not overwrite that range. That way, when you export a Chord track to DAW, it will have all the info Session guitars, or any other instruments that use key switches need in a single midi track. I think it is a good candidate for 2024 wishlist. Should not be too difficult to program.



P.S. Ray, I am sorry, I can only offer virtual ibuprofen

That's what I had in the snap midi to chords script, you can set the ignore range for keyswitches.
You could have an empty track as the midi chord track and Re-route that to the Kontakt track that has the keyswitches.
I tried putting the keyswitches on another channel on the chord track but as you generate a new chord track it deletes them.
So you just need to copy the switch notes from another track to the chord tracks before export, or solo both chord and keyswitch tracks then drag Master to MID and you will get one midi file with chords and switches.

A few DAWs such as Cakewalk by Bandlab and Cubase offer Articulation lanes or tracks where the VSTi keyswitch midi data is separate from the midi note data.

The DAW understands the difference between a VSTi midi note and VSTi articulation note by reading an Articulation map.

The problem is every VSTi using articulations requires an articulation map to properly work in a DAW that can follow an Articulation map. The good news is since Cubase seems to have originally come up with the Articulation map idea Cakewalk is following Cubase's lead. Between the two DAWs a fair number of VSTi Articulation maps are available. +++ HERE +++ is a link to Articulation maps in the Cakewalk forum. If there is not a map for your favorite VSTi they are pretty easy to create.

Jim,
Articulations are another animal. I am strictly talking about key switches for pattern based VSTi's for programming pattern changes and shots/holds

When you create a Chord Track through Preferences>Output Chords, you are given a choice of range. The easiest way, I think it can be done is to have a "second" range reserved for key switches, that will remain in place, no matter what you do with re-generation or chord changes, to be only edited manually through piano roll, while the "active" range will rewrite block chords when chord or bar changes are introduced.

There are couple of workarounds, mainly what Musocity mentioned, but that would require extra steps and re-routings. What I proposed will be a single track that includes both, a chord changes and key switches. Universal file for BIAB or any DAW. I have to think about this for some time before heading to wishlist.

In the Output Chords dialog there should be an option to automatically change/update the block midi chords when changed in the chord sheet and an option to ignore/leave all notes outside (above/below) the note range set for chords.

Misha,

Do you mind providing one or more VSTi example of a pattern based VSTi that can program pattern changes and shots/holds. I'm wondering if we are on the same page but maybe saying the same thing two different ways. If not I may better understand your request after looking at VSTis that work as you describe.

Musocity, I hope you'll post this suggestion in the Band-in-a-Box wishlist as it may get overlooked here.

Jim,
Ujam, Sonokinetic and I am sure many others that use key switches for pattern changes.

Seems Musocity is on the right path:
"automatically change/update the block midi chords when changed in the chord sheet and an option to ignore/leave all notes outside (above/below) the note range set for chords."

The issue is Band-in-a-Box does not have a way to address the use of VSTi articulation maps. Musocity's suggestion is one way Band-in-a-Box can address your suggestion. I hope he will post the suggestion in the Band-in-a-Box wishlist.

Misha, thanks for providing the development company names. It was interesting to look at their products.

As far as a DAW is concerned there is no difference in applying an Articulation map to trigger VSTi generated phrases than using an Articulation map to select sustain or legato.

I took a quick look at the reference guide for the Ujam virtual guitarist, Silk and virtual guitarist Amber. It looks as though Articulation maps can be used to select common phrases and style phrases for both virtual instruments.

I also looked at the manual for Sonokinetic's Toccata Epic Pipe Organ. Articulation maps can be used to select any of the 20 pipe organ registers through upper manual, lower manual and pedal articulations.

MusicLab guitars have articulations and comes with a pattern library and you can create custom patterns.
I will let Rusty post in the wishlist.

In RapidComposer I can create keyswitch map for all the articulations any instruments, below I'm using Ample Bass Guitar then you just right click on the note and it will set it to any articulation, so you can save the midi phrases with the articulations and they will fit any chord section any octave but still retain the keyswitches.

Musocity,
Thanks for honors, I will post that wish that you formulated well. But... there is more to that.
Chord Track was a good move by PGmusic, which btw was initiated by justanoldmuso, however it is missing couple of important pieces in my view.
If I am thinking it right it needs 3 items:

#1 What we discussed here on ignoring all "other" notes.
#2 Ability to create more chord tracks that will accept changes, without going into "generating a chord track" each time change is introduced.
#3 Possibility to create tracks with different specified ranges that will also accept changes automatically / simultaneously with tracks with other set ranges.

Simple example:

NI Session Guitar + Synthmaster in BIAB.

In Reaper I would have the one chord track then use a send to another VSTi track and transpose the midi input to another octave for different VSTi's.
I think there was a transpose input just added to BB23 ?
But you could have one on each track at a different octave, you would just need Biab to keep track of what tracks they are on and the octave so they can be updated with chord sheet changes.
But to have options to do it whatever way suites the user is good.