Camera not taking JAM Sync 30.5.0

[Curtis Abbott]

Hi All,

I have a camera that is not taking JAM sync from the sound dept. We have tried using the RED timecode cable directly from his recorder. Also Have tried using a Denecke lock-it box. But the camera will not take the JAM. I have jammed this camera in the past on this build. I also did a reinstall of the build. Is it possible that the port has been fried? Thanks in advance for any suggestions.

Curtis

 

[Stuart English]

JAM SYNC

JAM SYNC

I am sure that you have already but can you check four things:

Is JAM SYNC enabled in the TIMECODE menu ?

Is the timecode cable good ?

What does the timecode value in the UI say - T or E preceding the value ?

If you make a short recording on the camera what happens ?

 

[Thomas Wright]

And dunt you got to turn off time code out?

 

[Curtis Abbott]

Stuart,

I was toggling JAM SYNC on and off in the menu, also tried CROSS, just incase the sound guy was feeding me 29.97. I also toggled OUTPUT just incase, but nothing.

We tried using a 10' RED Timecode cable, that I have used before. Also used the BNC to LEMO cable that went from the Deneke to the RED. Sound was able to sync the slate from the Deneke lock-it box with the same BNC to LEMO cable.

It was a T we were looking at Timecode, not edge code. I also did not get the typical chain and lock logo in the top.

We were able to record fine, just went old school and smart slated everything.

Thanks for the quick response Stuart, anything else I can do to get this working for future jobs?

 

[Joe Kleber]

Is it possible that this is a bug in 30.5?

...having the same issue on a shoot right now. ...tried all the same trouble shooting steps.

Our cam was working at the beginning of the day and mysteriously stopped working sometime during the day. ...hasn't worked since.

 

[Mike McCall]

We recently, within the last few months, had this problem happen. After going back and forth with Red we sent the camera in. There was nothing fried and connector was good, the board simply wasn't taking the timecode. They changed out the board, to a tune of $1200, and it all works fine now. Their only reasoning was component failure.

I would say as long as all settings are correct, and it appears they are, I would call RED. They will have you pull a log file and they will be able to tell if it is seeing the timecode or not. We were on build 21 at the time, now we are on 30.5 and all is well

 

[Stuart English]

Jam Sync

Jam Sync

Is it possible that this is a bug in 30.5?

No.

 

[David M. Geary]

I haven't been able to jam sync to the red from my 744t since the MX upgrade/build 30.5. I can jam the 744t from the RED but it has stopped working the other way. I'll call RED support on Monday but $1200 for a board does not sound appealing.

 

[Deanan]

I haven't been able to jam sync to the red from my 744t since the MX upgrade/build 30.5. I can jam the 744t from the RED but it has stopped working the other way. I'll call RED support on Monday but $1200 for a board does not sound appealing.

Try 30.6.0 also but it sounds more like a cable pin wiring issue.

 

[David M. Geary]

Thanks Deanan, I'll try 30.6.0 this evening, but I doubt its a cable issue. I had no issues with the RED Lemo cable before and I tried a new cable this morning with the same result. I have a new cable that I haven't opened back at the office, I'll try it tonight.

 

[Deanan]

Thanks Deanan, I'll try 30.6.0 this evening, but I doubt its a cable issue. I had no issues with the RED Lemo cable before and I tried a new cable this morning with the same result. I have a new cable that I haven't opened back at the office, I'll try it tonight.

try reversing the direction. It could be you have a cable only wired with in or out but not both.

 

[David M. Geary]

I reversed the cables and I tried a brand new cable bringing the total RED lemo cables that no longer work to three. I also tried 30.6.0 and still no luck.

 

[Deanan]

It does sound like something is fried.