![]() ![]() Time for a quick lesson, OpenCL is a primary open source API and you want CUDA to be the sole provider of this tech and somehow blame it on MAC? hmmmīTW nVidia Cuda works perfectly fine in our office, an in fact we can run Cuda and OpenCL at one on the same program (ever since nVidia decided to embrace OpenCL). Which is seen strongly in programs like OpenCL performance in high profile movie studios and VFX like in FCPX, AVID and in house toolsĬontrolled and strong-armend their proprietary tech for the first 4 years until they noticed the competition embracing and out performaning CUDA at the Hollywood filming VFX level and with FCPX and AVID. It's generally provides superior acceleration performance then Cuda could provide back when nVidia was shunning OpenCL in favour of Cuda in most regards. Made for everyone, Not locked down to a particular platform, AMD video cards, OSX, Linux, Unix, Solaris, IBM, FreeBSD, Intel, AMD, Samsung and maybe even BeOS! So you are saying that it is the the users of OSX products (or possibly Apple) are the ones making it hard by embracing OpenCL? I'm bored in bed and just had to sign-up to these forums as after reading Vladdies thought process on this thread. ![]() I have been running in NVIDIA OpenCL GPU acceleration. I completely erased my drive, have a new installation of OS X 10.10.4 and I do have this problem now. However, I have updated in order to troubleshoot items a bit better. If it were me, I'd be running Premiere Pro CC 2014.2 on OS X 10.8.5 with NVIDIA CUDA enabled.
0 Comments
Leave a Reply. |