Audio Output Routing - Companion variables not updated directly
When a routing is set in ATEM Software control it is not reflected immediately in the Companion Variables (only after a Companion restart). Same for when the routing is set within Companion.
Examples$(atem:audio_routing_destinations_2001-1_2_source_name) is "No Audio" while ATEM Software Control is saying it is Input 1 1/2 (as set in ATEM Software control). Action atem: Fairlight Audio: Audio Routing {Aux1 5/6 (Aux1)} {Input 2 1/2 (Input 2 1/2)} does set it correctly. Visible in ATEM Software control but not in the variable list in Companion.
Action atem: Fairlight Audio: Audio Routing from variables {2001-3_4} {4-1_2} does set it correctly. Visible in ATEM Software control but not in the variable list in Companion.
Note, Feedback "atem: Fairlight Audio: Audio Routing (from variables)" does work correctly but the variables are needed to display the values on a button.
Tested on Mac with Apple Silicon - macOS 14.6.1, Companion v3.4.2 stable version, and ATEM Constellation 2 M/E HD, ATEM Software and firmware v9.6.2
still seeing the same issues on 3.5.2 stable
Additional info: bug still present in v3.5.4. The variables get refreshed after a reconnect. I have setup a dial to change the route (checking the atem var and then selecting the next route). It’s unworkable without the feedback (with displaying a custom var as workaround)
This is fixed in v3.17.0 of this module
Great. Manu thanks!
Op zo 25 mei 2025 om 12:01 schreef Julian Waller @.***>
Julusian left a comment (bitfocus/companion-module-bmd-atem#325) https://github.com/bitfocus/companion-module-bmd-atem/issues/325#issuecomment-2907731896
This is fixed in v3.17.0 of this module
— Reply to this email directly, view it on GitHub https://github.com/bitfocus/companion-module-bmd-atem/issues/325#issuecomment-2907731896, or unsubscribe https://github.com/notifications/unsubscribe-auth/A25NECAFVA7DRIJWZOVYZMD3AGIHXAVCNFSM6AAAAABPR76HQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBXG4ZTCOBZGY . You are receiving this because you authored the thread.Message ID: @.***>