[Alex Cameron]

Hey Guys

Reed I believe that guys at AMD, Apple and Adobe have all come out saying it shouldn’t be anything to do with bad VRAM and that it was a software issue rather than hardware. However, I don’t want to rule it out completely and will be very interested to learn if taking it in solves your issues. Please keep us posted.

This does however highlight my major problem with the fact that there does to seem to be a definitive answer here from any of the parties involved. None of them have really come out and accepted that there is an issue and offered any reassurance that it will be fixed or even when. That is the most frustrating part as it just feels like this is a phantom problem that maybe I am imagining or something and finding a solution to the problem looks about as unlikely as me becoming PM!

I’d really love Apple, AMD and Adobe to come together here and give us all one place to keep up to date with information regarding this issue and to quash any rumours of fixes that aren’t working etc.

Incidentally, 10.9.5 was released over the weekend and I wonder if anyone has tried this yet and what the outcome is? Any one who has please do jump in!

[Alex Cameron]

Hey Reed

Great work on the troubleshooting and it’s a shame you can’t continue as your trial has expired. Totally understand not being able to justify purchase until the platform is working correctly.

I’m still experiencing issues with playback and on rendering/encoding work out via either Premiere directly or via Adobe Media Encoder which itself is buggy as hell (continually freezing when starting a queue of premiere sequences or multiple outputs to one sequence).

Haven’t had much chance to troubleshoot or try reinstalling systems as I am so busy with work and just currently making do! Luckily my older MacPro2012 with Nvidia GTX680 in it is capable of handling the encoding tasks but it means that I have two machines tied up and have to keep moving machines which is annoying.

Likewise I feel this issue must be affecting a lot of professional editors working in Premiere Pro CC 2014 on the new MacPro with Mavericks 10.9.3 installed. I can accept that bugs occur from time to time and am prepared to be patient but now it is getting to the point where I feel like both Apple (particularly Apple) Adobe or AMD don’t seem to care as it isn’t affecting a large enough volume of people for them to worry about it. If this were resolved then I would be a REALLY happy camper and I’d love to hear more from the companies involved as to the following:

1) an acknowledgement that there still is an issue
2) reassurance that they are working on a fix
3 When we might expect the fix

I know that OS 10.10 Yosemite is coming soon as well as a new version of Premiere Pro too(which looks great by the way with a lot of organisational features – I’m quite a tidy editor so this really gets me going!) 😉 Hopefully one of these updates will quash the bug finally. Worried though as I hope that Apple doesn’t break something else with the new OS.

For me this still is a huge problem and costing me a lot of valuable time in looking into it. If you are reading this Adobe, Apple or anyone else who can help, we are all really keen to be kept in the loop about any information relating to this issue that you are able to share. Reassurance that there is a fix coming would be amazing.

Cheers

[Alex Cameron]

Hi Andy

I have and still having the same issues! Others are too.

So odd and really frustrating as no one at either Apple or Adobe is prepared to help or listen.

[Alex Cameron]

Anyone heard any more about this issue?

So frustrating!

Switching away from Adobe to FCPX which isn’t having these issues!

[Alex Cameron]

Just want to add here that I am finding huge issues with 10.9.3 and 10.9.4 on the new Mac Pro 2013 with dual AMD d700s.

I believe the issue is something to do with the GPUs and how they work in sync (or not) with OSX and Adobe Premiere Pro CC. It is a seriously frustrating issue and one that is seriously hampering my workflow.

I loathe the suggestion from Adobe “switch it to software only mode” which they then follow with “sorry for the inconvenience”! Sorry guys, I didn’t invest in a state of the art system which cost in excess of £5000 along with software that I licence from you for £50 a month just to be told it can’t work they way it is clearly stated to work. I’m sorry but I refuse to have to live with the software only mode and lose the seriously powerful GPU acceleration. You need to resolve this or reduce peoples licences until the issue is resolved. Also AMD, Apple and Adobe need to fix the issue together. I bought FCPX the other day and it’s great and it is what others will start to do if Adobe don’t pull out their fingers and sort this issue.

I appreciate it isn’t just Adobe’s fault but it is affecting your product so it should be high on your agenda of things to resolve. I am more than willing to help supply any information Adobe require in order to assist resolving the problem.

Hoping for a fix soon.

BTW, have any guys that are Apple developers tried Yosemite yet? Are the issues occurring on this OS too?

Cheers

Alex Cameron
Camera On Films