Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

A master and TWO slaves?

J G Harding

Member
Joined
Feb 4, 2011
Messages
8
Reaction score
0
Points
0
Location
London, Cambridge UK
Hello all,

I've not posted before here, but look forward to doing so more often in future.

I have a quick question:

I'm shooting with three Epic bodies at once.

At the moment I plan to have them genlocked at least.

But is there a way to have one as master and TWO as slaves, sharing all settings and clip starts and stops?

I'm aware that this sounds unorthodox, but so is the job. They need to have identical settings and ideally start and stop times, at all times.

I understand it's possible for for a single master and slave due to stereoscopic shooting, but can I slave two and have them share everything the master does?

It would save quite some time if it's possible.
 
Last edited:
As the ethernet port on the brain is set to either master or slave I don't think you can daisy chain them.


Using a Aja Gen10 you can multiple gunlock and you can make a multi-turnover switch that will start/stop all cameras at the same time.

You should be able to set camera settings once (Master) and boot a slave camera connected to it to transfer settings at the start of the day.
 
You can't daisy-chain the ethernet ports, but you can connect all three cameras to a network switch (or any typical broadband router) and test your configuration.
 
As the ethernet port on the brain is set to either master or slave I don't think you can daisy chain them.


Using a Aja Gen10 you can multiple gunlock and you can make a multi-turnover switch that will start/stop all cameras at the same time.

You should be able to set camera settings once (Master) and boot a slave camera connected to it to transfer settings at the start of the day.

There is no Master or Slave setting. Using the default setting of "Target: All", you actually have a multi-master setup. If you were to connect all three epics up to a hub/switch you can start and stop all three by starting any one of the cameras.

You CAN setup a Master/Slave environment by setting the slave to "Target: None" - which means outgoing messages from the slave would not control any cameras.
 
I see!

So one camera could target all others with it's controls, while the others target none.

I've not networked Reds before so I'll need to clarify:

Will this automatically send all parameter changes? For example, I change a shutter angle to 90 degrees on the camera with target all, will other cameras on the network follow suit?

If not, is there a way to make this happen, or can I only send start/stop?
 
I see!

So one camera could target all others with it's controls, while the others target none.

I've not networked Reds before so I'll need to clarify:

Will this automatically send all parameter changes? For example, I change a shutter angle to 90 degrees on the camera with target all, will other cameras on the network follow suit?

If not, is there a way to make this happen, or can I only send start/stop?

yes, it seems like you understand it correctly.

It will send all the settings (that would normally be shared between cameras in a 3d setup) across. I don't have the list in front of me but it would include things like frame rate, ISO, integration time, color temp , etc. along with start/stop control.
 
Excellent, many thanks.

So what more will I need to add to my kit hire list to get these three bodies talking?

This is not studio based so I guess I'll need to have a portable router of some kind... plus cables.

I find the network and protocol section of the manual quite difficult, as I'm not much of a network man...
 
Back
Top