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

Have you contacted BlackMagic tech support?

Yes I did and they advised to go to a previous driver version which doesn't work either.

OUCH!

I'm using 10.0.6 under ML 10.8.2.

My Blackmagic Intensity Pro can only monitor audio from FCPX when it is routed via the system output.

In other words the system audio output (used when watching YouTube or iTunes, previewing Quicktime etc etc.) has to be routed to the BlackMagic. With AV output selected in FCPX the audio from FCPX appears at the system output instead of going directly to the Intensity.

Odd.

It doesn't do this with FCP6.0.6

Not sure if this has been discussed but I’m having rendering issues with Magic Bullet Looks.
Basically when I render the effect I’m seeing green and upside down frames, all kinds of craziness going on.

Sometimes I can slightly tweak a parameter to force another render and then it will render just fine but most times it will render with the same issues. Note the glitches in the render are completely random and are not always on the same frame.

MBL worked flawlessly under 10.0.5 (other then disappearing on-screen controls) but 10.0.6 seemed to have wreaked havoc on the way MBL renders/process frames.

Im on the latest version of Mountain Lion and MBL. I noticed this issue when I upgraded to Mountain Lion from Snow Leopard and upgraded to 10.0.6 so I’m not sure which upgrade may be the culprit.

Anyone else having issues with MBL? I don’t see any fix from Red Giant

Still no update yet from Red Giant for MB Looks:

"As we posted earlier, we are aware of the issues with both Magic Bullet Looks 2.0 and Magic Bullet Mojo and the FCPX 10.0.6 update. We are working with Apple to determine the root cause and will provide you with a fix as soon as we have it! Some bugs are obvious and easy, and some require a bit more investigation – we’re doing what we can to get this one resolved!"

www.redgiantsoftware.com/blog/2012/10/30...tes-for-fcpx-10-0-6/


I'm afraid to use it until they post a fix.

Yep, it's a known issue and Red Giant seem to be dragging their giant feet on the matter. They are well aware of the issue, but evidently feel other software with bugs are more important. They discuss the known issue slightly on their blog. It's been 4 weeks now since the release of 10.0.6. I purchased looks just 3 days after the update as I had been test driving it for 2 weeks before the upgrade trying to decide if I wanted to bit the bullet (no pun intended) then they ended up having issues. It's quite frustrating to say the least, but I've still got my fingers crossed that they will have a fix any day now.

Red Giant isn't the only one having problems with this last FCPX update, there are several 3rd party plugins that are broke. To be honest, I'm not sure if it's the 3rd party suppliers, or Apple that has messed things up. I sure wish someone could shed some light on the issue.

OH, btw, I haven't been able to duplicate the Magic Bullet Looks problem on my 2011 Macbook, just my 2011 iMac, so my guess is, that's it's got something to do with the graphics card. I have the AMD Radeon HD 6970M 2048 MB card in my iMac and the AMD Radeon HD 6750M 1024 in my MBP.

You can always buy a Mac Pro. MBL2 works fine with that and ML. Ughhh...sorry :ohmy:

Problems solved.
FCPX 10.0.6 works with Blacmagic Ultrastudio 3D and with Matrox MXO2 Max.
After updating to last drivers problem is solved.
On Matrox the playback has delays but I can see the output on the sdi monitor.
Please be advised that is not enough to set up the output to your matrox/blackmagic card in fcpx preferences. You also have to highlight av out on the windows tab.
Good luck everyone!

Just wrote to magic bullet re: Looks. Twice now on one project, but in different clips, where I have made adjustments using Looks, I get a spurious, single frame which is unrendered with the look and is also upside down! For your enjoyment, I attach a sample.

mjscox wrote: Just wrote to magic bullet re: Looks. Twice now on one project, but in different clips, where I have made adjustments using Looks, I get a spurious, single frame which is unrendered with the look and is also upside down! For your enjoyment, I attach a sample.

I consistently get the same issue. Anxiously awaiting a fix from Red Giant and/or Apple.
In the meantime you can try and force a re-render by deleting render files or tweaking a parameter of the clip. Sometimes it will render fine with a 2nd or 3rd pass.

You can write NeatVideo and see what they say, but also, and don't get me wrong here, I'm no purist, but for the price, purchase FCPX instead of relying on the trial version. I'm not even saying I prefer FCPX over Premiere, because quite frankly I find myself torn between the advantages each offers. However, you're unlikely to find Premiere at the low price of FCPX--unless you can qualify for an academic discount.

