playback release after clock change

After changing the clock of my RH4 all running playbacks were released. Did someone had the same issue? How to fix it?

Comments

  • Michael_GrahamMichael_Graham Registered User, Super Moderator, HES Staff
    Are you changing the date/time of the console?
    If yes then a pop up should appear asking you to confirm the change, if you hit apply then the console will log out of the current show. This is expected behavior.
  • Go_ButtonGo_Button Registered User
    Yes I was changing the console clock. But why is a log out necessary? The following happened. Our director asked us to match our clocks about 5 min before the show starts. I didn't expect something like a log out because of a simple time change. The audience was taking seats when suddenly the hole venue got dark. I was getting really angry about a behavior like this, because keeping the DMX output alive should be the highest priority of a console.
  • Michael_GrahamMichael_Graham Registered User, Super Moderator, HES Staff
    When you change the date and time we ask you to log off/on in order for the change to commit.
    Output should have stayed until you logged back into your show file.
  • sandersander Registered User
    Interesting! This one was once requested already...
    https://forums.highend.com/index.php?p=/discussion/comment/68803/#Comment_68803
    nice to bump this again.
  • MLorenzMLorenz Registered User, Hog Beta
    Sorry to say, the console doesnt log out on its own. You need to confirm that.
    Time and date change and also external monitors resolution change still require that log off/reboot.
    As I have been told this will be resolved when the new Linux Kernel is implemented in of the next major releases.

    The output will stay until you reboot or log back in your show.
  • Go_ButtonGo_Button Registered User
    Thanks for that information.
  • stephenwykerstephenwyker Registered User, DL Beta, Hog Beta
    Lets not forget a screen calibration also requires a reboot ...
  • Go_ButtonGo_Button Registered User
    Keeping the DMX output and all playbacks alive should be the highest priority of a lighting console! @ HES this is beginner level! I really have no words for this.
  • Simon LXSimon LX Registered User
    But we know that either a time/date change or a monitor calibration requires a reboot. Quirky and annoying, but that's the way it is. So don't do it at 'mission-critical' times. A reboot is the software turning the desk off and back on again - no desk will hold its DMX output or playbacks alive when you do that!
  • Go_ButtonGo_Button Registered User
    Incorrect. GrandMA does. You can shutdown the system and start again with no DMX dropouts. The console starts with exactly the same values before the reboot. You can do this during a live situation and nobody will take notice of this.
    We are an operating company. We own different types of lighting consoles like GrandMA, Martin M1, Camsys and Hog4. We often speak about advantages and disadvantages. Actually the Hog is the lighting console with the most incomprehensible issues and the least functions. What I like to hear is whether HES is working on a solution or not. At some point we need to take the decision if we stop the cooperation with HES or not. Saying" it is what it is" is not the right way. Time is going forward but HES seems to be far away....
  • MLorenzMLorenz Registered User, Hog Beta
    But I guess only when you have external NPUs....
    If you have your DMX Output local and shutdown your system you wont get any output?! Or?!
    Also thru a reboot I guess...

    And there is good and bad everywhere:
    ... try to change your patch in the middle of a programming session with multiple consoles or add same fixtures without having everybody to stop working... This is something other brands should also think of...
  • Go_ButtonGo_Button Registered User
    If you do a reboot the GMA is keeping the DMX output alive even if you use the local outputs. Did this twice last year during a show.

    I don't wanna say everything on HES is bad but the software has some really illogical behaviors.
    Some are so basically that I have no words. Of course HES don't need to copy everything the others do. But issues like this one don't make it easier to trust the HES System.
    @HES please think about your priorities!
Sign In or Register to comment.