I have a show that has been running on the same console every week for 7 years and it has been run on almost every version of the Hog 3 in that time. Currently we are running 3.1.9 I started having issues at version 3.1.8. Sometimes when running the show the console will jump to the last timecoded cue in the show, it has done this three times at completely different times in the show, beginning middle and toward the end. Incoming timecode has not changed and comes from a Tascam 2424. What could cause this and how to prevent it. This is very dangerous becauase the last cue in the show that it always jumps to fires confetti.
This must be very annoying for you. i never change software in a long running show, when everything is stable. In this situation i should downgrade and take no risk in the show.
[QUOTE=Hans B;53556]This must be very annoying for you. i never change software in a long running show, when everything is stable. In this situation i should downgrade and take no risk in the show.
If this console was never downgraded it would still be running version 1 and all the bugs that come with it.
You said "This is very dangerous becauase the last cue in the show that it always jumps to fires confetti."
I understand that your show has been running for many years, but please be aware that it is not standard practice to operate non-lighting hazardous systems via DMX. In fact the DMX specification warns against this. If you are going to use DMX to trigger something like this, it is suggested that a "dead-man" switch is used within the system to require human interaction before the trigger can occur.
I just wanted to make this clear for yourself and others who may be reading this thread.
Lighting Consoles and DMX should *never* be used to control anything dangerous like pyrotechnics, motion control, or aerial launchers. DMX has absolutely no error detection, so a momentary glitch or line noise can cause unexpected activation.
Even if you ignore the DMX issues, lighting consoles are not developed to the level of fault tolerance necessary to control hazardous systems. If running a cue unexpectedly is causing dangerous conditions on your stage, then you need to re-design your control system for that hazardous effect.
This advice isn't specific to Hogs or HES/FPS/Barco, It applies to any lighting console.
I am having the same issue sporatically with my Road Hog console running SMPTE 30 over LTC widget. The playback will snap to the last cue containing a timecode value. It only happens at one of two times (the show has two timecoded segments, and for the section between them another cueslist is run manually), and both of those are when timecode has just been enabled on the list. It never occurs in the middle of a timecoded segment, only when timecode starts up after a period of being stopped. This issue seems to occur most often only in the second or later show after the console is booted. Also there seems to be no way to predict when it will or will not go wrong, sometimes it goes a month between occurences and sometimes it is twice in the same week.
The console is running 3.2.1 although the issue was present before that upgrade I believe. My "Jump after" setting is 60 frames to give SMPTE plenty of time to stabilize and also I have tried more than one LTC widget with no difference.
It is a nuisance because the first cue in each segment is a slow fade up and only with a couple of lights, whereas the last cue in the show is the brightest state of the whole show so essentially it blasts the whole audience with bright light and completely ruins the opening of the show because it takes a few seconds to correct it each time.
Any advice/assistance in any form would be greatly appreciated.
