by Guest » Fri Jul 23, 2004 10:48 am
Labarynth,
I may be wrong, but I believe the Reset message resets the entire card/module, so it's working from a clean slate. That way you don't have have, possibly, data left over from a previous state that may cause confusion and weird effects on tracks. I am very adamant about doing this, and making sure that ALL tracks have performance data (Program Changes, Volume, Pan, etc.) inserted at the proper places. I learned the hard way what happens if you leave it to it's own devices. It's much harder to track down things later, than earlier. For instance, I have done some things where I pasted one file to the end of another. This is where it REALLY gets interesting, and where I had to figure out what was wrong. Believe me, it's easier to find things before you merge files, than to wade through 40 MIDI tracks of event data to figure out exactly where to insert a change. And often, I'd have to search for the proper patch, because the instrument in the Tracks View is going to stay whatever was loaded first. So if that track changed from a trumpet to a flugelhorn, it's still going to list a trumpet.
Also, the numbers in the Track View representing volume, pan, etc. don't follow the performance, so I can't rely on them. If I want to be sure things do what I want them to do, the Event List is the only sure-fire way I have figured out how to do it.
You could leave the Reset message in the beginning of the second part of the tune, but I have been removing it after I paste. As long as it was reset at the first, and all the changes were inserted, it should play back properly.
HDB