Skip to main content
Participant
September 21, 2016
Answered

Mac Os Sierra & Premiere Pro CC 2015.3

  • September 21, 2016
  • 20 replies
  • 41009 views

Is anyone aware of any issues with Premiere Pro CC 2015.3 and Mac Os Sierra?

2015 MacBook Pro 15"

   2,5 GHz Intel Core i7

      16 GB 1600 MHz DDR3

          AMD Radeon R9 M370X 2048 MB

    This topic has been closed for replies.
    Correct answer Kevin-Monahan
    • OS X 10.12 "Sierra" is now listed as supported in Premiere Pro system requirements.
    • As usual, back up all major files before updating an OS.
    • We recommend that you avoid updating any OS unless you are between major projects.

    Regards,

    Kevin

    20 replies

    Participant
    October 16, 2016

    Still the same problem. I´m also having the same problems and I wasn't aware of this constant amount of crashes.

    Please help!

    Participant
    October 15, 2016

    I wish I had read this post before installing Sierra. Sigh. Files that rendered fine are now returning errors. The files are completely and utterly destroyed. Every transition has stopped working. And timecode adjustments cause errors. I am screwed! I can't preview. Nada!

    ADOBE HELP!!

    Jean-Boutros
    Participant
    October 6, 2016

    I've been facing the same crashes since I upgraded to OSX Sierra.

    The CPU and RAM usage are very high, though I have no third party plugins or any program running that might affect Premiere's performance.

    Rameez_Khan
    Legend
    October 10, 2016

    Hi Jean-Boutros and Mark-MVS,

    Sorry for your issues!

    Jean-Boutros, did you experience the memory leak issue on OS X 10.11 too, or is this new with macOS 10.12?

    We're aware about this memory leaking issue and it will be fixed in the next release.

    Thanks,

    Rameez

    Jean-Boutros
    Participant
    October 10, 2016

    I've restored my mac back to OS X 10.11 and I've been facing the same problem occasionally. Less frequent than Sierra, however is still occurs. Usually it occurs as soon as I open a project and the project starts loading the files. If my bin is in thumbnail view, only few thumbnails are loaded and the rest remain grey. When I try to play any of them, I get the media pending image until Premiere becomes completely unresponsive and I have to force quit it.

    !

    Participating Frequently
    October 5, 2016
    Warren Heaton
    Community Expert
    Community Expert
    October 5, 2016

    The management of hardware and software is 100% the responsibility of the individual that owns the computer.  Hopefully you have an IT professional or value added reseller (VAR) that specializes in video editing systems and provides you with personalized support for your specific video editing needs so that you can focus on the craft of video editing; however, most freelancers, pro-sumers and consumers don’t have either. If you fall in this category and you don’t want to (or can’t afford to) hire someone to maintain your workstation(s), you have to get up to speed on a broad range of topics.

    Here are a few general things:

    • Your video editing workstation is the sum of it’s parts, both hardware and software.
    • Hardware and software vendors cannot possibly anticipate how every possible combination of hardware and software will perform.  At most, they can offer known stable configurations, best practices, and updates as issues become known.
    • Keep meticulous track of the version numbers of everything installed.
    • If you cannot afford any down time whatsoever (who can?), install only software that is necessary for your video editing workflow including 3rd party plug-ins.
    • While it’s fairly common to have one workstation handle your rough cut, graphics, motion graphics, audio mix and online edit, consider configuring separate workstations for these tasks with only the corresponding software installed.
    • Maintain a bootable backup of your boot drive (this is very easy to do under Mac OS X). If or when something unexpected happens after a software update or upgrade, you are one restart away from being back to where you were before the change to your software.
    • Avoid updates and upgrades to hardware and/or software while in the middle of an important project.
    • If it’s an update to Adobe software, Creative Cloud Desktop has the option of not removing the old version of an application, leaving the version of the software that you probably have clear expectations of installed and available for use should there be anything unexpected with the new version.

    Any software application installed has the potential to make other software applications do something that’s unexpected.  Decades ago, there was a 3rd party fax extension under Mac OS 8.6 that would cause all source footage in After Effects to show as 0 pixel by 0 pixel.  To this day, it’s one of the crazier issues that I’ve ever had to troubleshoot while maintaining a workstation for a client.  With that fax extension disabled, AE worked as expected. Be mindful of every last bit of software that’s installed at all times.

    Participant
    October 10, 2016

    "The management of hardware and software is 100% the responsibility of the individual that owns the computer."

    Wrong, just sounds like you're passing the buck (so to speak.)

    - The editor edits, they don't write or create the software that they use to do their editing.

    - Adobe & Apple need to have better communication and in this case Adobe needs to do a better job.

    - It is Adobe's responsibility to be in on the ground floor regarding new OS and test, test and then test some more. The idea being that, when the new OS is released, the Adobe software (that Adobe collects a lot of money for) works properly with the new OS.

    - We have to pay Adobe whether their software works properly or not. If the system was such that Adobe wouldn't collect money from us if their software doesn't work with the new OS, then some of what you were saying would make sense.

    - We're professional editors, we have work to do and don't have time for this nonsense.

    - Adobe is a software creator and they have work to do too.

    So let's stop making excuses, let's stop blaming the editors (who don't make the software) and let's get this taken care of.

    Participating Frequently
    September 23, 2016

    Personally, I feel it's ok to wait a bit before upgrading To Sierra.

    There is nice features with Mac OS Sierra, but there's nothing for me that is going to change my life.

    But I'm really looking forward to Premiere Pro new update annonced at IBC. There was already lots of new features in June, but Team Projects is a huge feature that will change the way I'm working. Other features announed are nice as well, like the keyboard mapping new interface...

    I imagine Adobe have lots of work to make this new release out, and I'd rather that they focus on this update supposed to be there soon, instead of delaying this big one by releasing a small update that gives just the compatibility with Sierra.

    I remember last year, there was a small update for El Capitan, but honestly, I really can wait 1 month for the big release and compatibilty to Sierra at the same time.

    Participating Frequently
    September 23, 2016

    I don't think it's as much a question of waiting to install 10.12… Usually it's a safe bet to install on the update after a major OS refresh (i.e.: 10.12.1 etc…). I think the real breakdown is that Adobe is staying quiet to Pro Users that require the software to make a living. The point of the CC was to stay on-top of updates and not worry, but Abode has broken various updates in AE (just as recent as March of this year -- and it was doozy -- After Effects CC 2015 (13.7.1) had the update), which makes some of us very suspicious and wary (read: me and all of my colleagues). I feel the most important thing is that Adobe be as transparent as possible and tell their users what is happening.

    A side note: It is very hard to find * anything * on this site. I usually google the query, but I still find it very difficult to find any real answers to issues on the Adobe Support pages. It's usually buried in some obscure part of the community forums, and usually with very little help from actual Adobe support staff (going back to the AE CC 2015 13.7 debacle -- you could not preview renders in realtime -- it took me about a month to figure out it was an error w/ Adobe's update and not with my system. Way to go Adobe).

    With all of this said, just communicate to your users about the process. I think you'll find that users will be more at ease when you respect them (because we pay you - and monthly at that).

    Kevin-Monahan
    Community Manager
    Community Manager
    September 23, 2016

    Hi Sinse,

    With all of this said, just communicate to your users about the process. I think you'll find that users will be more at ease when you respect them (because we pay you - and monthly at that).

    I have requested that the product team do just that. I hope that they respond ASAP.

    Thanks,

    Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    Participant
    September 22, 2016

    I'm gonna call BS on this, Kevin Monahan. You mean to tell us that no one at Adobe was in the Sierra beta program from DAY ONE testing to see what worked and what didn't? That as the beta went forward no one noticed any anomalies such as those described here? That no one at Adobe - one of the largest, most popular software makers in the world - doesn't have a relationship with Apple to the point where they can work with them to solve these issues before a major update like Sierra? I find that extraordinarily hard to believe. To leave thousands (millions?) of editors swinging in the wind because WE didn't do a check to see if there are compatibility issues is specious. The onus should NOT be on us editors/users, we don't make the software, we aren't privy to Apple's plans, but I'd bet dollars to donuts Adobe is. Premiere for me is now useless until you patch it. How in the world can your company even IMAGINE that this course of action is the correct way to treat customers who now pay MONTHLY to use Adobe kit? You should be so far out ahead of these problems that we - your customers - should never even have to wonder if there will be issues.

    Bill Roberson

    Digital Trends photo/video editor

    mike_mike_motorbike
    Known Participant
    September 22, 2016

    Adobe's habit of making these types of things the fault of the user is inexcusable.

    I stopped using the adobe after effects forums because the attitude from moderators was always so combative.

    The subscription system was sold to me as a sure fire way to keep up to date.  It makes it very hard to be sympathetic about this issue.

    I mean I got a bong on my task bar today telling me about a sales seminar.  Cant those same marketing people send out updates?

    Participating Frequently
    September 22, 2016

    One thing I think about all this is that the idea that an OS update is a thing editors have to avoid - and I could be wrong - but I'm guessing it's Avid-related. I can't think of an iteration of Final Cut (beyond 6) where this was even a thought, and Premiere wasn't a player until FCPX. The thing about Avid is that from the software development/UX side, it's not what is expected in the year 2016. It's confusing, frequently stupid, and ugly. That said, Avid is extremely powerful and has a legion of devotees, and I have nothing against its capability, but it operates on the idea that only professionals should be able to use it, and that those professionals should know not to update until given the OK by virtue of the fact that they are professionals. For Adobe to adopt this attitude with respect to their update preparedness seems inconsistent with their attempts in recent years to attract editors of all skill levels. You should be testing throughout the beta, yes, but it's also true that the final release could introduce something unexpected. Which is why I think that at the very least, Adobe, you could be out with a post on launch day telling us you're working on it. Just so we know that it's even something you're dealing with, because that is, as we've seen here, not something that your users know. If I'm waiting on something from graphics and it's been a day, I'm gonna check in with my producer. Not because there's anything I can do, just to keep the ball in the air. Maybe take a second to keep the ball in the air.

    mike_mike_motorbike
    Known Participant
    September 21, 2016

    This is an incredibly frustrating. And not even for me - because Adobe is the reason i always buy a new hard drive and do a clean install before upgrading, because inevitably Adobe isn't ready on an OS launch. The fact that you guys were on stage last year at the keynote gives users the false comfort that you're ready for stuff like HUGE ios releases that have been in public beta for months.

    Why act like the onus is on us to keep track of this stuff?  It's not like i can pause my CC subscription while i wait.

    Kevin-Monahan
    Community Manager
    Community Manager
    September 21, 2016

    Hi mike_mike_motorbike,

    Sorry for the frustration.

    • inevitably Adobe isn't ready on an OS launch
    • you guys were on stage last year at the keynote
    • false comfort that you're ready for stuff

    I don't know of an example of a NLE application that was ready in advance of an operating system launch (without unexpected behavior). Most editors I know expect to wait for a following release to expect any compatibility.

    Why act like the onus is on us to keep track of this stuff? It's not like i can pause my CC subscription while i wait.

    Unfortunately, the onus is on us as video editors because the craft is very hardware intensive, which makes our applications highly susceptible to OS and GPU driver issues. When OS or drivers are updated, you have to hold off and protect any existing project files until the coast is clear and the manufacturer has indicated as such. As a CC subscriber, and a video editor, you'll be faced with certain issues that are similar to this.

    You do have some valid points, however, and it would be great to get your feedback along these lines here. I'll also share your feedback with the team.

    Thanks,
    Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    mike_mike_motorbike
    Known Participant
    September 21, 2016

    Thanks for getting back to me Kevin.

    I have no problem with you guys needing time to get it right - but when there's almost no documentation about where the process is (for example an email or pop-up on the CC interface in the task bar) it's almost safe to assume things are going smoothly! Lots of people have been using the public beta for months.

    And it's not even for me - i did a clean install on a new drive - I just feel bad for the people getting burned. You're getting a lot more people in the mix because premiere is bundled with CC now. Like i said, all i'm really asking for is a head's up.

    Kevin-Monahan
    Community Manager
    Community Manager
    September 21, 2016

    Hi Ruan_Oberholster,

    We haven't announced support for this version of OS X yet to my knowledege. OS X 10.11 is the latest Mac OS that is recommended: Premiere Pro System Requirements for Mac OS and Windows

    It is not recommended that you install this OS on a production machine at this time.

    Thanks,

    Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    Participant
    October 26, 2016

    Is this answer still valid? I just checked the requirements for Premiere Pro and it states "Mac OS X  v10.10, v10.11 or v10.12", and I'm sure Sierra is 10.12?

    Premiere Pro System Requirements for Mac OS and Windows

    mike_mike_motorbike
    Known Participant
    October 26, 2016

    Poor form on their part. After Effects and Premiere don't work properly.

    mike_mike_motorbike
    Known Participant
    September 21, 2016

    Im getting consistent crashes.  It's totally busted.

    ilfury
    Participant
    September 21, 2016

    Thanks Mike - will hold off on installing.

    mike_mike_motorbike
    Known Participant
    September 21, 2016

    Yep, i would.  Could be a million things - the migration, the NVIDIA card in my mac pro - the humidity!  But it's totally FUBAR for me.

    ilfury
    Participant
    September 21, 2016

    Same question for Apple's "newest" Mac Pro, which I'm sure many video professionals use:

    Mac Pro (Late 2013)

    2.7 GHz 12-Core Intel Xeon E5

    64 GB 1866 MHz DDR3 ECC

    AMD FirePro D700 6144 MB