Message
Mystery: Per Note CC64 (sustain) & ext clock [ was: Re: [xl7] Re: BTS - Triggering from the Sequencer (Beats Mode)
2017-03-26 by smw-mail@...
Yesterday I did a live (in home) performance with a usb/midi keyboard connected to my P2500. I did my usual thing of setting up presets on the different midi channels, so I could change the global midi channel on the controller and play each P2500 Channel/Preset [C01A-C16A] one at a time. The 16 buttons were set up to play a BTS drum pattern/beats on C16B.
For C01A-C16A, I have a knob on the keyboard set up to CC 64 (sustain on/off) so I can layer arps, bpm, and other presets that have internal auditory motion--such as through LFO sound shaping on up to 16 channels.
The midi clock was set to ext so I could slave it to the midi clock serving other gear. (This seems to be important to the effect experienced todayI)
At power up (and when I reset the settings from the multi-setup I saved), the midi clock clock is set to ext. The current clock at power up a tempo (120). When I change the tempo via the display/data knob, the mysterious effect disappears but returns when I restore the multi with midi clock = ext.
The current tempo remains at what I last had (e.g., 80 or 20 or whatever).
THE MYSTERIOUS EFFECT(S):
With the midi clock at ext, but with a numerical tempo displayed, it seems that one of the LFOs with a bpm rate (1/4 in this case) is picking up the bpm clock from the same source which drives the displayed clock (i.e., not the ext midi clock, because I have no ext midi clock coming into the P2500.
I have seen the residual current tempo before, but until now it never occurred to me that there might be potential for multiple clocks--one ext and one internal. (Has anyone else seen or taken advantage of this?)
The REAL Mystery--which seems like per note CC 64 (sustain on/off):
First of all, the preset I had on C01A is XROM arp:Palomar; the arp does not play [probably because the arp is expecting to get its bpm from ext]; LFO2 has a square wave octave modulation at 1/4 bpm evidently picked up from the "current" tempo.
If I press a note and then turn CC64 on, the preset (with its square wave modulated octave effect) sustains. When I press a different note, that' too sustains.
When I turn CC64 to 0, those notes continue to sustain as if they are latched. I can play other notes and they don't sustain. When I press the keys for the sustaining notes (one at a time), they turn off (one at a time). And, no, it is entirely independent of my global/button latch settings.
Am I missing something? like a per preset latching thing? I haven't looked, but I suppose there could be patchcords (flip/flop?) set up as sustain toggles that seem to function as per note CC64 sustains due to dynamic note assignment at playtime?
It might be something very simple, and I wanted to write this down so I can come back to it to explore, but thought I'd ask here, in case anyone else knows what is eluding me at the moment.
Foot notes:
I have CC28 assigned to MidiL (LFO2 Rate). That changes the rate of the octave jump modulating (square wave or whatever I change it to). I also have CC27 assigned to MidiK (LFO2 Amount) which affects the modulating cutoff frequency
If I turn the arp status off in the preset, the effect that seems to be per note/latching sustain goes stops the sustain on all notes previously sustained and the per note effect no longer works for subsequent notes.
Anyhow, I am now wondering if this is related to the kind of interactivity I explored before. However, I have used up my time allotted to this. Maybe someone else can explain what is going on here.
Steve
.