Now, to the very freshly clicked idea. Somehow I have a feeling this could improve the musical output a little more in ftn. Here how it should work, it is quite simple:
__________________________________________________________
Case with two note input, assuming recorded seq 'a,b,c,d':
1. First note transposes the lowest note, to itself, keeping the rest
Example: First note is g, result: 'g,b,c,d'
To me this is somehow more musical than resulting in 'g,g,g,g'. Which loses somehow all previous musical interval information, too much loss of information, which makes it for me kind of 'unmusical'. The relationship to the previous recording is almost completely lost, interval-wise.
2. Second note transposes the highest note, to itself, keeping the rest so far
Example: Second note is f, result: 'g,b,c,f'
____________________________________________________
Case with three note input, assuming the same above:
1. and 2. same as above
3. Third note transposes the second highest note, to itself, keeping the rest so far
Example: Third note is e, result: 'g,b,e,f'
___________________________________________________
Case with four note input, assuming the same above:
1. 2. 3. same as above
4. Fourth note transposes the third highest note, to itself, keeping the rest so far
Example: Fourth note is c, result: 'g,c,e,f'.
Those cases would be enough I think. For one note input case, only step 1. from above.
Would this be easier to accomplish with current Sequetron code? I hope yes, as it does not contain too much analysis, just knowing the order of the pitches from lowest to highest. Also, releasing the keys one by one, should move the sequences in the same way to its original state 'a,b,c,d', backwards. For example 'trance music' uses lots of such 'progression' where the upper notes stay same, but only the bass note moves, then maybe just one upper note moves and so on, this we could achieve in real-time using Sequtrons new ftn-mode behaviour.
