Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations Premiere Pro – I could be convinced!

  • Premiere Pro – I could be convinced!

    Posted by Steve Connor on February 9, 2013 at 2:59 pm

    Despite being a “Cheerleader” for FCPX I’m not stupid enough to ignore other options. I’ve been experimenting with PPro over the last few months and I’m very impressed.

    Merlot fuelled rants aside, how are others here finding it in real world use? also how is the XML out as we use Resolve extensively. Although I could be convinced by Speedgrade when Adobe hopefully sort out xml roundtripping with PPro.

    Steve Connor
    ‘It’s just my opinion, with an occasional fact thrown in for good measure”

    Mike Cohen replied 13 years, 2 months ago 19 Members · 62 Replies
  • 62 Replies
  • Bernhard G.

    February 9, 2013 at 4:26 pm

    Hello,

    recently we finished the first real projects with FCP-X.
    Within FCP-X we had 90% of the features we needed for 90% of our work.
    Additionally, FCP-X has high-end image processing algorithms under the hood.
    No doubts regarding quality. A very streamlined process.

    PP CS6 has some great special features and it benefits from the whole CS suite.
    It’s consequent native format support it great! Because of this it is confusing, PP needs ‘render files’ at all. Mercury runs very well! Also confusing is the sequence setting by codec instead per video standard. I also get headache when I need to do rocket science to get full quality out of it (GPU yes/no, 32bit float yes/no, etc…) or hack my app for GPU support at all… WHY???

    Too much of thinking…
    Too many plugins and other CS-apps needed…

    To convince me, Adobe needs to implement all those boring features, no evangelist on this planet could convincingly praise as ‘awesome’, but that are extreme important for real professional workflows (100% 32bit float, motion-compensated de-interlacing, spline-masks, color-grading, etc…) so that 90% of work in 90% of the projects could be done within PP.

    Currently I have a clear bias towards FCP-X !

    Best regards,
    Bernhard

  • Cameron Clendaniel

    February 9, 2013 at 4:35 pm

    Slowly becoming devoted to PrP6. Works very nicely with the Magic Bullet suite and I find it handles everything I throw at it with good speed and stability. The flexibility of easily passing projects back and forth with FCP7 is also a big plus for me over Symphony6. It’s also been rock solid with my LHi (monitoring at least). Audio scrubbing could be improved.

    Cameron Clendaniel
    Film Editor, NYC
    718-254-8027
    cam@camclendaniel.com
    http://www.camclendaniel.com

    Mac Pro: 5,1 2.93 12-core
    Memory: 32GB RAM
    GPU: nVidia Quadro 4000
    System Drive: 512GB SSD
    Media Drives: CalDigit HDOne 8TB, Internal RAID-0 8TB, Miscellaneous eSATA
    I/O: AJA Kona LHi
    NLEs: Avid Symphony, PrP 6, FCP 7

  • Gary Huff

    February 9, 2013 at 4:47 pm

    [Bernhard Grininger] “Also confusing is the sequence setting by codec instead per video standard. I also get headache when I need to do rocket science to get full quality out of it (GPU yes/no, 32bit float yes/no, etc…) or hack my app for GPU support at all… WHY???”

    Because you’re not using a support GPU? Perhaps you should try paying attention to the specs? Plus, Adobe needs to certify that the GPU in question would cause issues in rendering. Why support what you haven’t thoroughly vetted and then, it if causes errors, then people get upset. This way, you know what you’re doing isn’t officially supported yet, and if you happen to get a render error, you very well can’t get pissed at Adobe. And don’t for a second think it’s easy to vet a GPU.

    BTW, why are you setting your sequence settings manually? I’ve never had to do this, I just load up my footage, drop it into the timeline and Premiere will ask if I want it to automatically set the timeline for it (hint: the answer is “yes”). You don’t have to create a sequence as soon as you start a new project if you’d rather do this. Just click “cancel”.

    [Bernhard Grininger] “Too many plugins and other CS-apps needed…”

    For what exactly? You do realize that everything you’re using in FCPX to apparently do 90% of the work you need is actually a plugin too, right? And at least with Premiere you get stuff like Curves.

    [Bernhard Grininger] “(100% 32bit float, motion-compensated de-interlacing, spline-masks, color-grading, etc…) so that 90% of work in 90% of the projects could be done within PP.”

    It’s already there (not spline masks, but that’s easy enough with AE dynamic linking…and besides, doesn’t that require Motion to pull off anyway?).

  • Bernhard G.

    February 9, 2013 at 5:27 pm

    [Gary Huff] “if you happen to get a render error, you very well can’t get pissed at Adobe”
    I do not get ‘pissed’ at Adobe. No app is perfect. No company is. And I understand well Adobe can’t test all configurations out there, especially on Win-PC side.
    With DaVinci Resolve, BMD follows a model of self-responsibility of the user.
    When enabling Mercury GPU, PP could warn and inform the user that the GPU isn’t officially supported and force to confirm this.

    [Gary Huff] “Premiere will ask if I want it to automatically set the timeline for it “
    Yet I have to activate 32bit float and MRQ manually.

    [Gary Huff] “You don’t have to create a sequence as soon as you start a new project if you’d rather do this.”
    Good point. Then why does the dialogue appear at all?

    [Gary Huff] “You do realize that everything you’re using in FCPX to apparently do 90% of the work you need is actually a plugin too, right?”
    How do You know what I need for 90% of my work 🙂

    [Gary Huff] “that’s easy enough with AE dynamic linking”
    Agreed. Dynamic linking is great! But tools directly inside PP would be more streamlined.

    [Gary Huff] “doesn’t that require Motion to pull off anyway?”
    Again: no app is perfect. Spline Masks and Motion Tracking would be VERY useful
    inside PP as they would be inside FCP-X.

    Best regards,
    Bernhard

  • Gary Huff

    February 9, 2013 at 5:36 pm

    [Bernhard Grininger] “I do not get ‘pissed’ at Adobe.”

    I didn’t mean you. I meant the universal “you”.

    [Bernhard Grininger] “Yet I have to activate 32bit float and MRQ manually.”

    You’re activating it for the MPEG render files that Premiere generates when you select the “Render Work Area”. You don’t need to bother with this unless you want Premiere to utilize these MPEG render files when exporting the final, which I never do. You’re just wasting your time otherwise.

    [Bernhard Grininger] “Good point. Then why does the dialogue appear at all?”

    Because some people might get upset if that wasn’t the default? I have no idea, but clicking “Cancel” takes a second.

    [Bernhard Grininger] “How do You know what I need for 90% of my work :-)”

    Because I would assume by “work” you mean more than just stitching clips together? Willing to concede that I’m wrong if that’s all you actually do.

    [Bernhard Grininger] “Agreed. Dynamic linking is great! But tools directly inside PP would be more streamlined.”

    Except each app is geared towards different kinds of workflows. You can make a jack-of-all-trades NLE, but then it wouldn’t excel at anything. Premiere is powerful enough for basic stuff in and of itself, and then AE adds an additional level of complexity for projects that require it, all easily accessible with each other through Dynamic Link.

  • David Roth weiss

    February 9, 2013 at 5:37 pm

    Hey Steve,

    Don’t forget, NAB is right around the corner, and so, the release of Adobe CS7 is only 8-weeks away.

    Although I’m not privy to any of the secret sauce Adobe is releasing in CS7, I do know they very much intend to wow the industry and to further position themselves as a real contender for professional editors.

    FYI, I do have it on good authority that there will be no more .5 versions of any Adobe apps or suites ever again, and users will be able count on new releases at NAB every year for the forseeable future.

    I’m looking forward to seeing your review of CS7 after your first look.

    David Roth Weiss
    ProMax Systems
    Burbank
    DRW@ProMax.com

    Sales | Integration | Support

    David is a Creative COW contributing editor and a forum host of the Apple Final Cut Pro forum.

  • Steve Connor

    February 9, 2013 at 5:44 pm

    [David Roth Weiss] “Don’t forget, NAB is right around the corner, and so, the release of Adobe CS7 is only 8-weeks away.

    Although I’m not privy to any of the secret sauce Adobe is releasing in CS7, I do know they very much intend to wow the industry and to further position themselves as a real contender for professional editors.

    FYI, I do have it on good authority that there will be no more .5 versions of any Adobe apps or suites ever again, and users will be able count on new releases at NAB every year for the forseeable future.

    I’m looking forward to seeing your review of CS7 after your first look.

    I hadn’t even considered that! Also I didn’t know that there will be no more .5 versions.

    Steve Connor
    ‘It’s just my opinion, with an occasional fact thrown in for good measure”

  • Gary Huff

    February 9, 2013 at 5:49 pm

    [David Roth Weiss]
    I’m looking forward to seeing your review of CS7 after your first look.”

    Are they skipping CS6.5?

    EDIT: Glad I’m Cloud…automagically upgraded!

  • Steve Connor

    February 9, 2013 at 5:55 pm

    [Gary Huff] “EDIT: Glad I’m Cloud…automagically upgraded!”

    Cloud was a very good idea, it sold me!

    Steve Connor
    ‘It’s just my opinion, with an occasional fact thrown in for good measure”

  • Richard Cardonna

    February 9, 2013 at 6:22 pm

    Would this mean that upgrades will cost double? $800.00.

    Boy they want to push the cloud very much, and I don.t like it.

    Ric

Page 1 of 7

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