Thanks, everybody!

David, you are correct. Preserving keyswitches and updating chords is Chord's track's Achilles' heel. Dan and I requested for quite some time to fix this. Specifically, so C.Track writes and updates block chords on the note range specified in C.Track menu, while leaving note range outside of the specified range intact, to be reserved for keyswitches. Maybe PGM will listen and includes the fix in the patch? Who knows. In their place I would do it ASAP - as they finally released VST3 support and many newer VSTi's rely on keyswitches. Very likely an easy "filter" fix.

U-jam is just a tip of the iceberg. I've tried Strings, Bases and most of Session instruments from NI. EZkeys re-interpreted chord track to melodic phrases with it's MIDI out triggering completely different synth, etc. You can do pretty interesting and creative things, as these phrase and arpeggio based VSTi's add a very different flavor to PGM's content. You can experiment with different PGM tracks without leaving BIAB and without doing import<>export routine, until you get it the way you want it. When you done, export project files to DAW.

The iceberg part:
Advancements in AI in a home studio recording setting seems to translate in part to "smarter" plugins. And while PGM tries in some way to embrace the technology, I think a more efficient, long (longer) term solution would be to enhance connectivity, routing, tools and workflow to be accepting of this new wave of technology. Some examples would be: Intuitive VST to VST Midi routing, Chord Track has couple of serious but easy to fix issues, as one mentioned above. Piano Roll enhancement: Tool palette, better navigation, better selecting/drawing / deleting / moving notes. Easy MIDI drag in/out of tracks. And while final production will still likely to happen in DAW, this is so people can get most of the "bones" done in BIAB without crazy acrobatics - the easy way. These are relatively minor changes that would have long term impact.

Breathe out.