Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

New Mac Pro

the best thing would be to take this to the apple boards or tech support....they usually don't acknowledge anything but behind the scenes will take it seriously....
 
a positive note: downloaded matt's dragon clip today and it plays full at a 100% in rcx....which is faster then my epic files....pretty crazy, especially considering rcx only uses one D700...
 
paul schefz said:
the best thing would be to take this to the apple boards or tech support....they usually don't acknowledge anything but behind the scenes will take it seriously....
Click to expand...

I submitted bug reports to apple all yesterday...mostly while I screamed at my computer.
 
I filled out bug reports too. We also have to consider that a huge part of the 10.9.3 update was to be fixes and upgrades to video drivers and OpenCL / OpenGL. Some of the "bugs" we're encountering with Resolve or whatever could be due to a bug on their end that just happened to work before and now don't since Apple "fixed" something. We see that a lot. Developers may identify a problem within and OS or driver set and instead of waiting for a proper fix, they implement their feature anyway and use some work-around or alternate and improper method, which then breaks when the aforementioned fix comes along.

I'm not trying to be an Apple apologist, but the door swings both ways on these things. RC-X and several of my other OpenGL / OpenCL apps are working great. Where I'm faulting Apple on this one is that there are big changes in this release of 10.9.3 that were not present in the previous beta seeds. Something got goofed up somewhere. Even for developers who are on the ball with the betas, this release build had to catch them off guard.
 
I really don't care who carries the blame, as long as it gets fixed. Premiere seems to function 'okay' with open CL off, but I'm basically not using a KEY hardware component of my machine now to enable that fix.
 
I was doing well with the first three new Mac Pro installs here.

Now the fourth and fifth are driving me insane with stupid "System error...kext" crap coming up constantly.

Then the perm issues which doesn't make sense since I haven't even put the computer into the wild yet :P

One culprit was the RED ROCKET kext error (thanks RED for the fix).

This occured twice on one system which also has a slew of third-party install kext errors such as Avid, Pace, Graphics, etc....

The installs from machine 1 to present have been the same.

Just 10.9.2 here
 
I am considering purchasing a nMp mainly to use the OpenCL features of Premiere and Resolve but not sure what version of Mavericks it will ship with.
Does the OpenCL feature in Premiere and Resolve in general work fine if youre running 10.9.2 or are you guys having problems with Mavericks period?
 
John Desay said:
I am considering purchasing a nMp mainly to use the OpenCL features of Premiere and Resolve but not sure what version of Mavericks it will ship with.
Does the OpenCL feature in Premiere and Resolve in general work fine if youre running 10.9.2 or are you guys having problems with Mavericks period?
Click to expand...
the nmp is great and it will ship with the latest os version when you buy it....10.9.2 was fine for me, all 10.9.3 betas were ok as well (i needed the 4k support, that is why i was on the betas) this final release version seems wonky.....i am sure this will be figured out very soon....

i agree with jeff that it is hard to point fingers because there are so many variables these days....and we usually never really know because everybody blames everybody else.....
so everybody is guilty and no one is...
the nmp is definitely not at fault
 
Mavericks crashing into the rocks?

Mavericks crashing into the rocks?

The relationship between the OS and all the resources it controls has traditionally been about 3rd party developers coding to the environment. As Jeff noted, this often leads to "workarounds" in 3rd party drivers that don't adhere precisely to OS conventions - but get the product working. Over the years this has led to patches on top of patches on…

Apple decided that the vagaries of this method (or lack of same) was not in the best interest of the user experience they wanted to promote. With Mavericks they have attempted to bring as many 3rd party drivers as possible right into the OS - peripherals like printers, displays, etc would use resident drivers in the OS rather than users constantly downloading the latest drivers from the 3rd parties as the environment evolved through OS upgrades. In theory they have the right idea, all the 3rd party drivers would be vetted by Apple and users would simply update the OS regularly rather than chasing all over the net for 3rd party drivers.

This laudable goal was never going to be easy to accomplish, but IMO a little short term pain was a fair trade off for less failure points in the future. Based on 25 years of experience with the MacOS it felt like we were far enough downstream from the Mavericks debut to expect 10.9.3 to be the solid release we typically get a few months after a big jump. Evidently NOT. Sure hope this gets dealt with quickly, I really don't want to go Windows but if both platforms bring similar amounts of IT overhead to the party I might as well get the lower cost headache…

Cheers - #19
 
