Scheduler

I haven't had any luck getting the scheduler working..

Hog 3 v2.3 b1928(edit) 2 DPs USB playback wing.

So here is what I did.

Opened a cuelist
double click in wait cell of cue I wished to trigger
Clicked on clock
set the date and time
clicked OKAY
pressed ENABLE CLOCK
held down OPEN and pressed CLOCK


at this point the time for the trigger is displayed in the Wait cell and I could see the Next Trigger Time/List/Cue

When the time came.. the cue was not trigered - instead the time changed to the word 'Clock'.

Am I missing something?

Thanks,
-Mark

Merry Christmas!!
  • I have also noticed that enabling the clock turns the 'is a chase' option off. It makes sense that you can't trigger a chase from the clock, just like you can't with SMPTE (at least directly) but could the enable clock button on the cuelist toolbar be greyed if you are in a chase list? Otherwise you could quite easily undo a chase accidentally. Something to be careful of anyway.

    Thanks
    -Mark
  • Hey Mark,

    Where did you get the 1923 from...?
  • Hey Mark,

    What values did you have in that cue? It seems to work fine on my desk. The cue will execute (showing the fade percentage in the cuelist window with a grey background) and then the word clock will appear in the wait column to indicate that the trigger is in the past.
  • One list I tried it with had a blank cue with a comment macro another one had maybe 6 desk channels at full for a curtain warmer.
  • Okay - I got it to work! The snag is I had to create a new cuelist. The clock trigger won't work with lists created in previous software versions.

    -Mark
  • [QUOTE=MarkScott]I have also noticed that enabling the clock turns the 'is a chase' option off. It makes sense that you can't trigger a chase from the clock, just like you can't with SMPTE (at least directly) but could the enable clock button on the cuelist toolbar be greyed if you are in a chase list? Otherwise you could quite easily undo a chase accidentally. Something to be careful of anyway.

    Thanks
    -Mark
    Just wanted to give this a bump - any thoughts on this?

    -Mark
  • Mark,

    We have not seen this problem in our offices. Can you please send me a show file via our uploader at: upload.highend.com

    Also what version was your show file created in? Please let us know which list(s) you had trouble with.

    thanks,
  • Hi Brad,

    The show should be uploaded now. It is called PLATIUM LIGHTING.

    Here is what to do.

    select PAGE 31
    select VIEW 6 "List"
    On Master 3 you should see List 76 "50/50" and on Master 6 List 128

    List 76 was created in a previous software version (can't remember which) List 128 was created in 2.3.0

    Make sure is a chase is enabled on both lists.

    Now on either list Enable Clock from the cuelist toolbar.You will see that Is a Chase is now unchecked. Now disable the clock from the toolbar and you will see that the Is a Chase is still unchecked.

    My concern is if you accidentally Enable Clock during the course of programing, when you come to a show your chase 'suddenly' doesn't work.

    It isn't a huge deal as long as you realize what happened but I could see it turning into a troubleshooting nightmare for someone who thinks his chases are randomly being turned off.

    Thanks.
    -Mark

    Edit: Hog 3 with 2 DPs 1 usb playback wing and two external monitors....
  • Mark,

    Ah I see what you are talking about. You are correct that clock functions do not work with chases. This is as designed. Once you have decided to make a chase into a clock triggered list, the list does not remember that it used to be a chase. I suppose that you could UNDO the changes (depending upon how many you make). However "accidentally" pressing many buttons can mess up a show. For example if you accidentally press "learn timing" then play your list, it will add times to all your wait cells.

    I will look to see if there are any changes we can make to prevent accidents such as you describe.

    thanks,
  • Thanks for taking a look, Brad.

    Like I said, it really isn't a huge problem, just something I noticed. And of course we should all take care when programming!!

    -Mark