DP refresh rate

I've re-installed a Hog 3 on a local Christmas show in it's third year. The show file is a continuation from the first year with some fixture changes and additional programming. It seems that all timed functions of the cues run much faster than last year. There are some new fixture types in the rig now that don't have very good dimmer curves but the faster rate appears global (including desk channels). One thought that I had was perhaps the rate was actually slow in the older software and now everything is up to speed. Is there documentation to support what I'm seeing onstage? Does the refresh rate of the DP impact timing functions? I noticed that the DP on this desk is set at 25 Mhz. What is the normal refresh rate?

SWV 2.2.2 installed.
Parents
  • The normal refresh rate is between 25-30. I wouldn't think that to be the problem here though.

    Have you changed any of the components that the DMX passes through? Opto-splitters, etc.

    Are you running off of SMPTE? Is the SMPTE coming off a device that uses a hard-drive rather than tape?

    I would say that a more likely culprit would be SMPTE coming off a device that uses a hard-drive. When changes are made to the SMPTE code it is never a simple "add 2 seconds and 10 frames here" kind of thing. I've done entiire shows where all the SMPTE needed to be "re-learned" and adjusted because changes near the beginning of the code. My suspicion is that the hard-drives' seek and retrieve time is never consistent and this can screw things up down the line in an exponential manner once a change is made to the code. Once adjusted though things played back as they should.
Reply
  • The normal refresh rate is between 25-30. I wouldn't think that to be the problem here though.

    Have you changed any of the components that the DMX passes through? Opto-splitters, etc.

    Are you running off of SMPTE? Is the SMPTE coming off a device that uses a hard-drive rather than tape?

    I would say that a more likely culprit would be SMPTE coming off a device that uses a hard-drive. When changes are made to the SMPTE code it is never a simple "add 2 seconds and 10 frames here" kind of thing. I've done entiire shows where all the SMPTE needed to be "re-learned" and adjusted because changes near the beginning of the code. My suspicion is that the hard-drives' seek and retrieve time is never consistent and this can screw things up down the line in an exponential manner once a change is made to the code. Once adjusted though things played back as they should.
Children
No Data
Related