Hi Ed,
I think the problem is that setting DIRect in the matrix means that the
controller value is applied directly to the parameter. However the Mod wheel
sends values from 0 to 7F (where 0 is off). Whereas, the VCF Mod depth
parameter runs from 0 - 7F.....but 0 corresponds to -63 and 7F corresponds
to +64 i.e. the 'off' value for VCF Mod depth corresponds to 40 hex (64
decimal). So you have to offset the Mod wheel values by 64 if you want the
Mod wheel full down position to correspond to zero VCF mod depth.
Note: Of course if you do this then you can only apply positive VCF Mod
depth (i.e. it will stop having any affect once the Mod wheel goes above its
centre position.
Regards
Gary
Email:
gary@... http://www.yme.co.uk/yme-----Original Message-----
From: Edwards, Ed [mailto:
ed.edwards@...]
Sent: 20 December 2000 16:37
To: 'AN1x List'
Subject: [AN1x-list] Parameter overlap and Matrix Set "Depth"
Ok, I admit it... either I'm too stupid to grok the concept or is it just
that the manual says nothing about this:
A simple, commonly used modulation I want to add to a patch is Mod Wheel to
LFO the VCF (filter). Seems simple right? Go to the Matrix, find an unused
Set, make the parameter VCF mod depth, the controller the Mod Wheel, and the
depth (seems like should be) direct. So I raise the Mod Wheel, and what
happens? The VCF LFO works fine. But when I lower the wheel to "off" the
stupid is still wavering from the LFO.
Now, it took a while to discover this, and I still don't understand the
reason, but this was the fix: Set the parameter depth to -63. Now the Mod
Wheel is off when down, and works when up, and then is off when down again.
WHY? Does -63 mean that the controller range for the Mod Wheel now begins
at "0"? It would seem that the default for a mod wheel would be down=0 and
fully up=whatever the top of the range is.
Please don't tell me that the "depth" parmater is explained fully in the
manual, because it ain't.