< Back to IRCAM Forum

Jump to label command

Antescofo
#1

Hello!

I really miss a command for not only going to a label like I do with “gotolabel $1”, but also to jump to a label executing all the messages from the label/some labels earlier including all LFWD/GFWDs. The main reason for this is, that I like to make long preset chains with lots of effect/control modulation that are going through many cue points (labels) for about 4-5 minutes. So if I have to test or to make a rehearsal starting at some exact label within a long effect/modulation chain I manually have to go through all the labels before, waiting for all delays in the antescofo score to be executed. Here is an example for that in attached file. It is the large piece from my actual antescofo score.

If you search for “reset bang” in the text, you will see that I reset my matrix only at the beginning and at the end. So if I’ll start at label cue25 I have to click manually through every cue beginning with cue14 to get an exact reproduction of my matrix and effect presets at cue25. I know that maybe it is because of my poor programming skills but i really didn’t find any other solution to implement all FX-chains I wanted.

Marco told me about the “jump to” command in antescofo that should make exactly that thing that I want - going fast through the score executing the cues with exact sequence and zero delay, but unhappily I couldn’t find that command (Marco also wasn’t sure if this command was implemented). So if you can give me a solution for this problem, I would be very grateful. If not, it also would be ok the way I do it now as going through the cues many times isn’t so bad because I find more and more bugs every time. :wink:

corev2_cue14.txt (10.4 KB)

#2

The command in question is jumptolabel and it is in the “PerformanceControl” patcher of the main help file.

What it does is the following: for example if you send [jumptolabel cue20] (for your score after it’s loaded) into Antescofo, it’ll launch ALL “global” actions from where you are currently (from 0 location if you are nowhere) until that label.

Obviously, if you have an action with “@local” attribute it’s going to be missed.

“@local” attribute thus for an action makes sense if it’s local to an event and does not have a global score. Global is the default behavior… . Example: A harmonizor parameter on a single note that be treated as local, whereas a patcher initialization should be treated as global. This way, your score will be more “fault tolerant” during performances. For example, if the note/chord/trill event corresponding to an initialization is missed, you won’t miss the initialization itself during live performance!

We have not exposed this command much (although very useful in concerts and rehearsals) because we fill that there’s something missing in practice… if you have any suggestions, it’d be more than welcome.

Thanks for bringing this up.