This does change depending on location and Internet access. The connection is a little slower, but I’ve seen about a 1.5-2 second delay from initial tests. You may need Administrative IT to do that. There is one big difference: you must first open Port 1935 (or similar) on your Firewall. Very similar to connecting across your WAN. The video will be sent via Intranet (as long as both the ATEM Mini Pro and Streaming Bridge are on the same network) to a location that can also either record, stream, or play on a monitor.Īdded security with a stream key, but anyone with the XML file can connect to the ATEM Mini Pro. ![]() This is great for larger buildings, and campuses. ![]() This is perfect for a studio to either record or stream video, or send video to a lobby to know when a person is on-air. Configure the Bridge, and set up in the Mini Pro. Plug the cable from ATEM mini Pro to Streaming Bridge. This setup only requires an Ethernet cable (no cross-over cable needed). You can also send signal in streaming, or Hyperdeck data rates (around 50 Mbps). You will have to connect the Bridge up, then use the ATEM Setup to create an XML file that will import into the ATEM Mini Pro. USB-C is included, but the connection is to configure the device. Two ways to genlock the video with Ref-in options. Video can then be sent to a monitor, computer for streaming, or recording device via HDMI or SDI. The Streaming Bridge will connect in via Ethernet cable (no WiFi). The end result as a 1080p video to the source location for streaming or recording. This will not control the source camera or switcher (at least, not yet). !(upload://b1aJdYwg9kuZbOjLUOHdGrJdR7m.This is a device that will connect your ATEM Mini Pro or ATEM Mini Pro ISO to a remote location. 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. 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 Comments
Leave a Reply. |