Hello, this is the only place I could find to leave a comment. Sorry if it's in the wrong place. about xkeys-atem-remote HOT 5 CLOSED

Is there any way to ask if the code is similar for the AETM as Resolve for T-bar control, and to share whatever you get? Thanks! [email protected] 323-497-4963

Since I’m watching this thread, I should get notified when you add code to control switching on the AETM? Thanks!!! [email protected] 323-497-4963

Thanks so much. As someone just starting out, this is very helpful. I’m going to look up the definitions of each line. Slowly start to engineer what I want. Is this Yes Resolve’s API is very tight, as BM is trying to sell hardware. I totally understand. To be honest I don’t know how the can pull of the feats they have been in recent years. Must be a serious drain on profits. Thanks! [email protected] 323-497-4963 On Jan 17, 2021, at 9:07 AM, Andreas Reich <[email protected]> wrote:  I just added T-bar support. The relevant code is here: 9dc0923 #diff-e727e4bdf3657fd1d798edcd6b099d6e092f8573cba266154583a746bba0f346 <9dc0923#diff-e727e4bdf3657fd1d798edcd6b099d6e092f8573cba266154583a746bba0f346> But honestly I doubt it'll be of much use to you. Interfacing with the T-bar itself is pretty trivial, it's talking to the device you're controlling that will be most of the effort - and that's where ATEM and Resolve have completely separate APIs. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASBTAOO6G64AEOWMGXZC5EDS2MKM3ANCNFSM4WE7IDPA> .