SamsonAnderssonMusic

*solved* Hey everyone! Thanks for all of your replies! You led me to the right place. I found the IAC driver too buggy to be usable, but I took the external instrument approach and I’m now controlling Kontact as a stand-alone application through the “Kontact 5 Virtual Input”. I create a new external instrument for each patch, add Chord Trigger, and then send to Kontact. It works perfectly! Mainstage loads up 30-40X faster and loads of memory and CPU have been freed up. Thanks again!

Also, I’m not familiar with summing stacks. Would that work with mainstage as well?

I am using Mainstage. I want to be able to apply many different midi FX (a different one for each song) to the same kontact patch. Currently, I’m having to load a new kontact patch (killing my memory and CPU) for each song because alias’s can’t have unique midi FX and I can’t use an aux strip because I need to manipulate midi data. I need a different setting of ChordTrigger for each patch. I was hoping to be able to create a midi chain and simply interchange different Chord Trigger parameters for each patch before sending it to the same kontact. Maybe I could send midi out of the hb and patch it back in? I’m not sure. Can you send midi date from channel strip to channel strip?

Hello everyone, Is there a way to create a “midi bus”? I currently use Chord Trigger to program parallel monophonic harmony lines and play them live with VST horn software. They are awesome, but it’s killing my computer. I need a different setting on ChordTrigger for each song so I have so far been unable to utilyze the alias function. I would love be able to route my midi through a unique channel strip with Chord Trigger and send the resulting midi data to a single aliased Kontact strip. Is this possible? Any other ideas? I’m using in conjunction with an HB-1 midi interface/breath controller and a Korg Kronos. Thanks in advance! Samson