Jump to content

Recommended Posts

Posted

I'm having an issue getting time code from my zaxcom ERX into an atomos Flame. The flame has the updated software to sync thru the BNC sync connector. When jamming the flame claims the time code is a different frame rate. Both are set at 23.98. The flame jams fine from an F55. Time code is fed from my 788t thru a trx900CL shows up fine at the display on the ERX. Any thoughts ? 

Posted

 It jams directly out of the 788 . I also tried turning off the auto tc function on the zaxcom and it did not help. I will try other options when I get time to trouble shoot more. The flame is new to the DP and he is not quite up to speed with it either. More to come....

Posted

Try a even frame rate like 30DF or 30 NDF and see if that makes a difference. You would only need to set the ERX to 30 the CL can stay at 29.97 for the test.

 

Glenn

Posted

So it appears to have been a multi level issue. 1st. The a7sii that was feeding the flame only feeds 59.94 out of the hdmi output according to the DP. So he was telling me 23.98 and I was matching that with the erx. Because it was actually 59.94 into the flame it would not jam to 23.98. Once we figured that out I switched to 29.97 and it would jam temporarily and then lose code just as quickly. After turning off auto TC function on the Erx it held code, all though if the cable was bumped on the erx it will still lose code temporarily and the rejam almost as quick. Not sure if this is a bad cable, bad jack on my erx or just the limitations of a 1/8" mini connection.  I have a new cable on the way and will check with a different erx as soon as I get a chance. Does anyone make a locking 1/8" to bnc and will it lock down on the ERXtc3 ? Thanks for the help ! The unrecognizable frame rate warning on the flame was when I was still feeding 23.98 but had turned off the auto TC feature. Thanks again. ! 

Posted

The DP should set the HDMI output resolution to 1080i (likely has it set to 1080p) and in HDMI cadence, set for progressive with 3:2 pulldown for 23.98 recording framerate.  Then in the Flame, it should be able to be set for input 3:2 detection to record a progressive 23.98 file.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...