hi - looking for some advice.

im working on a music project where i have 4 cameras, not timecode locked, where a couple of cameras have no on board sound

my usual workflow with this sort of thing is to find a visual sync point in the footage that i can hear on the correct audio track - eg, the first click of drum sticks on a count in. or an obvious vocal. or the first clap of applause...whatever. i put the 4 cameras down on separate tracks using that sync point as a reference to manually sync them up. then i set an in, and match frame to each track in turn to set an in point. then i group clips by those in points. so far so good. this has always worked for me for many years...

what i'm finding on this project is 3 of the cameras are syncing up in the group, but one of the cameras misbehaves. when i right click to edit the subsequent group, avid it seems has ignored my in point and started the group from the first frame of this clip.

one more thing: this camera has been recorded as 50P footage (was a sony a7III recorded via an atomos ninja V and it outputs in this format for some reason...)  so a timewarp is applied to make it 25P like the rest of the project. i'm wondering if this is the thing which is creating the odd behaviour. if so - why? and how do i fix it? 

is it a bug or am i doing something wrong ? i'm aware avid has been making changes to the multicam functions so wouldnt be surprised if it has become buggy...

i'm on MC 2021.9.0

pretty sure it's to do with the 200% motion adapter on the 50P clips, but cant figure out how to do it....my brain hurts :)

I would think your theory is correct that AVID isn't liking the time flex on that clip.

You could do a test by 'baking' the framerate of that clip to match the other clips... whether in AVID or another application... and see if the problem goes away.

Just make sure that if this works, you'll have to use that new "baked" clip as your original source going forward, through color and finish.

Best,

j

thanks for the reply, yes i'm sure that's what it is. i'm working with some very long 4k files tho (60 minute live concert footage) so will take a bit of time to transcode/mixdown, but that is a fix.

for future reference, i would still really like to know why exactly this happened, and whether it's a mistake i've made, or a bug.