Hello,
I’m currently looking at using the transport command visitlabel instead of jumptolabel or gotolabel when the listener gets lost or stuck at a place.
Visitlabel seems to be the perfect fit as the listener goes directly to the event rather than scrubbing from the beginning (and the scrubbing can be slow when I have multiple variables). However, I found that if there are multiple time signature changes, visitlabel seems to go to the wrong event. This seems to be unique to visitlabel as jumptolabel, gotolabel and startfromlabel seem to get to the label just fine.
This behaviour is slightly strange because if you feed a test file where the key signature is at 4/4 for the whole piece, visitlabel works perfectly.
I was also looking at visitbeat, and it works perfectly if the score position is before the visitbeat. But if the listener’s position is after visitbeat (i.e. the listener skipped a few important labels and you want it to rewind a little), it gives the error message: “Semantics of visitbeat is not yet established. Report what you want.” and it may or may not go to the beat.
I’ve attached a quick video of the behaviour and the asco.txt file which has the time signature changes (you’ll have to visitlabel measure200 or more to see the issue). I can probably upload a higher resolution video, but wasn’t sure what is the maximum size.
I am using the latest distributed Antescofo (1.0-599) on Max 8.6.5 on MacOS Sequoia on an Intel Macbook.
Thank you so much for your time!
Screen Recording 2026-03-12 at 8.26.47 PM|video
untitled.asco.txt (59.2 KB)