Feather edges

Try this:

https://fcpxtemplates.com/product/feather-edge/

[I'm trying out a new delivery system...]

It is currently free. If you need it for an older version of FCPX, follow the instructions for backdating (I believe this could be backdated all the way back to FCPX 10.0.0) — it's easy to do and just a couple of easy to follow edits. (I really can't do it myself because I have no way of testing backdated projects—but appreciate feedback to let me know which version backdates are successful.)

Okay— hmmm — thanks for getting back to me on that. This is a new development and could be part of Apple's move to all-64 bit in the near future (which will also mean some fundamental changes in backward support for templates in general in FCPX.)

How far back did you backdate the original? [also the OZML/DisplayVersion data must match each other according to that list which I had to create from templates I created within the versioning times for FCPX... (maybe there's an error?)]

I backdated *this* version back to 10.0 (theoretical):

http://fcpxtemplates.com/share/sc_featherEdge-10-0.zip

Will this one work in Sierra?

Interesting. In the previous build, the effect would appear in the Movies folder with a generic document icon. This version appears with a legacy FCP style icon. FCP 7.0.3 is at the top level of Applications.

If I open it on TextEdit it seems to be missing the displayversion line. Looks like this

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE ozxmlscene>

<ozml version="5.0">

<factory id="1" uuid="0e8d443513b611d89395000a95af9f7e">

<description>Channel</description>

<manufacturer>Apple</manufacturer>

<version>1</version>

Should I just add in the displayversion line with line breaks before and after?

No - there is no displayversion used in the first four subversions of FCPX 10.0 to 10.0.3. You can't mix and match OZML versions and displayversions. FCPX does some kind of strict format checking on the file. TextEdit is not my first choice for editing these kinds of files, although, technically, there is no reason that TextEdit should be problematic (other than a few formatting preference options that might interfere). I tend to use TextWrangler (still, even though it is no longer being updated) which protects the "original integrity" of documents.

Try right clicking on the .moef file and Get Info. Set the Open With to Motion. Make sure the Name & Extension shows the appropriate file type ending (.moef).

The file type is the correct .moef in Get Info. I can't set Open with Motion as I don't have a version installed in Sierra. I can't assign an application in the other partitions or drives as they're APFS and not seen in Sierra.

This is an interesting wrinkle. Up til now, all of the backdating attempts I have been aware of have worked (except where FCPX was too old to support newer features of Motion). What happens if you set the Open With application as Final Cut Pro?

Sorry about the delay to get back to Sierra. I tried setting Open with to FCP10.1.4. Didn't change the behavior. I loaded Motion 5.1.2, the oldest version I have, the version corresponding to FCP 10.1.4. I set the effect in TextEdit to 5.6 and 5.1.2. I tried opening the effect in Motion but got an error that the document could not be opened. Still doesn't work in FCP 10.1.4.

Thanks for your help!

Somewhere in the FCPX 10.1 time period is when a lot of changes were being made. I'm trying to narrow down the "break point".

I have templates I did back in 2011 for 10.0.0 that have worked and still work in all versions of FCPX. I backdated Feather Edge to 10.0.0 and theoretically, it shouldn't need any further modification for any version of FCPX (it is working just fine in 10.4.4 on my system [High Sierra]). If you could replace the version you've been working with, with this one:

http://fcpxtemplates.com/share/sc_featherEdge-10-0.zip

and try it out an any version of FCPX, I'd be interested to know which versions is actually does work in. I do suspect there is a cutoff point for how far backwardly compatible templates can be made simply because I have found tags in the older templates that do not exist in the newer templates and there are <version> tags for one or two other sections. I've been trying to narrow down the "break point", if you will. I haven't been able to pin down when these tags "changed" but suspect these are the test points when the documents are "scanned" for compatibility.

I'm not as concerned about actually being able to have newly made templates in Motion 5.4.x being made compatible all the way back to fcpx 10.0, that's a diminishing field. However, having an approximation for which earliest version of FCPX new templates can be made to run in is quite useful. There are still a lot of people using pre-10.2 (advent of 3D Text) versions who would like to have access to newer templates, if possible. Most of the people I've worked with backdating haven't gone back nearly so far. Usually the 10.3+ range. There may have been a couple going back to 10.2, and so far, this is as far back as I *know* can handle this backdating cheat. [It would be really nice if there were a Save option for a target version — I'm sure a lot of template makers would appreciate it.] On the other side of that is how many times I've been working with people on these forums — if I "whip up" an example in Motion 5.4.2, and they're running less than FCPX 10.4.3, they won't even be able to open it.

If you've "had enough" of this topic: that's okay, I understand. The information on my compatibility page is still valid, I'll just have to emphasize more clearly that there may be a failure point before some version before 10.2, no matter what. That's still being able to turn back the clock nearly four years!

I went down to 10.2 in Sierra successful. After that I hit a problem. 10.1.4 or older all crash as soon as I apply the effect, either by dragging it or with double-click. Even skimming the effect in the browser crashed 10.1.4.

Thank you very much! That is very helpful. Closer inspection of some of

my files show that there are tags that are missing in newer templates

which must have once been important. There was a substantial change when

Metal was introduced (circa FCPX 10.1.2 - June 2014). I'll have to do

more research. [I'm not sure how much value there is in going back that

far. I'd need to get some more feedback or stats on how many people are

still using pre-10.2 versions of FCPX.]

I don't know enough about these things to understand why, but I couldn't get it to work on any version in Sierra. The oldest FCP version I could run it on was 10.3.4 in High Sierra.

I am not sure I fully understand exactly what you are trying, but here is a way you can feather just the left side of an image:

1. Make sure the % on the viewer is small enough so that you can work a little outside the frame, if necessary.
2. Add a Draw Mask effect to the clip you want to feather, and draw it so as to encompass the full clip except a margin on the left
3. Adjust feather (you can type directly in the box if you need greater values than what the slide provides - see image below)