Skip to main content
bubbahgump
bubbahgump
Participant
November 1, 2017
Question

Premiere Pro CC 2018 Update or No?

  • November 1, 2017
  • 11 replies
  • 16480 views

I'm always terrified to update to the full release of CC.

Is it like Adobe always does where they use the first full update as a beta and their unwitting customers as the guinea pig beta testers? 

I can only assume it is full of bugs and everyone is crashing and nothing works as per usual.  They usually take a couple of incremental updates to figure things out.

Please correct me if I'm wrong and Adobe has for once done it right and has not thrown the beta testing on their paying customers.

BTW I'm on the newest Macbook Pro 15" OSX 10.12.6, 16gb RAM, Radeon Pro 460

    11 replies

    Show previous replies
    R Neil Haugen
    R Neil Haugen
    Legend
    November 1, 2017

    I'm on 2018 on my Win10 rig, totally stable and working happily since day one. As someone with a decent 'sampling' of this board over the last 5 years, this is probably the fewest total posts per day for the first week or so of a release yet. Are there some issues? Yea ... no kidding! ... But how big a percentage of the user base has them? Apparently, not so large.

    Which is still to say ... when upgrading, PLEASE be smart. This is a full upgrade, not an update. A complete new build series. 2017 was the 11.x builds, 2018 starts the 12.x. Which means you can have both 2017 and 2018 installed together.

    Before upgrading, check your downloads. If you still have the download for 2017, copy it to a different folder.

    When you tell the CC Desktop app to upgrade, when the dialog box pops up, click on the Advanced Options box and uncheck "remove previous versions". In fact, if your upgrade dialog does not give you the "Advanced Options" bit, cancel it. Sign out of your CC Desktop app, reboot, and sign back in. You should now be able to "upgrade" with the Advanced options available, and again, uncheck the "remove previous versions" line.

    Start new projects in 2018. To test migrating old projects, always migrate a copy of the project file. You can try simply opening them in 2018, which will choose to update the project ... or create a new project in 2018, and in the Media browser, navigate to a copy of a PrPro 2017 project and click the project file, and import the assets or even the project itself that route.

    I tend to use the Media browser, as it seems to work better except for the 2017 release, where the simple updating worked more reliably for me. I've been selecting projects in the Media browser and importing them quite reliably in 2018 ... but always, always test. And use copies when you do even for operating projects!

    This guarantees that if anything does croak on that project, you still have the 2017 version ready to work.

    Neil

    Everyone's mileage always varies ...
      bubbahgump
      bubbahgumpAuthor
      Participant
      November 1, 2017

      Neil,

      This is all great to hear.

      Yes, I learned my lesson a few versions back to always uncheck "remove previous versions".  Got bit hard and had to find a third party site to download the previous stable version until Adobe got their act together.

      What I'm most excited about is the ability to open multiple projects at once!  What a novel idea.  It's like going in the way back machine to something we all could do long ago with FCP.

      Having been bit before I'm still going to hold off until I hear from someone (or many someones) on OSX who's had a positive experience like you.  I don't even want to mess around with it.  I know I would be safe by keeping 2017, but aint nobody got time for that.

      Thanks for the great input!

      Cheers! 

      andrew_articom_sthlm
      andrew_articom_sthlm
      Participating Frequently
      November 1, 2017

      Hi,

      Be careful with multiple open projects. I find it's sometimes confusing to know which project you're saving. It also means a regular quick cmd-S doesn't always mean you're safe anymore. Or, for example, a colleague of mine lost a couple hours of work when he had a "junk" project and the "real" project open at the same time. Managed to save the "junk" and discard changes in the "real", which was a real bummer.

      //A

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices