Cut button

[Kirkup_xp]

We've been working through a tech this week and an issue has come up with long crossfades.

 

We're using a lot of 2/3 minute crossfades, and even with the override wheel set to full they still take a good 30 seconds to run through. Would it be possible to impliment a keypress to 'cut' to a cue. Perhaps F4 + Go? Basically that would activate the cue in a time of 0s, with all attributes snapping to their values. It would be REALLY useful during tech-rehearsals when we quite often have to re-run sequences.

 

My suggestion for the user interface side of things would be to use the normal method of selecting a cue, and then pressing F4 + Go. If you're already running into a cue, all you'd have to do would be select that cue again in the cue stack and press F4 + Go to finish it.

 

Another useful thing which I know has been mentioned before but really would have helped would be a way of seeing the progress of the Playback X fade times. Is there any way we could have a little counter, on the bottom of the memories screen - "Current Fade: xx%"

 

Thanks

 

 

Peter

[K-Nine]

The 'Cut' feature sounds like a good idea and shouldn't (?) be too difficult to implement.

 

Frog Reference 5486 - 'Cut' Function - providing the ability to Go to the Next memory ignoring all timings, ie snap to programmed levels.

 

As to the fade indicator, this has been mentioned before, CLICK HERE.

 

Frog Reference 5433 - Indicate the time remaining or % through a memory on the memory stack (Playback X) on the monitor screen.

 

The question is, with fade up, fade down, LTP fade and dwell times making up the total duration of the memory - what do you take as 'the fade time' in order to determine the % of how far through you are ?

[Kirkup_xp]

I suppose you could have an indicator for all 3. Or maybe it could use whichever is the longest, thus giving you the reading relative to 'completion' of the cue.

[K-Nine]

That's kind of one of the problems - do you regard the 'end' of the cue as being the end of the fade up, fade down, end of the HTP (brightness) cross fade (whichever is the longer of the two), the end of the LTP fade, if longer than the HTP fade, or at the end of the dwell time ?

 

Some people would regard the end of the fade (HTP or LTP) when the outputs have reached their programmed state as the end of the fade or cue, and the dwell time as irrelevant 8O

 

The dwell time is only really applicable if the next cue is automatic and represents the time that the current cue remains at it's outputs levels before the next cue is triggred

 

... as I have discovered recently while working on a new specification/design, this is sometimes known as the 'wait' time of the next cue 8O

 

Either way, the resultant outputs are the same - it's just that the time is associated with a different cue.

I gather this is one of the reasons why some users have been confused by dwell times 8O

[Kirkup_xp]

Thanks for explainng the problems, K9. I appreciate that its not an easy thing to impliment, but there must be something that can be implemented to show how far through the cue you are.