- #Xtouch mini osculator to atem setup file how to
- #Xtouch mini osculator to atem setup file software
- #Xtouch mini osculator to atem setup file zip
They have the same osc command as the tie ones, but are set to react then the value opened #85 for this issue exclusively. TEMPORARY SOLUTION - I’ve created separate buttons for untieing background as well as usk's. REASON - USK tie when OSC value increases and untie when it decreases Also, /set-nextusk/ works exactly the same as /nextusk/ When I press the button again, it remains tied instead of turning off as it would be in case of DSK. ISSUE 1 - Upstream keyers can only be tied. Please note that it is written for my old switcher and has to be modified for newer models. If you want the OSCulator file for this, I can send it. The lights don’t change, but are still very useful. Colors of the frames above correspond with LED colors. I’ve also written feedback commands for the LEDS.
#Xtouch mini osculator to atem setup file software
My current workflow is: AKAI APC Mini > MacBook > OSCulator > atemOSC > ATEM 1 M/E Production Switcher.įirst important fact: ATEM SOFTWARE 7.4 DOES NOT WORK WITH 1 M/E PRODUCTION SWITCHER.
#Xtouch mini osculator to atem setup file how to
It is pretty easy to set up TouchOSC, but OSCulator is a bit more tricky so I’m looking for some experts who also uses OSCulator and can teach me how to solve my issues. E.g.I create this thread to address certain issues I’ve stumbled upon while configuring my stuff. Method or property option after the me using a period to separate. GetCameraFocus Method double GetCameraFocus(byte CameraID)ĬameraID, double PanValue, double TileValue) Void CameraDisplayBrightness(uint32 CameraID, double BrightnessValue)ĬameraShutter(byte CameraID, int ShutterValue)ĬameraID, int16 tempValue, int16 tintValue) 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. 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. This is a Windows application to control a Blackmagic Design ATEM switcher.
0 kommentar(er)
