![rapidcomposer drums rapidcomposer drums](https://snipboard.io/A1L9FC.jpg)
It all seems to work this way and maybe I need to set up switches to enable or disable this.but the downside I see for now are twofold This seems to let me use my midi controller normally, and/or to direct to the rapidcomposer plugin.
![rapidcomposer drums rapidcomposer drums](https://windows-cdn.softpedia.com/screenshots/RapidComposer_16.png)
What I have so far is to first turn off the sum input in the environment and then to take the input from actual keyboard and split it using a monitor object, so that the data goes both to the sequencer and to the mixer object holding rapidcomposer that is not associated with any track, and thus not getting input from the sequencer. For example it has features to record midi patterns and play chords to recognize them, etc. The only thing left is to figure out the best way to direct a midi controller to RapidComposer as needed. At least its sending all Rapidcomposer midi channels over IAC.and feeding them into the sequencer, where I can demux as needed to feed to various tracks hosting instruments. I'm probably getting some strange timing problems using external instrument plugin, but I will figure that out later. Fine so far for routing midi from rapidcomposer to the sequencer over IAC. Then I use external instrument in the instrument plugin slot to send the output to an IAC bus. Magically the midi is picked up that way just fine, WITHIN THE CHANNEL STRIP. I can do this because I'm using BlueCatAudio patchwork to host the VST plugin, and BlueCatAudio can take a VST and wrap it inside AU-MFX form. In order to use midi-out, I have to put the plugin into the AU-MFX slot, so that outgoing midi from the plugin is actually received by the channel strip in logic. I did manage to get RapidComposer onto a mixer channel object that is not associated with a track.
![rapidcomposer drums rapidcomposer drums](http://www.digital-notes.de/wp-content/uploads/2015/01/rapidcomposer-1.jpg)
![rapidcomposer drums rapidcomposer drums](http://www.digital-notes.de/wp-content/uploads/2015/01/rapidcomposer-1a.jpg)
Every time I have tried to mess with that, I have become extremely confused, but I will try it again.Įric, if you turn off automatic management of channel strip objects, what are the ramifications of that when using the GUI? The fundamental problem is the single funnel that Logic uses to pass all incoming midi through one sequencer port to get to all the tracks. I have tried that in the past and it made my head explode trying to keep track of whether it was getting midi or not and was very easy to get into endless midi loop by clicking on buttons on the track header wrong way. The idea of putting rapid composer onto a track with some kind of auto demux, etc. that would eliminate the possibility of an endless midi loop, but on the other hand, sometimes I *DO* need incoming midi from my midi controller to get to it for midi interaction.maybe I can patch that in the environment though, I will play with this some more. Seems like you are suggesting that I can get a mixer object to host the plugin.and it will do what it needs to do, dis-associated from any track, without receiving any midi coming into the sequencer. I guess I could probably just create a track and then reassign the track to something else to dis-associate the track from the mixer object.but yea.I get your point, I will play with that. At the moment this appears not doable in Logic.but any ideas will be welcomed. So maybe there is some other way to host a midi-out plugin somehow that I am missing? It needs to be such that the plugin will sync with host playback and such that the midi-out can be routed to all the other tracks/channels hosting actual soft synths and such for playback, without an endless midi loop issue as mentioned above. It shows up and seems ok at first, but when I hit play on logic, RapidComposer doesn't play with it. Somehow rapidcomposer doesn't quite work right in the AU-MFX slot.the plugin also responds to midi input when you're using it, so the problem is that when the IAC bus is looped around to the input of the sequencer again, the other instruments all get the midi, but so does RapidComposer again, creating an endless loop problem.This seems easy enough on the surface then, can use it as a AU-MFX and then in the instrument slot of that channel, use "external instrument" to send the midi to an IAC bus, which will be looped back into Logic, and into the sequencer. This plugin will output multiple channels of midi, intended for different instruments, the midi out from it needs to be routed back around to the input to the sequencer, so that it can be directed to different tracks at the same time for playing back other soft synths that are hosted on other tracks/channels. The problem to solve is how to route the midi. It is a VST, so i have to use a wrapper to get it to work in Logic, using BlueCatAudio's, patchwork, which will let me use it as either an AU instrument or AU-MFX midi fx. This may involve some environment trickery or not, but I haven't been able to figure out a good way to do it thus far. I am hoping some of you gurus can help me figure out the best way to handle a certain midi-out plugin.