I agree Jason. Its not wise to rely on brandnew hardware to work with current software such as Adobes. As for myself Im working off my previous Macbook as we speak to finalize my projects. What I do find upsetting and worrying though is how long it will take companies such as Adobe to notice a bug of this magnitude. Kevin revealed something which is actually quite shocking to me about the time and effort it takes to get new hardware from Apple to test for compatibility. He called it a "reality check" and if its true I believe Apple is definitely another big reason why it takes Adobe longer to discover some an issue like this themselves. However I do think they should clearly find another procedure to make it easier for everyone thus being able to get customers fixes quicker. Im also criticle of the obvious fact that communication inside / outside Adobe seems to have a few flaws. First of all I think there should be staff (even if its interns) that will check if things about major bugs are suddenly reported on a lot of Mac/ tech sites. Adobe knew nothing about reports popping up all over late Nov/early December as Kevin confirmed yesterday because HE had been to busy to even notice. Or to put it otherwise there is apparently noone else who could monitor the outrr world for reports like that.  Very strange to me Secondly my experience with their support team still not knowing of this at the end of December whilst people  on this very thread were already discussing this matter with a Adobe staff member by mid December was very strange also. Again, Kevin explained this by saying we should always ask for the video support team not the general support. One would think if you ask for support concerning their video software they would automatically pass it on to that team accordingly. Apparently that is not the case as we now know. Not good though And last but not least even though everyone who makes a living using software such as Adobes should always be aware that brand new hardware may not work straight away, BUT  I believe as soon as something of this magnitude is discovered, Adobe should clearly warn their customers straightaway and very openly about it. Including the info in a support document to me is clearly not enough. Being as transparent and open as possible will put more trust in a company than trying to keep an issue like that almost a secret. As they say the truth will set you free. If I was Adobe I would put out the message to Mac and tech sides that they know what's going on and are currently working on a fix. ... View more

Rather "..had told HIM" Brandon since schmollywood is actually male haha ... View more

Thank you Kevin, At last some answers and transparency many of us have been waiting for. You are right about the fact that only relying on brandnew gear can be risky and as for myself I never do. I kept my previous machine to be able to keep working if something goes wrong with the new equipment. But as you can see from my questions one huge reason for frustration and mistrust is miscommunication and a lack of transparency. Due to Adobes Xmas break it has obviously made things worse. So yes, I do believe there should be some kind of an emergency staff present at holiday times. Its not as if Adobe is too poor to afford it I believe. You explained why you get new Apple hardware for testing purposes often times later than consumers do. I think that's extremely bad. And since this obviously leads to customers coming across issues earlier than you do its probably time to change something about this procedure. Even if it means eg somehow ordering new Macbooks like consumers would so you'd get machines at about the same time after they come out. However, I believe something is not ideal with the current way its set up. And even though it turned out after months and months the CUDA thing wasnt on Adobe as you explained I truly hope this current issue can be solved a lot sooner. One last thing , would you be able at this point to give us at least an idea if this current issue is most possibly driver / software related and a hardware problem is very unlikely ? Since other software (including the video editing software of your competitors) works just fine and actually very fast (as some here are currently experiencing) my bets are on the software that needs to be fixed. Im sure many here who have spent a lot of dough on these new machines would sleep a lot better if they knew that they dont need to go through the time consuming annoying process of a hardware exchange/ repair. Thanks again and lets hope the fix will be there very soon. ... View more

Hi Kevin, Lets just hope and pray this doesnt turn into some sort of scenario such as the one many of us experienced on their previous Macbooks with Premiere namely CUDA support. I remember when you turned up on the various Adobe forum threads concerning the bug(s) connected to CUDA trying to calm everyone down and promising a fix that never actually happened. Even though Premiere could not take advantage of CUDA accellaration (which wasnt cool) at least we had OpenCL to fall back on. But for now theres not even that anymore. I have a few questions for you though about the lates issue: 1. Will Adobe finally make an official statement that can be easily found and accessed about this current issue namely  the current incompatibilty of their video apps with the new Macbook Pros so others will be able to find out about this issue before they make a new investment in hardware and possibly software (eg in case they are not already a CC customer) only to find out it does not work after spending thousands of dollars / euro ? 2. Why would Adobe offer Metal support in their video apps when apparently everybody who tried it (including me) as an alternative says its not working either , and not only on new Macbooks. I dont understand that. 3. Why doesnt Adobe test their software with new hardware straight away after its released by Apple ? It would have taken a maximum of a few hours to come across this weeks ago and could have saved a lot of time getting this fix you are talking about. Why are we the ones who have to report back to you before anyone noticed anything over at Adobe ? 4. And why on earth would Adobe only get wind of the issue weeks after many many Mac/tech sites have already reported about this issue ? Why would noone have a clou about this when I called Adobe support still by the end of December ? I think I can speak for most of us here that we are very interessted to understand what we are dealing with here and how cases like these are handled by Adobe in the present and future. Its about trust that many of us have a hard time with when situations are handled as sloppy as they have been so far. Thank you ... View more

