FCPX 10.1.2 PRE-RELEASE DISCUSSION

Disproportionate Pictures wrote: ProApps were never going to be part of this event. Never have been, never will.

Was hoping the reason we haven't seen an update was because of dependance on new hardware.
Well I guess we won't see anything hardware related until September/October now.

That makes me think any FCP X update will most likely be bug fixes until then. Hope I'm wrong.

Apple pro apps department needs a spokesperson. Maybe even three, one for video apps, one for audio apps and one for photo apps. I think Al Mooney is doing a great job at Adobe, and Apple should have done that some time ago. If we have Federighi for OSX and iOS, and Schiller for hardware, then there should be someone for FCPX, Motion, Aperture etc. I know it's a small share of their market, but they should do it anyway, it wouldn't cost them too much I guess.

Seanus wrote: Was hoping the reason we haven't seen an update was because of dependance on new hardware.
Well I guess we won't see anything hardware related until September/October now.

That makes me think any FCP X update will most likely be bug fixes until then. Hope I'm wrong.

I think you're proceeding under the false assumption that new hardware is always driving FCP X updates.

There's only been 2 X releases tied to hardware- First 10.0.5, which was a release specifically to address Retina support for the just-launched rMBP in 2012. Second, 10.1 which was tied to optimizations for the MacPro last year.

So only 1 feature release has had anything to do specifically with hardware.

I don't see anything happening with Macs this year that will delay FCP X updates. X is already Retina; so regardless of whether Apple releases a Retina MacBookAir, or iMac, or Cinema Display- FCP X is already ready for that. And the only other thing will be the regular annual processor improvements from this year's Intel chips. There's no reason why that should affect anything either.

Well just saw this and found it interesting...


forums.macrumors.com/showpost.php?p=19177316&postcount=83

Yup. Alex had tweeted about this. shortly after the launch.

Curious. But they've got until October or so to get things going. This IS the first Beta. It's going to be rough going for a while.

I was able to get final cut (current version) to open on 10.10 by showing package contents and launching the unix executable directly. after that everything seems normal minus the fact that it doesn't want to go "fullscreen"

Now, I'm thinking the Ppro, Avid and Smoke 2015 were probably shaking their heads and started worrying again.Because, they probably wonder if their NLE will work with the new OSX.


Also, I'm a bit of worry about FCPX. My concern is that, is FCPX developer team are lacking to add new concepts in FPCX? Is it because these NLE competitors are taking over with their advance features (UI design,color board,trackbase,keyframes,compositing, motion effects,3D graphics, desktop subscription,etc.) And that's the reason million of users subscribed to Adobe CC and recently, it caused them outage issue but it has been fixed. And we know for sure, it can happen to other NLE.

We know for sure,FCPX just want simply,fast and better NLE. But it's still lacking of pro features. The 10.1. came out it has all the pro features and still not enough for professional editors. And it can't even caught up with Adobe,Avid and Smoke 2015. Yes, the price for FCPX is only $300 and some people still complaining about it due to lack adding new features and bugs issue that until now it haven't fix yet. And until now, we are still waiting for the update to be available in App Store. :pinch: :oops: :dry:

ejis1979 wrote: We know for sure,FCPX just want simply,fast and better NLE. But it's still lacking of pro features. The 10.1. came out it has all the pro features and still not enough for professional editors.

That's so funny....

Each time I have to go back and re-open a project created in Premiere Pro I feel it's so old and clunky and missing so much that I now take for granted in FCPX.

Sure, FCPX doesn't have send to AE or Audition, but as an editor it's so much quicker to work with, and exporting the final project is orders of magnitude faster for me on FCPX than with Premiere Pro.

Sometimes I really long for the times when betas were still tested secretly and in silence by professionals who knew what they were doing. And when people posted comments based on facts and not on presumptions.

- Ronny

Seanus wrote: Would love to see much better match framing. It is far too difficult to get back to the original source if you've used a Multicam clip. Also it's a pain in the ass how hitting match frame take you back to the Event and not the keyword collection. Takes ages to figure out where the clip even Isfahan you have hundreds of clips.

