• State Not Answered
  • Date
    strobie1
  • Date
  • Replies 29 replies
  • Subscribers 22 subscribers
  • Views 1217 views
  • Users 0 members are here
Options
Related

help

Hi, as mentioned before this has been happening on another show. running latest version, on pc with nano for programming.

hog 4 pc becomes unresponsive and must be forced to close, and end process on all 5 processes after doing any of the following:

while after starting a new show, it crashes every time i try to record a cue or list to a master.(now wont record any cue lists anywhere) even after re install, restarting ect.

after naming a bunch of scenes or cue lists.

updating a cue in a list

------------------------------------------------------------------------

after starting new show, opening patch window and loading fixtures is, selecting the fixtures, i press @ and nothing happens. if i restart it works.

hog 4 disappears occasionally from my screens but is still running in the back ground.

every time any of these instances above occur, hog 4 pc is still outputting dmx, and play back still works, even if hog is not actually running on the screen.

i have a major festival in 2 days time, site programing is to commence in less than 20 hours from the time of this post. ive already tried your hotline, nobody answered. I'm in Australia. please help.


i had no problems with the last update or any of them really except for that ftdriver issue, now total chaos. i should mention that the file runs fine on fb4, but that doesnt help me now while programming on pc.
Parents
  • 0
    Of course! We are here to help you guys and want to you to know some one is there.

    Assuming these crashes are repeatable with the show file, (are they?) Then it helps Michael/Chris duplicate the problem.

    Are there any specific steps on any one of the show files which would always produce the crash? Repeat-ability not only helps recreate the issue so the SW guys can see it happen for de-bugging, it's probably just as crucial when a potential SW fix has been done to test against.

    Countless times we get show files where there is a crash, but we are unable to re-create it in the test lab, so it becomes difficult to know if the fix is correct.

    While I'm thinking about it, you didn't by chance send any of the .log files from the console. Most times when the console experiences a crash, it creates a dump file. If created, this is located in the 'Logs' folder in the file browser. SOMETIMES (not all) sending these log files along with the show file can be helpful, as the give the SW guys a little more data about what the console was doing when it crashed.

    If you experience a crash, AND it's repeatable, I would go and delete any old log files from that folder, re-create the crash, and then send that log file in with the show file.

    v2.6.0 really had one major change in it, and that was the show-file compression to essentially reduce show file size and add a bit of efficiency.

    Michael should be back to you soon.

    Anyone can also feel free to email me directly paul_hancock(at)highend(dot)com.

    Hope this helps,
Reply
  • 0
    Of course! We are here to help you guys and want to you to know some one is there.

    Assuming these crashes are repeatable with the show file, (are they?) Then it helps Michael/Chris duplicate the problem.

    Are there any specific steps on any one of the show files which would always produce the crash? Repeat-ability not only helps recreate the issue so the SW guys can see it happen for de-bugging, it's probably just as crucial when a potential SW fix has been done to test against.

    Countless times we get show files where there is a crash, but we are unable to re-create it in the test lab, so it becomes difficult to know if the fix is correct.

    While I'm thinking about it, you didn't by chance send any of the .log files from the console. Most times when the console experiences a crash, it creates a dump file. If created, this is located in the 'Logs' folder in the file browser. SOMETIMES (not all) sending these log files along with the show file can be helpful, as the give the SW guys a little more data about what the console was doing when it crashed.

    If you experience a crash, AND it's repeatable, I would go and delete any old log files from that folder, re-create the crash, and then send that log file in with the show file.

    v2.6.0 really had one major change in it, and that was the show-file compression to essentially reduce show file size and add a bit of efficiency.

    Michael should be back to you soon.

    Anyone can also feel free to email me directly paul_hancock(at)highend(dot)com.

    Hope this helps,
Children
No Data

www.etcconnect.com