+1; -1 frame when using PIX 240 and RECINE conformation

[Meddy MOST]

I'm trying to create a new workflow using the PIX 240. As it seems to work pretty well with the RED.
So, I edit offline using PIX 240 Apple ProRes LT on FCP 7(RED metadata, timecode and SDI FLAG) then I go to REDCINE using FCP XML export/import and, in RECINE, I point all my editing to the R3D SSD folder to relink and conform my PIX Footage into RED RAW
It is working pretty well but I have a small issue which is in fact a real problem...

I have +1 frame at the start of the each of my clipss and -1 frame at the end of each them ... it is the same for every clips, +1, -1 ... (I'm working in 25fps) this is pretty strange ... when I choose another frame base, this +1-1 is changing to something else
Is it a problem when we use 25fps or I may have done something bad in my conformation

 

[Meddy MOST]

Sorry I made a mistake in section I wanted to writre
I'm talking about REDCINE-X. This thread should move to REDCINE-X

thx for the move

 

[Jeff Kilgroe]

moved.

 

[Simon N]

We are having a lot of problems with the pix workflow. We are experiencing similar 1 frame offsets but have found a workaround in how we sync everything together. Our issue though is that the offset is not consistent. if we shoot 25 tests with the same settings, then 22 will be rock solid and 3 will be out by 1 frame. We too are working in 25fps.

I assume that it is the pix files that are off by 1 frame and any seperate sound you have is in sync with the r3d footage, transcoded or otherwise?

 

[Tom.Wong]

the curious frame is that the system should be locking in via timecode first before frame count. have you only tested this with rcx? have you tried anything else to conform with?

 

[Marcus Struzina]

Doesn't the Pix have a timecode offset adjustment in it ? Wouldn't this solve the problem ? assuming that you set the offset before you record footage on the Pix. ( I don't have a Pix 240 by the way )

 

[Greg M]

So is this offset, a sync off set or is the footage on pix just not the exact same length vs r3d?

 

[Simon N]

We have experienced several anomalies, some of which we were avble to rectify by offsetting in the pix. The issue is still though that even if we get some footage in sync, there are the odd takes that are still 1 frame out. I am wondering if it is a 25fps issue or something to do with the sdi feed, after all, there is an issue with black bars so something is amiss with the sdi?

 

[Greg M]

The black bars are a known issue that will be addressed in next FW.
Set Epic to 5KFF and you eliminate bars on sides. You'll still have a slight letterbox because FF is not 16:9

 

[Patrick Tresch]

I think Meddy is saying that the Pix files are shorter by 1 frame at the head and the tail compared to the R3D.
And therefore he can t relink them to the R3D.

Or... is there a slip of the TC by 1 frame? Is the length of the shot the same comparing r3d and prores?

Pat

 

[Greg M]

Shorter is to be expected, it's being triggered by an SDI flag. This shouldnt effect relinking

Simon, is this what you are experiencing too? I thought you said in the other thread that the audio was one frame out of sync. Is it just that the clip is one frame shorter than r3d?

 

[Sam Edwards]

On Smoke this would be a 2 clicks to fix the entire sequence.