I’ll admit that was my first thought too, but these are not for PyraMIDI use, in fact you’ll probably want it disabled for this.
The idea here is to ASSIGN incoming CC’s of your choice to whatever FX parameter controls you need. The values here explain how the FX parameters respond to the value associated with a CC message, but creating the CC number - FX parameter mapping is up to you entirely.
See this thread for some background and instructions.
it would be really useful if the CC number was included somewhere in the headers above the values.
I’ll admit that was my first thought too, but these are not for PyraMIDI use, in fact you’ll probably want it disabled for this.
Heh, this was my first thought as well - “ok, so these are the values, but what CC are we talking about here?”. But I quickly realized exactly what you stated, that the CC number for controlling FX is freely assigned by the user.
For my general usage, many of these are just continuous values that don’t benefit a whole lot from complete mapping tables - things like Gate, Gain, Dry/Wet, Velocity%, Random%. Caring about precise values for some settings is almost like endeavoring to add an exact number of grains of salt to a recipe when you could just season to taste. (Perhaps this argument could be made about many of the things for which I do strive for high precision though, so I totally appreciate the attention to detail).
But some other tables here are, without question, extremely useful - e.g. Arpeggiator Style, EQ Base Note, BPM, all the Scale values, etc.
Thanks for this! It does make me wonder how labor intensive these tables were to compile.
Ive stared longingly at Lemur for years.
I have no iPad, and although it’s available for Android, i experience way too much latency and dont feel like learning a new system just to do something i can do with hardware…when i can afford the hardware. LOL (always seems to be one more piece i need)
Any MIDI Fx parameter will respond to the CC of your choice, selected via the Assign procedure. These are the values and what effect they have on the infividual MIDI Fx parameters.
Note: btw, an incoming CC can only be linked to one parameter on one track. I wanted to do something like CC 0x30 modulated Scale Type and have it affect all tracks that have the Scaler Effect, but alas: no go.
thank you for this, have been wondering how to do the same! Now I’ll try to use my Novation SL MK3 (whose sequencer lays unused) to sequence MIDI CC for FX control on the pyramid…in particular the chance of FX happening, sounds pretty cool
Glad it helps.
FYI - i think i made this realisation well after i made this document, but the Pyramid responds to 120 CC msgs on each 16 channels. So, just in case you have a setup routine that alters your MIDI Fx before song start, you have waaaay more than just 120.
And that is by design, so it wont be some overlooked feature that gets nerf’d in a future OS update.