BUG - Submasters not unmarking

Question

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

Matt Pumplin · Answer

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): 
 
 Chan 1 Full, Record Sub 1 
 Chan 1 Effect 1, Record Sub 2 // Chan 1 is running a basic linear effect 
 Clear - Sneak - Enter 
 Sub 2 {Properties} Priority 5 
 Sub 1 at Full 
 Sub 2 at Full 
 Sub 1 Out // Allow it to complete 
 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.

BUG - Submasters not unmarking

Top Replies