[David Powell]

Make a hard cut on V1
Drop the film burn clip on on V2 with the full burn right over the transition
Add avid FX to the film burn clip on the timeline.

Patch to v2 and go into effect mode click Avid FX to open it.
Avid FX will show both tracks click on your film burn clip and change the composite mode to “Add”.
I like to bring the opacity down a little bit as well. Do this in Avid FX instead of MC.

Apply. Now Go into FX mode once again and drag this effect to your FX favorite bin and name it burn transition or “add mode 60per opacity” and drop it on all the rest of your burns. Or you can make one at full opacity and use it to change composite modes on any clip.

Think of Avid FX as your “inspector” in FCP/Motion parlance.

[David Powell]

After doing some research online, I think the problem is that I’m using the trial mode. Seems there is a codec issue with the trial mode that doesn’t exist when you subscribe.

[David Powell]

So just for the heck of it I tried to open an Avid AAF project in premiere. Did an old school stack multi-cam (dslr is a nightmare to multicam in avid) with 3 layers of video and 7 tracks of audio.

Premiere CC wouldn’t open it. Same error as the FCP file. So then I fired up PPCS6 and tried the same thing. It actually did open the AAF but for some reason the video is cropped and the sequence setting is DV and unchangeable. One of the video files in underneath the audio tracks, and the whole thing preview monitor froze after a few seconds of play at 1/2 res. Mind you there is only one stream playing at a time. I have a pretty beefy iMac. That being said the translation is horrible either way. And of course the FCP X27 xml didn’t open at all.

Any idea why CS6 would at least half ass work with the AAF and CC won’t at all?

[David Powell]

I need to get it in my head that that is always the first place to start. Got used to being able to work natively in the others. Steve, bring make another project for your mixed frame rate material, then bring those bins into your main project.

[David Powell]

It was my understanding that Xto7 did translate multicam but finalized the media. Any other preferences I need to setup to make Premiere accept it?

[David Powell]

Well I bought X 2 7 and it’s been all bad so far. I decided to export an xml from my most recent X project to run a test. To my pleasant surprise premiere actually modifies the original media and now the fcpx project is messed up and crashes. On top of that the xml won’t even open in Premier so far. Took off to the gym to blow off frustration. Hopefully I can find a solution to both problems when I get back.

[David Powell]

There are several things that have changed with FCPX that certainly could not be called “features” imo. The range selection behavior vs i/o points is one of them. You have to get used to your range disappearing if you click anywhere in the Storyline. You can’t use them as a strong marker or point indicator the way you can in 7 or MC. True matchframing doesn’t really exist in X in the many ways that it’s useful in other NLE’s.

There are quite a few things that annoy me to all end. I just accept X for the things it does well and try and ignore all the lack of features.

[David Powell]

Honestly, all the “problems” you’ve mentioned are very simple things. If you’d spend $60 and buy avid media composer essentials book and about 3 hours to read it, it would save you all your headaches. I’ll spoon feed you one. Adding markers from the keyboard.

I have a completely custom keyboard so I can’t remember if there is a stock command. Hit “command 3” this will show you where everything is mapped. Now go to “settings” tab where your main bin is, press “K” double click keyboard, click “button to button reassignment” you’ll find markers (previously called locators) under the last tab I believe. Drag it to the button of your choice. Hit “shift” to learn whats mapped under the modifier or to to map it to a modified command.

make sure you don’t leave the Command pallet open, it will cause playback problems.

I will mention that the command modified stuff is not show unfortunately. In this regard fcp has better functionality. But most strokes don’t use “command” in avid thanks to modes, which makes for a better experience. You can easily change the font bg color etc in the interface. Avid’s interface is far more customizable than fcp’s especially with the workspaces, which you’ll have to do some reading on.

[David Powell]

I switched from FCP to Avid several years back. I decided without ever having fired it up to cut a feature on it and did so successfully. Reason was I had Steve Cohen’s “Avid Agility” at my side the whole way. I’ve since done pro certification with Avid, but that book gave me everything I needed to competently edit and then some.

The trimming in Avid so far advanced over FCP 7 or X (both of which I’ve used extensively) that you will not want to go back after you get the hang. It would be worth paying someone who’s used both to sit with you a couple of days and have them show you the differences. The importing and file handling differences are probably the biggest hurdle. The feature set is very deep in Avid and but you can get the basics down rather quickly.

[David Powell]

Just set up another custom layout and give it a different name. The Go to “Final Cut Pro-Commands and you’ll see all the different layout names you’ve made.