OT: Why a copy of 10.1.3 could be helpful

This probably only affects a very few people.

While working with XMLs a lot cause of the environment I working in I discovered an ugly bug with 10.1.4 when importing XMLs with links to fxPlug based effects.
If the XML contains modified settings for the effect the (re)import of the XML might fail and end end up with a crash of FCP X.
I got aware of this using the DH_SubtitleX generator. FCP X doesn't succeed to link the used Motion template values to the matching fxPlug.

Using 10.1.3 doesn't have this problem. Once imported you can quit this version and open the library/project in 10.1.4.
In the XML you have to change the line "<fcpxml version="1.4">" to "<fcpxml version="1.3">"

I waited some time to publish that to make sure it's not my setup which is causing this. It is confirmed to be a bug.

Similar errors can happen to other fxPlug based effects.

- Andreas

P.S.
Just for understanding: a fxpPlug based effect needs a Motion file to communicate with FCP X.

HHmmmm... very interesting, in deed. Thanks for posting this info.

Thanks for the information, Andreas. I assume you have reported this issue to Apple?

- Ronny

Not personally. But I know some vendors have and Apple is aware of it.

- Andreas