By the way I tried to upload a sample video and it didn't upload; you know what I mean, anyway. I keep forgetting this is a U.S. holiday so Red Giant, etc., aren't responding as quickly as they do on a regular weekday. As for Apple responding: Hah! You have better luck with Santa Claus.

My generators that use the Scrub effect or behaviour on drop zone clips no longer work in 10.0.6.

That means my Alex4D Retime graph generators don't work in 10.0.6. They provided Final Cut Pro 7-style retime graphs in X.

Don't know if this is a side effect of the way 10.0.6 implements the new drop zone time offset control (when choosing the drop zone clip, you are also choosing the first frame of the source clip to be sent to the generator).


Also my Magic Lantern HDR plugins no longer work for similar reasons.


Sorry its taken so long to report these problems.


@alex4d

Red Giant is claiming that the rendering problems associated with Magic Bullet Looks is all Apples fault and will not be fixed until Apple issues an update. This really sucks Apple, please fix this right away!

Here is a copy of the email I received from Red Giant today on the matter:

Hello Ron,

Unfortunately, we do not have a timeframe of when the render issue in Magic Bullet Looks will be corrected, we are also very patiently awaiting an update from Apple on this issue. Our engineers have looked in to any possible scenario to implementing a fix on our end, however unfortunately, this issue is not coming from Magic Bullet Looks as what was previously presumed, it's actually a post-render issue and it will require an update from Apple. We've also found that many other 3rd party plug-ins are running in to this same problem. As we learn more, we will continue to post new information on our blog or on our Twitter and Facebook. I'm sorry for this inconvenience.

My apologies for not being able to do more for you on this issue.

Thank you,

Jeremy H
Support Manager

Sheesh! Glad I did not update to 10.0.6 yet.

What is it, I wonder, about FCPX that seems to be causing so many problems with 3rd Party plug ins and the updates? This has never been the case with other software and plug ins, to my knowledge (or at least not as regularly as it seems to be happening here).

Is this the shape of things to come forever with FCP? If so that will be a real drag.

Is there some email address we can bombard at Apple support to address the issue of 3rd party plug in issues? I mean for me Neat Video & MBL fill vital gaps in the core software, and there are a great number of other small plug ins that really round off the editing experience. I wish Apple would address this, or let us know that they are aware of the situation, and are addressing it.

Not knowing whats happening is the most annoying thing.

Apple doesn't say anything to anyone until a product is actually launched. Get used to it. But why would anyone think Apple is not aware of bugs and is not working on them? They always have so far, what evidence is there anything is different now?

To Apple's credit, this was the biggest, most major update of FCP X so far, so the bugs are going to be there. That is simply how software works. The larger the update, the larger the possible bugs. We will most probably see a 10.0.7 bug fix update some time soon.

As for contacting Apple, they do read, catalog and track what you send in via the Feedback page. That's where you give them your personal feedback. Fill it out, often.

FYI, the updated AJA universal controller (driver) version 10.4.1 works just fine. No more desktop support for the Mac, though. But they were having problems with that all along writing drivers for FCP X. So that's an Apple issue I guess. But AJA products work just fine!

If everyone having problems with FCP X used the feedback page you would see results. I have been contacted by Apple regarding several issues that I (and I am sure others) reported via the feedback page. Most of them have been corrected.

As BenB says, "Fill it out, often".

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.

To be honest, I really hadn't started using any 3rd party effects and plugins in X until after the release of 10.0.6 and I can get by a while longer without them (although I've already invested heavily in them), I just don't like it when software companies aren't upfront with known issues, it reminds me of the deceitfulness associated with Adobe, and no company deserves to be compared to Adobe.

Red Giant continues to depict MBL as being compatible with FCP X right on their overview page of the product. That's wrong. They know of the issues, whether they're Apples fault or not, they need to be upfront about the associated problems, not hide their comments somewhere in their blog 5 weeks deep (and counting) where no one is going to see it until after they purchase the software and bang their head against the wall for a month troubleshooting it, then wondering why they've become unpaid beta testers once they find out the "rest of the story".

Apple also needs to step up to the plate, learn from their mistakes, and communicate more effectively with their customers if they want to win back the hearts of those that have left FCP after the initial release of X. Timothy D. Cook appears to be more forthcoming then Steven P. Jobs ever was, let's hope it wears off with the rest of the kingsmen (or Knights) at Apple!