[David Bogie]

[jameyS] “FCP offers the ability to ease in / out on a motion path, but not for simple motion like panning and zooming.
Is there a way to manually control velocity in FCP that anyone knows of, or any workaround inside FCP ?”

That’s it, there’s only the one way and apparently you’ve already found it.

FCP’s motion editor is NOT After Effects. It’s not simple and it’s not direct and it doesn’t offer you any of the control or creative flexibility of AE. If you render out of AE using your native codec, there is no render hit when you come back to FCP so the time involved is a wash.
FCP’s motion editor totally blows, forget it for stuff you already know how to do well in AE .

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

>t’s basically impossible to keep track of it all unless this marker/text overlay/paper log is done. I can’t think of another way to do it.< Simply not true. Paper, pencil, stickies, still photos, voice/over calls on the takes, heads and tails slates

[David Bogie]

Todd’s probably correct, easy to check. Sequence markers appear in the timeline, toward the top of the display. Clip markers appear in the clip itself and you can see them in the Viewer and in the copy of the clip that is in the timeline.

You are probably in for many frustrating hours of more copying and pasting. That’s how I learned about markers, too.

I will suggest, however, that depending upon markers to hold notes or production hints is not a good idea. Use them for chapters and sync hits. JMHO

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

There really isn’t any point in posting the same question to all of the FCP forums at the same time unless you’ve got a real emergency. You’re going to be addressing from the same people or you’re going to get similar responses. Why not post at one place, wait a few days, synopsize what you found out, post here and ask for more or conflicting opinions?

You’re wasting my time. No, that’s not true, I’m wasting my own time, not your fault. I made the deliberate decision to open your post even though I have read it and responded to it elsewhere, and now, here I am, taking time to create a useless post that is, honestly, a far larger waste of resources than either of your originals. But it’s satisfying.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

> If I drop any of the first three onto a cut, FCP just shows me black – even if I render.< Most transitions will only work between adjacent clips. If you apply them to only one clip, like a filter, no, they won't give you results that you expect. bogiesan This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

Most people who post here asking about RAID do not really know what they want or if they need a RAID system. It just sounds cool.

You need RAID in FCP only for two reasons:
1. Backup data security (subset hot swappable array towers)
2. IMproved throughput for high bandwidth media

If you your need is #2, you should be consulting with whoever makes your proprietary card or input system.
If you need data security, talk to some data security people. If you need hot swappable arrays so you can move projects form one suite to another, you need to spend a few hours googling the topic.

start here:
https://www.staff.uni-mainz.de/neuffer/scsi/what_is_raid.html

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

I’ve see this, too.
Did you get the warning that the project will update and to save into the new format?
I think you must do this in order to render to the new engine. You should get a box that says you have three choices for the render quality when you update the media files.

I’d make a copy of your 4.5 project files at the Finder level before updating them.

Hope you get it fixed, Chris, stuff like this usually doesn’t stop you.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

(short rant, do not read if you want to defend FCP.)
I’ll never look back at terminating our expensive relationship with those rat bastards at Media 100 company but there is a long list of stuff I wish FCP did half as elegantly as Media 100.
Here’s one: Take a look at the Viewer. The set i/o buttons and go-to buttons are at opposite sides of the window, as far apart as possible. That’s stupid.
Here’s another: Look at all four of the time readouts in the Viewer. They are in the four corners, as far apart as possible, and they’re little itty bitty numbers with meaningless clock icons. Bad design.
Wait, I’m on a roll: Media 100 was smart enough to know when you were using the number keypad that you were controlling the deck or clip playback. FCP thinks you’re entering text unless you specifically click into the the movie. Lame.
How about the list of feedback M100 gives you when capturing?
Last one: In m100, when a partial clip was created from a longer clip and you opened the partial clip, the timeline in the viewing window scaled to the length of the clip. Say you have a 10 minute clip and you pull ten seconds from it. In m100, you’d see the ten second portion which meant you could actually edit in the viewing window. In FCP, you see the entire clip’s boundaries making it impossible to fine tune within only the ten seconds you’ve selected. (I assume I still haven’t figured out subclips in FCP.)

AutoSelect, destination patch, scrolling timeline … long freakin’ list of sour grapes.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

You can search for the term here, ’twill find nought but ill.

Apple clearly states no processor upgrades are supported and the experience seem sto indicate presence of CPU cards or replacements can prevent installation of many Apple products.

You’re on your own. If you go this route, please contribute to the story line by posting your results.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

These are render files and there has been a long-standing problem with FCP’s render manager knowing what to throw away and when.
You’ve probably got these files as parts of nests or reference movies. FCP thinks they’re no longer needed since it ha sno knowledge of any reference movies you may have exported. Nor can it see upstream to some nests.
Only cure is to export your nests and precomps as self-contained movies.

If you’re not looking at parts of nests or references, you’re seeing parts of sequences you may have deleted or no longer need. Maybe drafts or rough cuts. Delete the sequences if you don’t need them any longer.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”