BTW my postings are being moderated now.  someone at Adobe may not like my contributions to this thread it seems.... However, you are right Sam, that answer is some sort of bad joke. Also, when I received the support answer they also marked it as "case closed" ... View more

Of course not. Very generic answer "For now we suggest installing a previous version". Isn't it great when getting advice from Adobe experts? ... View more

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 ... View more

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. ... View more

Of course RameezKhan, my case number is 0188515963. The support request has been placed with your support agent Mathias Kunzendorf on Dec 28th ... View more

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 ... View more

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 ... View more

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 ... View more

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 ? ... View more

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 ... View more

Lets hope that winter brake doesnt take to long Rameez, because it seems Adobe has been on a break since hese new machines came out weeks ago. It really baffles me why a company such as Adobe wont properly test their software , but rather lets us do the beta testing .In case of such a huge (hopefully temporary ) incompatibitlty Adobe should then warn users about issues like this. Adobe surely knows most of us arent using their software as a hobby, but to make a living.  As for myself I specifically bought the new Macbook to use with Premiere, AE and Media Encoder. Since the new Macbooks came out I counted at least a dozen bigger sites that reported about these graphics problems with Adobe software on the new Macbooks with Touch bar at the end of November. Why hasnt Adobe done anything since ? Why after contacting the German support 8 days ago am I even told "We havent heard about this yet !" after you claim here that "A fix is on the way" ? Whats wrong with Adobes internal and external communication ? Heres some examples of the bigger sites that reportet about this issue at the end of November already: https://9to5mac.com/2016/11/25/2016-macbook-pro-gpu-problems-glitches/ Users Find Some New MacBook Pros Suffer From Major Graphics Issues - Mac Rumors BTW, Adobe has never been able to fully fix the CUDA problems on previous Macbooks when using Cuda excelleration caused a lot glitches and unstable system performance also. Lets hope this wont become the same scenario. ... View more

OpenCL wont make a big difference Andy. At least thats what most users with this issue seem to experience. Hardly anyone even uses Metal. Under OpenCL it may work for 20 Min or an hour or two, but suddenly out of the blue you will see something like this: MACBOOK PRO LATE 2016 - Graphic Card Issue? - YouTube 2016 MacPro AE Crashing - YouTube The only option working would be Sofware Render only which is not really an option in a professional workspace. ... View more

hi erlend, thats right, people who report that they did exchange their new macbook pros because of this issue say it has not helped. according to them the issue keeps coming up on their exchanged Macbook Pros as well. also. from what Im reading and experiencing myself with my new machine the issue is clearly linked to Adobe software only. no other apps except for adobe's seem to trigger this major issue. Users also report Final Cut X works flawless on the new Macbook Pros. Adobe would need to put out an official statement saying "Some Adobe apps are currently NOT compatible with Macbook Pro 2016" . But it seems they rather want to keep attention to this issue to a minimum as always when something like this is happening ... View more

Theres a the thread (in the link below )which has an adobe staff member responding to the latest issues with the new Macbook Pros, apparently "Adobe is working with Apple on a fix", at least thats what the Adobe staff member claims . Everybody please voice your issues with Adobe software and the latest macbook pros under the following thread as loud as you can. Its time to end this unbearable situation : : Graphics Issue on my macbook pro 2016 when using premiere ... View more

Rameez Im glad Ive finally found this thread since I contacted Adobe Support in Germany today to report the problem. Their answer seriously was: "We have not heard about this and I can't find anything about it in our system" .... I then asked the support guy to google "MacBook Pro 2016 Adobe Premiere Pro graphic issues" since there are just about a couple of hundred entries about the issue since the Macbook came out . Ive received my new MacBook Pro 15' with Radeon 460 a week ago. Ive Installed almost nothing except for Adobe CC to keep the system as clean as possible for video editing which is my professional business. Whilst my first edit Adobe Premiere CC 2017 crashed 4 times with the exace graphic glitch error described by the other users above. Mostly suddenly whilst encoding but also whilst editing a graphic glitch happens which leaves the screen in a huge green or red pattern just like in this youtube video: 2016 MacPro AE Crashing - YouTube It crashed the machine completely. Both Mac OS Sierra and CC are on their latest versions (OS Sierra 12.12.2 and Premiere CC 2017 at  11.0.1 (Built 6). This whole issue reminds me of the mess with Adobe software and Cuda drivers on my late 2013 MacBook Pro . There are very long threads about graphic glitches, crashes etc. on the Adobe forums as well.  The issue went on forever, it was never fully resolved. I truly hope Adobe will fix this latest issue on the latest Macbook pro machines as soon as possible .  It's truly getting ridiculous at this point. ... View more