- #Xtouch mini osculator to atem setup file software
- #Xtouch mini osculator to atem setup file zip
- #Xtouch mini osculator to atem setup file download
Void CameraColorGainMaster(byte CameraID, double gainValue) Void CameraColorBars(byte CameraID, int status) Other Input values are based on the ATEM InputID which are listed in appendixĬameraAutoExposure Method void CameraAutoExposure(byte CameraID, Properties that only have a Get can only be read. Properties will read the current value if = is not used and will set the value This can be an inline PowerShellĬommand or a call to one of the many functions I have provided in theĬommands to control most functions of the ATEM as described below. That is executed when the button is pressed. Not all values are currently used (Mode, command, Caption andĭescription are planned for a rich UI based tool).ĭocumented in the image at the end of this document. Keys configuration optionsĬontains a block of name value pairs that define each physical button andĮncoder press. Main sections to control the Keys, LED Mappings and Encoders. You canĮdit this file with any text editor but I recommend using VSCode. XTouch buttons and encoders is controlled by the XTouchMini.json file. You want to trust them (and use the application).Ĭonfiguration is now documented here !ApGpqMMpRLhikKdb8X9a_samf1zM6w?e=SwPowt so ignore everything below… Report the files as coming from an unknown source.
#Xtouch mini osculator to atem setup file download
Download the latest version from !ApGpqMMpRLhikKdb8X9a_samf1zM6w?e=SwPowtįile, right click on it and from the Properties menu, check the “Unblock”īutton or tick box at the bottom of the window.
#Xtouch mini osculator to atem setup file zip
You just need to place the files included in the ZIP into a directory.
There is no installer for the application. There are a couple of different versions that support firware version 7.5.2, 8.0.2 or 8.1. !(upload://b1aJdYwg9kuZbOjLUOHdGrJdR7m.This is a Windows application to control a Blackmagic Design ATEM switcher. You will need to edit the aliases to the controller and application ports you are using. I’ve attached a diagram of the proper setup to do this as well as an example project file. Please be sure to annotate which fader you are moving and the resultant fader movement in ATEM within the log capture so that we can adjust appropriately. Then you can turn on logging and we can have a look. What you need to do for me to be able to help is set up Bome MIDI Translator with your MIDI controller as input and the ATEM application as output (IE Bome MIDI Translator 1) and visa versa with the routing as shown below. I’m not that familiar with ATEM capabilities but if you can monitor the MIDI messages that are being sent with your controller that moves your faders (using the logging capability of Bome MIDI Tranlsator) then we can certainly translate these messages the way you want them. I believe the ATEM OSC bridge only works on Mac.
#Xtouch mini osculator to atem setup file software
There is software you can get for your ATEM to accept OSC messages and then you can use OSCulator to translator MIDI to the OSC message of your choice (whatever the ATEM OSC bridge accepts). Now, if the ATEM does not allow for direct MIDI control of the faders,Īnd you are running OSCulator. If the ATEM allows for direct MIDI input, and the sliders are already defined MIDI messages, then yes.įor instance if ATEM allows for Mackie MCU MIDI control of the faders, then we can use Bome MIDI Translator to translate the fader 5 mackie MCU message to the fader 1 MCU message and so forth.
0 kommentar(er)
