Stop/Back request

This behavior is the long-standing preference of many users, myself included. It's the way that the Obsession series works, but it is not the way that the Expression series works. The Back button is not a Go-last button, and it has special rules  Back is treated much the same way as an out-of-seque move like Go to Cue  

There is probably a case to be made for an option when fader controls and playbacks get refreshed, but the default behavior is pretty well baked in at this point. 

i would avoid making Loops with links because of the problem you have described. Instead, you might look at Building a second cue stack or an effect. 

all the best;

P

This behavior is the long-standing preference of many users, myself included. It's the way that the Obsession series works, but it is not the way that the Expression series works. The Back button is not a Go-last button, and it has special rules  Back is treated much the same way as an out-of-seque move like Go to Cue  

There is probably a case to be made for an option when fader controls and playbacks get refreshed, but the default behavior is pretty well baked in at this point. 

i would avoid making Loops with links because of the problem you have described. Instead, you might look at Building a second cue stack or an effect. 

all the best;

P

Hmmm... well if it's the preference of the majority fine, although having no history on the obsession or the expression series myself (I came from Strand, which IIRC does behave as I described, but I'd have to check to be certain) I don't agree personally.

I'm not quite sure I understand what you mean by the "The Back button is not a Go-last button, and it has special rules Back is treated much the same way as an out-of-seque move like Go to Cue ". I can't see Stop-Back described in the manual section regarding out of sequence cues, for example. I do see from the manual, however, that "pressing [Stop/Back] will step backwards sequentially through the cue list from that point." What I hadn't realised is that for [Stop/Back], sequentially is purely in decreasing cue number, and does not respect links.

This effectively means that links and loops should never be used by the look of it, which is a shame when the director asks you to move the interval part way through a run, as happened to me, and was achieved using links rather than by physically changing the cue numbers or copying the cues. This was on a Strand GSX and it did correctly step back through the moved interval when required to do so during a technical check.

Anyway, if the way it works is how it's meant to work and how people want it to work, so be it, although personally I don't think it makes sense.

Speaking broadly, there are two models for the "opposite of Go" button on lighting consoles:

•A straight "step back" function, (used on Obsession and Eos), which always moves the playback to the previous numbered cue, using the "Back Time" you set in setup.

•A "Go Back" function, (Expression/Express, and others), which moves the the playback to the previous cue, and usually uses the time of the previous cue for the move.

There's no right answer on this topic.

I use links and loops when I build sequences on auxiliary cue lists, and I use them in my main cue stack as a quick temporary way of skipping cues in rehearsal.  But I never leave a link in my main list for the reasons you suggest.