Hi -
Does anyone know if there is a reason why a CHORD-SEQ will add an extra onset element into the list of onsets when the patch is configured like the example below?:
I would expect the onsets list to be (0 500) - the same length as the corresponding lmidic, ldur, lvel lists. But instead the lonset list is (0 500 1000).
Is this intended behaviour?
Thanks,
Graham
Dear Graham,
This is not a bug. It is intentional. The last onset added is to indicate the duration of the chord-seq. It was always the case in OM. Indeed, it doesn’t seem very logical but very useful. It is the same case if you enter a simple list of midics such as '(6000 6100 6200), The output of chord-seq’s lmidic will turn into: '((6000) (6100) (6200)). You can think of it as “rules of behavior” of the chord-seq once evaluated. It will format the given inputs to conform with it own way to deal with its values.
If you enter your onsets as '(0 500) it is ok. The chord-seq will recalculate the last “ending” onset which by the way is not an onset. That’s why it is somewhat disturbing. But you’ll get the duration of the last chord in it.
Best
K
Aha! Thank you, Karim!
I understand now. That last element in the list of onsets is the total duration of the sequence from zero, factoring in durations of notes too. I can see how that would be useful. Good to know that’s nestled there.
Thanks again!
Graham