Yes, I think we all agree on that. This is something that has been pointed out by several users. Also, as Richard Taylor mentions in his Top Request List , Match Frame should work better with Compound Clips and Auditions (Request #78), as well as Multicam clips.

We should be able to match frame to the original "Compound clip / Audition / Multicam clip" in the Browser, and then, to a particular source file inside them. This is something that works really well in Avid (with a simple Match Frame command to go back to any previous iteration of a clip), and that FCP Legacy didn’t implement that well in my opinion, with many different commands for the same purpose: Match Frame Master Clip, Source File, Subclip Parent Clip, etc.

The problem that I see for this to work in a similar fashion inside FCPX is that without a track selector or something like that, how can we “tell” the software to which source clip/layer inside the Compound/Audition/Multicam clip we want to match frame to?

In FCPX the only way is to:

- Open the combined clip in the timeline.
- Select the desired layer by placing the cursor on top and pressing the “C” key, and finally hit “Reveal in Browser” (Shift+F) to match frame to the selected source clip.

When you open a Compound clip, the playhead is placed in the same frame where it was in the main timeline. This works as expected, so there is nothing to fix here.

The problem with Multicam clips and with Synchronized clips is that when you open them in the angle editor or timeline, the playhead jumps to the beginning of the clip's timeline. This is the one thing that should be fixed.

Since we cannot "open in the timeline" an Audition, I don't think there is an easy way to match frame back to a particular source clip inside the audition. This could be the easiest way to fix this: to make Auditions behave like compound clips, in the sense that when you opened Auditions in the timeline, you would see a stack of all the clips inside it.

ronny courtens wrote: Sometimes I really long for the times when betas were still tested secretly and in silence by professionals who knew what they were doing. And when people posted comments based on facts and not on presumptions.

- Ronny

Ronny, I could not agree more.

That's why I'm about to click the 'Unsubscribe' button, so I don't get an email every time someone posts here.

@Alex4D

Disproportionate Pictures wrote: I think you're proceeding under the false assumption that new hardware is always driving FCP X updates.

Nah was just hoping if they showed us some new 4K gear they might want to show off some nice software running on it.

I've been around too long to try and predict when and what Apple will update.

I just live in hope.

And I wish the SUBSCRIBE button was OFF by default. Or am I missing in something?

I've just realized starting FCPX that we are bound to get a very different icon soon, since the current one is very 3D and not at all flat. I wonder how it will look, and whether the new icon will coincide with new features. Just a thought...

It's possible! R.I.P. Preview Kid

www.tuaw.com/2014/06/05/after-14-years-t...review-icon-is-no-m/

Although not the kid himself, who is probably as the article states about to start college. I hope whoever he is will be relieved his baby photo won't be on every damn mac he sees anymore.

Well, they've got until October/November to come up with the new version. The metaphor's aren't totally different. Overall it 10.10 wasn't the supremely dramatic redesign that many were expecting/fearing.

Dark Mode is interesting.

I hope they don't wait until that long to update FCPX. At least throw us a bone with a bug-fix update. We need one BADLY. So badly. It's like they barely even care about fixing these bugs. Hopefully they're going over them again and again to make sure they're actually fixed. That's optimism at it's best but I'm psessimistic by nature (which I highly recommend, by the way).

Seanus wrote: And I wish the SUBSCRIBE button was OFF by default.

You and me both! I also wish there were bounding boxes around the quotes to make them easier to identify. The whole forum really needs a facelift. Who is responsible the forum, by the way?

Darren Roark wrote: R.I.P. Preview Kid

I wonder if they used Pixelmator's new healing tool to take the kid out of that picture?

I Think that this week's WWDC announcements should be a good object lesson in the fact that Apple IS listening. This will be old news to some around here, but it bears repeating.

Developers had been asking for the same things for years, and many had though it simply wasn't in Apple's nature to provide some of the services and features they were looking for. Literally the week before WWDC I'd listened to several popular podcasts talking about their wish lists for iOS and developer tools- bemoaning that they were probably not on Apple's radar.

Well, a week later, MANY of those things are now in developers hands.

So keep making your problems and wishes known via the feedback tools. Someone is reading that stuff!

In case anyone missed it... there was a big OS announcement! :huh:

and FCPX 10.1.1 won't run on the Yosemite Beta.
I think its clear the wait for major update is OS related...

But the fact that we've waited a bit for a major feature update usually means that the next one will be big.

Finger's Crossed.


--- then again ---
What the hell do I know...