Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Premiere Pro 2018 fixed yet?

  • Premiere Pro 2018 fixed yet?

    Posted by D j Harris on January 12, 2018 at 5:39 pm

    Hi, we had massive problems with the 2018 version of Premiere Pro, very sluggish (took seconds to respond to a single key press) and constant crashes. Because of this we reverted all our suites to CC 2017, which works fine, but of course we can’t use any of the new features.

    We do operate over a SAN network, but CC 2017 works fine in this way, and we still experienced lag and crashes when editing from a local drive. We’re not using any strange formats (mostly shooting using an Fs7).

    However it seems Adobe have gone a bit quiet – has everyone solved the problems they were having with CC 2018?
    No updates seem available through the CC app – I am answerable to the company directors, so am I going to have to try and justify us spending a subscription fee on a platform where we are stuck with the 2017 version forever?

    We are recent converts to CC (from Avid) and it was my idea to switch the whole company to Adobe, so I have to explain that decision – I thought CC2017 was good, but can I expect CC 2018 to ever be fixed, based on your past experience with Adobe?

    Thanks

    Dan

    Eric Santiago replied 8 years, 4 months ago 3 Members · 3 Replies
  • 3 Replies
  • Greg Janza

    January 12, 2018 at 6:20 pm

    Dan, sorry to hear that you’ve had so many problems with CC 2018.

    Your assumption that CC 2018 is problematic for everyone though is incorrect. I’m on CC 2018 on Windows and I work almost exclusively with Sony FS7 footage and I have no issues. It works just as well as CC 2017.

    Hopefully Adobe will release an update to 2018 soon. Until then you may need to assess if there’s other issues in your workflow (i.e., the san) that are contributing to your problems.

    I Hate Television. I Hate It As Much As Peanuts. But I Can’t Stop Eating Peanuts.
    – Orson Welles

  • D j Harris

    January 15, 2018 at 10:20 am

    Hi guys,

    Thanks for the responses. Our fix for now is to just revert to cc2017. There may be things the cc2018 doesn’t like about our SAN but cc2017 works fine, so CC2018 is effectively a downgrade for us.

    The reason we switched was that I felt Adobe is better for our workflow – we’re a small production company (shooting and post production) and most of our corporate jobs involve some level of After Effects work. The dynamic link is really useful to make quick changes (rather than the old procedure of having to create something in AE, export and import into Avid etc – then the client wants amends…

    I’d have to say we also had problems with Avid, usually with the database and things going offline, crashing, or corrupted render files, and then you have to go through the whole ‘find and replace’ procedure – it was very time consuming. With Adobe cc2017 I found it to be quite reliable, stable and even if anything did go offline it was easy to fix.

    To be honest, for our projects I’d still prefer Adobe but only cc2017, which worked more or less faultlessly for us, even over the SAN.

    Thanks for the advice Dave, I think we’ll also remain a version behind in future!

  • Eric Santiago

    January 15, 2018 at 8:24 pm

    CC 2018 is working fine on the Mac network using Synology NAS RAIDs.

    We converted one nMP for testing and so far so good.

    However, we leave all the major projects on one that works and so far were at CC 2015 on 2 seats and 1 with CC 2017.

    Those are fine too.

    I learned my lessons with Avid as far as updating too quickly.

    Were still two versions behind with MC.

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