Forum Replies Created

Page 81 of 195
  • Robin S. kurz

    February 13, 2016 at 1:11 pm in reply to: 10.2.3 Update is here

    [Tony West] “I should be in the other forum with this, but how do I step through the different fabrics once I have it in Motion. Can you do that?”

    Erm… simply delete the ones you don’t want? They’re just regular, everyday image layers.

    – RK

    ____________________________________________________
    Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

  • Robin S. kurz

    February 13, 2016 at 12:50 pm in reply to: 10.2.3 Update is here

    [Walter Soyka] “your “aside” means that there is no compositing-oriented workflow between FCPX and Motion?”

    Quite the loaded question. But sure there is. Use it all the time. Aside from some of the most features and functionality that I’d go to Motion for (e.g. b-spline masking) are now directly available inside of FCP. On the other hand that’s also assuming that that’s even what everyone with the FCP/Motion workflow even need or want to do or it is even intended to cater to, which I personally think is obviously not the case. Could that aspect be more convenient? Yeah. Will the addition of some sort of “Send to” be happily accepted? Sure! Is it somehow the all governing, make-or-break feature it’s being made out to be? Nope.

    [Walter Soyka] “but there’s more there than meets the eye [link].)”

    Wow. Now that’s what I call intuitive and user-friendly. How could I think something (normally simple) like that is far better implemented with X/Motion. ;-D

    – RK

    ____________________________________________________
    Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

  • Robin S. kurz

    February 13, 2016 at 12:48 pm in reply to: 10.2.3 Update is here

    [Herb Sevush] “Since I had already defined “send to motion” as a two-way, or bi-directional process, this implied that there is an equivalent to a “send feature.””

    That’s what you get when you bring a knife (+misconception, lack of expertise etc.) to an FCP discussion.

    It helps to understand what it is your “dueling” over before you enter into it, to avoid strawmen, the usual loaded questions, false causes, a slew of other logical fallacies and hearing what you want to hear as opposed to what is being argued. Because with my previous explanations I was refuting the claim that somehow the process isn’t “two-way, or bi-directional”, where—as everyone actually using X knows—it very much is. Nothing else.

    Whereby my actual use keeps me from trying to sell anyone on the notion that “two-way” as a whole somehow hinges exclusively on the existence of a “Send to” command as opposed to being one of many possibilities for exchange.

    I wasn’t offering up any appeasement alternatives to “Send to”, but rather pointing to why its absence isn’t even close to as dramatic as you would seemingly love to make it out to be. It’s called “arguing from personal incredulity”. Made obvious by apparently assuming that said feature holds the exact same level of necessity that it did in legacy, which, again, it does not.

    But then you have your “two-way” and “Live-Link” etc., so all’s good! No idea what there is for you to be upset about.

    – RK

    ____________________________________________________
    Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

  • Robin S. kurz

    February 13, 2016 at 12:16 pm in reply to: Title Template Causing Frame Blending in FCP

    Any chance you could post the file so one could have a look? Otherwise one can only guess. But it’s certainly nothing I’ve seen happen before.

    – RK

    ____________________________________________________
    Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

  • Robin S. kurz

    February 10, 2016 at 8:38 pm in reply to: Send to Motion….. Could Automatic Duck tackle this?

    [Bret Williams] “I don’t want a new slot. I want my motion project stored along side my PSD files…”

    With “slot”, for lack of a better word, I meant direct support of vanilla Motion projects (no “publishing” etc. of any kind), which in turn would obviously and automatically bring exactly what you describe, yes. That was my whole point.

    [Bret Williams] “every single transition, generator, title, and effect that doesn’t come stock with FCP X “

    That on the other hand is a whole other ball-o-wax, since you’re dealing with potential 3rd party copyright and/or licensing issues. Don’t see how they might solve that without leaving that potential crime up to you to commit and not essentially “aid and abide” in the end. The crux of the chosen system. For default material you clearly don’t need them saved extra, everything else is still up to you. So I’d say that part stays the way it is or the whole system changes on various levels to accommodate. I wouldn’t hold my breath for the latter. We’ll see.

    – RK

    ____________________________________________________
    Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

  • Robin S. kurz

    February 10, 2016 at 7:48 pm in reply to: Send to Motion….. Could Automatic Duck tackle this?

    [Bret Williams] “Oh how I hope you just broke your NDA.”

    LOL… I should be so stupid. 😉

    I’m thinking there just has to be a new “slot” if you will for just plain, regular Motion projects, which currently are, rather ironically, not useable AT ALL for FCP without turning them into a generator. Kinda tells you something I say. Once you allow for their direct support, I’m guessing the rest is a given, since they wouldn’t be relegated to any “media browser” cage as everything else is. So how else are you going to organize them if not exactly as you do everything else i.e. in the Finder/Event/Library, amirite? 😉

    But something tells me they’re going to conjure up something even far more clever than just that. 😛

    History points to the next update being another big(ger) one, so… who knows.

    – RK

    ____________________________________________________
    Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

  • Robin S. kurz

    February 10, 2016 at 7:32 pm in reply to: Send to Motion….. Could Automatic Duck tackle this?

    [Bret Williams] “So they need to fix two things, let the motion projects reside anywhere I want and show up in the EVENT, and either allow me to “open in motion” right from the event or from the timeline or at least dynamically update if I update them in motion.”

    I’m pretty sure that describes a good part of what’s coming. 😉

    – RK

    ____________________________________________________
    Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

  • Robin S. kurz

    February 10, 2016 at 7:29 pm in reply to: 10.2.3 Update is here

    Again, I don’t recall ever saying that a sending option was somehow a bad idea or that I’d somehow be disappointed if it ever shows up, which I’m sure it will. Nor am I exactly sure how you managed to extrapolate anything along those lines out of the above.

    – RK

    ____________________________________________________
    Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

  • Robin S. kurz

    February 10, 2016 at 7:20 pm in reply to: Send to Motion….. Could Automatic Duck tackle this?

    [Bret Williams] “Some would. I just don’t come across the need that often.”

    Me neither. Given the exponentially improved integration with X compared to 7, both in terms of functionality and most of all speed. Due to the fact that the most relevant tools and features for which I even ever needed Motion are now inside FCP, it’s lost a huge amount of importance for me. Everything else I do with Motion, which is a lot, is completely independent of any “sending”, since it starts in Motion anyway. In which case the exchange is there as needed. I really only wish that it wasn’t necessary to replace “old” instances in a timeline after editing to refresh. That’s lame.

    I certainly won’t be disappointed once it shows up, but I already know that it won’t have anywhere near the same relevance to me as it did with 7 and below.

    – RK

    ____________________________________________________
    Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

  • Robin S. kurz

    February 10, 2016 at 6:58 pm in reply to: 10.2.3 Update is here

    [Walter Soyka] “you were actually agreeing that there is no effective workaround for the lack of “Send to Motion” in a compositing context?”

    Erm… where exactly did I do either i.e. do more than acknowledge the fact?

    [Robin S. Kurz] “Aside from not being able to send a clip directly from the FCP timeline…”

    Whether the various options described are “effective” for others is not actually for me to decide. But apparently it’s not a huge issue with actual users from what I’m reading, no. Go figger. 🙂

    As much as I will welcome a sending option as much as anyone once it comes, it is far from the ultimate defining aspect of Motion’s current integration with X. Assuming one is even familiar with it and doesn’t just want it to be for the mere sake of argument. Again: it is exponentially tighter and more powerfully integrated with X than it ever was with 7. With or without send. But if SEND is all that matters to you, ah well… there are options. One of them being the app “SendtoMotion” by the way, if that should strike you as more “effective”.

    – RK

    ____________________________________________________
    Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

Page 81 of 195

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy