[Ben Balser]

Not sure what you mean by “open” them. You don’t open them, you apply them to the Timeline, then use the Inspector to make adjustments. No, FCPX can not “open” a Motion project file. But it can use it in the timeline. So I’m confused, no clue what you’re trying to say.

[Ben Balser]

PFS does not have a very good reputation, I’d simply stay far away from their products.

But no, you can’t lock Motion created templates, but not all templates are created in Motion.

Some Templates are made in Motion, and you can modify them.

And some templates are coded with FxPlug and Xcode, and you won’t see them in the Motion Templates folder, you can’t open them in Motion, you cannot alter them. Unless you’re an experienced programmer and know how to recode them.

Simple as that. They may be coded thus you can’t alter them in Motion. This is true for any developer.

Again, I’d not trust PFS products at all.

[Ben Balser]

What do you mean they won’t open? Can you apply them to a Project timeline?

As for the templates themselves, in the Motion Templates folder, they don’t open into FCPX, they only open into Motion.

Can you give us specific templates, and exactly what is happening, step by step?

[Ben Balser]

1st, there is no built-in way to replace your own proxies with your own originals. FCPX demands it handle everything. 2nd, it’s actually rare you need to use proxies in the first place.

But now that you have used low res images, you’ll have to import the full res versions and manually match them up. There’s no automatic way to do that in FCPX.

[Ben Balser]

First, yes, that can happen. Happens to me on occasion. Usually when you’re slowing a clip down by a small percentage. Most of the time being sure you have “Preserve Pitch” checked in the Retiming Menu. That should handle it.

[Ben Balser]

Corrupted media is rarely the cause for this erroneous error. Trash pref files (hold opt+cmd while launching) and render files (select the Library in the Browser, File > Delete All Generated…, select all render files). Those are the most common causes of it. FCP since v.1 has been notorious for render files corrupting and causing a lot of issues. And as mentioned, a full system drive can cause this. A system drive is full when less than about 15% of its total capacity is left as free space. The OS (UNIX or Windows) needs that space to write temporary working files that are totally hidden from us end users. If there’s not enough space to do so, it can create very odd issues. Many folks carry this over to secondary drives, though technically they don’t really matter as much, as they’re not used for this function.

When it actually is corrupted media, the frame number should be consistent, not random.

[Ben Balser]

Don’t knock AE, it is vital to higher end effects work. Most people I know who do that high end stuff whiz through AE fast. Both apps have their place. You can use one, and not bash the other.

[Ben Balser]

User manual is faster, easier, and more accurate.

https://support.apple.com/guide/final-cut-pro/welcome/mac

[Ben Balser]

https://www.cgdirector.com/premultiplied-alpha-vs-straight-alpha/

[Ben Balser]

“No it imports the files to the library but once I eject the card it gives me a red screen.”

You’re not waiting long enough for the files to import completely. Open the Background Task window when importing to verify the import is complete before ejecting a card. It takes quite some time for video files to import from cards, and is NEVER an instantaneous process.

Give a screen shot of these clips in the FCPX Browser, with the card inserted, I bet it shows they’re not completely imported. I’ve seen this happen quite a bit.

Also, check your FCPX Settings > Import, be sure that shows files to be copied into the Library, not left in place. This affects imports when you do drag-and-drop. But even if you don’t drag-and-drop, it’s a good idea to have it set up properly for your needs, anyway.