alert time in eos

I loved the alert time too - it was a great feature  - is it so difficult to program it in EOS?The Thread started 20 months ago......

nobody said it was difficult. but there are a lot of people who want new functions in eos, and alert time is just one line on a list that's multiple pages long

I want the alert time too !

And I know my collegues in the Opera want it too.

That feature was really appreciated in our old system (Prego).

We've tried some workarounds in eos but so far we haven't found anything useful.

So please... move this "line" upwards :) if it is not difficult to apply!

Internal Timecode?
Start with the first GO for the show.
Every press at GO-Button will be record.
With this timings you can create a Macro fire by the timeline.
And in a Magic Sheet see it.

Just an Idea.
Never try it.

Out of Topic:
Och,....for me is a real Darkmove more important...*GGGG*

I keep seeing this but in all of the threads there has never been a description of what "REAL DARKMOVE" means.

Presumably it is some convenience shortcut to doing something the console (or fixture) is already capable of doing some other way or it would garner more support.

sk8rs_dad there was an old german brand of lighting consoles that used the term Darkmove for what is now automark. it could do some things more than automark can do now (and some things less) but the biggest difference is that it tolerated sloppy programming by ignoring FCB move instructions if Intens=0.

Louis internal time code counts upwards. the whole idea of alert is a countdown. yes you can get it to show e.g. a magic sheet after a certain amount of time but the alert time function is meant to create less work rather than more work

sk8rs_dad there was an old german brand of lighting consoles that used the term Darkmove for what is now automark. it could do some things more than automark can do now (and some things less) but the biggest difference is that it tolerated sloppy programming by ignoring FCB move instructions if Intens=0.

Louis internal time code counts upwards. the whole idea of alert is a countdown. yes you can get it to show e.g. a magic sheet after a certain amount of time but the alert time function is meant to create less work rather than more work

I guess using "Record Only" instead of "Record" may fill the gap to some degree.

in most situation it's caused by working in CueOnly

And you can give different Movetimes for every parameter.
Also change this timings via setup individiual during a running show.

With EOS you can only give one Movetime and change it only global for all parameters.

I need different times for Scroller and MH Movement.
How do it on EOS?


And,..it is NOT a question of sloppy programming...

discrete timing allows you to change the mark time for every single parameter in every single cue, which is something Darkmove couldn't do ;)

Not really.
The question is not programming a show.
The question is do changes in the show.
Then you often get useless moves of Scrollers for example.
Clean Up later in Blind is not comfortable.

But if the Desk will ingnore all Moveinstructions if an Intensity is at Zero, the problem is solved.

Different move times are set using discrete timing.

I can.
I must only load via Macro a change in M651.
Thats works in backround
And,...then i can give in my "PSD" a Name for this macro that told me what happen.
How do i name a Macro at EOS in PSD???

And i NOT need in every cue a new Movetime.
I need global different Times for P/T and Scrollers.
With your methode i programm for every move they do in every cue a different discrete movetime?
I also ever though Mark and Automark are for give less work, not more...

You can use query to select fixtures by their type and apply the mark time you want as you program the show.

Query Fixture_Type [Scrollers] Marking Time 7

Query Fixture_Type [Not Scrollers] Marking Time 2

etc. (I’m not in front of a desk right now, so let me know if the syntax is off, but it’s something like that)

If you want to make global changes, yes, that would take longer, and that’s why we keep seeing requests for a query function to select groups of cues, but you could make a macro that loops as many times as you have cues that runs this query, clears the command line, and proceeds to the next cue. It would probably need wait for enters in it so that you have the opportunity to clear the command line if the syntax error of “no channels selected“ comes up, otherwise you’d just change the timing of every cue in the show, but it would turn a million keystrokes into enter, enter, shift clear, enter, etc...

Of corse I can do many.
But thats all says, the Desk CAN`T do it automatic...

A real Darkmove can...

I had hoped to be done hijacking this thread to discuss darkmove yet again. I suspect the way default parameter times might be implemented in some future release would be with time palettes and the default preset. That presupposes time palettes ever get implemented.