Forum Replies Created
-
[Andy Neil] “They cost me $1200.”
When did FCS ever cost $1200?? I only remember $999.
But I feel the same about my CoSA After Effects disks. A full TWO of them and a good ol’ box. ????
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Al LeVine] “Seems like Apple will stop silently supporting our old (rotting) friend in 2018.”
With the beta, at first…

… oh the irony! ????After that: crash.
But let’s be real. Anyone running 7 neither needs nor is even vaguely interested in running the latest and greatest in OS. At least I can’t think of much more of a hilarious contradiction. So I’d say it’s a non-issue. Everyone else can keep an LC III lying around. ????
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
Robin S. kurz
June 7, 2017 at 4:38 pm in reply to: Why is the Premiere Pro titling tool so horrible?[andy patterson] “or did you simply use a canned title effect that was created by someone else using Motion”
You still haven’t grasped that every single title in FCP X is a Motion project, have you? There is no such thing as a title that wasn’t created in Motion, period. Unless maybe it’s 3rd party, but even then…
????????♂️
This is such a non-discussion.
-
So the entire thing actually came down to your being set to proxies? Or had you been using the same settings as in your video the whole time? Or both? Because both (be it together or by themselves) will of course lead to your issues.
Either way, in the context of using them in FCP, you’ll want to publish your projects instead of rendering them 99% of the time, yes.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
Hey Alex! … can you be reached elsewhere? I have a proposition that may or may not be of interest to you in this context, but your site doesn’t list an email (for you) and the forum has no messaging system to speak of ????. Cheers.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Glenn Grant] “I wouldn’t switch just because a few new guys know Premier better.
As for NAS, there are some pretty solid solutions for FCPX so that shouldn’t be a problem.
Depending on what you use After Effects for, you might be better off using Motion with FCP. That would be an easier and more cost effective switch than going to Premier.”
I agree 100% on every count.
Also, the round-tripping to/from X is exponentially more solid and far lossy than to/from PPro, thanks to Resolve’s native support of FCPXML and no need for the painfully outdated and limited XMEML (v7 XML).
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
Robin S. kurz
May 29, 2017 at 8:33 am in reply to: Why is the Premiere Pro titling tool so horrible?[Brian Seegmiller] “This funny.”
Yeah, no kiddin’. ????
Never mind that that was A SIERRA BUG (or quite possibly even one of the usual shoddy drivers for BMD hardware) not an FCP one. Once FCP was updated for Sierra (I believe just a week later?) everything was of course fine.
Never mind that the only instances of the word “horrible” (4) anywhere in this context were uttered by… guess who. ????
https://bit.ly/1QjHPfs -
[Neil Goodman] “It’s about haveing a bigger canvas”
Again: then a laptop simply isn’t for you. So? That still doesn’t mean it’s not a perfectly fine solution for many many others (that don’t use their NLE as a DAW). Having three monitors when I’m stationary does not make me any more efficient or give me more options that I don’t otherwise have as well. It’s a convenience and luxury. Nothing more, nothing less. The compromises are completely negligible. At least, for me, in the context of FCP that is. It may well be far worse with others. If the situation demands it (e.g. client review) I’m one cable away from monitoring etc. etc. All without sacrificing mobility and various other advantages that a setup like that grants me.
I can most certainly “do my job” on that screen, even with 26+ tracks. It lacks no accuracy whatsoever compared to any other display options or NLE. Unless you can name something? I can turn waveforms on and off as needed (even JUST for the audio group of primary interest if I want) with a simple keystroke, making it exponentially easier to focus on the actual task at hand, thanks to massively reducing visual clutter. AND I can move whatever audio, be it dialog, music, fx, VO, whatever to the top, bottom, middle as it suits my needs and current focus with one simple swipe of the mouse. That on the other hand being something you most certainly can NOT do with any other NLE and something I don’t want to have to do without ever again either.
Oh, and btw… if I were to hide the “Audio Lanes” (only had them showing for demo purposes), as I usually do, then the amount of vertical space needed would be reduced even more (potentially down to just a few “tracks”), since we (thank god!) are not tied to the painfully inferior concept of TRACKS and everything can scoot together automatically if a space opens up. Again something that no other NLE (or even DAW) can offer… unless I missed some massive recent update of some other NLE.
Horses for courses, like I said.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
[Kay Ghey] “I’ve gone ahead and recorded and uploaded a quick screen cast to see if anyone can spot me making the mistake, located here.”
Well, for starters, in that clip you have the render set to ALPHA ONLY and not COLOR + ALPHA. With that, you are rendering only the black and white alpha channel not an RGB clip with alpha channel!
[Kay Ghey] “Alpha channel is non-functional when FCPX display settings are set to “Proxy Media” it would seem…”
THAT of course being the step that makes near every other irrelevant, yes. Proxies are rendered in 422 Proxy. Ergo: no alpha.
But either way, I don’t understand why you even insist on RENDERING the clips, when you could simply PUBLISH the project as a generator. In which case there would be zero alpha issues, not even with FCP set to proxy. Not to mention just a fraction of disk space and time required.
– RK
____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich! -
Robin S. kurz
May 28, 2017 at 9:20 pm in reply to: Why is the Premiere Pro titling tool so horrible?[andy patterson] “My video was in response to all the people claiming Premiere Pro has a horrible and outdated titling system.”
Okay, now that you’ve stated that over and over and over and over again ????… do tell: who? When? Where? Because it apparently had to have been a BUNCH of “all the people” here, since why else would you post this otherwise unrelated clip in this particular forum? Feel free to quote any and all of the oh-so-many occurrences of proclamations or horribleness. Or is it just yet another straw man after all? I for one don’t recall seeing a single such claim. How bout a pointer?
And, I dunno… maybe someone got the notion from you?
https://www.youtube.com/watch?v=XQWXq7KpxBQ
????