ATEM Macros: Switching cameras with foot pedals

I have been tasked with setting up an ATEM switcher with 3 foot pedals so that: pedal 1 = Camera 1, pedal 2 = camera 2, camera 3 = pedal 3. I just noticed that the Just Macros website is dead. Is there any other way to set this up since it appears that JustMacros is no more.

Thanks in advance for any advice/help with this.

It can be done with an Aurduino and software from:
https://github.com/kasperskaarhoj/Ardui ... -Switchers

Short video tutorial.

It can be done with an Aurduino and software...

There has to be an easier way. Any JustMacros users here?

Thanks for the reply Richard.

I would suspect this could be done with Ian Morrish's Powershell library.

Arduino is the way to go. It is just a question on if you want a stand alone box that uses Ethernet connection to the switch, or use the Arduino as a simple I/O device and use a PC (or Mac) scripting solution to interface to the ATEM.

I use PowerShell and did something similar but it was the preview switch on Sony RCP's which is just a relay contact.
Sample code is here for detecting the switch closure events.
https://ianmorrish.wordpress.com/2017/01/22/using-arduino-as-an-input-trigger-to-powershell/

The only thing you have to do to the Arduino is upload the Firmata library. Literally no coding is required on the Arduino side. An Uno is all you need.

Let me know if you want to try this and I'll give you the PowerShell script to switch inputs.

Hi Ian:

....or use the Arduino as a simple I/O device and use a PC (or Mac) scripting solution to interface to the ATEM.

We have a Mac Mini running Windows (JustMacros was Windows only at the time) to run the ATEM control software. So just to get an overall sense on the set-up:

3 XKeys footpedals connected to a X-keys USB 3 Switch Interface to the iMac mini.
Arduino Uno with Firmata library connected to the iMac mini via Ethernet.

Literally no coding is required on the Arduino side.

How would I set up the ATEM to recognize the foot pedal events? I'll look at the link you posted. Sorry. Total noob when it comes to this.

Let me know if you want to try this and I'll give you the PowerShell script to switch inputs.

Yes. I would really appreciate this.

Thanks to both of you for your help.

Hi,
I have used the X-Keys API to add their normal keyboard support into PowerShell.
Their ,Net SDK has support for the XK-3 so I should be able to add that. Will be a few days before I can do it.

Is this the device? http://xkeys.com/xkeys/xk3swi.php

Is this the device? http://xkeys.com/xkeys/xk3swi.php

This person from JustMacros suggested this one: XK-1202-UHS12. http://xkeys.com/xkeys/assets/documents ... rface.html

Will be a few days before I can do it.

No problem. Thanks so much for your help.

I have updated my x-keys PowerShell support for both the xk-3 and xk-12 switch interfaces.

But, you can probably do what you want without any scripting. Just remembered that X-Keys allows you to assign the switches to keyboard commands. So I would say it is safe to go ahead with the hardware purchase either way.

I have updated my x-keys PowerShell support for both the xk-3 and xk-12 switch interfaces.

Hi Ian: Do you have a direct link the the updated PowerShell? I want to make sure that I'm downloading the correct one.

Once again, thanks a lot. I'll post back once we have everything and update you on our progress.

https://1drv.ms/f/s!ApGpqMMpRLhiiv4zoZRIXcnbIInsLQ
After downloading XKestTest.zip, right click on the zip and under properties select Unblock. Then unzip somewhere.

You need to run the 32bit version of "PowerShell ISE (x86)" which you should find by typing that in from the Windows Key search. (I can create a 64bit version but I use this on a little PiPo 32bit machine).

The following script should confirm that PowerShell can see the device. Copy this into a new script window in ISE)

add-type -path 'C:\Path to where you unzip the files above\VISE_Xkeys.dll'
$XKeys = new-object VISE_Xkeys.xkeys
$keys = $Xkeys.GetDevices()
$keys #this should print out some information about the device

$xkeysActiveDevice = $Keys[0].DeviceID
$XKeys.NewDevice($xkeysActiveDevice)
#Shour show True if command above worked.

#create event to display when switch # is closed
Unregister-Event -SourceIdentifier KeyPressed -ErrorAction SilentlyContinue
$MyEvent = Register-ObjectEvent -InputObject $Xkeys -EventName KeyPressed -SourceIdentifier KeyPressed -Action {write-host $event.sourceEventArgs.KeyID}

#script now waits for key/switch event
#We can add the ATEM stuff after we know this works.