[Morten Carlsen]

I thought that Article was full of non-sense…

Been using Logic (Protools HD is my main DAW) since 1995.

The programming team is sitting in Hamburg, Germany.
And AFAIK, they are still there.

Logic wont be dumped.

We’ll see

[Morten Carlsen]

Probably folks used THAT shot before Kubrick — only they didn’t do it in a H-Wood Flick… and catch fame for it

[Morten Carlsen]

Well.. You ONLY use Proxies DURING working… When rendering out the final project you HAVE to switch back to High Quality Media…

Proxies are a god-sent.. Use them and smile. The way FCPx lets you work with proxies is the most amazing thing I have ever experienced…

Only caveat.. If you work with files having an alpha channel… The proxy does NOT support alpha channels… Aside from that, Proxies are the way to go regardless of original media. It will make FCPx fly !

[Morten Carlsen]

You need to set the compressor ratio to ZERO and Compressor Threshold to 0 ZERO…

Also you NEED to make sure that your signal peaks are actually reaching ZERO db.

Put a GAIN plug before the limiter (compressor) and set to overshoot. Then Add the limiter – now it should NOT cap at -6 db…

[Morten Carlsen]

First of all, you NEED to set the clip to optical flow to properly preview it… Optical flow is fantastic but cause LOTS of artefacts if motion blur is occurring in the clip. So you dont want to just slow down the clip and then in the end set them all to optical flow. That could cause unwanted behavior

If you dont care about that, in your timeline, give the clips which you are slowing down a meta tag…call it, i.e., slowdown… Then when you are done, goto the timeline index and select all the clips with a slowdown TAG (Could even assign “Slowdown” to a role) Then goto the Retime menu and set them all to Optical Flow… or use/program the shortkey… Thats it 😉

[Morten Carlsen]

This is known. And this happens a lot if you have ANY effects applied to the clip.

Use the Feedback options in FCPx and report it to apple, they DO listen and REPLY 😉

[Morten Carlsen]

Go to Audio Effects > Levels…. and insert the “Compressor” from the logic category.

Set Compressor threshold to 0 db and engage the Limiter on the right side of the user interface.
Set it to -0.2 NOT 0… This will “protect” your signal at the threshold set.

Make sure you use the “Platinum” form the circuit type (Should be default)

[Morten Carlsen]

If you dont do this already, use proxies. Using Proxies doesnt get any easier than with FCPx.. And it will seriously speed up your app.

Aside from that if you want the smoothest FCPx you can get, use an SSD drive instead of a spinner; preferably hooked up via Thunderbolt.

[Morten Carlsen]

yes, overusing the KB effect looks like crap. However, imagine having a 1080p project which you plan on releasing as 720..

You’d create a 720 project and ingest the 1920 clips with spatial conform set to none… Here the KB effect becomes extremely interesting.
The KB effect is nothing but animating keyframes only automated… In above scenario the KB effect will save many many hours.

Consider the KB effect as animating several keyframes at once and that on motion pictures. I often use the KB effect to smooth a real camera move.
I’ll just “anti” the move but slightly less which will save me from smoothing the move via motion tracking in AE…

Just a thought

[Morten Carlsen]

We love FCPx and that since the start… However, I do agree that we are reaching a turning point, which I dont like..

The overall stability of 10.0.6 is the worst since its initial release. We had to drop back to PPRO on certain projects because FCPx is so erratic.
Using 2 monitors is more or less a complete no go if you want to maintain your skimmer…

Handles are not acting correctly when setting them back to defaults… The last frame goes black although set to defaults.
Effects’ keyframes are set one keyframe further left than playhead.
Compound clips keep exhibiting black frames when used inside a project.
Relinking Project files has an enormous bug which will cause all sorts of havoc when sharing projects…

Since 10.0.6 — I have personally reported beyond 100 new bugs… All which I can re=create 100% and that on 3 different systems running 3 different OS X…

10.0.6 sports great features but its overall stability isnt even worth a beta state… I feel like a beta tester. And I dont like that one bit 🙂

That said,, FPCx is the also the most advance NLE the world has ever seen… We just need to get those nasty bugs ironed out ! So keep feedbacking Apple… The DO listen and respond !