so after a bit of a break… Im getting back to this, as Id like to get some kind of beta/early access out there…
however, there is one thing I need to tidy up before this EA release - nomenclature
tl;dr; what nomenclature (and abbreviations) should we use on modules for axis and key position?
(see below for options, explanations)
this is very important, since as I create more modules it becomes an increasing burden if I want to change… so I want to get it right first time !
lets review …
EigenD
- row/column - for ‘key’ position
- roll (pitch) , yaw (timbre), pressure
common in MPE
- x (pitch) , y (timbre), z (pressure)
it doesn’t really have a ‘key position’ , but things like linnstrument I believe use row/column.
others
ok, there are others like slide/glide/tilt, and things like timbre but these don’t really feel generic enough, or relevant to the eigenharp, and I don’t want to create my own terms either… enough confusion already !
note: I really do not want to use timbre/pitch, as x/y can be used for alternative use-cases.
summary, if we don’t want x,y,z , then Id go for existing eigend terms (roll, yaw, pressure)
where we are now…
MetaMorph
- x (pitch) y (timbre) z (pressure) for axis
- row/col for key position.
note: I will need to use R/C as abbreviations for row/column in certain UI elements, though will have tooltips to expand to explain.
this has a couple of oddities
a) in maths (etc) Y is the vertical axis … not horizontal!
b) I do want to create a module which rotates areas, so row → column, column->row
(a) is most ‘concerning’ … and I cannot switch y to be pitch, as that’ll be more confusing.
(b) is not really an issue, but its just a bit odd … I mean if you do x->y, y->x is not really any clearer !
alternative?
this did have me thinking perhaps switching to roll/yaw/pressure. (hence this post!)
BUT that also is problematic…
first , we can’t use abbreviation - (R)oll and (R)ow, thats a big issue.
second, I dont think the terms roll and yaw, mean much to users… unless familiar with eigend. its not immediately obvious which is which.
so whilst its ok in EigenD, I’m not that convinced to switch … which I guess is why I chose x,y,z when in the first place when coding … but that Y = horizontal axis is bugging me
I could switch to Y(pitch) X (timbre), but I suspect that’d be more confusing, unless you are into maths.
so, I think likelihood is I’ll leave as Ive got it, and sort out the consistency… but be very useful to get some feedback.
thoughts? ideas? suggestions?