Replacement opcodes for extended CCs

[MTornPDX]

Should we consider a way to phrase extended CCs in a more intuitive way?
For example, I use cc131 (velocity), cc133 (note number), cc135 and cc136 (random) A LOT. And if my keyboard had aftertouch I'd use cc129 a lot too.

These numbers are quite secret and unintuitive, in fact I didn't discover them for quite a while. And I still have to look them up often to remind myself what number does what.
Shouldn't we be able to write things like cutoff_onvel or offset_onunirand, or perhaps amplfo_depth_onkey (or perhaps it should be _onnn)?

A few of the ccs above 137 are useful too (others are just a bit weird) - I like cc140 (key delta) and cc153 (number of keys held down).

[paulfd]

As a solution in the meantime you can define constants, e.g.

#define $velocity 131
… cutoff_on$velocity=…

I am on a phone so I didn’t test but it should work!

[MTornPDX]

Al

As a solution in the meantime you can define constants, e.g.

#define $velocity 131
… cutoff_on$velocity=…

I am on a phone so I didn’t test but it should work!

Almost! It works with

#define $velocity cc131

I've never played with Define, it might be pretty useful.
Of course, you still need to either memorize the secret ccs, or look them up.

[DSmolken]

Would definitely be a good idea, especially when it comes to adding even more extended parameters.