Forum Replies Created

Page 109 of 137
  • Scott Witthaus

    October 3, 2014 at 11:29 am in reply to: 10 Things Steve Martin wants in FCP X

    [Steve Connor] “[Scott Witthaus] “Hey, let’s start a posting on the top ten things we want in Premiere and then Dennis can really get some info he can send back to corporate!

    ;-)”

    #1 Send to Motion :)”

    #2 An interface that doesn’t look like a 10 year old designed it.

    #3 No tracks

    Here ya go, Dennis. A start for your report!

    😉

    All in fun. I don’t do a lot of work in Premiere and try to avoid it if possible. I am sure I could get as fast on it as, say, Media Composer….

    Scott Witthaus
    Senior Editor/Post Production Supervisor
    1708 Inc./Editorial
    Professor, VCU Brandcenter

  • Scott Witthaus

    October 2, 2014 at 9:44 am in reply to: 10 Things Steve Martin wants in FCP X

    Hey, let’s start a posting on the top ten things we want in Premiere and then Dennis can really get some info he can send back to corporate!

    😉

    Scott Witthaus
    Senior Editor/Post Production Supervisor
    1708 Inc./Editorial
    Professor, VCU Brandcenter

  • Scott Witthaus

    September 30, 2014 at 4:00 pm in reply to: 16 Channels Issue

    Interestingly when I round-trip back to X from R11, the titles all go back to their normal formatting, but on a very simple XML from R11, I am missing two of the eight clips in the timeline. They were rendered out but not placed back in the X project timeline (the titles were, albeit over a blank clip).

    Scott Witthaus
    Senior Editor/Post Production Supervisor
    1708 Inc./Editorial
    Professor, VCU Brandcenter

  • Scott Witthaus

    September 29, 2014 at 5:05 pm in reply to: 16 Channels Issue

    I have seen a fair bit of weirdness testing out X to R11, mainly in titles. Have not encountered any audio issues yet.

    Scott Witthaus
    Senior Editor/Post Production Supervisor
    1708 Inc./Editorial
    Professor, VCU Brandcenter

  • Scott Witthaus

    September 26, 2014 at 11:37 am in reply to: FCP7 is dead. Why can’t there be a new FCP7?

    [Shane Ross] “Can’t help but notice that the OP has yet to come back and reply. Seems like a troll stirring the pot needlessly.”

    Exactly. Some folks must be very bored.

    Personally I don’t want someone to re-make FCP7. It’s old and dead. Having just done a little work on Premiere, that just confirms my thoughts.

    Scott Witthaus
    Senior Editor/Post Production Supervisor
    1708 Inc./Editorial
    Professor, VCU Brandcenter

  • Scott Witthaus

    September 25, 2014 at 12:42 am in reply to: This time next year…

    [Lance Bachelder] “Plus FCPX makes me feel young again”

    And it is something that is natural for young folk too…no pill needed. Once again, I watched my students edit last night and FCPX is just so natural to them. Really amazing to watch. Way more than FCP7 ever was. Apple got something very right here. Now, if they just keep on supporting it…

    If so, FCPX will grow faster than Pp and Avid, IMHO. I think they (MC and CC) have plateaued and now get into the real fight for new customers. One could look at raw numbers and say “gee, look at how many CC and Avid subscribers have joined up..” but that’s just the hard core switching over. And just wait until that subscription price rises in 18 months…

    😉

    Scott Witthaus
    Senior Editor/Post Production Supervisor
    1708 Inc./Editorial
    Professor, VCU Brandcenter

  • Scott Witthaus

    September 23, 2014 at 6:18 pm in reply to: This time next year…

    [Marcus Moore] “The reports I’ve had from people I trust is that they’re on a great track but not there yet.”

    I have R11 on a brand new, totally tricked out Mac Pro and the playback performance is awful. I like the product and will keep learning it, but it’s a long long way from being an every day, heavy-lifting editor. FCPX is far ahead of it.

    Scott Witthaus
    Senior Editor/Post Production Supervisor
    1708 Inc./Editorial
    Professor, VCU Brandcenter

  • Scott Witthaus

    September 23, 2014 at 2:11 am in reply to: 10.1.3 bug?

    [Oliver Peters] “You wouldn’t have had this problem with tracks ;-)”

    And how is this?

    Scott Witthaus
    Senior Editor/Post Production Supervisor
    1708 Inc./Editorial
    Professor, VCU Brandcenter

  • Scott Witthaus

    September 22, 2014 at 8:41 pm in reply to: 10.1.3 bug?

    [Bret Williams] “Why not just turn off the audio in the inspector? Simpler, cleaner, and reversible.”

    That is a good tip and thanks for that, but to the original point, I don’t think this should happen in the first place.

    Scott Witthaus
    Senior Editor/Post Production Supervisor
    1708 Inc./Editorial
    Professor, VCU Brandcenter

  • Scott Witthaus

    September 18, 2014 at 6:13 pm in reply to: Avid Restatement

    [Andrew Kimery] “Avid offers a perpetual license option and a subscription option.”

    But still, you either buy the annual support by 12/31 or when you do want to upgrade, you pay full license price. So, that is what I mean by “force”. Or am I missing something here.

    For example, in my market Avid has largely gone away. Maybe one shop that clings to it, but usually uses Premiere or FCP. I still have an MC7.0.3 license on my computer for “just in case”. But quite honestly, I have not had a paid Avid gig in years, so paying $299 makes no sense. However, if I don’t do it (buy their support) before the 31st of December, I am penalized and have to basically re-purchase the license. Good for Avid revenue, bad for me.

    Now I know some people will say “it’s only $300 bucks! Just fork it over!”. Sorry, I don’t think that way. So while Avid may get a surge of revenue at the end of the year with this “tactic”, they have lost me as a paying customer and I am sure many others like me. Hello, FCPX and Resolve (when it’s worth a sh**).

    Scott Witthaus
    Senior Editor/Post Production Supervisor
    1708 Inc./Editorial
    Professor, VCU Brandcenter

Page 109 of 137

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