Welcome to our community

Be a part of something great, join today!

Log in
  • 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 :)

camera to camera sync?

Genlock monitor and shutter syncing and timecode jam do all work on both Epic and Scarlet. Scarlet of course has some framerate limitations but within those limitations the process is the same for both cameras. Any statements about Scarlet not syncing would be going back to the original 2/3" version.
 
Kemalettin, can you post more about what you tried and the results?
 
Dave i have Gig-E cable http://www.red.com/store/cables/product/lemo-to-lemo-cat5e-ethernet-straight-cable-4 and this one http://www.red.com/store/cables/product/3bnc-to-00-lemo-sync-cable
tried first with Gig-E cable connected both cameras assigned different ip's 10.10.10.1 first one 10.10.10.2 second one.i have tried every option but sync was always red on both lcd.
didnt have to chance 3bnc to lemo cable because i dont have any timecode generator.
i just want to trigger both cameras at the same time can you please help me about this?
 
Kemalettin,
First, the SYNC icon has no connection to camera-2-camera sync that you would achieve with the gig-e cable. That cable is only for settings and control. It does not come into play for shutter timing. The SYNC icon is related to shutter timing. Because the word 'sync' has been so badly abused in this thread, please indicate exactly what you want to achieve.

Assuming for the moment it is camera-2-camera control sync, which would allow you to trigger both record from one camera, the default settings in the communications setup menu should allow you to simply connect the GigE cable to bother cameras and go. Use Target=All, and make sure C2C box is checked. IP address can be left as both to 10.10.10.10, but setting them as you did should be fine.
 
Hi Andrae (or anybody who can help),

I'm looking for advice and a bottom line for the sync out topic.

My intention was to sync my motion control rig to the scan sync out supplied on the CTRL connector.
I have seen that the sync out signal on a Epik-M is at the sensor frequency, but I could not prove that time that the phase of the signal (to sensor exposure) was the same on every power up (simply because I had no tools at hand at this moment). Does anyone have experiences?

Second I could not manage to get the sync out signal out of an Epik-X. To be honest, I'm not familiar with the Epik. But only setting the sync out option in the Setup (like done on the M before) didn' t make the job. Does anyone have hints on further settings needed to enable the sync out option?

Thanks for any help and best regards from Vienna,
Hansi
 
Hi Hansi
THere is no difference in the EpicM versus EpicX in this function. You should be getting the same results given you are on the same code, same cable, same settings.
So lets start with what code both cameras are on. There was a point where we lengthened the pulse to make it easier to detect on a scope. Prior to that it was very short and difficult to work with.
And please describe the complete setup you have and how you are judging there is no signal. i.e. Oscilloscope?
I can confirm that the pulse coming out is coincident with the beginning of sensor exposure, and does not vary with power up.
 
Sync pulse always at the same position is very good news !
I've checked the signal with an oscilloscope, and pulses were short on the M (a few 100us at 25fps?), but no problem to detect.

But I could not get the sync signal out of the X. I could set up for the tally signal proving that I'm on the right connector pin.
Simply switching in the Setup - Camera Output from GPO to Sync Out didn't make a signal appear on my oscilloscope.
Are there any other settings I have to care about for the sync signal?
(Currently i have no X at hand for playing with and I will see the cameras for shooting next week for the first time.)
 
Dave , can you also describe the 'moco' labeled sync setting I think I saw in there on the beta build ?
Thanks!
 
Sure. This used to be Shutter, then External. Apparently confusing and I can see why. Although the manual usually helps quite a bit ;)
its MoCo for motion control. The idea is, in this mode, some external device provides a pulse, the leading edge of which is used to start an exposure. When recording is started an image is added to the file for each pulse. So you could expose, move the rig, expose, etc. You could implement time lapse with this, claymation sort of things, miniatures - programmed move (motion control), scaling. You can use this in 3D feeding the same pulse to two cameras. The pulse would come in the GPI/Sync in pin on the SYNC port. Select Sync In as the functionality.
There is a very important note here: images only come when you give it pulses. So no preview without pulses. Shut your camera down in this mode and it will look pretty dumb until you give it pulses. There is also a pipeline involved. When recording you need to give it 4 more pulses at the end after hitting record stop to get it all flushed out. i.e. you want a 10 frame clip, that means 14 pulses. Your clip will have the first 10.
 
>what code version was on the M and the X?
Good question I should care about myself in the future in advance, blame on me.
The M with sync out pulse (which I expected to be the older one) has firmware version 2.0.5.
The camera I ment to be a X (w.o. sync pulse) turned also to be a M, but with firmware 1.6.42.
Does this shade some light on my problem (I could not find a hint in the release notes)?

Best regards, Hansi
 
I've checked the sync out on an Epik X (code 3.0.0) from Maddels/Hamburg and everything looks fine (500us pulse train on sync out).
Can it be a firmware issue because of the old release 1.6.42 or does it look like a hardware problem which needs repair to you?

best regards, Hansi
 
we are working on a 3d project with 2 Epic 3.0.7 Firmware we provide genlock with lockit and sync with master&slave cable its working perfect on 25fps timebase and normal framerates but when we try 2K 300fps both cameras gives different frames it doesnt sync actually.B camera gives almost 100 frames more footage

http://i.imgur.com/PLX9q.png
 
Hi Hansi
That explains it. The pulse is there in 1.6.x but its really short, 10s of nanoseconds. Easy to miss, especially with a timebase on a scope set to see a whole frame or more.
 
Kemalettin
If you can, upgrade to the 3.2 beta. We have seen some cameras have this issue due to component tolerances, especially at 25 project and high framerates. 3.2.x has a firmware upgrade for this.
 
Kemalettin
Please contact your BombSquad rep and send a log from the M showing this problem.
 
One more thing about MoCo mode: dont use audio. It is essentially a varispeed condition. Current 3.2.x does not enforce this, but future builds will automatically disable audio when MoCo is selected.
 
You must log in or register to reply here.
Back
Top