Marcus Moore
Forum Replies Created
-
Uh, yeah…
Creating traditional freeze frames from project or event clips was added back in 10.0.6 almost a year ago.
There’s a section on it in this write up by Steve Martin about 2/3rd the way down.
https://www.kenstone.net/fcp_homepage/fcp_x_first_look_06_martin.html
-
I agree that there will always be a difference between Pro and consumer- I think the supposition might be that the consumer-side will be able to do more (as the general literacy of video increases), and the Pro side will become less opaque as the UI of the tools evolves; and that its the ‘prosumer’ tools that are being squeezed out of existence- the lower-tier AVID solutions, the Final Cut Expresses, and the Soundtrack Pros which are disappearing. Now there’s only Garage Band and Logic Pro X. iMovie and Final Cut Pro X.
-
Yeah. It’s a bug Apple definitely needs to fix.
-
Unfortunately, synch clips will not retain TC from the RED files. This would obviously be an issue going to resolve.
Having just gone thru this process- I thought was was screwed getting ready to export to Resolve. Good news is that when you’re ready to export, just use the Timeline index to select all your sync clips, then use the “Break Apart Clip Items” function and that will separate your Red sync clips into the raw RED files and the zoom audio.
-
And you can use the up arrow to lift clips out of the primary storyline as well. I find this helpful if I want to play around with a few clips without disturbing the timing of the primary storyline.
-
I agree. The execution of CC in FCPX is very good, with its own version of Resolves “power windows” and “qualifiers” making some fine work pretty simple. What’s lacking is depth to the controls (keyframes, curves, alternate 3-way interface, tracking or at least key framing for masks). But just like with audio- there is very likely a ceiling to the complexity to the controls Apple is interested in integrating. Knowing that anyone in certain workflows will always end up punting that part of the process to another person working with specialized software.
-
I think it will too. At least I really hope so.
After moving 2 of my clients over to FCPX in the last year, I’ve run into some resistance from a couple of my other close-working still-FCP7 editors. They know and trust me, but the volume of negativity from other people they know in post can be, I’m sure, unsettling. My response, and I’m fairly sure I’m correct, is that much of the sh*t talk is coming from editors who’ve either NEVER opened the software, opened it make a quick judgement and bailed, or finally tried it VERY early on and haven’t kept up with how big the improvements have been.
While features are nice, I think by biggest hopes for 10.1 are at a very fundamental level. FCPX presents some radical departures from other NLEs. Where they’ve implemented a complete solution, like Event metadata and logging structure, the benefits are clear. Its in the timeline that I think FCPX needs to fill the gaps and make a clear case for the magnetic/connected/”trackless” paradigm they’re presenting. The Project timeline is a mess, and desperately needs to use the metadata at least as effectively as Events do in terms of organization. As I’ve said many times before, right now the Project timeline is like The Event browser if there were no Keyword/Smart collections. It’s a soup of clips. And while in simple timelines that’s no an issue, the deeper it gets the more frustrating it becomes.
Especially after seeing Stack Tracks in the new Logic, I can SEE very clearly a Roles-based structure which brings clear organization back to the timeline, without sacrificing the flexible editing that FCPX “trackless” editing allows.
-
That’s me as well. Switched my interim laptop with my wifes 2011 iMac while waiting for the new MacPro. It’s been a competent machine, but I’m excited to be on a Mac Pro again. The lack of an SSD in this thing after having one in the laptop is especially painful.
There are very few things I could see being “exclusive” to the MacPro. This discounts the general speed and performance benefits that come with a faster machine.
1. BACKGROUND, background rending. Apple says as much on the MacPro website. While perhaps not technically MacPro exclusive, this feature could very well be limited to dual-GPU machines.
2. Dual scopes. Again, this could possibly be tied to dual GPU setups.
If Mavericks does bring some OS based enhancements, then perhaps 10.9 might be required to run FCPX 10.1. I’m sure that would cheese some people off, but Apple is very keen to keep users up to date with OSX. At this stage, there’d be very few machines that people would want to use FCPX on that couldn’t run Mavericks.
While the MacPro is a nice tie-in to launch a major new version of Final Cut, I truly hope that there will be much more meat to ACTUAL improvements in the software. We’ve been getting a couple features here and there for 2 years now, but with a YEAR between 10.0.6 and now, there’s development room there to make some BIG improvement to the software. In UI, in editing workflow, in cross-program compatibility…
They’ve had a year to execute on user and industry feedback- if MacPro optimization is the big FCPX news this fall, I’ll be a bit disappointed.
-
I don’t think the MacPro optimization will be the big deal. If you’ve got a new MacPro, great- but most won’t.
The good thing about the MacPro is that it has ended the discussion on Apple walking away from a high-end machine. It may not be THE high end machine everyone wanted, but it closes the door on the “no more MacPro” discussions. And that was important. The release of Logic Pro X is is also a good bellwether for Apples interest in the Pro market.
But ultimately I think its what features and improvements they’ve made to the software since last October that will continue to chip away at the doubters arguments that “it’s not Pro software”, and spurn new adoption.
A year later, the big issues still remain:
• audio mixing
• collaborative workflow
• motion round-tripping
• timeline organization -
It will probably be a full year since 10.0.6 came out by the time 10.1 is released.
I’m thinking late October, but that may be dependant on the launch of both Mavericks and the MacPro.