10.07 available

Just bug fixes though

Wow. They did manage to fit in 10.0.7 in 2012! With 10.0.6 coming out so much later that we all anticipated I was doubtful they'd get in under the wire... but there you go.

No update to Apple's FCPX page showcasing any upcoming features (like they did with 10.0.2) though...

It's nice to see Apple updating FCPX so often! Can't think of another company that is so responsive with their editing software!

Interesting.

Can anyone confirm if the bug fixes includes a remedy to the problems with Magic Bullet and Neat Video?

I am still on 10.0.5; presumably 10.0.7 includes all of the features in 10.0.6 too, right?

simonpwood wrote: I am still on 10.0.5; presumably 10.0.7 includes all of the features in 10.0.6 too, right?

Unquestionably.

My question exactly. I was just on the Red Giant website and didn't see anything. What is up with that company?

Disproportionate Pictures wrote: Wow. They did manage to fit in 10.0.7 in 2012! With 10.0.6 coming out so much later that we all anticipated

You mean YOU anticipated! :lol:

They released it exactly when I thought they would. Heh heh.

Great to see Apple working hard to make sure we have a happy Christmas and best of all it means that it clears the way for the next feature update in April (my wild prediction) will be 10.0.7 which will have collaborative editing. (My 2nd wild prediction)

Just a heads up... .07 broke some CoreMelt transitions... All part of Coremelt Free I believe...

The 3 Delta V Motion transitions and the 4 Trx Filmic transitions immediately crash FCP X every time.

I went through everything of theirs I have just in case... SliceX (thank god!), gadget, luminous, pigment and shatter effects all work fine. The SliceX adjust title plugins work fine. The C2 Free Templates transitions all work fine...

Yep, for me, too.

Seanus wrote: You mean YOU anticipated! :lol:

They released it exactly when I thought they would. Heh heh.

Great to see Apple working hard to make sure we have a happy Christmas and best of all it means that it clears the way for the next feature update in April (my wild prediction) will be 10.0.7 which will have collaborative editing. (My 2nd wild prediction)

You are 100% correct on that first part. I put my money on the table and was way off. But there was just no previous data to suggest even a feature update would take that long- and that's all I was basing my projections on.

With that honest self-deprication in mind, I will reveal that I was informed post 10.0.6 that the release date was pushed back "several weeks" because it wasn't ready. It still would have been outside my projections, but not quite yours either :lol:

It was what it was, and "Better better than sooner" I say.

As for predictions, here's my cards again.

I say we see a feature release 10.0.8 in late February. Interesting to note that this is the first time we don't have a preview tentpole feature list. Followed by a 10.0.9 in early April, mostly bug fixes, but perhaps supporting 3rd party plugin announcements at NAB.

That will set the stage for a 10.1 preview at the Supermeet and a launch around June.

I don't think we'll see features like collaborative editing, audio mixing, or whatever "next generation" features until 10.1- which WILL be a paid upgrade.

Stabilisation - still missing thou, I have tried opening clips in their own timeline and still no stabilisation option?

Hi, yes 10.0.7 broke some CoreMelt plugins (transitions) and didn't fix a major render glitch bug which effects many third party developers. We didn't get any warning of this update so couldn't test it.

At this stage we advise you not to update to 10.0.7 if you use our transitions. We're already working on a fix for this.

The guys from NeatVideo are saying the issue with their Plug-In has not been resolved also.

Dammit.

They are saying essentially the same thing that the guys from Red Giant and CoreMelt are saying; this is an issue with the FCPX 10.06 update and they are unable to get to the root of the problem. It needs to be dealt with by Apple.

The have reported the issue to Apple and have requested that users do the same:

"The best solution would be to ask Apple to fix the bugs as soon as possible because these problems affect many people.

You can use this form to do that: www.apple.com/feedback/finalcutpro.html

Please ask to fix the "flickering" / "colour glitch" / "rogue frame" bug in FCPX and, as it turns out, in Motion 5 too.

