-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, Oct 24, 2007 at 07:47:23PM -0700, Ken Restivo wrote:
I experienced a strange problem in PHASEX where the
BPM settings were saved in a patch file, but, when the file loaded, the BPM settings
wouldn't.
The problem was that I had the "lock parameter" box checked in the MIDI map for
that parameter (BPM). I don't remember if I set that, or if it is the default.
When "lock parameter" is set, not only will PHASEX ignore any updates from MIDI
for that parameter, but also from the patch files. This could be kind of a useful feature,
i.e. when playing a song and switching patches, often you don't want the BPM of the
delay changing unexpectedly, just because you changed a patch.
However, when saving patches that go with a particular song project, you definitely *do*
want the BPM to change when you load the patch. So I unchecked this, and I save that
unchecked MIDI map with every project, so that the patch will load and have the correct
BPM.
Saving MIDI maps along with the project is also a good habit to get into. It sucks to
open a sequence and load a patch and the MIDI maps you'd recorded no longer do
anything.
One more note for the archives: the BPM, MIDI Channel, and Master Tune parameters are all
Locked by default when you load up PHASEX. Every time you load up PHASEX, you have to
right-click on BPM, then uncheck the "locked" box, and then close the window.
Then, if you load a patch via the Open... dialog, the BPM will be restored from the
patch.
Interestingly, if you're just flipping through patches using the Program # box, or
MIDI program change events, the BPM will *not* restore. You have to manually click on the
"Load" box in order to force the BPM to restore, even if it is not locked. I
didn't expect that, but I could see how it'd be very useful.
- -ken
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHIPU6e8HF+6xeOIcRAopMAKCArtmKXBZxcRSlsFzTC4bafPMq9wCeMqgI
y1q17RR0/0fmdHVMY+5uQxg=
=lYlB
-----END PGP SIGNATURE-----