Skip to content
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

Atem function to change supersource input doesnt work #27

Closed
T68 opened this issue Sep 24, 2019 · 4 comments
Closed

Atem function to change supersource input doesnt work #27

T68 opened this issue Sep 24, 2019 · 4 comments

Comments

@T68
Copy link

T68 commented Sep 24, 2019

Describe the bug
When in Companion creating a button that uses the Atem function to change Supersource box source, it has errors.
The supersource box source in atem changes to the assigned input on the companion button, but at the same time the box inactivates and the settings (size etc) resets.

To Reproduce

  1. Create a supersource setup in Atem with chosen sources
  2. Create a button in companion to change Atem supersource box source and assign a source to one of the boxes (another source than already chosen in Atem).
  3. Press the button in Companion.
  4. Check the supersource in Atem. The source is probably changed but inactivated/resetted

Expected behavior
Only the box source should change. No other settings or inactivation should happen

Screenshots
If applicable, add screenshots to help explain your problem.
comp_error1
comp_error2

Desktop (please complete the following information):

  • W10 64bit
  • Browser: Chrome
  • Companion Version: 2.0.0-fd488b6-1762
  • Atem version: 7.5.1
@josephdadams
Copy link
Member

Moving to the ATEM repo.

@josephdadams josephdadams transferred this issue from bitfocus/companion Sep 24, 2019
@Julusian
Copy link
Member

This will be resolved soon as part of #26, but it needs a bit more testing before being merged. Hopefully I will get this sorted over the weekend

@krocheck
Copy link
Member

@Julusian was this one included in the merge? Didn't see it in your checklist.

@Julusian
Copy link
Member

@krocheck In my testing the other properties weren't affected, so I will call this fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants