JS `S16384` seems to be resetting the patch as well as time base

[bwhitman]

amy_add_message("i1iv4K0Z");
amy_add_message("S16384"); // reset ticks to 0
amy_add_message("i1n72H396,0,1l1Z");
amy_add_message("i1n72H444,0,2l0Z");

If run from a JS REPL will play first juno-6 but on a 2nd run plays a sine wave

[bwhitman]

I don't have an explanation, but doing the reset call first fixes this:

amy_add_message("S16384Z"); // reset ticks to 0
amy_add_message("i1iv4K0Z");
amy_add_message("i1n72H396,0,1l1Z");
amy_add_message("i1n72H444,0,2l0Z");

[bwhitman]

I've confirmed that the reset_osc parsing is correct, that is, it's only resetting the timebase when getting S16384Z. I don't know what is making the instrument/patch assignment go bad if you call S16384 after you call i1iv4K0. Another clue, this also works:

amy_add_message("i1iv4K0Z"); // just once

amy_add_message("S16384Z"); // reset ticks to 0
amy_add_message("i1n72H396,0,1l1Z");
amy_add_message("i1n72H444,0,2l0Z");

e.g. if you skip the instrument / patch assignment step it works fine every time.

[dpwe]

I can't reproduce this.

.. plays the note with Juno patch 0 both times. Am I doing it wrong?

[bwhitman]

That doesn't surprise me. Me and the original user were calling them all at once (like as one block of code, then hitting enter). I bet there's some race thing with instrument / sequencer. Try typing the four lines all at once and trying again.