swamptooth
hey superg take a try with tts1 and see how it works. i vhecked the midi file for weird sysx commands and there werent any. still scratching my head.
Ok - I popped it onto TTS-1. I like the Roland GM better than built-in Microsoft..
Actually, I mostly do a quick run through with TTS as an evaluation to see if a midi is something I'd like to play with, I just don't remember if I had done it with this one. Love the double-bass in this one (don't we all..)
Anyway, it's still crashing.
Originally, I had the same identical symptoms as yours. The display was all
weird - as you moved the mouse. various parts of the screen would refresh, but in the wrong places.
It had me
stumped as to why it started crashing, and then I remembered something. I had figured my best
guess was that as this was related to the midi stream it was likely a memory error. *Blink - lightbulb flash* Ah - this means that the behavior of the software after whatever is exactly the trigger point can vary - because we really don't
know which part of memory got hosed over. The thing is, every PC is gonna load programs in different places depending on what software, drivers, OS options, and so on. In Sonar, the type and number of plug-ins, synths, controllers all may change what gets loaded where. There's just no telling. The only person who can know for sure is the developers themselves, and it's gonna be somewhat different even for them.
Here's what I do now to get around it - it's fairly straightforward.
So... for Aria, basically what you need to do is convert the program changes for articulations like pizzi and such over to key switches. Use the program changes as guides to line up the now-pointer, but just don't ever open tracks with program changes in notes or the PRV. Just add key switch notes to a new track and then patch that track to the same channel. The goodness is - you can mute all the key switch tracks and still save the project as a standard GM compatible file, or unmute and you have a really slick Garritan version. Some folks have told me they do this in their workflow
anyway - it's a lot easier top find and edit key swtiches.
Oh yeah - thanks for mentioning Arias' reverb. On that other muting issue - I played around and discovered (drum roll...) it's putting out reverb on all channels
from all channels. That's at least partially responsible for the channel bleed-over, I don't know about the rest yet, but now that I understand it's behavior it's not gonna bother me anymore. Definitely a head scratcher - then I though about how I'd do it - and the first thing I thought was no way would I do 16 instances of a reverb, it's just too dam costly CPU wise. We use things like sends and busses here and in the physical world for those reasons. The implementation probably follows the same. Send every channel into an single internal reverb bus, but sum some of that back into each channel (as there's no thing such as synth master bus, at least not officially?) - but you're hearing *everybodies* common reverb, not just your own - I guess I learned something today.
Oh well, it's nice to have the option of using the synth's reverb, but it's just as easy to put a reverb on a master bus in Sonar as well....
Whaddaya think?