MIDI Fader for ATEM T-Bar issues #3794
Unanswered
matijaserdar-ctrl
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I am totally new here but I work with Companion for years now and it has changed the way I work - mostly because of the community. I want to say that I am very greatful what has been acheived and for any advice! THANK YOU!!
My setup: Behringer X-Touch mini sends it's MIDI signals to Companion so it can take actions on ATEM switcher(s). I can interpret the pressing of the MIDI buttons so the ATEM takes action on active cameras, CUT transitions and so on..
My problem(s):
The ATEM T-Bar top/low position behaivour:
1a) It stops just before 0 (when I pull the MIDI Fader to the lowst point). It should of course finish the transition totally but it doesn't. Companion receives the value 0 (I see it in the log) but apparently it doesn't send it to the ATEM (or there is another problem?).
1b) When the MIDI Fader is slided to the top part it used to make big problems, but I managed to restrain it until the value of 101 (it natively goes up until 127). "101" because the same issue with 0: It seems that the value 100 is only been sent if after the value it gets another change --> therefore 101. And it works! But I cannot send -1 so it never sends 0 (I guess).
1c) Sliding the MIDI fader from top down it makes the T-Bar jump a few times, that brings me to the next part (see point 2):
T-Bar relative/absolute position: "Normally" faders for video switchers like ATEM don't mess up the direction of the T-Bar. The transition always takes place from the active camera to the one in preview no matter which is on top/bottom. Therefore the MIDI fader should be interpretet als a relative position not an absolute.
--> Problems Companion could/should solve:
For both problems with the interpretation of the MIDI values there should be a way to manipulate those values before they are given to the ATEM switcher. At the moment triggers in Companion or other places do not support any scripting as far as I have seen. (It used to be different?!).
There are other issues I am working on.. if you have got so far I guess you might be interested..
That is all for now. I really hope it is understandable what the goal is. I am very greatful for every attempt to help!!
Beta Was this translation helpful? Give feedback.
All reactions