I just came off a support chat with adobe, the agent said because Premiere works in software render mode, it is "could be a GPU acceleration issue that may happen due to driver issues":
"its more of driver optimisation issue, apple has been informed regarding driver optimization for several GPUs, the team is working in this and should be sorted soon.... drivers are made by GPU manufacturers like Nvidia, AMD or Intel and then they are optimized by the GPU and OS manufacturer for different uses, they have been informed regarding such issues, team is working but we dont have an ETA on this".
Does anyone know of any non-Adobe software that uses GPU acceleration or optimization? Would be good to test this theory.
I totally agree. Why not make one clear statement about what's going on and when we can expect it to be fixed. I get it's a holiday season but like others said, this problem has been around for quite some weeks now and those of us who run a business would love to get some things cleared up.
And I'm not here to mock about stuff, I usually don't care about small glitches and bugs at all, but this one is starting to cost me quite some money. Here I am, new machine in front me, paying for a CC subscription but I can't even meet my projects deadlines because of this stuff...
Can't wait for the day I get a nice little "Premiere Pro update available" popup.
Hi Jrfsl, What sounds like a small adjustment in GPU drivers can sometimes become a neverending story. It happened before, also with Adobe software on the Macbook. My late 2013 Macbook pro has an Nvidia GPU with CUDA excelleration. The usage of Cuda with Adobe CC software caused (as you might have already guessed) graphic errors and crashes. Long threads can be found on this very forum. To cut a long story short, the issue has never been fully fixed. Instead Adobe asked Mac users to only use OpenCL instead. Of course that also meant the speed that CUDA excelleration brought in reality was useless on the previous generation of Macbooks .
So you may understand why I am very very sceptical if it comes to statements such as "it should be sorted soon" . Lets hope for the best, but Ive experieced a situation like this before with Adobe promising again and again that a fix would be underway. It never happened. The only fix was switching drivers which this time around is not even an option. Metal support is still a mess anyway , although (for whatever reason ) it can be switched on in the Adobe apps and Open CL support is broken right now also
That is disappointing. I am subsisting on software render mode at the moment (Open CL has crashed on me) but render times aren't a lot faster than my 2011 mbp.
I just moved from fcp7 to premiere (a bit late I know - old dogs and new tricks and all). I like the premiere interface but if Adobe is so unresponsive to customer feedback I may just go back to Avid.
Eventually, adobe and apple are going to lose customers to more responsive hardware/software companies.
m having the same issue, bought this machine
MacBook Pro 2016 15"
gpu: Radeon pro 460
core: 2.9 GHz i7
planning to teach myself premiere pro after christmas when i got my new Gopro. Just sat down to edit my first video and have had my machine crash on me 4 times in 30 mins with no issues prior to this since I got the machine on 2nd December. Whether its Apple or Adobe thats at fault this needs sorting fast!!!! How is this sort of issue not picked up before release? If anyone is going to use Adobe's software its Apple users. Its crashed when adding effects, playing my timeline and trying to export! What am I paying for? It's useless as it stands at the moment. Really disappointed, I wish I had gone for Final Cut Pro!
I'm now on my 2nd replaced Laptop, because I was advised by Apple support that it was a Hardware fault over the phone - I also had trackpad issues with the first one I bought.
Macbook always crashes when exporting in Premiere Pro.
Unsure who's company is to blame, but I have lost hours of work to this problem - and when you're paying ££££'s for these machines, you'd expect them to be able to manage exporting a 3 minute, 1080p video in one piece!? I'm getting into trouble for not finishing work on time, simply not acceptable really. I think my mobile phone can manage it better than this Mac can...
MacBook "Pro" 2016 15"
Radeon Pro 450
Hey Andrew, As for the Premiere Pro issue you can see you are not alone in this. Of course its difficult to pinpoint for sure who is the one to blame, but if one thing is standing out in this case its that it seems only Adobe apps are affected and since I was forced to work with FCP X now because of this mess, I can report ( just as others did before me) that I was able to work without ANY problem whatsoever on my new Macbook.
I am a Premiere editor though and I subscribe to CC to work with Premiere Pro, After Effects and Media Encoder and I do expect a company like Adobe to test out their product immediately and very thoroughly when new Macbooks come out. If they would have done just that, let someone at Adobe work with/test their own apps for just one day on one of these new machines, they would have found out about it weeks ago THEMSELVES ! Instead many Mac/tech sites and of course us users had to bascially do their job, test their apps on the new Macbooks when they came out and discovered this issue right away (by the end of November !) .
One would think maybe at that point Adobe would have noticed theres a larger problem to sort out, but not even that. It is only weeks later after several complaints on here that someone at Adobe actually notices this. And I keep asking myself honestly how can this be for a huge company like that ?
I will add my name to the list as I'm experiencing all the other same issues as everyone else. Literally I jumped on premiere for 20 minutes and the screen went funky like yours when I was just playing with clips in the timeline.
I'm a professional video editor who has been working on my 2011 macbook pro (yes the one with inherent GPU issues that meant the board got replaced over and over - http://www.macworld.co.uk/news/mac/widespread-2011-macbook-pro-failures-petition-lawsuit-r epair-programme-3497935 ) and was hoping investing a lot (too much actually) of money in the best mac laptop money can buy would be the silver bullet for moving forward. I do worry that even though premiere may come up with a software fix that there may be a problem inherently wrong with this new machine, which will truly effect the longevity of this machine. As experienced with my older MBP, once these type of issues begin (like a car that has a minor accident) it gradually snowballs / perpetuates over time in wearing the machine down.
Specs : 2.9GHz quad core Intel Core i7processor, Turbo boost up to 3.8Ghz. 16G Ram. 1TB PCie-based SSD. Radeon Pro 460 with 4GB Memory.
1 person found this helpful
This whole thing has got me rethinking all my Mac/PC/FCPx/Premiere choices. I have been so frustrated with the crashing of my new MacBook Pro that I bought a new speced out Surface Book with Performance base over the weekend. Thought I would share some preliminary numbers. One of the big time sucks for me is exporting timelines for client review. I thought I would see how these things did side by side with a raw 1min 6k Red Dragon timeline. No color correction ...just exporting to a 4k Youtube preset. Here are the export times.
MacBook Pro 2016 (Open CL) - 30min 16sec
Surface Book with Performance base (Cuda) - 14min 50sec
Then I took the SAME timeline into FCPx on the MacBook Pro and it took 4min 41sec for the same 4k export. Its amazing how much faster FCPx was. I may need to invest more time in learning FCPx.
Just to add some weight to this thread, I have the same issues with the same screen as the OP.
I can reproduce the problem easily by just using Premiere or media encoder. I did just that in front of a Genius Bar representative before the New Year too. It doesn't happen at any specific moment such as export or effects. It seems to happen by just using Premiere or Media Encoder.
It is completely eliminated by using software rendering. I've edited several projects in this mode over the Christmas period and it hasn't red/green screened on me once but since I'd like to complete a project before I have a full ZZ Top beard that's a pretty useless option and I might as well go back to my 2013 MBP as it's probably faster!
As others have stated, this doesn't happen using Final Cut. I've been trying to learn FCP over Christmas as an emergency tool and it doesn't miss a beat.
For the record, it happens in projects created on my last MBP if I open them on this new machine.
I echo others' sentiments too by saying that almost everyone who has a new MBP with Radeon 460 bought it with the intention to make a living out of it. This isn't an inconvenient glitch in a computer game. It's people's livelihoods.
I'll ask the question I asked on another thread again: Has anyone got a 460 Pro equipped machine with Adobe products that DOESN'T have this problem? I asked in other threads and nobody has come forward in about a week.
I just called adobe and asked for an update and was told it's a hardware issue!!!
You get a different story depending who you speak to. I mentioned this thread and how someone from Adobe had posted that they were working on a fix with apple and was then informed that this was not the case and it was my hardware at fault.
I have therefore reverted my CC subscription to the photography only plan as Lightroom and photoshop seem to work Ok. I'm not paying for something that doesn't work when they can't even admit there's an issue.
Will try final cut tonight and if it does what I need it to Adobe can keep their apps. They are great in a way but very glitchy in my experience and they are not handling this well at all.
Your experience with Adobe support is as expected. My support guy claimed they haven even heard about this issue a week ago when Rameez Khan of Adobe was already saying here "We are working on a fix with Apple ". Now your Adobe support says its apparently a hardware issue. If you scoll up you can see what other contrary answers Adobe support has given us e.g. ""could be a GPU acceleration issue that may happen due to driver issues": Their internal and external communication is obviously terrible, not just their software testing
I still reckon its not a hardware issue since all other software except Adobes works fine without any issues like this. But lets face it its always easier to blame the other party
In November 2016 I bought a 15" MacBook Pro with the Radeon Pro 460 graphics card. Almost immediately I started having crashes using Premiere. Apple had me do some resets - Pram and something else and it settled down for a short while, but then continued to crash, ending up crashing every time I played a clip. When the the computer crashed I got the green checker box freeze with red flashes. The computer was replaced by Appleat the end of December. Now the same crashes have started to happen on the new machine. I have contacted Apple and Adobe. Apple has made no suggestions other than to say “Ask adobe”. Adobe had me reinstall the app, but it is still crashing. The new computer has crashed 4 times during 5 hours of work. When I got the first machine in November I did a fresh install. I have little else installed on the machine other than the essential Creative Cloud apps and no 3rd party apps or LUTs. I did migrate to the replacement machine (from the fresh install of a few weeks earlier).
Same problem 2.9/460 TB Played a 4k clip on the time line and 30 seconds in it started freaking out and had to force shut down. Help us out adobe.
Thanks for the news and your feedbacks guys.
Then, the fix would be like an update of adobe right ??? We don't need to send back the macbook pro to apple ?
Thanks for your help
This seems to be the case based off of everything I have read on these forums and my personal experience diagnosing the hardware with Apple. My issues are isolated to Adobe apps that use GPU accelleration.
We can't be certain Sam, but since it looks as if only Adobe apps are causing this issue for everybody here a software issue seems very likely
I have a 3 year old MacBook Pro running the same OS and Premiere software without issue. Could you explain how this could happen?
hey wideangleprod , Id say ita a combination of a different GPU and Adobe software. Often newer systems need software adjustments to keep things working. It seems Adobe didnt want to go through all the trouble testing out the new Macbook hardware themselves, but rather leave the testing to us their faithful CC subscribers . Apparently you can get away with that kind of customer care
1 person found this helpful
Sadly, I don't have any good news to give you, as of today.
schmollywood and jrfsl, I don't know why you got such an answer from Adobe support. Could you give me the case numbers of the support sessions? I can check with the agents and provide appropriate feedback.
Anyone who is contacting Adobe support, please make sure you're connected with our Premiere Pro/Video experts and not just generic support agents.
Thank you all for your patience!
Of course RameezKhan, my case number is 0188515963. The support request has been placed with your support agent Mathias Kunzendorf on Dec 28th
my my first session was case 0188521532, I think I don't have a case number for the second session, but it was with Sumeet at Jan 2, 2017 11:26:04 AM EST
Hmm, I had a horrible time with the CUDA — also. I was looking at how well video scrubs in FCPX today. Hate to loose the color corrector in Pr but my shoots are pretty dialed in these days. Perhaps it's time to cram on FCPX and make the transition. I have been around the block with doing troubleshooting and development for manufactures - starting with Avid in 88. At least they seemed to care then...... so tired of this lack of professionalism.
Moderator note: do not use profanity. It is against Adobe community guidelines.
@RameezKhan, you really have to understand that this issue is a BIG problem, so I don't know how high is your position but you have to make it move forward fast. People are using ADOBE softwares to work. Or maybe you want people to switch to FCP. If it continues like this, we'll do that!
I have cancelled my subscription to CC and reverted back to the photography plan for now.
Started using Final Cut Pro X last night and it works like a dream, didn't skip a beat! Adobe had no excuse for this, they're programmes seem to never have enough speed of memory to run properly whatever machine you buy and now they can't even make it work on a new £3k+ laptop when people are paying £££££££ for they're services!!!
Im not a professional at this, it's a hobby and will do the best I can with any other software I can use. It actually annoys me that there is no real alternative to Lightroom otherwise I would be cancelling that too!!!
I totally understand Scubalooba and Im considering the same if they cant sort this mess out asap.
Dealing with this issue made me also think, why Adobe next to OpenCL support (which is obviously broken for everyone here) would even give us the option to choose Metal in addition as a render engine when Metal is not working either and so far it never has, not on the new Macbook and not on my previous one . It really makes me wonder if anybody at Adobe actually works with their own apps on the same machines as we do, because if so it wouldnt take more than a few hours to figure out its just a complete mess.
1 person found this helpful
Based off the lack of news and the time that has already passed I am no longer waiting. I have deadlines and choose not to lose my clients because of sloppy engineering and nearly silent customer support.
I would like to give some constructive feedback to Rameez and his team at Adobe. I am a vetran commercial filmmaker and for some time I felt like Adobe was my partner in creating post production tools that allowed me to get my work done. I no longer feel this way because of the complete lack of feedback in how this very serious problem is being resolved. If I had some sense on how this is being addressed or an official response from Adobe it would be extremely helpful. The reality is my post production train keeps moving and I have clients with very real deadlines. It is irresponsible for me to partner with a company where I cannot finish projects and I lose clients and money that affect my ability to support my family.
The good news is I really do have some fantastic alternatives to most of Adobe's product line, especially Premiere. I have been forced to work in FCPx over the past few weeks and I cannot believe how much faster and more reliable it is than Premiere. I exported a 6k timeline in 4min instead of waiting 30min to export the same timeline in Premiere. My advise to everyone else on this thread is to explore other solutions. Im kinda shocked/glad that I was forced down the FCPx road. Good luck to everyone. Im moving on.
I'm on the same page! I have significant experience with both Premiere and Final Cut - and have well established workflows in both. I was trying to use Premiere with my latest string of projects (my video/editing is mostly for hobby and not something I do full time) because some of the latitude it provides over FCP sometimes offers me more creative freedom. However, over the last week or so, I've moved back into Final Cut Pro and it's significantly faster in every way.
In Premiere, for example, if I took some 1080p footage and sped it up 10,000%, it would NOT play. I had to export to see how it looked, and trying to match to beats - forget about it, impossible.
Final Cut (latest version as of this post), no lag whatsoever in playing in the timeline, easy to match to music. I may actually go back to capturing some footage in 2.7k!
Anyway, pretty excited about Final Cut Pro right now, sorry Adobe! Hope you get your act together.
On the plus side, I'm still happy with Photoshop!
I'm currently at a point where I'm seriously about to smash this Macbook. Like Bryan said, I too have deadlines and explaining my clients I can't deliver because "my software isn't working" is of course not a valid reason.
Don't get me wrong, I really want to help where I can. I try to recreate the problem but it really just happens at random moments. I've had it freeze over a nested sequence but the rest were "just" while playing back normal clips.
Anyways, one last time I'll post some crash reports:
• No crash for first 2 hours of editing (woohoo, felt good editing again).
• Went somewhere else and started editing again (no charger attached)
• Within 30 min - 2 crashes (1 time - while previewing my timeline these "Transparent" blocks appeared and the system froze, audio was still playing (no effects or weird speed ups applied, just 4K footage scaled to 1080p). 2nd time - same, just no "weird blocks" this time).
• Then back at my office, editing with charger again, but still crashes every 10 to 30 minutes.
• Just now - when previewing a clip - screen just turns completely black (again no effects applied).
• Restarted - continued editing - within 5 minutes, again a black screen.
• Again, same. Have to stop working as it's just impossible..
The last thing I want to say about this; is how can there, at this time, not be a few pissed off managers at Adobe realising how bad this is and start communicating (in- and externally) and force their crew to fix this asap?
Hi Kevin, I'm sharing the same as you. We have to spread this everywhere, I totally agree with you and I am amazed of their "relax" attitude.
This has suddenly got a lot worse! My whole desktop is now glitching out. Only got this MacBook Pro 15" yesterday (2.7Ghz Radeon 460).
I started getting the same problem in Premiere Pro CC last night which would freeze up my screen with the red pattern and crash the Mac.
I thought I'd see if I could get through exporting a 4K video this evening and half way through it must have crashed in the same way, not sure how long it was like that as I had walked away for 5 mins... so I hard rebooted. BUT when I got to my login screen I noticed that pattern from when it freezes was faintly emblazoned on the login screen. When I logged in my whole desktop started glitching out with that faint pattern.
Videos showing all of the above including first two crashes then the login screen and desktop as it is now are in the following Dropbox: Dropbox - Macbook Pro Problem
I'm totally gutted because I figured oh well I'm sure Adobe will find a solution soon and I'll live with it till then... but it seems to have corrupted something and now the whole Mac appears to be screwed! However I see reports of the desktop glitching on the early releases of the new MacBook but I've not seen any recent reports here. To confirm this desktop glitching is happening without any Adobe software running.
Regardless of what has caused this I'm now facing the reality of the long drawn out process of replacing the machine I just spent the last day setting up. So disappointed. Contacting Apple next.
UPDATE: Next day my desktop is back to normal again but I feel like I'm "working on thin ice!"
(Below: the pattern now flickering on my desktop even without Adobe software running - but caused by the crash while running Premiere - see video in Dropbox above)
(Below: original crash screen while playing down video in the Premiere timeline, only 1920 x 1080 H.264 video)
Intel Core i7 2.9 Ghz
Radeon Pro 460
Same issue sue with me too. Every pro I know who has bought a new Mac has sent their MBP back to Apple If they use PP, not realising it's an Adobe issue. Ive just recalled mine from the repair shop and will sit tight for an update.
I get the Red Screen of death or a bizarre disco flickering every time I import and scrub through 4K.
Rameez can you pass onto the tech team that this is the quickest and easiest trigger I've found to break it.
I've always been thrilled with Adobe customer service in the past, with one of the chief engineers Steve Hoeg flying out to an OB I was working on to personally write a patch to fix our issues. As everyone is saying Rameez this needs to be sorted quickly and treated as an absolute emergency for you guys, as you will have pro's deserting you in droves the longer this goes on, and undo all of the hard work you've done as a company to position yourself so well in the market.
I for one can't switch, as I'm halfway through a feature film, but if I weren't I'd be switching back to Avid fairly quickly andbi REALLY don't want to do that.
Since I really had to finish something I switched to "Metal" one more time to see if it would work this time. This time I was able to work another 4 hours in Premiere (+ export) WITHOUT any glitches or crashes. Once I hit play, the preview monitor was very glitchy during the whole process (see attached image - multiplied screens and buggy windows for no reason) but at least it didn't make the computer freeze. I don't know if I just got lucky these fews hours and I know it doesn't work for a lot of you, but as a kind a of "emergency fix" it's worth trying for some of you to be able finish your project in Premiere for now.
File -> Project Settings -> General --> Change Video Renderer to "Metal"
Is this an issue when editing with 4k footage or all?
I'm in the process of upgrading my mac book pro but looking at these posts I'm thinking of holding off until a fix is found - it sounds a nightmare!
sueh6011233 it's not specific to 4K... mine first crashed with simply 2 minutes worth of 1920 x 1080 H.264 footage in Premiere. That's not the case for everyone but it's unpredictable. I've read of someone getting weird graphics glitches as soon as they installed the Creative Cloud app and hadn't even installed Premiere and other apps yet... whatever profiles Creative Cloud installs is perhaps causing the problem and Premiere just triggers it the most often? That's just guessing though.
I'm really sorry for your issues!
I'm advocating for all of you and have already passed the feedback to the Engineering Team. I'm sure this will be fixed soon.
mrjonkane, I haven't seen any cases where the Creative Cloud app has caused this problem.
Thanks RameezKhan the reference I made was to the following post over at Macrumors forums: Graphic card freaks out with brand new MBP 2016 | Page 27 | MacRumors Forums - Interestingly he found that going into "Color Profiles" seemed to temporarily reset the glitch he was having (though with the problem most of us are having we wouldn't get the chance to do that because the screen freezes entirely).
Another comment in that forum said "It's been stated several dozen times by experienced users that the 'glitch' is a Quartz rendering bug caused by the switches in the colour profiles and drivers." - not sure if that explains anything or relates to some way Premiere could be more likely to trigger whatever bug still exists. Apple thought they had got rid of it with the fix back in December but it seems they didn't dig deep enough, hopefully between your teams they can resolve it quick...
Just started a 30 day trial of Final Cut so I can at least work on something but I don't want that to be a permanent solution... I like Premiere!
1 person found this helpful
Here's a short update of my support request regading the issue that is haunting us. Ive received a message from Adobe Germany today which translates:
"Unfortunatley this is a software bug. We are currently working on a fix with Apple. The only solution we can suggest for now is to install the prior version of CC Creative Cloud-Applikationen herunterladen und installieren "
So, basically nothing new except that the plot thickens in terms of a software and NOT hardware error which would be good news for everybody experiencing this issue
1 person found this helpful
MacBook Pro late-2016
Intel Core i7 2.6 GHz
Intel HD Graphics 530
Radeon Pro 450
First experience of crash [video]:
Second experience [photo]:
Third experience [video]:
Adobe, this is unacceptable.
After receiving my brand new MacBook Pro 2016 with the above specs only seven weeks ago it was barely two weeks before I was having to contact Adobe support due to this abrupt, flashing red glitchy screen interupting my professional edit sessions. After a very lengthy live-chat with your technician in which he remotely took control of my machine, readjusted Premiere settings, downgraded my software to CC2015 and ultimately admitted "I'll be honest with you here, this is a known issue happening on the new Macbook Pro's" [quote] I've continued to encounter this extremely disruptive issue beyond the examples lonked above to the point where I'm now unable to confidently work on a single project without holding my breath waiting for the problem to reoccur (which it inevitably does), meaning I now have to pay for the hire of an alternative method in order to complete my professional projects. This is all despite paying a substantial amount of money for a product I'm completly unable to use.
- “This is unusable from an editors standpoint”
- “I was told by adobe support to use software only render..it has not crashed again...but 6 hrs to export a 15 clip is way too much”
- “Ive Installed almost nothing except for Adobe CC to keep the system as clean as possible for video editing which is my professional business.”
- “This is our livelihoods”
- “…this one is starting to cost me quite some money. Here I am, new machine in front me, paying for a CC subscription but I can't even meet my projects deadlines”
I sympathise and agree with each of these users who have paid your company considerable amounts and what you've given in return is a product that does not work and does not meet the acceptable standards of a program fit for sale or purpose. It's under-developed. It's not ready and I'm very interested to know how you plan on compensating the industry professionals affected so far who've had to spend more of their own money resolving this mess themselves, all while you continue to point fingers and keep a firm hold on the subscription fees you've accrued. To have not even received so much as a generic e-mail apology for the inconvenience some customers may have been affected by is a disgrace.
Please consider this post an official complaint, because if these issues have or have the potential to cause any as yet unknown hardware, component or overheating defects in my new machine rest assured I'll be holding Adobe accountable to rectify it.
Adding my name and very frustrating, similar experience to this thread. I have hours invested into a PP project I cannot finish and must either push back client deadlines or more likely recreate in FCPX.
MBP Late 2016 - 15" 2.9GHZ - 16GB Ram w Radeon Pro 460
OS Sierra 10.12.2