Cutting through cues quickly

Thanks, Jon. I understand I can do it with macros - but I feel that there should be a way to do it by default. After looking into it more, I've worked out that I can either disable playback timing, and re-enable it afterwards ... or [Goto Q][Next][Enter]. But they're both long-winded ways to do what I used to be able to do in a single convenient keystroke on the Strand.

Holding down timing disable and Go will cut the pending cue.  Time Disable and Back does the same with the last cue.

a

Thanks Anne - that answers the question as far as the Eos is concerned. What about the Ion, though? Timing Disable is hidden on a context-sensitive softkey. What about being able to hold down Fader Control and hit Go? Not sure whether that would be a workable idea - but it would be great if there was some way of doing it quickly and intuitively with only a couple of keystrokes.

Understood.   Well, the load button used alone is intended to assign content.  And we already have a plan for holding down load and using either go or stop.  Will ponder.

thanks,

a

I thought the Shift key was something that wouldn't be appearing for a little while yet?

1.9.8 includes the Shift key. This version recently went to open beta so it should become generally available shortly (see footnote).  If I were to speculate, I would expect 1.9.8 to be available the same time Gio starts shipping.

Footnote:

In the words of Anne V....

"Shortly" is a weasel word often used by developers and marketeers to explain a time frame in which several unpredictable unknowns exist. ... "Shortly" seems to be the word that most defines our goals, without promising dates that we may simply be unable to meet.

[Shift] [Go] would be awesome.  That would make to very useable for the ION users.

-Steve Martin

[Shift] & [Go] would be good on the Eos too (it'd be easier to one-hand it as opposed to the awkward one-hand [Timing Disable] & [Go] ). [Shift] & [Stop/Back] as well, of course...

-M

So where is the Shift key going to go on both desks? I guess it'll be a keycap swap somewhere on the Eos? But from what I can recall based on my short time with the Ion so far, there aren't any unused keys on the face panel?

Funny you should ask...

Currently Shift replaces the Follow/Hang key on the Ion, and the follow/hang action has been moved to Shift+Delay on the adjacent key (or Cue + Softkey).

There's a school of thought that wishes it were the Escape key. No matter where it goes there are some operations that become two-handed so I believe the current placement will hold up for the 1.9.8 release and may get revisited if user feedback dictates something else.

Hmm. Personally I think I'd prefer to retain the follow/hang key and make delay a shifted function of that. But I guess it's quite a personal thing.

I wouldn't want it to be the escape key - doesn't strike me as being in the right sort of area on the face panel.

I believe the reasoning behind replacing Follow/Hang was a combination of location and utilization. Shift is certain to become a frequently used key so putting it on the corner of one of the key clusters makes sense. As for utilization, early beta testers reported that discrete timing was changing the way they built cue lists, the trend being to use discrete timing and delay to build single cue in preference to  using follow/hang across multiple cues. It's one of those debatable design issues where asking 100 people will get you 100 different preferences.

I can totally see the rationale behind putting it in the corner of a key cluster.

I can also see your point about discrete timing being something which changes the way people think about programming sequences with multiple timings - personally, I haven't used our new desks enough yet to be able to say whether that'll be the case for me (although I suspect it might, as I like the way it works and I've used discrete timings a little bit on other desks). My comment in my earlier post was based on my experience with plotting on Strand desks, and I'm sure the process of altering my thinking to migrate more effectively to ETC will gather pace as soon as the start of our next season arrives and I start using the consoles in earnest.

I can totally see the rationale behind putting it in the corner of a key cluster.

I can also see your point about discrete timing being something which changes the way people think about programming sequences with multiple timings - personally, I haven't used our new desks enough yet to be able to say whether that'll be the case for me (although I suspect it might, as I like the way it works and I've used discrete timings a little bit on other desks). My comment in my earlier post was based on my experience with plotting on Strand desks, and I'm sure the process of altering my thinking to migrate more effectively to ETC will gather pace as soon as the start of our next season arrives and I start using the consoles in earnest.