Blair S. Paulsen said:
Based on 25 years of experience with the MacOS it felt like we were far enough downstream from the Mavericks debut to expect 10.9.3 to be the solid release we typically get a few months after a big jump. Evidently NOT. Sure hope this gets dealt with quickly, I really don't want to go Windows but if both platforms bring similar amounts of IT overhead to the party I might as well get the lower cost headache…
Click to expand...

Blair nailed it in his post. This is the first time I've been really burnt my an update. And what a week ago felt like a badass and fast machine has turned into a glitchy garbage can. I Hope this gets resolved and fast.
 
update from my side...after a couple of days with it now today was smooth sailing...all in fcpx...purring along, no issues at all....did not touch resolve (or adobe) so no problem.....
did notice that one fcpx effect really slowed things to a crawl....i am wondering if the Open GL "fixes" are the problem....
on the other j\hand it looks like 10.9.3 allocated more vram with 10.9.3 and mb airs and retinas? maybe something to help 4k on those machines? i don't really care but when i had all these problems with resolve (and initially with fcpx as well) it seemed like there was something going on with my vram and ram (in general) management....anyway...
on of the reasons to get the nmp for me was that i am betting on fcpx....and i am sure if anything apple will make sure it is tuned and tweaked to the max...
 
Unfortunately GPU acceleration technology and Cloud based distribution with update on demand has changed the board. Updates that could cycle in months or long time frames must now be deployed in weeks or a month. Changes to 1 application that has a strong presence in the industry require changes to other applications, drivers, and even OS elements. Apple's philosophy model does not work well with update on demand. The philosophy is actually counter productive to it since communication between R&D's of the partners involved is not organized or developed to handle these variables in these short time frames. This means issues make it to the end user well before testing, responsibility, and resolution can be implemented. Expect this to continue and possibly get more volatile as GPU acceleration evolution is pushed even faster. New frontiers equal new challenges and new pains far before the new gains are made. Microsoft's model is far more adaptable to this because the partners involved can dynamically adjust/update without waiting on Microsoft R&D to coordinate. Linux's module based system that is basically building blocks on demand is probably most suited for this but the development costs and time are still too high.
 
Last edited:
It's generally a good idea to not update the OS until Blackmagic Design says Resolve is compatible with that new version of the OS. BMD almost always releases a new update for Resolve within a few weeks of the OS update to make it fully compatible with the new OS update. If you call BMD, they will tell you that they don't support 10.9.3 yet and to go back to 10.9.2. Another option, if you've already updated and are having an issue is to install the combo update (if you updated via software update or downloaded the delta update), or even reinstalling the combo update could fix things that broke from the first update sometimes.
 
Anyone experiencing the OpenCL issues on the new mac pro with 10.9.3, I have a tentative working solution. Premiere, or rather adobe cc requires the NVIDIA Cuda Drivers to be installed on the machine, even though the D700's aren't obviously OpenGL. That said I just manually updated the Cuda Drivers...and things SEEM to be back to being solid.

Anyone with this same issue want to give it a go and see if they too are seeing better stability?

http://www.nvidia.com/object/cuda-mac-driver.html
 
New Mac pro = overpriced tool that does not perfrom well in the real world. So glad I did not buy one. If I wanted headaches like this I would buy more PCs.

NVidia GPUs generally have no issues. I now have a system that runs about 4X as fast in Resolve/Adobe as the best NMP and cost about 60% of the nMP price. 12 core Old Mac Pro, 2 Titans in Cubix expander. My system will only improve with time as I add more cards - nMP is stuck being non-upgradeable joke on pro users.

I fail to understand why anyone would want a new Mac Pro when other Mac option on eBay are so much cheaper and faster. If you want "design" on your desk support a local artist and buy a real sculpture - do not support Apple's fumble.
 
Nvidia updates their Open CL version with their drivers along with Open GL. Likely that is why installing the Nvidia update fixes the Open CL memory management Adobe is using.
 
Isaac Marchionna said:
Anyone experiencing the OpenCL issues on the new mac pro with 10.9.3, I have a tentative working solution. Premiere, or rather adobe cc requires the NVIDIA Cuda Drivers to be installed on the machine, even though the D700's aren't obviously OpenGL. That said I just manually updated the Cuda Drivers...and things SEEM to be back to being solid.

Anyone with this same issue want to give it a go and see if they too are seeing better stability?

http://www.nvidia.com/object/cuda-mac-driver.html
Click to expand...


Hilarious that one can fix AMD OpenCL issues by installing nVidia drivers.
 
Open CL is standardized and implemented by the application designer. Potentially either Graphics driver can update changes to the OS for the Open CL used by that application.
 
You must log in or register to reply here.
Back
Top