The more people will ask the more chance that the bugs will be fixed soon."

Interestingly they say this in a later post:

"We are getting some indications that it might be fixed with the upcoming update of OSX itself. The problem may be there, in the system core or in video drivers."


Either way; I'm glad I'm still on 10.05.

simonpwood wrote:
"We are getting some indications that it might be fixed with the upcoming update of OSX itself. The problem may be there, in the system core or in video drivers."

Yes, understand I'm speculating here but this is my guess. Apple changed the render methods in a major way for FCP 10.0.6. In FCP X 10.0.5 and before background renders were using a software render method and you might have noticed they were many times slower than doing an export. Apple changed this in FCP X 10.0.6 so that all effects rendered using the graphics card when doing background renders. They now seem to have a glitch that corrupts renders when using complicated effects chains, even with only their own built in effects.

Fixing this is complex, and probably is going to to involve the FCP X team working closely with the graphics driver and OS X teams to find a solution.

However, it looks to me like they changed the render method for compressor in 10.0.7. I "send to compressor" today and couldn't produce any render glitches, while in 10.0.6 I did.

So it seems a work around is to use send to compressor to output if you get render glitches.

I find it very odd that Apple doesn't give plugin developers advanced notice of updates? Can someone explain this phenomenon. I've done lots of beta testing in a previous decade and the software companies were really interested in keeping plugin developers in the loop. It seems like basic respect.

What's the point of an API if you dis the people who are trying to implement it?

Scratching me head.

Yes, its very weird. Especially as a lot of these plug-ins fill in the gaps of the software, and improve it overall.

Surely the support of 3rd party plug-in developers is an indication of how good the software is (who would want to buy software that is not really supported by 3rd party developers - Sony Vegas; I'm looking at you)?

There is definitely room for improvement in this regard.

Hmm. That may explain the crashes I was having when trying to export an XDCAM timeline that had two FCPX filters and two CoreMelt Slice X filters. That said, when I did the old "Render All" before I exported, no problem. It may be something to do with how the system and the card work to render on export? Above my pay grade.

CoreMelt wrote:

simonpwood wrote:
"We are getting some indications that it might be fixed with the upcoming update of OSX itself. The problem may be there, in the system core or in video drivers."

Yes, understand I'm speculating here but this is my guess. Apple changed the render methods in a major way for FCP 10.0.6. In FCP X 10.0.5 and before background renders were using a software render method and you might have noticed they were many times slower than doing an export. Apple changed this in FCP X 10.0.6 so that all effects rendered using the graphics card when doing background renders. They now seem to have a glitch that corrupts renders when using complicated effects chains, even with only their own built in effects.

Fixing this is complex, and probably is going to to involve the FCP X team working closely with the graphics driver and OS X teams to find a solution.

However, it looks to me like they changed the render method for compressor in 10.0.7. I "send to compressor" today and couldn't produce any render glitches, while in 10.0.6 I did.

So it seems a work around is to use send to compressor to output if you get render glitches.

simonpwood wrote: Yes, its very weird. Especially as a lot of these plug-ins fill in the gaps of the software, and improve it overall.

Surely the support of 3rd party plug-in developers is an indication of how good the software is (who would want to buy software that is not really supported by 3rd party developers - Sony Vegas; I'm looking at you)?

There is definitely room for improvement in this regard.

I'm really surprised that people are taking this bug and lack of communication from Apple so lightly. Seems to me that whoever is managing FCPX is simultaneously a genius and an ass.

10.0.7 seemed to fix Neat Video for me. Magic Bullet never broke in 10.0.6 on my system and works fine so far in 10.0.7. They decided to not fix a DVCPRO HD import issue that got messed up in 10.0.6 this time around. I love FCPX, always keepin' us on our toes!! Cant wait to see what 10.0.8 fixes and breaks!! I don't think I've ever loved and hated a program any more than this one.

Anyone else working fine with MB Looks and 10.0.7? I stopped using MB Looks when I upgraded to .06, and would like to be able to bring it back into my workflow.