Marcus Moore
Forum Replies Created
-
Agreed. I don’t see any advancement in editing that involves fundamentally MORE movement. I can see the integration of desk level touch devices for functions which quick keys aren’t the preferred form of data input, like Color Correcting or Audio Mixing. Basically the same things physical consoles are already used for. I will be interesting to see if the next FCPX follows in the steps of Logic Pro X and has an accompanying iPad app for functions like this.
Apple has already poo-pooed touchscreen desktops years ago. Saying it was (rightfully so) ergonomically awful.
-
True enough. I guess “Fall” just reads to me as a bit more early leaning than “later this year”.
My guess is that we’ll get some update on availability at an event in late October. No stage time (it had that moment in the sun at WWDC)- just preorder dates or something; with a big update to the MacPro page on apple.com for more details and pricing info.
-
Yeah… the placement of this ad in theatres is a bit bewildering. I suppose people who might buy a MacPro could be seeing a movie…
The only salient information is framing the release as “Fall” vs “later this year” from WWDC. “later this year” is pretty pessimistic. “Fall” is slightly more encouraging.
Yes I will be buying one.
-
[Andrew Kimery] “If I remember correctly they did ask a few select people for feedback (one of these editor’s gave a demo at LAFCPUG a couple of years ago but I can’t remember his name) and the feedback was promptly ignored. Like you said, Apple had a vision and the stuck to it. I’d imagine the requested feedback was more to gauge reaction than for shaping the software.”
I know who you’re talking about, but I can’t remember his name either. That initial preview event was in February of 2011. FCPX was demoed at NAB in April, and launched in July.
I think, realistically, it wasn’t that his feedback was ignored so much as there wasn’t time to implement it before launch. It would be interesting to go back and see how much of that feedback has been implemented now.
While I think most of FCPX’s new methodology works very well, IF 10.1 is as big an update as some are theorizing (it having been a year since the last feature update), this will be the time to see if there are any major “course corrections” back to Legacy ideas. We might have already seen Apple do this by bring back the Program monitor (though that could have always been part of their plan, we’ll never know for sure), and I’m sure if ultimately one aspect or another of FCPX just isn’t working out the way they have planned, I don’t doubt for a minute that they’ll fix it. For instance, there’s been a lot of people wondering if the advantages of Event/Project structure outweigh the disadvantages.
-
I wish we could get away from this “listening to editors” circular logic in reference to X.
You can’t get feedback from users to create something which doesn’t exist yet.
Did the FCPX development team listen to customers when coming up with the core concepts of the magnetic timeline, connected clips, or trackless timeline? No, of course they couldn’t. Because they were trying to define some key differences in methodology between the way legacy and X were going to function. You can’t ask for directions when you’re hacking a new path thru the jungle.
This is the decision they made.
But in refining FCPX thru 9 updates over the past 2 years, has the dev team listened to people who’ve used the software, and updated it to make it better for editors. Absolutely. Everything they’ve added back has made it a better, more professional Final Cut Pro X.
Apple does listen. But they’re also not simply reactionary. FCP8 would have obviously been a simpler sell. They HAD to know they were taking a huge risk.
2 years later, from where I sit, I think their gamble will ultimately pay off. I know for a fact that I have reaped enormous rewards from FCPX in terms of my productivity and profitability. Right now the tool set encompasses my needs, but not everyones. I feel pretty confident that as the feature-set grows and deepens, the core strengths of the software will apply to more and more workflows.
I couldn’t have asked Apple for FCPX 2 years ago, but 2 years later I’m sure glad they didn’t ask me!
-
Agreed. An iPad app as a control surface for FCPX audio mixing, colour correction would be the bees knees!
-
As if by coincidence- or Larry Jordan is trolling these forums!
https://www.larryjordan.biz/fcp-x-create-freeze-frames/
-
To be fair, I wasn’t sure about this myself. But I did remember a MacBreakStudio where they talked about this. Couldn’t find the video tutorial, but the article from SM refreshed my memory.
-
I guess I’d wonder why you’d want your bins cluttered with FF that would only seemly have a single Project use.
-
The simple non-destructive way to do what you want is
1. Go to the point in the sequence you want the freeze-frame
2. With the clip you want selected, SHFT-F to find the clip in the Event Browser
3. OPTION-F to add that keyframe back in as a connected clip.Two keystrokes. Very fast.
I’d agree that being able to just do OPTION-F right from a Project clip would be one stroke less, and therefore faster. But what’s above is at least as fast as it was before.