v1.2.0.3
possible vox leaks. play:
^s n1 ^d n14
notice the intentional syntax error (a double with no second). and you only hear the n1 which is probably correct (ie. not playing invalid syntax)
then play
^s ^n2
and notice the missing morshunote is found!
im not sure if this will be a problem for live rook voxes though
ah ok i think i have a better test case to trigger what i was talking about:
^s ^d -n17 +4* ^d -* +4*
this plays two doubles of a low b (-1) and fsharp (+4). the second double is missing the b when ditto is used. it seems like going negative is tricking something. using n17 on the second double works.
if you switch the notes, the b isn't played at all!
^s ^d +4n17 -*
but if you do:
^s ^d +4n17 -* -*
(ie. playing the low b individually after the double) even that is wrong. it sounds like a +4-*
v1.2.0.2
this seems like a related ditto bug:
!tc vox ^s ^d n17 ^d +3-* +5* ^d * ^d +3-* +5*
this is using double chaining to play 3 notes (c major chord). note how the second chain is missing the base c note when played. in this case im using * for notes except the first one, since the note/sfx never changed. but if you change this to
!tc vox ^s ^d n17 ^d +3-* +5* ^d n17 ^d +3-* +5*
it plays correctly. in this case the first note of the second chain was replaced with n17 instead of a ditto
it looks like normal doubling isn't working if the '*' (repeat) character is used as the first note in the pair.
^s n17 ^d *+3 *+5
just plays the first note, but this works:
^s n17 ^d n17+3 *+5
on 3/17/22 __ ver 1.2.0.1
chess edit: fixed! ditto was foolishly trying to ditto commands. i didn't have to account for this with the previous ditto functionality and forgot about it. oops!
