I am trying to add a few more ram heavy instruments to the Global Rackspace so they can be triggered via the a Local Rackspace using OSC. (I already have a Friedlander Violin and Session Horns instance in the Global rackspace, which work fine.
Right now I am trying to add Soundpaint Tenor Sax.
I can’t figure out what I am doing wrong.
The problem seems to be getting the midi to the Global Rackpsace.
I can trigger the midi keyboard in the outgoing midi block
And, when I use the virtual keyboard for the plugin (Soundpaint) in the Global Rackpsace I can hear the audio, which is being sent back to the Local Rackspace.So, that part seems to work fine.
So, I am doing something wrong in getting the midi from the Local Rackpsace to the Global Rackspace.
I might not have all the relevant screenshots, but here are some. Thanks for any help with this.
I think @npdudar supposed that it is obvious. But happy if it works for you now.
Having said that, the MIDI in block that you use in the Local Rackspace is also available in the Globlal Rackspace. Is there any reason why you don’t use directly the MIDI in block in the Global Rackspace ?
Not that I know of. I would have to think how that might change my options/flexibility as I use it in different rackspaces along with other instruments. (I basically just tried to follow the blog).
I still haven’t got this new instrument working.
To someone who knows nothing about OSC going in, pretty much nothing is obvious.
Assuming I want to do this the same way as other (Midi In Block in local rackspace), anyone notice anything wrong? There must be some setting off
The problem seems to be that in the MIDI OUT Block I used “set handle” but that did not show up in the midi in block. I had to write in the specific correct information (with slashes etc.) in the midi in block itself.
[I am not sure why there is an active “set handle” option when you are in the Local Rackspace when it does not effect the OSC MIDI OUT block.]
Re (from Davie-San): Having said that, the MIDI in block that you use in the Local Rackspace is also available in the Globlal Rackspace. Is there any reason why you don’t use directly the MIDI in block in the Global Rackspace ?
Hello, David-San,
To answer your question about putting the MIDI IN Block in the Global Rackpsace (simpler), my impression is keeping the MIDI IN block in the Local Rackspace gives you much more flexibility in using the plugin (in the Global Rackspace).
For example, with the MIDI IN Block in the Local Rackspace, I can use the plugin in a different (local) rackspaces (along with other instruments) more and easily change the keysplits or transpose.
Also, I can use the plugin with my other hardware keyboard (which uses a different MIDI Channel).
So, I think it is worth the effort of using the MIDI IN Block in the Local Rackspace when I put a (usually sample-based) plugin in the Global Rackspace.
[FWIW, I think making a simple, seemless way to route midi data from the Local Rackspace to the Global Rackspace would be a nice enhancement for future versions of GP]
