Robin S. kurz
Forum Replies Created
-
Yepp. In an “ecosystem” sense Motion is to FCP what After Effects is to Premiere… more or less. 😉 As with AE, you can use any and all independently. But in conjunction with i.e. in the context of FCP X is where Motion can/will really shine.
-
Sure Steve. 🙂
We certainly agree on one thing: Don’t like it? Don’t need it? Have something that suits you better? Well gee… don’t use it. Pretty simple. No clinging to a long list of classic logical fallacies even needed for that! 😀
You with your, as you say, newbie questions have clearly established yourself as a complete expert on all things FCP.
-
“you still do have to rewrap everything and end up with double or more the footage size worth of project file.”
How so? You have to copy the footage from the camera either way, right? Rewrapping doesn’t *convert*, transcode anything nor does it add data. You still have the original, native file, only wrapped into a QT container. If you’re getting the “”still on the camera” error, then you simply haven’t let the transfer of the files from the camera complete, during which it is rewrapped. It’s not a separate process. In that case you should have a small camera icon on the particular clip(s). Simply select and choose “Import from Camera/Archive”, let it finish and all’s good.
-
Click on a value and use the scroll function of your mouse to change the value up/down. My personal favorite.
-
Yeah, Steve. You’ve clearly got Apple aaaaaall figured out. 😀
-
Sorry, but you just merely demonstrated that you are missing even the most basic knowledge of FCP X. Every single command/shortcut you list in fact exists in X. Unfortunately that exact thing is what X has been suffering from for the last three years: completely false claims and presumptions… and people reading them and simply taking them to be true without any scrutiny whatsoever. Then they parrot those same “facts” repeatedly elsewhere. *sigh*
“I see no advantage in switching to get Libraries”
Wow.
“I’ve got zero problems with how it is.”
Clearly, you do.
And just FYI: I started in film school in the late 80’s on Steenbeck/Movieola, but never mind.
PS1: X has even up to *3* viewers, sorry, and is most definitely far more performant than Premiere by ways of the “gimmick” OpenCL 2.0 (not to mention CoreVideo etc. etc.) alone.
PS2: X has had back timed edits since day one, should you have been suggesting that it doesn’t.
And I’m also not “arguing about NLEs” nor have I. I couldn’t care less what anyone else uses or prefers. I’m merely set the record straight when I see the usual plethora of false claims that are based in nothing more than simple lack of knowledge, since 3 years of it are truly enough… even though I know it won’t change anything about some peoples’s dead set opinions in the end either way.
-
“I’m not sure I want to learn a whole new set of Apple concepts just to do what I’ve been doing almost 40 years.”
Other than some alternate nomenclature, I don’t see how “Apple’s concepts” are somehow radically different. You have bins (with a different name), ins and outs and a timeline.
“I was recently surprised to find my old copy of Premiere Pro CS6 edited 4K XAVC without any need for proxy.”
How is that not possible with FCP X? I recently even edited a 12 angle 4K multicam with 10.1 at full res (which I highly doubt, from experience, Premiere did or does) without a hitch. Obviously given the right hardware.
Either way, your best bet it 10.1.x (*only* bet actually if you need custom resolutions). You could always just install Mavericks on a separate partition.
I’m also intrigued by how amazingly long Avid needs to qualify their software every time with any and every change, even if it’s tiny, compared to any other NLE. That bullet-point alone would drive me from an MC in a day, were I still using one.
-
Simply go here and follow the recommended workflow, if it’s in fact an issue, and you’re fine:
And if you in fact haven’t updated, I’d have to ask WHY, since it’s something you most definitely want to do.
-
1. Simply click and drag the value in the inspector. Or drag the layer by its anchor point which snaps it to the guides.
2. Use the retime menu to set the clip in the timeline to “automatic speed” which will (obviously) slow it down accordingly. That’s assuming your project is set to 25fps. And if you’re not seeing custom resolutions, then you must not be using 10.1.x.
-
Too lazy to read the entire thread, so sorry for any redundancies. 😉
1. OPTION-click on the clip. It used to be the other way around. Glad it changed.
2. Simply click them off and you’ll know if you changed anything. If they were OFF by default, you’d have to remember to turn them ON first before making changes to actually have them apply. The way it is is the only logical way IMHO.
4. You should be using PASTE ATTRIBUTES instead.
5. CTRL-Z doesn’t undo *anything*, only COMMAND-Z. And there are a few exceptions to what falls into the area of an undoable action, but “critical visual changes” certainly shouldn’t be one of them and aren’t as far as I can see. Unless I don’t in fact know what you mean by that. Any and everything I do in the inspector is undoable.
P.S. Something you need to talk to the Natress people about. The fact that visuals are exported if left on is THEIR decision/programming, not FCP’s/Apple’s.