Took me awhile to see that this is a very old thread, from March 7, 2012 in fact - But I'll join in since in the original thread,
ernietamminga, the OPO, said:
"...here is a more detailed version of the excellent instructions that were posted a while back by browser (in February of 2011)...""browser" is the common typo for my user name "rbowser" - He was referring to a post I apparently wrote three years ago!
This thread was revived by
GBO323, since it looks like he was searching for help on setting up GPO.
Do you have it all going on now GBO323? Setting ARIA/Garritan up relies on the same basic principles of setting up any multi-timbral synth/sampler. When that's a new process, it can be a bit of a struggle, as ernietamminga was saying. I've used GPO for so many years now that it's second nature - I'll set up a new project in just a couple of minutes, even without using templates, because it's as engrained in me as turning on a water faucet. That's the way all this kind of thing becomes after repetition.
Now with the combination of old and new posts on this thread, I wanted to insert a few things:
"...After I had successfully done all of the above and recorded a test-song or two, sometimes subsequently when I would reload one of those songs, and/or create a new song from my saved template, things would get all screwy. My MIDI controller would trigger a sound completely different from instrument on the MIDI track I selected. If I later reloaded the song again and/or set up a new project from the template again, it would work correctly. I have no idea why this happens. Possibly has something to do with GPO’s handling of computer memory(?)..."I wonder if ernie's still around - I'd like to know if that kind of problem kept happening even after he became a more experienced GPO and Sonar user. What he's described there has literally never happened to me, not in 9 years of using GPO. That's a very odd behavior he was experiencing.
Ernie's steps for setting GPO up seem essentially right. He describes setting up all the MIDi and audio tracks in Sonar, and loading instruments in ARIA. Then he says something confusing, since up until this bit, he was talking about setting up a single instance of ARIA with 16 instruments.
"...and so forth, until each MIDI track is assigned to an individual instance of the Aria Player ..."He probably meant "until each MIDI track is assigned to an individual slot in ARIA." He was correct that each track can be directed to a different instance of ARIA, but before that sentence, he hadn't been talking about multiple instances. Just potentially confusing to newbies trying to follow the instructions.
He also sed:
"...You’ll probably find it useful to relabel each of the MIDI tracks, so that they’re not just “Track 19, Track 20 (or whatever numbers)”, etc. I relabeled mine MIDI-1, MIDI-2, MIDI-3, etc..."You definitely need to re-label the program generated names for tracks - But why replace the track numbers with MIDI numbers? The best thing to do is to just type in the instrument's name. You'll know at a glance what track is controlling what instrument.
Later he sed:
"...Sometimes (not always), after I've set up everything just the way described in the instructions above, then when I select a MIDI track (for example, the track that is assigned to MIDI channel5), then when I play my external controller, that instrument in the Aria interface responds, but INSTRUMENT NUMBER 1 ALSO RESPONDS..."Bob Bone's new post addresses that:
robert_e_bone...I assign the appropriate midi channel in the dropdown just under the FX bin for each midi track.
It is all then controlled by whichever Echo Midi On buttons are lit. Sonar, by default, will automatically light the midi echo on button for a midi track when it is brought into focus. That then will cause that particular synth or individual instrument in a multi-timbral synth to play...
--I think Ernie was having the doubled instrument problem because of accidentally having activated the Echo button on his first instrument's track.
Alkemy realized from reading Ernie's posts that he'd been setting the MIDI output of his keyboard incorrectly:
alkemy
"...I switch MIDI channels on my keyboard to play the various instruments. I think your way of doing it is better, because the track you want to play has to be highlighted anyway, so there's no reason to assign different MIDI channels to the tracks..."That's something that often comes up - People thinking they need to laboriously change their keyboard's channel each time they want to hear a different instrument. Therein lies the path to madness! Bob Bone reiterated what Ernie said in his original post - You set a specific MIDI Channel for each track in its header (inspector) and then when that track has focus, that's the instrument that plays - the one on the same MIDI Channel in ARIA. The keyboard can remain on MIDI 1 - it doesn't matter. The track settings are sending the data that's needed. That's why in the PRV, if you haven't done any bouncing, you'll see Channel 1 listed for all the controllers - that's the original data sent by the keyboard, but the track settings determine what channel that data is actually sent out on.
And - so forth!
Interesting to see this come to the surface again.
Randy