• State Suggested Answer
  • Date
    Ryansearle
  • Date
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 187 subscribers
  • Views 680 views
  • Users 0 members are here

BUG - Submasters not unmarking

Having weird issues with submasters not adhering to an off & unmark command via macros.

Multiple submasters being sent to 0 with unmark at 0 not unmarking. 

Also have seen iterations where it has turnt on other submasters that haven't been told to turn on. It is a repeatable issue but the same channels do not get turnt on each time it happens. 

This is a critical issue as submasters are holding intensity & NP's in submasters that are not active. Have split up submasters being sent to zero and also have tried sending them to zero multiple different ways with the same issue being repeated. This is also true on newer versions of EOS.

Have a large multi console system with 5 consoles across multiple studios, all on a user & partitioned control. 

Happy to send over the showfile. This is on a large system which doesn't have any down time and is active 24/7. on v3.2.5.13

Parents
  • 0

    Perhaps related, I just submitted a bug about submasters maintaining 0 intens when layered with other playbacks. Here's the bug report I sent in:

    Steps to reproduce:
    Sub 11 Full
    Sub 20 Full
    Sub 11 Out
    Sub 20 Out

    Group sub 20 will have yellow zeros and are no longer controllable by sub 11.

    In my case I'm just running the subs manually, and sub 20 is priority 5 with an effect. v3.2.7.

  • 0 in reply to Taylor C Jensen

      Thank you for submitting your showfile and steps to recreate the issue.  I found that in your case, it is unrelated to Unmark at 0%. Instead it is caused by Sub 20 having a higher priority (P5) than Sub 11 (P4). 

    I could reproduce the issue from scratch (after a Deep Clear):

    1. Chan 1 Full, Record Sub 1
    2. Chan 1 Effect 1, Record Sub 2
      // Chan 1 is running a basic linear effect
    3. Clear - Sneak - Enter
    4. Sub 2 {Properties} Priority 5
    5. Sub 1 at Full
    6. Sub 2 at Full
    7. Sub 1 Out
      // Allow it to complete
    8. Sub 2 Out

    Result: Chan 1 still controlled from Sub 2 (yellow text), at level 0%

    Expected: Chan 1 released from control.

    Note: Setting Sub 2 to Full a second time, then Out, will cause Chan 1 to be released from control. 

    I filed this bug report: [EOS-55725] Higher Priority Sub does not release control when another sub had control then released it

    I found that this was broken sometime during v3.1.1 development - it works correctly in v3.1.0, but not in v3.1.1 and higher.  

  • 0 in reply to Matt Pumplin

    Thanks for the info Matt. I've noted this bug number and look forward to seeing it resolved in a future update.

Reply Children
No Data
Related

www.etcconnect.com