• State Not Answered
  • Date
    rautasami
  • Date
  • Replies 17 replies
  • Subscribers 5 subscribers
  • Views 1041 views
  • Users 0 members are here

3.2.1 questions and bugs

I'm wondering what is the logic behind log timestamps... Also it's pretty difficult to figure out what happened, cause when I open the H3 log in H3PC things look very different.

I have had quite a few times strange laggy output and when I monitored Art-net outputs the refresh rate is under 10 fps in my universes. After restarting the console everything runs fine. Any idea what might cause this?

I have managed to crash the desktop many times, when I have tried to open the DP settings from network window (using right click). I think there's a read out of bounds error in log when that happens.
I saved a log after that
dl.dropbox.com/u/18000606/Hog3/Network%20window%20crash.hlg

I crashed the desktop in CD burning. I created a folder to CD master, moved the files there and started burning. The disk had already files on it so it asked a folder again. I typed the folder and when I tried to start the burn desktop crashed. What happened can be seen in the log file at timestamp 69:39:11:306 dl.dropbox.com/u/18000606/Hog3/CDburning%20crash.hlg

I'm also wondering what are those post REFRESH_DMX to Desktop Failed!
errors in the log?

My system:
H3 + 2 x DP8K
DPs have cloned patch and outputting only Art-net (ID 1 2.0.0.10 and ID 3 2.0.0.13)
Parents
  • 0

    Lets break this down:
    The log viewer is meant for internal use by our software developers.
    We ask for this when a crash occurs beacuse its a snap shot of what the desk was doing right before the crash.

    Point taken.

    Laggy output using artnet:
    Was this just in playback or also during programming?


    It's affecting both.
    Also, like I mentioned before the refresh rate of the universes drops dramatically. (and it's different in different universes)
    I used Luminex Luminet Monitor V2 to monitor the output.
    The lag could be seen also in the fixtures... the delay was more than two seconds and no fading.

    Next week I will upgrade to 3.2.2 and see if the problem goes away. If not I will test this again with different switch and running only with one DP.
    If I manage to make the lag happen again I will check if it happens also with DMX outputs.

    Desktop Crash when performing right click to open DP setting:
    Tested this on a Road Hog and a Hog 3 and did not crash the desk.
    I will need to look into this some more.


    This is happening here pretty often, but not always (like the laggy output)
    and like I said there's always that read out of bounds error.

    Desktop Crash when buring a CD:
    Did you use the internal keyboard to name the folder? We did have a bug in 3.2.x
    that would crash the desktop when using 'enter' on the internal keyboard. This is fixed internaly and will be included in the next patch.


    I used external...I will check if I can repro it.

    Can you please upload your show file?
    wetransfer.com/
    MGRAHAM@barco.com


    I will send it tomorrow.
Reply
  • 0

    Lets break this down:
    The log viewer is meant for internal use by our software developers.
    We ask for this when a crash occurs beacuse its a snap shot of what the desk was doing right before the crash.

    Point taken.

    Laggy output using artnet:
    Was this just in playback or also during programming?


    It's affecting both.
    Also, like I mentioned before the refresh rate of the universes drops dramatically. (and it's different in different universes)
    I used Luminex Luminet Monitor V2 to monitor the output.
    The lag could be seen also in the fixtures... the delay was more than two seconds and no fading.

    Next week I will upgrade to 3.2.2 and see if the problem goes away. If not I will test this again with different switch and running only with one DP.
    If I manage to make the lag happen again I will check if it happens also with DMX outputs.

    Desktop Crash when performing right click to open DP setting:
    Tested this on a Road Hog and a Hog 3 and did not crash the desk.
    I will need to look into this some more.


    This is happening here pretty often, but not always (like the laggy output)
    and like I said there's always that read out of bounds error.

    Desktop Crash when buring a CD:
    Did you use the internal keyboard to name the folder? We did have a bug in 3.2.x
    that would crash the desktop when using 'enter' on the internal keyboard. This is fixed internaly and will be included in the next patch.


    I used external...I will check if I can repro it.

    Can you please upload your show file?
    wetransfer.com/
    MGRAHAM@barco.com


    I will send it tomorrow.
Children
No Data
Related

www.etcconnect.com