Author |
Message |
ThreeFingersOfLove
Joined: Oct 21, 2004 Posts: 162 Location: Greece
Audio files: 3
G2 patch files: 1
|
Posted: Tue Oct 26, 2004 1:58 am Post subject:
Extraction of values |
|
|
Hmm,
for quite some time, I have been struggling to extract a value from a module. And I mean any value, other than its output. For instance, you can patch the output of say, a sequncer to a compare module which means that the current value of the sequencer is compared against a fixed value and you get a logic signal carrying the result of the comparison.
Now...the signal from a filter is obviously a "composite" signal containg the current cutoff, current resonance, current key-tracking and so on. None of these paramteres is available in its own. How do I monitor for instance the cutoff frequency or resonance per se and trigger some other events when their values (and not the output of the filter as a whole) meets some criteria? That would be easy if the parameters had outputs themselves, but they don't. I feel that there must be a way for parameters that have dedicated inputs but I am not sure about others.
Anyone? |
|
Back to top
|
|
|
jksuperstar
Joined: Aug 20, 2004 Posts: 2503 Location: Denver
Audio files: 1
G2 patch files: 18
|
|
Back to top
|
|
|
ThreeFingersOfLove
Joined: Oct 21, 2004 Posts: 162 Location: Greece
Audio files: 3
G2 patch files: 1
|
|
Back to top
|
|
|
egw
Stream Operator
Joined: Feb 01, 2003 Posts: 1569 Location: Asheville NC
Audio files: 18
G2 patch files: 8
|
Posted: Wed Oct 27, 2004 6:44 am Post subject:
|
|
|
It would be easy if your mod amount on the filter was at full value, right?
Then you could trigger it from the LFO signal. (i.e. when the control signal reaches 36)
So, send your LFO through a modamt module with depth set to 61. Then you can trigger off the output of that. |
|
Back to top
|
|
|
cappy2112
Joined: Dec 24, 2004 Posts: 2465 Location: San Jose, California
Audio files: 2
G2 patch files: 1
|
Posted: Sat Apr 30, 2005 1:37 am Post subject:
|
|
|
jksuperstar wrote: | MIDI is your friend! This is described in the manual where it covers the use of the CtrlSend MIDI module in the Module Reference. See the attachment for example. Notice the MIDI CC assigned to the Filter Cutoff...it is the same as the CtrlSend module (CC#20), and MIDI channel is set to "This". |
I don't undestand your patch. I can get the filter cutoff in this patch to respond to CC20, without using the CtrlSend, so what is the purpose of the Ctrl Send in this patch ? |
|
Back to top
|
|
|
jksuperstar
Joined: Aug 20, 2004 Posts: 2503 Location: Denver
Audio files: 1
G2 patch files: 18
|
Posted: Sat Apr 30, 2005 7:41 am Post subject:
|
|
|
It's a loopback control. Some knobs on modules have no modulation input. So, in an instance where you'd want to use an LFO to control a knob, you send the LFO out on a MIDI CC, then assign the knob to the same CC value. This is also very effective when you have all of your sequencers in one slot, with sounds generated in another slot.
I thought the initial problem was trying to find the value of a knob (on a filter). So you could either put the control elsewhere, where you have access to the controlling signal, then MIDI it over to the knob for control.
You could also use a CtrlRecv assigned to the same value as the knob. But this doesn't help you when using a modulator like an LFO on the knob. |
|
Back to top
|
|
|
|