[J.d. Vaillancourt]

So I figured out somewhat of a workaround. I converted all the audio files to AIF and then reconnected the AIF files instead of the WAV. FCP is still giving me the same warnings and the timecode is still changing from 1:00 to 59:27, but all the timing isn’t messed up like it was with the WAV files, it may be a split second off, but workable. This is really weird and frustrating.

[J.d. Vaillancourt]

I just realized it’s only the audio WAV files doing this and not the video file, weird. Then I found this thread with somebody having the same problem

https://forums.creativecow.net/thread/8/1141179#1141179

The music flew are 1:00 on the dot, the finder and Quicktime say they’re 1:00 and the browser in FCP says they’re 1:00 until I reconnect them, they change to 59:27. What gives!?!?

[J.d. Vaillancourt]

Thanks Dan!! Worked like a charm!

[J.d. Vaillancourt]

Everything is working and all good on my end, so I’m happy.

Does your 7D footage say UPPER under field dominance? Probably not, now that I’ve solved the issue I’ve realized it only happens with certain codecs rendered from After Effects that FCP misinterprets as UPPER instead of none. When I transcode my 5D footage and bring it into FCP the field order is NONE.

Try this… switch the field order in the browser of a couple of your 7D clips to UPPER, start a new sequence with the field dominance set to NONE, then bring those 7D clips in and put a transition between them. Render the file and I bet you’ll have aliasing on the footage where the transitions are.

SO GLAD I figured this out… I avoided doing any compositing of AE clips in FCP for a long time for this exact reason… when you bring Animation compressed clips from AE into FCP, the field order is wrong and it aliases the comped image… so I just avoided it and did everything in AE… WOW

[J.d. Vaillancourt]

Update, thanks to Matt, he made me realize I can change the field order of a clip in-sequence… and by turning the visibility on and off, FCP refreshes and sees the proper field order, fixing the aliasing.

[J.d. Vaillancourt]

OMG! Thanks Matt! Wish I knew that yesterday before I re-timed my entire edit! I forgot you could edit clip formatting in sequence… still took a while, but MUCH less time than redoing the edit. Live and learn I guess haha

Cheers

[J.d. Vaillancourt]

That’s what I thought, but apparently it does matter for rendering. If the field order is not set to NONE it renders aliased transitions.

Once the footage is placed in the sequence with the wrong field order it will always render the transitions wrong for that edit. I tried changing the field order and it still had aliasing, I tried copy and pasting the clips into a new sequence after fixing field dominance and it still had aliasing, it wasn’t until I had all the field orders set properly BEFORE I placed the clips into a fresh sequence that the aliasing went away!! I learned this the hard way as I completed my whole edit with FCP interpreting the field order as UPPER and there was no way for me to get rid of the aliasing from the transitions. Setting the field order to NONE fixed the problem if I brought the clips from the browser into a fresh sequence, but it did not fix the transitions in my original edit… weird. It seems once you’ve brought in a clip to a sequence with the wrong field order, FCP remembers it and changing the field order in the browser does nothing. I even tried trashing the render files.

So I re-did my entire edit with the exact same clips as the original edit, making sure field order was set properly BEFORE I brought them into the fresh sequence and everything worked perfect. Yes you are right, the field order didn’t make a difference on the footage, but it caused aliasing when rendering transitions. I learned this the hard way, but it’s solved quite a few issues that I’ve had in the past with compositing AE clips in FCP.

Cheers
JD

[J.d. Vaillancourt]

Hmmm, I just went through this same problem and field order was the issue for me. Just make sure in your render settings in AE the field order is set to none, that your FCP sequence settings are set to NONE and in the browser the field dominance is set to NONE for each clip. Just ran a test myself and it work great, even tried it with some Alpha clips (straight) and they were nice and smooth.

I know you said in your message you had all the field orders set to none, but double check all 3 avenues, then start a fresh project, make sure all the field orders are set properly and then drag your footage in. FCP has a tendency to remember the settings when a clip was dragged in to a sequence and it does not recognize in that sequence if you’ve changed the field order. I tried this test by changing the field dominance in the browser while the clip was already in a sequence and I still got the jaggies.

I just went through this exact pain and had to re-edit an entire project!! All the stuff imported from AE had a dominance set to upper, I edited the whole project, noticed the aliasing in the transitions of the final edit… ran some tests, discovered it was field order, tried to change dominance, still got jaggies, tried to start a fresh sequence while pasting the old edit in, still got jaggies… it was until I took those exact clips from the browser into a fresh sequence that the jaggies went away. So if you’ve already done your edit with the field order set improperly in the browser, you’re pretty much euchred and have to recut the edit in a fresh sequence. Hope this helps, I’ve definitely learned my lesson!!

Cheers
JD

[J.d. Vaillancourt]

At last! After 2 hours of testing I have found the problem. It seems that Final Cut interprets certain codecs rendered from After Effects (Animation, ProRes) to have a field order even though they don’t. It was as simple as scrolling over to the field order setting of the clips and setting them to none. Oddly enough, it doesn’t interpret XD Cam or Photo JPG compression to have a field order.

At least I can say I learned something today!

[J.d. Vaillancourt]

Use the motion sketch. On your timeline, set an in and out point for your vibration. Go to ‘Motion Sketch’ it’s under ‘Window’ on Mac, not sure about PC. Click ‘Start’ capture, grab your layer or comp and shake the mouse around for the duration of your in/out points, it should simulate a shaking. Tip: to get small, less obvious shaking, zoom in on your comp window, the more you zoom in, the less shakey it’ll be, almost like vibrating.

jv