So, what did you say to the new Apple FCPX survey?

[Timothy Auld]

I said that I would love to be able to turn timeline magnetism off, as with Avid and sync locks. And that I found it very annoying that Command Z does not always undo the last action but seems to pick and choose what it will undo and what it will not.

Tim

[John Rofrano]

The feature I requested was a Master Audio Bus so that you could add a Brick Wall Limiter or a Compressor to the overall audio mix and make sure that the audio was broadcast safe. You need the same thing for video (a Maser Video Bus) to add plug-ins that affect the overall look or keep video broadcast safe as well. This is one of the things I miss in FCP X that Sony Vegas Pro has. Mixing audio is the weak spot for me in FCP X.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Scott Witthaus]

I asked for a Send To Motion and added a request for customizable and re-usable workspace layouts

Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter

[David Mathis]

Same here and keyframing for color correction.

Also, asked for tracks to be brought back! 😉

When life gives me lemons, there are two ways I look at it: As lemonade or a gas guzzling clunker that could fall apart on me at any moment. I prefer lemonade.

[John Rofrano]

[David Mathis] “Same here and keyframing for color correction. “

Darn, I forgot to ask for S-Curves. How on earth can you color correct without S-Curves?!?!

Someone who hasn’t taken the survey yet please ask for S-Curves to adjust luminance/gamma. 😉

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Scott Witthaus]

Yes, CC keyframes!

Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter

[Nicholas Kleczewski]

Performance, performance, performance!! I think I could honestly live without a single feature upgrade if I could be promised a world in which every time I clicked a clip in the browser, highlighted a clip in the timeline, did anything there was the .5 second delay (or longer as the memory leaks wear on in a day). It’s crazy going back to an old fcp7 or avid project and having the interface mostly always instantly respond. Sounds whiney, but it adds up on the sanity depleter!

Director, Editor, Colorist
http://www.trsociety.com

[Steve Connor]

[Nicholas Kleczewski] “Performance, performance, performance!! I think I could honestly live without a single feature upgrade if I could be promised a world in which every time I clicked a clip in the browser, highlighted a clip in the timeline, did anything there was the .5 second delay (or longer as the memory leaks wear on in a day). It’s crazy going back to an old fcp7 or avid project and having the interface mostly always instantly respond. Sounds whiney, but it adds up on the sanity depleter!”

What system are you using?

[Nicholas Kleczewski]

MPt with 280X, MacBook pro retina, 8 core nMP D700. All the same. It’s a UI issue. FCPX is trying to do too much all the time. I’ve suggested to them they create some sort of performance slider. How much caching of thumbnails, waveforms etc, vs instant UI response. There’s times when either are valuable. It got a lot better since 10.1 for sure, I like to think I had some small part in that, Them asking to be involved on a massive 4TB documentary I was editing and getting beach balls of death across the board. But it’s still a thing in genetically UI, that barely perceptible delay in actions.

I have found working off a raid getting at least 600 MBs does help significantly. My guess is it’s that Quick small file access exchange happening with FCPXs database on every move. But it’s still there over time even on an internal nMP project pulling 900+ MBs

Director, Editor, Colorist
http://www.trsociety.com

[Jeremy Garchow]

[Nicholas Kleczewski] “MPt with 280X, MacBook pro retina, 8 core nMP D700. All the same. It’s a UI issue. FCPX is trying to do too much all the time. I’ve suggested to them they create some sort of performance slider. “

I find that closing the inspector helps a lot. I think these small delays are due in part, to FCPX finding the associated landing clip, and then displaying all of it’s info in the inspector. I have remapped the inspector key to be a toggle (f16).