• State Not Answered
  • Date
    Reid36325
  • Date
  • Replies 23 replies
  • Subscribers 5 subscribers
  • Views 1344 views
  • Users 0 members are here

Sloooow Rollin'

My Road Hog recently decided to take ages to go to a cue. If anything on the console is above 0s, it makes twice the time to fade. Most of the cues I have are 3s because of the venue being a church. But occasionally I and a colleague use the console to program other (more exciting) shows. Loops that are 3 step loops at .2s a pice are 2 whole seconds between cues. Release times are about 12 seconds to release.
I updated the software Sunday to 3.2.5 and it did not do anything to help. Noting to my knowledge has changed. (Default times, etc.) The actual software is just sluggish. Even when I checked integrity it took it a good 6 seconds to process it.
So...What's up? (My inside says: WHATS WRONG WITH MY BABY??)

Thanks for the help.

(This may very well be operator error done by a volunteer that somehow got really deep down in a menu and screwed something up that I simply didn't think to check, though I doubt it.)
Parents
  • 0
    [QUOTE=ChrisTall;62112]
    Eric, it seems like it is hardware related.


    Maybe, maybe not. Some piece of hardware could be failing and the OS is spending most of its time in error handling. But someone could have configured aggressive power management in the BIOS and the system is trying to go to sleep when it really needs to be running cues or a dozen other non-hardware related issues. I just don't have enough information to say for sure. That's why I've suggested a number of troubleshooting steps like wiping the hard drive and defaulting the BIOS settings.

    [QUOTE=ChrisTall;62112]
    So what do you guys use to reference cue timing?


    The Hog software is an application and thus depends on the underlying OS for all of its timing requirements. In the case of a Road Hog the OS is XP embedded. Modern OS's have a variety of ways to say "Wait 40 ms then do this" and "How long has it been between these two times" and other time related functions.
Reply
  • 0
    [QUOTE=ChrisTall;62112]
    Eric, it seems like it is hardware related.


    Maybe, maybe not. Some piece of hardware could be failing and the OS is spending most of its time in error handling. But someone could have configured aggressive power management in the BIOS and the system is trying to go to sleep when it really needs to be running cues or a dozen other non-hardware related issues. I just don't have enough information to say for sure. That's why I've suggested a number of troubleshooting steps like wiping the hard drive and defaulting the BIOS settings.

    [QUOTE=ChrisTall;62112]
    So what do you guys use to reference cue timing?


    The Hog software is an application and thus depends on the underlying OS for all of its timing requirements. In the case of a Road Hog the OS is XP embedded. Modern OS's have a variety of ways to say "Wait 40 ms then do this" and "How long has it been between these two times" and other time related functions.
Children
No Data
Related

www.etcconnect.com