FCPX 10.0.6 3rd party products. What works and what doesn't work?

BenB wrote: Apple doesn't say anything to anyone until a product is actually launched.

Apple does provide information on known bugs and work arounds via Technotes and it's my personal opinion they should release a tech note on this issue.

At CoreMelt we have seen a similar render glitch when users stack multiple plugins together. When we investigated the problem we could reproduce the same issue using only Apple's own sample code for fxplug effects and built in plugins, and with none of our own plugins or any other plugins installed. We've sent them that information. I can't say for sure but it looks like Red Giant and most other plugin makers are experiencing the same problem.

Most of our customers don't see this problem, it not only depends on stacking effects it also depends on your exact combination of graphics card, mac os x version, other hardware installed etc. In some cases customers were having problems and upgrading the matrox drivers fixed it.

Our best guess is that its some kind of multi-threading render bug where subtle timing changes trigger bugs in the graphics card drivers.

We did find a work around, if you have a project that you need to output and are experiencing render glitches, render to an image sequence (by adding image sequence as a destination), then convert to a quicktime and your render will be glitch free.

RonPriest wrote: Hey Simon, unless you rely heavily on 3rd party plugins and effects, I wouldn't let these rendering problems stop you from upgrading to 10.0.6. The benefits far outweigh the associated render bugs with 3rd party effects and transitions.

Well as much as I like FCPX (and I really do like it), there are a number of areas that I find lacking. 3rd Party plug ins fill those gaps for me. Noise reduction can only be handled by Neat Video at the moment, and MBL really streamlines grading for me - so I'm not willing to lose those two plug-ins on a gamble that they might or might not work. If we had some sort of acknowledgement from the developers (of FCPX) that they are aware of the problem and are working on it then I might be willing to upgrade.

As it is 10.0.5 does everything I need, and while the updates sound fine its not worth the risk to me personally. For this reason I never upgrade until I know for sure that the 3rd party plug ins are working.

Hi Simon,

If you don't really need the extra features of 10.0.6 and these plugins are so crucial to you I agree you should stay with 10.0.5 at this moment. I have been in contact with someone at Apple about the MBL filters problem and although I can not speak on their behalf I can assure you they are aware of this issue. Unfortunately it is not as simple as one may think. I think we all agree that the dev team has gone through great efforts in the past year supplying frequent upgrades and fixes, so I'm sure they'll fix this as well in due time. FCP10 has been developed as a framework, so 3rd party plugins will always be very important to fill particular needs for individual editors. I think that's a good way of developing an NLE.

In the meantime I have been testing the BCC beta plugins for FCP10. There is a very decent noise reduction filter in this package that IMO can rival with Neat. In fact the quality of the whole plugin package is very high, but so is the price tag

Hey Simon, I'm happy to report that FCPX 10.0.7 has fixed the issues I was having with rendering effects in Looks!

That's great if fixed looks for you. Interestingly, Red Giant has said "Unfortunately this is not the update we are waiting for." in a comment post on their blog. Which I guess puts a fix into next year at this stage

Oh really? Well, I re-rendered a project that I had problems with, and didn't get any glitches. Perhaps I was just lucky on this one project. I'll continue to test it out. That's not good news.

I haven't run into the issue myself on a MacBook Pro (Mid 2010) with a 330M Nvidia GFX card. I think I read the 'looks bug' is only with certain gfx cards. So maybe they fixed it for some and not others in this release?

Or, I did read that popular image editing software pixelmator has an issue with the gfx drivers in 10.8.2. This is pure speculation but maybe the issue runs deeper then an FCPX update and it will take 10.8.3 to fully resolve it for everyone?

Where exactly do they say "Unfortunately this is not the update we are waiting for."? I did read where they say: "We have found it difficult to reproduce the issue in Compressor 4 and for those of you who own it, this might be a good workaround while we wait for a full fix in FCP X."

There was an update to Compressor today also. Are they saying that if you have compressor that you might not have the rendering problem?

The only place I've seen them reference the update is a brief reply in the comments of the original post on their blog. In response to someone saying "Hey, 10.0.7 is out" they reply.

"Unfortunately this is not the update we are waiting for.
We are just as anxious as our customers to get this resolved.
Kaylinn -RedGiant.com"

www.redgiantsoftware.com/blog/2012/10/23...get-it-now/#comments

I get the impression the bug is as frustrating for them as it is for users. I hadn't read about the compressor work around. That could be handy for folks needing a work around.

Yep, I was just able to duplicate the glitch in another project I was testing. So 10.0.7 didn't fix the MBL problem. Perhaps it IS just a MBL problem and not Apples problem? I'm certainly starting to loose confidence in Red Giant.

Lets wait till the dust settles before we start pointing fingers..
Unless, that is someone has a clear answer to the problem, I haven't seen one in this forum. or any other (tiff sequence didn't work for 10.0.6. still need to try 10.0.7)
Don't get me wrong, I paid good money for MB and FCPX to work for my projects, and I need them to play nice by early next month. For us, the combination of looks and Tonalizer is just what we're looking for. If there IS a work around, that's fine with me. i'll post here if i find a cure, and i'm hoping others will as well.
We can beat this!

I can confirm this is unfortunately not the update you are looking for. I've just done a test using only Apple's own sample fxplug code and built in effects in a motion template and I can produce frequent render glitches with FCP X 10.0.7

My personal advice is to stay on 10.0.5 if you have third party plugins that are an essential part of your workflow.