-
-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: M5ATOM Listener Client Doesn't Tally PGM/PVW if Source is assigned to any ATEM Aux Output #738
Comments
Hello there allen-harris 👋 Welcome to TallyArbiter! Thank you for opening your first issue for the Tally Arbiter project. Tally Arbiter fosters an open and welcoming environment for all our contributors. Please adhere to our Code Of Conduct. If you have more to contribute to this issue, please comment down below! We will try to get back to you as soon as we can. |
Does it happen on TA v3.0.10? |
I believe it is the same on 3.0.10. I was struggling with 3.0.10, I upgraded to 3.1, then 3.1.1 to see if the problem went away.. I am in production right now, but I will try 3.0.10 tomorrow to confirm if the same issue is there. |
It would help narrow down. I implanted a different way of calculating tally as what was previously in place did not allow for multiple aux busses. |
(In 3.1.0/.1) |
I just spun up 3.0.10 and it is working correctly. |
Ok. This prob means we will need to fix all listener clients that reference an aux bus. I will try to look at it sometime. Feel free to look at the git history to see what I changed if you want to help. |
I will take a look. |
Looking through the history, this issue is mentioned here. |
Makes sense. This was merged June 22 and v3.0.10 was released in April. |
What happened?
I am using 6 M5Atom Listener Clients with TA monitoring a BMD ATEM 8K Constellation. If the source is assigned to an AUX out, it tallies the Aux colour but doesn't tally when on program or preview. It is as if the Aux out is prioritized over the program and preview tallies. If I unassign the source to the aux outputs, the problem goes away. The tallies are correct on the Producer and Sources & Devices pages. This is only an issue on the M5Atom.
Version
3.1.1
Distribution
Docker
OS
Linux
What browsers are you seeing the problem on?
Chrome
If applicable, What Listener Clients are You Using?
M5 Stick
TallyArbiter configuration
Relevant log output
Error stacktrace (if applicable)
The text was updated successfully, but these errors were encountered: