Forum Replies Created

Page 6 of 195
  • Robin S. kurz

    January 21, 2020 at 10:43 am in reply to: Page curl filter

    I take it you’re rendering using the BEST setting?

    – RK

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

  • Robin S. kurz

    January 9, 2020 at 10:49 am in reply to: Can image be changed after putting in behaviors

    Simply drag whatever image onto the existing one until you see a hooked arrow and drop. Replaced.

    – RK

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

  • Robin S. kurz

    November 22, 2019 at 4:13 pm in reply to: FCPX & Blackmagic Raw workflows?

    [Brad Hurley] “Apple has a vested interest in promoting ProRes RAW so they might not go for it”

    The meme that won’t die until it’s actually out, I guess.

    Are you suggesting that B”RAW” and ProRes RAW are competition or that somehow Apple actually thinks that it is? ????

    [Craig Seeman] “From what I’ve heard the hold up is on Blackmagic’s side, not Apple’s.”

    Of course it is. Apple’s QA is exponentially tighter than that of Adobe’s et al’s. Once BMD get a stable and (unlike the PPro plugin) bug-free version of the codec to Apple it’s sure to be included. Why shouldn’t they?

    Of course B”RAW” isn’t even RAW to begin with, but I’m guessing you’re already aware of that.

    [Jeff Kirkland] “My understanding is that Apple removed the ability for FCPX to run third party codec plugins a few versions back”

    No, it’s not an FCP specific thing, it’s an OS thing. Meant to keep any and anyone just making (and installing) plugins willy-nilly. All of which pose a potential security and stability risk if not monitored, whather we think it’s a PITA or not. It’s actually a good thing in the end.

    [Joe Marler] “Atomos makes some recorders that record/encode BRAW from a few non-BM cameras, e.g, C300 II. “

    Most certainly not.

    [Joe Marler] “I wonder if Atomos will make recorders that record ProRes RAW from a Blackmagic camera?”

    That’s not AtomOS’ decision. It’s not like they can just pop an Inferno etc. onto any given RAW output port and capture away. But either way, I’d say the answer is clearly “nope“.

    [Joe Marler] “Blackmagic gives away a free open BRAW SDK for Mac OS, Windows and Linux.”

    I’d say you’re clearly and gravely conflating PLAYBACK and RECORDING. And as much as so many like to say so, the BMD SDK is anything but OPEN in the sense that everyone seems to think.

    – RK

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

  • Robin S. kurz

    November 12, 2019 at 7:48 pm in reply to: Motion 5.4.4 Save Current Frame problem

    That btw is not even to mention that you’ve been able to assign any random shortcut to any menu item in pretty much any app for literally years now… via the Keyboard System Preferences.

    I simply mentioned the other option first, since that’s the most obvious i.e. easiest one to implement.

    And just may explain why Apple has “refused” to implement your endless request. Maybe they just trusted you’d figure it out on your own eventually. ????

    – RK

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

  • Robin S. kurz

    November 12, 2019 at 7:40 pm in reply to: Motion 5.4.4 Save Current Frame problem

    Yeah. Two clicks more. Horrible. I forgot.

    ????????‍♂️

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

  • Robin S. kurz

    November 12, 2019 at 1:14 pm in reply to: Motion 5.4.4 Save Current Frame problem

    [Simon Ubsdell] “you don’t have a shortcut for the video Share”

    ???
    Erm… I just wrote it? ⌘E? How is that not what you’re looking for? ????

    – RK

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

  • Robin S. kurz

    November 12, 2019 at 11:01 am in reply to: Motion 5.4.4 Save Current Frame problem

    [Simon Ubsdell] “a) I’ve asked them endlessly but Apple refuse to give us a keyboard shortcut. […] Surely this is an easy fix?”

    Yupp. You simply go into the Destination prefs and make that the STANDARD destination? Then it’s on ⌘E. Just as in FCP. ????

    – RK

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

  • Robin S. kurz

    November 12, 2019 at 8:04 am in reply to: Motion 5.4.4 Save Current Frame problem

    Ironically I *just* had this exact same problem but in FCP two days ago! Had never seen it before. I tried exporting a frame from a clip that had the “Letterbox” filter applied (which, to my surprise, CROPS the clip and doesn’t, as I assumed, put black bars over it) and the bars came out WHITE, too. Have also reported it directly to Apple.

    So this isn’t something new?? … how annoying. ????

    – RK

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

  • Robin S. kurz

    October 7, 2019 at 7:44 am in reply to: Puppet Tool – finally!!

    [Tangier Clarke] “and more options for setting up parameters (and separating them)”

    Ironically that’s exactly one of those things that I meant by advancing/optimizing EXISTING functionality, yes. Add to that things like selection behavior and motion blur and a slew of other things that need serious improvement before anything else is added IMHO, and I’d be even happier.

    Of course, the subject of a planar tracker plays into the whole 3rd party thing I mentioned, seeing that there are endless options to be had there, too. Especially since I think Apple’s version of that tracker would probably compare to the others like 3D text compares to mO2. Would that really help i.e. actually be a better option? Because if it isn’t, why bother?

    – RK

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

  • Robin S. kurz

    October 6, 2019 at 9:53 am in reply to: Puppet Tool – finally!!

    [Tangier Clarke] “For the most part it does everything I need to do though.”

    I’d even guess it does far MORE than you’ll probably ever need. I know it does for me. Starting at probably a double-digit number of behaviors that I don’t know I will ever need or simply don’t understand well enough to put to good use.

    And yes, while I’d LOVE to have things like a mesh warp tool or camera solver etc. built-in as much as the next person, I also understand that a) they’re not easy to both develop and have work consistently i.e. meet expectations (i.e. are an inordinate amount of work) and b) you open yourself up to potential instability or just general issues, in turn resulting in even more work, disappointment, frustration, unneeded complexity etc. And really… for whom? For only a fraction of users? I personally like the idea of making the app a one-time, super cheap purchase and leaving niche functionality up to third-parties. That way no one is paying for functionality they don’t even need, and if they do, they just buy it on top.

    If there’s anything I would appreciate to see much more advanced/optimized, then that would be the EXISTING functionality as well as massive improvements and expansion on the existing FXPlug API. Because there are just so many basic UI and UX things that have plagued Motion for a very long time. Some things literally since day one! And I report them over and over. Add expanded FXPlug functionality, then it would be that much easier and less frustrating for 3rd parties to pick up the slack (and in turn diverting work and expectation away from Apple). Only, as it stands, I know that people like motionVFX would love to do MUCH more, but are extremely limited by the current state of FXPlug. Many of their plugins are in large part literal HACKS to even get them to do what they do, which also adds unnecessarily to further potential problems and instability. It shouldn’t be that way. Improve the API so others can do what they want, then the interest in supporting it, and with that, the interest in Motion rises accordingly!

    But, if you ask me, as it stands you’ll never see anything added to Motion (built-in) that doesn’t benefit/translate to FCPX first and foremost. And something like a mesh warp tool or camera solver would be that much harder to get working in FCPX in a relatively usable way. In which case… don’t bother. Something I can actually understand. But, as I said, don’t limit the APIs to the point where no one can jump in if they want to or simply give up because they hit too many walls!

    But as far as built-in, where do you draw the line with a ONE TIME $50 app? Add all that in and charge more? Start charging for updates? Because it would seem that everyone only ever expects a GIVE, but never a TAKE. That somehow is completely unacceptable. So, damned if you do, damned if you don’t. So… don’t. ????

    – RK

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

Page 6 of 195

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