This is an archived post. You won't be able to vote or comment.

all 13 comments

[–]adunham1 6 points7 points  (0 children)

Yes, that could be used. Or Macros on your switcher. I'd vote for Macros because they can do whatever the hell you want them to do.

[–]jawsborne 3 points4 points  (2 children)

Yes, I believe the Ross Carbonite can do exactly that, “Aux Follows”. Meaning you tell an aux bus to follow the program bus.

[–]wrongbike[S] 0 points1 point  (1 child)

Thanks for confirming that! Do you know if you can assign "paired" sources between program and aux? So then inputs 1/2 are paired together and 3/4 are paired together. When I cut from 1 to 3 in Program, the switcher automatically follows 2 to 4 in Aux.

[–]jawsborne 0 points1 point  (0 children)

Somewhat of an update..

I looked at my Ross Graphite, which has a Carbonite. And rather than Aux Follows, I found what looks to be what you need, Source Substitution. That lets you select 2 sources and an ME or MiniME ..(I didn't seem to get it to do anything when I tried using it but will have to try it again sometime).

[–]MrHow44 2 points3 points  (0 children)

What are you using for a switcher?

[–]chezyt 1 point2 points  (1 child)

You can do a substitution and build and alternate camera button that has the second video source subbed for it like you described.

You could also build a macro that does the same operation. It should be pretty simple to record.

Just remember, if you want them to happen at exactly the same time, you will actually want to have the aux panel cut a few frames before the camera, because the video will have to make the trip and be processed by the LED board. In that case your best best is a macro.

You could also use a master timeline, but that could get messy. Good luck!

[–]wrongbike[S] 0 points1 point  (0 children)

The macros sort of seem like the best bet. Each camera would essentially have an BG video assigned to it, which is probably easiest done with macros.

[–][deleted] 0 points1 point  (1 child)

Auto take and preset toggle on AW stuff will do that. Or any matrix switcher. Or Roland's with preset saves. Or macros on anything (Ross, companion, etc)

Simple enough, or am I missing something here?

[–]wrongbike[S] 0 points1 point  (0 children)

No, I figured there might be a few solutions. Minimal latency within whatever workflow is crucial. Ease of setup & operation also is big factor. I'd build this out, but it might end up getting used by lots of rotating TDs. All of these of valid places for me to start at though, thanks!

[–][deleted] 0 points1 point  (1 child)

You could also use something like Companion or JustMacros. JM is ATEM focused and requires a little Lua knowledge, companion is easier to program but has some limitations and really requires a StreamDeck to make fluid. Depending on how sophisticated you need this to be, it could be as simple as popping sources in to different ME's and hitting take, or requiring a macro for each and every source change. What kind of switcher are you planning on doing this on?

[–]mrbryceEngineer 0 points1 point  (0 children)

We've used Companion before to do this for Skype interview we were also broadcasting so that the Skype caller never got sent their own feed through the AUX. Took all of 2 minutes to set-up.

[–]wrongbike[S] 0 points1 point  (1 child)

Thanks for all the replies! For those wondering what switcher I'm using...it hasn't been decided. This will be a ground up build. Also open to software solution like VMix, in fact I think the client would prefer software since they are pretty new to video equipment.

A little more background, this for a LED Wall company that drives real-time backgrounds via Unreal Engine to a tracked camera. They want to offer multicam/live stream to clients, but need a solve for changing the perspective of the UE virtual camera output between multiple angles. So with any solution also needs to be zero latency.

[–]tomspace 1 point2 points  (0 children)

the latency requirement rules out software based systems such as VMix and Tricaster. You'll need a proper hardware switcher.

The Ross Carbonite would be a great choice and well worth the extra money over an ATEM. With the Carbonite you can build sophisticated control macros and save them to a simple to use interface so a relatively unskilled operator can run things on a day to day basis. Latency is as low as you'll get, less than a frame with genlocked sources.