FX Factory says problem with Tansitions is Apple's Problem

Here is a reply I received after I told them that their update didn't fix problem with Patterns. Of the ones I have checked, all you get is a flash of color:

Final Cut Pro 10.2 shipped with a problem whereby many effects and transitions do not animate correctly when used on secondary storylines.

Apple has been notified of this issue within hours of the release of Final Cut Pro 10.2. We hope it will be fixed soon, in the first free update to Final Cut Pro 10.2. Unfortunately Apple does not discuss their release plans publicly, so we do not know when the issue will be solved in their code.

We are also looking for a solution that we can implement on our side. If we find one, we will immediately post a free update to FxFactory.

One workaround that seems to work is creating a compound clip. Please let me know if this solves your problem.

Let me know if I can be of further assistance, if indeed this was helpful, or if this raises any other questions.

Regards,

Niclas
FxFactory

Hopefully FxFactory will get this fixed.

Have a rather large collection of transitions from many vendors including some from at least one outfit that has gone out of business. So far of what I have checked this seems to be the only group that fails to function. Just disturbing that something likes this gets out which can certainly cause a lot of problems.

Sorry to hear that Tony. Which vendor went out of business?

Stockeon sent a message a few months ago that they were going out of business. Haven't heard anything more from them, but their transitions still work. I believe they were outside the US.

What FxFactory writes is wrong. The vast majority of the plugins distributed by FxFactory do work in 10.2. I know that because I have all of them. So this has nothing to do with FCP X, nor with FxFactory for that matter. It's up to the people who distribute their plugins via FxFactory to make sure that they are kept up to date with the application they need to work with.

Of course FxFactory can push the developers to keep their plugins up to date by threatening they will not distribute them anymore if they don't. But again, that's not Apple's problem.

- Ronny

Ronny,

What FxFactory is saying is correct, there is a problem with third party plugins running on a secondary storyline.

It's up to Apple to fix, so I would imagine an update soon to fix that and the AVCHD black frame problem

Peter

Ah, I did not read the "secondary storyline" part. My bad. If there is a problem with all third party plugins on a secondary storyline then I agree, this an issue Apple must fix. Thank you for correcting this.

- Ronny

You know there were changes to the FCP API in 10.2?

Yes the FxPlug SDK has been updated to 3.1. It really surprises me that the bigger FxPlug plugin developers have had no access to the update prior to release so they could test if their plugins still would work.

- Ronny

I'm not sure what problem FxFactory is seeing. I have just tested animations and transitions on secondary story lines in FCP X 10.2 using CoreMelt V2 transitions and I don't see any problem. (Our plugins do not use FxFactory).

Apple's built in transitions and effects also seem to work fine and animate correctly on secondary story lines.

I would be keen to hear more details of the exact problem people are seeing so we check this on our products.

i know Neat isn't a transition, but their problem seems to be with projects that use media that doesn't match the project frame rate, 50p media in a 25p project. Maybe that's effecting sine transitions as well?

I've just tested this as well. 29.97 and 50p clips on a secondary storyline in a 25p project. Transitions work fine using our V2 Plugins.

Terrific. Thanks Roger for checking.