Forum Replies Created

Page 47 of 426
  • Steve Connor

    September 15, 2017 at 2:43 pm in reply to: Adobe – IBC

    [Oliver Peters] “Do the user stories on this page look like they are marketing to one-man-bands?

    https://www.apple.com/final-cut-pro/in-action/

    You also don’t bring on guys like Wes Plate and Tim Dashwood to keep FCPX a simplistic app either. All of this points to an internal direction to make FCPX more advanced in ways that will benefit single, but also multi-user environments.

    Good point, I hope that’s true and that their onward development doesn’t start to exclude what is clearly their core user base in single-user environments in a grab for the smaller, higher end of the market.

  • Steve Connor

    September 15, 2017 at 12:06 pm in reply to: Adobe – IBC

    [Oliver Peters] “A professional tool needs to be able to do more than service one-man-bands.”

    Why? what if that tool is marketed for people that are exactly that. FCPX seems to have sold very well without some the capabilities of other NLEs

  • Steve Connor

    September 14, 2017 at 11:59 am in reply to: Adobe – IBC

    [Herb Sevush] “[Bill Davis] “And the timeline index makes global transition removal a snap.”

    I’m hoping there is more than a global removal, I’m hoping there will be a “remove all transitions in selected area,” as there was in Legacy. That’s the functionality I really want.”

    Easily done in the timeline index

  • Steve Connor

    September 14, 2017 at 11:14 am in reply to: Adobe – IBC

    [Bill Davis] “No Timeline gaps ( magneticism rocks) for 6 years.”

    Really? you haven’t used the ‘P’ tool in 6 years?

    For those of us who haven’t mastered FCPX enough to avoid gaps then you can also remove them all easily with the very powerful timeline index!

  • Steve Connor

    September 14, 2017 at 11:08 am in reply to: Adobe – IBC

    [andy patterson] “Thanks for proving my point for the tenth time Brian. I appreciate it : )

    First: Don’t confuse my comment with my actual editing process. I simply pointed out that anybody new to FCPX could get gaps. I can also purposely create gaps and I admit it would be user error but gaps can happen. FCPX is not foolproof.

    Second: I did not create a video for the world to see of myself using the wrong editing tool with FCPX and then blame my errors on FCPX repeatedly. Jesus did suffer from user error but he repeatedly blamed Premiere Pro. That is why I stated in the other thread if someone gets gaps using FCPX you are quick to blame the user. To prove my point you tried to blame me of user error when I simply made a comment. On the other hand if someone gets gaps using Premiere Pro you are quick to blame the NLE. My point has always been you must use the correct tools in all the NLE to get the desired result.

    Third: I hope from now on you can spot user error on any NLE and not just FCPX. I also hope you will not confuse a comment with the actual editing process.

    Is there any possible way we can just leave this particular subject alone now? It’s getting beyond tedious and it’s crossing into unrelated posts!!!

  • Steve Connor

    September 13, 2017 at 9:54 pm in reply to: Adobe – IBC

    [Oliver Peters] “listens to and tests out new ideas with high-profile customers that you get new, advanced features. “

    I hear that’s what happened when they were developing 3D text ☺

    Seriously though I think what “Hollywood” Editors want feature wise may not be exactly the same things that most FCPX users want and I think Apple recognised this.

    Next FCPX update imminent with HDR and AR features added perhaps?

  • Steve Connor

    September 13, 2017 at 7:45 pm in reply to: Adobe – IBC

    [Bill Davis] “Curious as to how this is different from the FCP X timeline history switching we’ve had since 1.0?

    Isn’t this just storing projects (I guess “sequences” for Adobe folk) in available RAM and letting the editor navigate and cut and paste between them?

    That feature was in FCP X on its launch six years ago.”

    You’re too used to Apple terminology Bill, a “project” in PPro is the same as a “Library” (or even an event) in FCPX.

    So this enables PPro owners to have more than one “library” open at a a time and cut and paste between them.

    Just like FCPX 🙂

  • Steve Connor

    September 13, 2017 at 6:53 pm in reply to: Adobe – IBC

    Can’t wait for FCPX to get this……. ☺

    https://www.youtube.com/watch?time_continue=62&v=BcKc_DzVaRA

  • Steve Connor

    September 13, 2017 at 6:48 pm in reply to: Adobe – IBC

    Hopefully Apple don’ t start throwing development resources at Hollywood productions like Adobe seem to be doing, I genuinely don’t care if FCPX is used to cut high end features or network Television as long as it continues to develop for the vast majority of it’s user base like me.

  • Steve Connor

    September 9, 2017 at 8:08 pm in reply to: FCPX and color correction tools

    [Robin S. Kurz] “First off, amazingly, no one here ever mentioned: keyframes! Nobody misses them? Because that is actually one of the few things I’ve missed from day one, yes. Not being able to keyframe a correction/grade, e.g. for changing light conditions, clearly is quite the oversight.”

    I’ve got so used to blading a clip then adding a dissolve to change the correction after it that I’d forgotten about key frames!

Page 47 of 426

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