assurance-tunnel
assurance-tunnel
assurance-tunnel
assurance-tunnel

[ANSWERED] Counter limit/wrap



  • Hey Folks -

    I'm installing a permanent installation that runs fine for about 5-10 times then freezes in the second scene.

    I read in the forum that it could be a problem with the Counter actor being set to limit rather than wrap. I switch to Wrap but the problem is persisting- although perhaps it changes slightly? With Limit it seems to get stuck on a scene + even tho' I can click/highlight other scenes in the timeline, nothing actually changes.WIth Wrap it simply remains in the second scene + never jumps forward.

    Running on a Mac mini w High Sierra
    Izzy 3.02

    Any suggestions warmly appreciated



  • Of course I meant to attach the patch!

    Panofsky_F7



  • Try setting the "Sequential Trigger" in the second scene to 4 instead of 5 outputs. (The fifth outup is not connected to the Envelope Generator, so the envelope end trigger won't set Sequential Trigger back to step one. This can cause that you get stuck in scene 2.)



  • @streetpictures said:

    I read in the forum that it could be a problem with the Counter actor being set to limit rather than wrap.

    I am not sure what you read, but I am quite sure the Counter actor behaves as expected. (I have a feeling the post you might of read had to do with using an increment that is not 1... I remember some discussion about this but don't remember the exact post.)

    That patch looks sound to me. Movies 3-7 are 1280x1024 HAP movies, which also seems fine. What I guess I would look for is some situation that is repeatedly triggering the Movie Player and rapidly changing the 'movie' input -- I suppose if the speed with which movies was very extreme, you might get stuck in a scene. I would, just in case that's the issue, put a Multi Blocker after the Counter and before the Movie Player to ensure the 'movie' input doesn't change too fast.

    I see that your patch uses serial input, but I guess that's only to get from Scene 1 to Scene 2. So some some wildly varying serial input is probably not the issue.

    So, basically, I don't see anything that raises a red flag for me. If you continue to experience this problem, open a ticket and one of our team will work with you to get the patch and the media so we can try to recreate the situation.

    Best Wishes,
    Mark



  • @mark @streetpictures

    I think I had the same behavior on a Mac Pro 5.1, Izzy 3.02, OSX Mojave. I actually can't replicate it anymore on my MacBook Pro 2013 with High Sierra and I can't get onto the other machine anymore.

    It only happened when often switching between some specific scenes in the project. It wasn't to much of an issue, as it only happened when I was checking some things and jumping back and forth between those scenes. Just going through the scenes on show always worked.

    When the issue appeared, the GUI seemed to freeze. I still could switch between scenes and most of the action (playing video - fade to black, etc.) supposed to happen on stage in these scenes when they where activated, did work like they should do. But as the GUI got stuck in this specific scene it wasn't possible to work with it anymore. I could even save the state and restart the project, which then worked fine until the next time.

    These scenes weren't very complex, having only one movie player playing 1 HD movie, and two projectors with a soft edge configuration (with chop pixels and zoomer). Beside that an envelope generator and a comparator.

    Edit: there are as well some enter scene triggers only triggering some text trigger that shows up in a text controller or triggering midi controllers to reset a midi board.

    Best
    Delil


  • Beta Platinum

    @dillthekraut said:

    the GUI seemed to freeze.

     We did see this in the beta testing phase but it could never be reliably replicated. I have not seen or heard of this behaviour for many months until now.

    Best wishes

    Russell



  • @dillthekraut said:

    It only happened when often switching between some specific scenes in the project. It wasn't to much of an issue, as it only happened when I was checking some things and jumping back and forth between those scenes. Just going through the scenes on show always worked.

     OK. Well, if you come across this behavior again, let us know by opening a ticket quickly so, if it's related to a specific machine, we can try to help.

    Best Wishes,
    Mark


  • Tech Staff

    @bonemap said:

     We did see this in the beta testing phase but it could never be reliably replicated. I have not seen or heard of this behaviour for many months until now.

     Thanks to the fabulous @aled2305 and @Andy-Delmaine we got a repro for this during the Werkstatt. Mark has sinced fixed it and a related bug in the most recent internal beta so the next public release will have it sorted. (Finally my white whale is has been slain!)



  • @woland said:

    Mark has sinced fixed it and a related bug

    Ooops! I did? Wow I'm awesome! Except that, uh, I have no idea what bug you're referring to. (Make sure to tell me which bug it was.... totally spaced out on this.)

    Anyway, if @Woland says it's true I believe him. He's younger and his memory works better than the old man. ;-)

    Best Wishes,
    Mark


  • Tech Staff

    @mark said:

    He's younger and his memory works better

     Who are you? Where am I?! This isn't Applebee's!



  • Thanks all - - 

    I still can't figure it out - - only occurs after some number of instances. I don't think serial either as I'm only sending a change state ('near' 'far') that isn't doing much. I'll submit a ticket + go from there

    many thanks


  • Tech Staff



  • @woland I submitted a ticket before I saw this.

    woof

    I hope that was the problem. Will report back. Many thanks.