[Andreas Kiel]

You also may just download the manual of MTT.
MTT manual

It explains (hopefully) quite well how templates are working with FCPX.

-Andreas

Spherico
https://www.spherico.com/filmtools

[Andreas Kiel]

Unfortunately it’s the way it works with FCPX.

You can write an AppleScript to find markers in the XML and convert the times to TC.

-Andreas

Spherico
https://www.spherico.com/filmtools

[Andreas Kiel]

Angela,

What version of FCP are you using?

You can also send me an email with your phone number and we can solve that for sure within a few minutes. I’m in Germany as well.

-Andreas

Spherico
https://www.spherico.com/filmtools

[Andreas Kiel]

Angela,

There are two options.

First one:
Use TitleExchange Pro and do an FCP XML to FCP XML conversion.
With the free version it is limited to 50 titles. And even though TEP is a quite mighty app you may lose some of your special setting if subtitles do differ in color.

Next one:
Use a text editor(TextWrangler).It’s quite simple.
Export XML.
Open the XML in the text editor.
Search for Step thru the found items and replace the "value".

Import the resulting XML into FCP. This sounds like a tedious work but it's much faster compared to FCP.

If your subs do have all the same vertical offset it's kind a snip of the fingers.
Within the text editor copy the whole "block" and use the "Find & Replace". In the "Replace" entry change the value as described above. Then press "Replace all".

-Andreas

Spherico
https://www.spherico.com/filmtools

[Andreas Kiel]

You got good luck, as I just checked my mail.

Copy one modified generator, then select all the others and then “paste attributes – motion”.

-Andreas

Spherico
https://www.spherico.com/filmtools

[Andreas Kiel]

Will,

Obviously I don’t really understand what you want to do.

Some examples below (and as 3D is now fancy, look at them with red/cyan glasses cause it’s even more obvious)

You can add an image file to a clip of the primary storyline and apply an effect (Prism). This affects only the image as you see below.

Now take the “Lens Flare” which shows the “landscape” in the preview. Apply the “Prism” as well to this text. As you see in the screenshot the title is above the PNG. The title and it’s effect affects all underlying video. The PNG effect is doubled, while the primary is only affected by the title effect.

Move the title to a lower track in this trackless timeline. Now the PNG is not affacted — only the primary track.

Hope it makes it a bit clearer for you.
Some Titles/Templates behave like adjustment layers. Others do not.
And trackless doesn’t mean that there are no tracks — obviously.

You also can work with compound clip.

-Andreas

Spherico
https://www.spherico.com/filmtools

[Andreas Kiel]

No offense, you haven’t understood how the different titles work within FCPX.

All those who got a drop option for video will take the connected video automatically as source and therefore they will behave like an adjustment layer.
Those ones which don’t have a drop option won’t change the underlying video.

In most cases you can see it in the preview — if there is a kind of “landscape” visible they will change the connected video.
You can still change the title in Motion and remove the drop zone. But be careful, cause if you change it and just save it (if it’s not an internal one) all projects with this title in use will change as well – even though it’s not visible initially.
Modifying an internal template always creates a modified copy and you have to replace the old “bad” ones.

-Andreas

Spherico
https://www.spherico.com/filmtools

[Andreas Kiel]

Angela,

Saw your post by chance.
I tried it with a 1080×1920 project. And you’re right the titles move vertically. The crazy thing is that while rendering FCP resets the values of vertical position values randomly.
A workaround is not to use the generators vertical offset values but the motion offsets. This will keep them in place.

Andreas

Spherico
https://www.spherico.com/filmtools

[Andreas Kiel]

I belong to this group of people (as posted above) who read a lot, type in a reply and don’t post it.
I don’t belong to any of the groups of people which are FCPX Lovers or FCPX Haters.
I belong to the group of people which says we have to make it work.
I belong to the group of people which says we have to make it look fantastic, appealing and produce a (finacially) successful movie.
I belong to the group of people which says we have to keep the deadline.

Some of this, maybe all, can be achieved with FCPX in a specific environment or with a specific job. Other things can’t be achieved in another environment/job.

In Germany there is kind of saying “Don’t keep the ashes, but keep the fire”. With FCPX Apple went a new way and forgot some of the “fire”.

So people who say “it’s not that cuddly” are right, those who say “it’s cold or icy” and those who say “take an additional jacket” are right as well, also those who say “it’s cuddly – where is your problem” are right.
It’s all about what you want to do and how you want to do it. Again, that doesn’t mean that any of these kind of editors does anything wrong and should be hated or loved

An example in the original (old) blog had been multi-camera set up and handling. This example shows that there is no real need for Mike Fernanandes for this feature. Others do need it, for example me (or better those people who are involved in the production). The example given from Herb is one of the best for “keeping the fire” for the future. The old fashioned split screen can be a real good method (I did that for years even before FCP was released). And it is meanwhile integrated into FCPX.
yYears ago we tried to set up an efficient workflow for a lot of (world wide) daily soaps which uses only 2 cams for a 45 min show and external audio – at the end we decided to use FCP. We succeeded.
Earlier this year several people of the AAA teams flew over the ocean to watch this workflow. Everybody said “Whow” nobody said “We can make this work with our current (upcoming) version”.
These people (my customers) won’t publish anything in any forum or blog – that was already mentioned above.

My personal things…

… one is that with FCPX I lost more or less all control about metadata.
That doesn’t make FCPX a bad app – most people don’t need it. Maybe I’m just a one in a million.
And you can have two points of view with metadata. One is to keep and edit all of them in an event or project, the other is to keep them outside or better inside a file. Most of the people don’t care about what is kept in a file and just are happy to have have a smart NLE using FCPX.

The other thing most people don’t use is subtitling. Both FCP and Avid offer some hooks to create a collaborative workflow. With FCPX meanwhile a little weak hook is there. FCP had been the most open system and that’s why I mentioned the “keep the fire”.
Once upon a time Shane Ross send me an email about “how can my subtitles be spell checked and grammar checked by somebody else than me for a show”. FCP allowed to do that – FCPX allows that only somehow (meanwhile). There are ten thousands of users who just use an app of mine to juggle those subtitles forth and back. With FCPX a lot of options vanished. And there are many “FCPX Lovers” which finally said “It’s impossible” even though I tried to give them help to manage the job.

There are more examples about what works or doesn’t work. Even for the approach how to edit there are a lot – but that’s the same for all other NLEs.

Finally the title of the topic was wrong:
“Emmy award winning editor at NBC blogs about FCPX “
It’s emotional and divides people into emotional groups. But who cares?
I got several awards as well in a world which most of you don’t know.
So what would happen (if I’m not under NDA) if I post something like: “World wide known company XXX says that after a year of testing FCPX does not match their needs”
Probably nothing would happen rather than people would spend some of their valuable free time to start a discussion.

Just my 2 cents

-Andreas

Spherico
https://www.spherico.com/filmtools

[Andreas Kiel]

As said above, the TCR died with 10.0.4
I think quite a lot of people have filed that as a bug, so there is some hope it will be fixed.

Only chance is to make a copy of each of the files with burned in TC using Compressor or to use FCP.

-Andreas

Spherico
https://www.spherico.com/filmtools