-
My first official question. Could be FCP, could be Motion…
Okay, I’ve done some searching and not found what I’m looking for. That said, I’ll try not to embarrass myself too badly here. Also, for the record, I have already figured a couple of workarounds to the issue, so nothing about this is time-critical, but I have a burning curiosity to see if anyone can confirm what I believe is going on here.
I’m doing what I thought would be a very basic comp in FCP (FCP7 within FCS3 on Snow Leopard 10.6.7 on a drool-worthy Mac Pro, for the curious).
The basic premise is a simple side-by-side video. One video track (V2, again for specificity’s sake) on the left half of the screen, one video track (V1) on the right half. No big deal, crop and move each track, both video tracks show up fine, audio’s working, everything hunky-dory.
Now, over these two video tracks, right down the horizontal center of the screen, I’ve dropped a graphics crawl that I exported from Motion. It’s a simple, one-color (white) logo that crawls slowly. I’ve done this sort of thing a hundred times with no challenges until today.
As soon as the logo hits V7 (I like to leave a little space for other stuff – will collapse it down later), I lose visibility on track V2 (currently the left-side video) and only V2 in the Canvas, meaning the left side of the Canvas is now simply black. V1 is still completely visible with the appropriate right half of the crawl laid right over it. The entire crawl track is still visible. All audio still works, and an exported QT movie of the sequence has all video showing up again, but the Canvas simply refuses to show that intermediate track.
Here are some specs and things I’ve tried:
All video is 720p24 from a Panasonic HMC150. All ingested through L&T with no setting changes between ingest sessions. The footage should be identical.
The sequence is in the HDTV 720p (16:9) preset at 23.98 fps, square pixels, Apple ProRes 422 compressor. Same on I use as a default these days. Nothing new here.
The logo crawl is also 720p24 exported from Motion as a QT .mov file. Here’s one place I think might be the catch. The version causing the problem was exported as the default ProRes4444+Alpha. It was *not* exported using the Animation setting. One of my workarounds included switching to that export setting in Motion. That works, but of course now requires me to render the timeline clips to view them in the Canvas.
I have tried moving the clips to different tracks. No matter what combination I use, the bottom track is always visible, and the intermediate track is never visible under the crawl, almost as if there were some perverted Traveling Matte thing going on. I have not designated any tracks as a Traveling Matte.
I have tried altering the Composite Mode of the logo clip. Since it’s all white anyway, going with “Add”, “Screen”, or any of several other modes works fine and restores visibility to V2, but doesn’t answer my questions as to why “Normal” isn’t working where it’s worked so often before. Plus, just like going with an “Animation”-class export from Motion, a different Comp Mode almost always requires a render.
Yes, this whole BG render thing is one thing I’m definitely looking forward to in FCPX. Not to mention actually using all sixteen logical CPU cores to do it.
I tried an uncropped track on V2. That showed up fine under the crawl, but of course defeated the whole purpose by completely covering V1.
So, it would seem this happenstance is narrowed down to one of several possibilities:
1) There is some difference between exporting a Motion project in straight ProRes4X4+Alpha and exporting it in “Animation”+Alpha. Both claim “Millions of colors +Alpha” and seem almost completely similar in the Motion settings window, so any info on this front would be a learning experience for me. The thing is, I’ve never had any trouble to date using the straight ProRes+A version, and many of my Motion exports have been more complex than this one. But okay, I’m happiliy willing to gain knowledge on this.
2) Maybe it’s time to trash my FCP prefs to restore something that’s gone wonky in my Canvas. Has it been a week already? Seriously, though, this is actually a refreshingly rare thing for me to have to do. FCP behaves itself ridiculously well on my BeefyMac. I can count the number of times I’ve had to do this on one hand over the last two years combined. Like I said, ridiculously well-behaved.
3) Something goes wonky as soon as I Crop a track. Couldn’t tell you why, but then again, that’s why I’m askin’.
4) Something else I’m missing entirely.
So, anything anyone can come up with is welcome. Again, I did try searching, so I apologize if this is one of those “RTFM” situations, but this is kind of unique in my experience after lurking here for the better part of a year and using FCP for over 2 years. Also, again, workaround is already discovered, so it’s academic curiosity as much as anything else.
Thanks in advance for any insights,
Brian Wells
All-Too-Infrequent Media Guy
Walt Disney Travel Company
Anaheim, CAObligatory Disclaimer
Look, I am an employee (yes, we use a different term for it, but “employee” will do for this disclaimer) at this time, so you know the drill:
All opinions I may post here are mine and not necessarily those of my employer. The stuff I do for my employer, and the stuff and licenses to use the stuff with which I do it, belongs to them and not to me, so don’t ask me to cough it up under any public circumstances.
If I post any examples of the work I do for my employer, I will hopefully have remembered to go over it with a fine-tooth comb to remove any references to my employer’s specific intellectual property, or anything specifically trademarkable and/or copyrightable by my employer, and/or such material belonging to my employer’s partners, clients, guests, etc.
Should I forget or in any way fail to remove any such material, under no circumstances whatsoever is that to be interpreted as permission, license, or condonement to use, disseminate, profit from, repost, reverse-engineer, recreate, or make a casserole with any such material.