[James Agnew]

yes, and set everything to 25fps with the aja codec. on capture it acts as if it’s still set to 24, and quits capture due to a break in timecode.

[James Agnew]

Sorry for the delay, been away for a bit.

in FCP terms it’s 1080i50.

I got round this by doing the small sections I needed at 24fps using the AJA codec. but that’s something I didn’t want to do, so it would be good to find a solution in case I have this problem again. plus I was hoping I could use prores4444.

[James Agnew]

Sorry for the delay, been on holiday.

when I export from the FCP timeline, the Motion project appears to set itself up as XDCAM 1920×1080 23.98. as I say, my footage is pro-res captured from an SR deck.

it does seem to be de-interlacing with field rendering off, but if I turn it on my graphics move in fields.

these settings work fine if i just forget about the round trip and use a separate export in a different codec for the background. could it be that motion expects pro-res to be interlaced? doesn’t really make sense in HD but why does it insist on de-interlacing my pro-res background and not, for example, an animation codec background?

James

[James Agnew]

yes, and i’ve tried it with normal as well. it actually looks ok if I switch on field rendering, but I don’t want my graphics to move in fields. fields 1 and 2 are identical on the video footage, so I don’t kow how it’s introducing a field issue like this, especially as it can be cured by exporting and importing the clip separately, and only occurs on round trip from the FCP timeline.

also this is only a problem with the video background, the graphics look fine either way.