10.6.5 & Cuda
Good day guys.
Looks like 10.6.5 has come out.
I currently have Nivida Cuda v3.1.17 installed
But it seems with the update it tells me there is an update required.
Is nivida slow to the upgrade?
Will this cause issues?
should i uninstall it if so whats the best way?
I have a Quadro FX 4800 card and keep the drivers updated via the System Prefs (currently at 3.2.17).
However, I'm having a mysterious problem with starting up the Mac in the morning when it's cold. I get the spinning dial and then it stops more often than not. I have to force quit from the front of the Mac, then restart. At that point it always (100% reliably) starts up the second time around. I've shuffled RAM in and out, without fixing it, so I don't think it's the RAM.
The next thing I thought I'd try is turning off the CUDA driver. This all started in August when Apple did a system update and the CUDA driver was out-dated, so there's a chance it's the card or the driver.
Does anyone know how I can de-install the CUDA driver, or disable it temporarily?
Or if anyone has any other ideas about what it could be? It's getting tiresome!
Similar Messages
-
Mercury CUDA not enabling when using NVIDIA GeForce GTX 285 on Apple Mac Pro after Mavericks install
Been using the same setup since CS5 with the Mercury CUDA running perfectly. After recent upgrade of OS X to 10.9 Mercury CUDA is no longer available and only lets me run with the OpenGL or software options. Im using a NVIDIA GeForce GTX 285 for apple computers. Here are the results for the GPUSniffer program in the latest Premiere Pro 7.1.0 files. The LAST line make me chucle because it the first on the list of supported card in the "cuda_supported_cards.txt" file. Anybody else seen this?
--- OpenGL Info ---
Vendor: NVIDIA Corporation
Renderer: NVIDIA GeForce GTX 285 OpenGL Engine
OpenGL Version: 2.1 NVIDIA-8.18.27 310.40.05f01
GLSL Version: 1.20
Monitors: 1
Monitor 0 properties -
Size: (0, 0, 1920, 1080)
Max texture size: 8192
Supports non-power of two: 1
Shaders 444: 1
Shaders 422: 1
Shaders 420: 1
--- GPU Computation Info ---
Found 1 devices supporting GPU computation.
OpenCL Device 0 -
Name: GeForce GTX 285
Vendor: NVIDIA (Apple platform)
Capability: 1.2
Driver: 1
Total Video Memory: 1024MB
* Not enabled by default because it did not match the named list of cards.found a link from a couple of days ago on a creative cow forum post one of the poster saying they are from adobe stating this
Re: Mercury Playback Engine MacPro
by Peter Garaway on Nov 12, 2013 at 9:49:16 am
Hi Wendell,
Sorry for the inconvenience. NVIDIA is currently working on drivers that support CUDA on Mavericks 10.9 with some of the older NVIDIA cards such as the GTX 285 and the Quadro 4800.
For others interested, the Quadro 4000, K5000 and GTX 680 ect... work with CUDA in 10.9.
Best,
Peter Garaway
Adobe
Premiere Pro
I have latest CUDA drivers, so i guess i am just waiting till a proper update that have the fixes to support my card. -
Apple replaced the logic board, wiped the computer, did a fresh instal of the OS, and also a fresh instal of all the programs during the beginning of 2015. The GeekBench scores are the highest of any of the similar computers (at least on the day of my testing). But here's what's happening. The Macbook Pro Retina has a GeForce GT 650m with Cuda Technology and it can't handle editing in Premiere Pro with Cuda Acceleration turned on. Open CL, a second form of graphic acceleration on the Macbook Pro, appears to be functioning properly.
At the Apple Store on 1-10-2015, I was told that since the logic board and the graphic cards have been replaced that there is nothing they can do and they recommend contacting Corporate. This comes after they told me to buy a new logic board and that that would solve the problem. This comes after Apple did not listen, for over a month, about the possibility that they didn't properly build a professional notebook computer.
The computer displays a black program monitor screen, at random times, when the user edits footage with Cuda Acceleration enabled. It used to lead to an entire system crash and/or a Premiere Pro crash before the operating system was completely re-installed. My solution, since I bought the computer, was to edit in Open CL... However, I've come to learn that there is a major difference in performance between Open CL and Cuda Acceleration.
For the Macbook Pro Retina, Adobe Media Encoder render times are about 20% faster with Cuda Acceleration than Open CL. The 2013 Macbook Pro Retina appears to be able to handle Cuda Acceleration in Media Encoder, but I have had a number of issues leading to program crashes on every project before the new logic board and operating system were installed. For over a year and a half, I actually never used Cuda Acceleration. Having sent every crash report and user data to Apple over that time, I truly expected an update of some sorts and it never came.
FYI: The latest Macbook Pro Retina uses the GeForce GT 750m... This is essentially the same graphic card that performs about 10 - 20% faster due to a new "boost mode." More importantly, it actually has the exact same number of Cuda cores. Having the same number of Cuda Cores means that the Cuda Acceleration is essentially the same when exporting or viewing video. To prove a point to Apple that their 2013 Macbook Pro Retina isn't functioning properly, I bought the latest computer with the 2.5 i7, 16gb Ram, 512gb SSD and I can honestly say that the 2014 model works perfectly fine with Cuda Acceleration turned on while editing in Premiere. I can also say that a proper render test proved the 2013 and 2014 model to be the exact same.
I'm new to this whole pay $2700 for a computer that your manufacturer didn't / can't test properly, so I will be contacting Apple and speaking with Senior Advisors, their Customer Support division, and will soon speak with their Corporate branch. I'm confident that the Early 2013 Macbook Pro Retina with a 2.7 i7 16gb Ram and a 512 SSD is nearly the same at rendering video and editing video, provided the Cuda Acceleration works, as their latest 2014 Macbook Pro Retina with the 2.5 i7 processor 16gb Ram, and a 512 SSD. It's truly a great computer and a great build, minus their current inability to properly test / diagnose their computer.
Knowing that the latest graphic card in the Macbook Pro lineup is essentially the same model, I feel that Apple is not directly looking into the viability and life span of their current Macbook Pro Retina product line. They can't test for performance issues relating to their graphic cards, so why consider buying from them when the end user is actually in a position to experience up to a 20% decrease in certain professional programs.
For future reference, I'd strongly urge other individuals to avoid purchasing Apple products if they offer Cuda Technology. In my opinion, Apple is an Open CL organization, at best, who is not responsibly manufacturing / producing computers that fit their organization's strengths. For a fact, they can't test their Cuda Technology and won't even attempt to address Cuda Acceleration errors for Apple owners (01-11-2015). I say this having walked out of the Apple Store on 1-10-2015 with virtually no support other than to contact Corporate.Looks like a RAM issue.
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x000000000000000000000000000000000000
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x000000000000000000000000000000000000 -
CUDA always works great on timeline playback but sometimes not at all on Export+MRQ enabled?
Hi,
I have Premiere CS 5.5.2 on Mac with Lion 10.7.2. System is Q6600, 8 GB DDR2, graphics is Nvidia GTX 560, 1 GB DDR5, 256 bit. AVCHD 1080i material exporting to PAL DV.
CUDA works great on timeline playback but SOMETIMES (3rd time in 3 months) when I export with MRQ enabled it simply does not kick in at all. Exporting times are high as exporting without CUDA, the graphics card's coolers don't speed up like they do when I play the timeline or when exporting with CUDA was working.
If I cancel the export CUDA works just like before when I play the timeline. If I go to export, again, it does not work. Very high export times. I click cancel again and it works fine playing the timeline, the coolers on the graphics card go slightly up as to indicate that th GPU is beeing used, everything is just fine. MRQ is always enabled and the project preferences are set to use CUDA.
Twice I solved this problem by closing EyeTV since I thought that this was the issue because maybe this program was using somehow the video acceleration and no more room was left for CUDA, but last time even this did not work. I closed EyeTV, restarted Premiere but nothing. Same problem, CUDA worked just fine playing the timeline WITH EyeTV running but not when exporting with MRQ. I had to restart the computer to get CUDA to work on export with MRQ enabled.
With CUDA: 30 minutes of AVCHD 1080i footage + logo applied and export with MRQ = 15 minutes exporting time to PAL DV.
Without CUDA or when CUDA does not work on export: 3 hours exportinng time to PAL DV.
For those who don't know EyeTV is a tv tuner application and I use it on DVB-C to monitor 2 national TV channels that are on the same digital multiplex. I opened up even 6 channels at the same time on the same multiplex and CUDA still worked fine on the timeline.
MRQ is always checked, always ON.
All I want to know if there is anyone else with this issue, wheter on Windows or Mac, their observations and what they tried to solve this issue.
Thanks a lot,
Best regards,
Dj LyonTaken from here: http://blogs.adobe.com/premiereprotraining/2010/10/scaling-in-premiere-pro-cs5.html
"Maximum Render Quality can still make a difference with CUDA-accelerated exports for any parts of the render that are processed on the CPU." -
"Maximum Render Quality" Better to turn it OFF when using CUDA MPE?
http://crookedpathfilms.com/blog/201...port-settings/
"IMPORTANT NOTE ABOUT RENDERING TIME: Make sure you do not select “Use Maximum Render Quality” if you are utilizing the accelerated GPU graphics (Mercury Playback Engine). This will not improve your video and will only slow down the rendering speed by as much as 4 times!"
http://blogs.adobe.com/premiereprotr...e-pro-cs5.html
"For export, scaling with CUDA is always at maximum quality, regardless of quality settings. (This only applies to scaling done on the GPU.) Maximum Render Quality can still make a difference with CUDA-accelerated exports for any parts of the render that are processed on the CPU...
When rendering is done on the CPU with Maximum Render Quality enabled, processing is done in a linear color space (i.e., gamma = 1.0) at 32 bits per channel (bpc), which results in more realistic results, finer gradations in color, and better results for midtones. CUDA-accelerated processing is always performed in a 32-bpc linear color space. To have results match between CPU rendering and GPU rendering, enable Maximum Render Quality."
Here is what I got out of after reading those two sites:
I should turn it off for it's always ON (when CUDA MPE is used) regardless I check or uncheck it.Turning it ON only offloads the calculation to CPU (instead of GPU) hence slowing down the previewing and encoding performance.
So I guess I should have Maximum Render Quality setting turned OFF in both of squence settings and export settings.
However, David Knarr of Studio 1 Productions suggest otherwise:
http://www.studio1productions.com/Articles/PremiereCS5.htm
"When you startup Adobe Premiere CS5 and you don't have a certified video card (or one that is unlocked) the Mercury Playback Engine is in software rendering mode and by default the Maximum Render Quality mode (or MRQ) is to OFF.
(Maximum Render Quality mode will maximize the quality of motion in rendered clips and sequences. So when you select this option, the video will often render moving objects more sharply. Maximum Render Quality also maintains sharp detail when scaling from large formats to smaller formats, or from high-definition to standard-definition formats. For the highest quality exports you should always use the Maximum Render Quality mode.)
When you unlock Adobe Premiere CS5 so the Mercury Playback Engine can use almost any newer NVidia card (or if you are using a "certified" NVidia graphics card), the Mercury Playback Engine will be in the hardware rendering mode and the Maximum Render Quality mode will be turned ON.
Since the software mode is not set to maximum render quality, it can sometime render faster than the hardware render, but a a loss in qualitly. If you set the software to maximum render quality you will see that it is very, very slow compared to the hardware render.
Here is how to set the Maximum Render Quality.
1) Open up Premiere CS5
2) Click on Sequence at the top of the screen
3) Then select Sequence Settings
4) At the bottom of the window select Maximum Render Quality and click Okay
It is always best to be using the Maximum Render Quality mode,"
Now, I'm lost.Okay, I am loosing it..... You are correct.
I am not sure what I was remembering, I could have sworn that when I loaded Premiere CS5 for the first time before I unlocked the video card, the Maximum Render Quality mode was NOT checked. Then when I unlocked the video card, the Maximum Render Quality mode was check to ON and I didn't set it to be On.
I just when back and uninstalled Premiere and re-installed it, to see what was going on and I was totally wrong.
Sorry for the mistake and I will be updating the article on my website in the next 15 min.
Also, I have written a small program to do the unlock automatically. The program is free and it works with the cards listed under the Automatic Mode.
If your video card isn't listen, just let me know what your card is and what you typed into the cuda cards file and I will add it to the program.
David Knarr
Studio 1 Productions -
How to tell if CUDA is enabled?
So, I managed to successfully install the latest CUDA drivers for my newly installed Gigabyte GeForce GTX 760 GPU.
I am not sure how to check they they are working, but the CUDA option appears in my System Preferences, so I'm assuming they do for my system in general, but I see that there are many tutorials on enabling them specifically for Premiere and After Effects. There are, however no tutorials for anything above CS6. I have CC 2014.
I am not sure whether Premiere is using my GPU for it's Mercury Playback Engine or not. There is an option under Project Preferences to choose the rendering: "Mercury Playback Engine GPU Acceleration (CUDA)" acceleration is there, and it's not greyed out and I have selected it, but how can I tell if it is using it. Also, can anyone tell me how to set this as a permanent preference in Premiere? Not just for this specific project.Once selected it will work. It should come up selected for any future projects.
-
Final cut pro quit unexpectedly while using the CUDA plug-in?
Hello,
FCP 7 quits on Quicktime conversion export every single time.
Just to give some information as to how this issue started, we recently had to send our Mac early 2009 OSX 10.8.5 to get repaired because of permissions issues with the start-up drive. We had been running 10.8.5 and Final Cut Pro 7.0.3 for a while without any major issues. We also have a 3rd party graphics card installed, the Sapphire HD 7950 for mac which has been running for about six months and still seems to operate correctly. As part of the repair the Apple certified shop re-installed our OSX.
After they re-installed our OS, I ran Final Cut Pro 7 and realized that I was unable to export using Quicktime Conversion. Every time I try to export using Quicktime Conversion, Final Cut Pro instantly crashes saying "Final Cut Pro Quit Unexpectedly while using the CUDA plug-in". I asked Sapphire/AMD Radeon support what the problem was and they said this is a Final cut pro problem and not related to their card. Their response was "CUDA isn't supported by AMD hardware in MacOSX. My best guess is that either an option was turned on in Final Cut Pro to use CUDA, or the program is doing some sort of detection (possibly on installed NVIDIA Drivers). Without the NVIDIA hardware, the drivers would be running and hence the active but unsupported CUDA would fail."
Below is the log from the error that happens when I try to export using quicktime conversion. Any help would be greatly appreciated. Thank you.
Process: Final Cut Pro [17868]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCutPro
Version: 7.0.3 (7.0.3)
Build Info: FCPApp-1008261348~8
Code Type: X86 (Native)
Parent Process: launchd [195]
User ID: 503
PlugIn Path: /Library/FrameWorks/CUDA.framework/CUDA
PlugIn Identifier: com.nvidia.CUDA
PlugIn Version: 5.5.47 (5.5.47)
Date/Time: 2014-04-08 15:39:14.289 -0500
OS Version: Mac OS X 10.8.5 (12F45)
Report Version: 10
Interval Since Last Report: 100749 sec
Crashes Since Last Report: 12
Per-App Interval Since Last Report: 104765 sec
Per-App Crashes Since Last Report: 5
Anonymous UUID: A7DB7158-63B1-6A05-6194-B48755ED702E
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
VM Regions Near 0:
--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
__TEXT 0000000000001000-0000000000871000 [ 8640K] r-x/rwx SM=COW /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Application Specific Information:
/Library/FrameWorks/CUDA.framework/CUDA
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x90c99c12 CFStringCompare + 18
1 com.nvidia.CUDA 0x31d02f13 GetNVDADriverModelString + 371
2 com.nvidia.CUDA 0x31d067f0 cuda_driver_initializer + 112
3 dyld 0x8fe9bcda ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 230
4 dyld 0x8fe9bfde ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 64
5 dyld 0x8fe98268 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 356
6 dyld 0x8fe980ba ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 62
7 dyld 0x8fe8ce0b dyld::runInitializers(ImageLoader*) + 88
8 dyld 0x8fe92605 dlopen + 718
9 libdyld.dylib 0x91d5adbe dlopen + 68
10 com.apple.CoreFoundation 0x90d13c42 _CFBundleDlfcnLoadFramework + 210
11 com.apple.CoreFoundation 0x90cd9196 _CFBundleLoadExecutableAndReturnError + 822
12 com.apple.CoreFoundation 0x90cd8de6 CFBundleGetFunctionPointerForName + 70
13 com.apple.carbonframeworktemplate 0x6f1b7161 SMCudaInfo::SMCudaInfo() + 325
14 com.apple.carbonframeworktemplate 0x6f13a2c1 CPluginCollection::LoadPlugins(char const*) + 35
15 com.apple.carbonframeworktemplate 0x6f13a55b CPluginCollection::Initialize(std::string const&, char const*) + 55
16 SMIQTExporter 0x6eacafde CAceCompressionEngine::Initialize(char const*, char const*, char const*, char const*) + 752
17 SMIQTExporter 0x6e9f9597 SMUIData::Initialize(std::string) + 135
18 SMIQTExporter 0x6e9f8e4b MaybeInitUiData() + 123
19 SMIQTExporter 0x6e9f9204 GetUserOptionsHelper(std::string&, std::string&, bool) + 36
20 SMIQTExporter 0x6e9f93a0 GetUserOptionsFromUI + 96
21 com.apple.sorensonmedia 0x0e41411c GetUserOptions(std::string&, std::string&, bool) + 176
22 com.apple.sorensonmedia 0x0e4143c1 LoadUserOptions + 151
23 com.apple.sorensonmedia 0x0e41531a SMIMovieExportGetFileNameExtension + 140
24 com.apple.CoreServices.CarbonCore 0x955b5adb callComponentStorage_44 + 25
25 com.apple.CoreServices.CarbonCore 0x955a6abf CallComponentFunctionCommonWithStorage(char**, ComponentParameters*, long (*)(), unsigned long) + 45
26 com.apple.CoreServices.CarbonCore 0x955a6aff CallComponentFunctionWithStorageProcInfo + 30
27 com.apple.sorensonmedia 0x0e414311 SMIMovieExportComponentDispatch + 137
28 com.apple.CoreServices.CarbonCore 0x95520ade CallComponent + 151
29 com.apple.CoreServices.CarbonCore 0x95520b38 CallComponentDispatch + 29
30 com.apple.QuickTime 0x9407f269 MovieExportGetFileNameExtension + 43
31 com.apple.FinalCutPro.Plugins.QTM Reader 0x23df470e LongGOPChunkWriter::receiveSample(unsigned char const*, long long, unsigned long, long long, long long, SampleDescription**, unsigned long, unsigned long, long long, bool) + 12524
32 com.apple.FinalCutPro 0x0015e371 GetQTExportCompSubType(KGMessageableRec*, unsigned long*, unsigned long*) + 79
33 com.apple.FinalCutPro 0x001620a5 pKGExportQuickTimeDialog(KGDictInt*, long*, KGFileSpec*, KGMessageableRec**, void**, KGFileSpec*, long) + 543
34 com.apple.FinalCutPro.Plugins.QTM Reader 0x23df22ae LongGOPChunkWriter::receiveSample(unsigned char const*, long long, unsigned long, long long, long long, SampleDescription**, unsigned long, unsigned long, long long, bool) + 3212
35 com.apple.FinalCutPro 0x0015093f HandleMenuCommand(long, unsigned char, unsigned char, unsigned char, KGErrorCode (*)(long, long, KGDictInt*, void*), void*) + 325
36 com.apple.FinalCutPro 0x00150b11 HandleCommand(long, unsigned char, unsigned char, unsigned char) + 263
37 com.apple.FinalCutPro 0x004149db CommandProcess(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 369
38 com.apple.HIToolbox 0x96eb99bb _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
39 com.apple.HIToolbox 0x96d41394 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343
40 com.apple.HIToolbox 0x96d40780 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
41 com.apple.HIToolbox 0x96d54655 SendEventToEventTarget + 88
42 com.apple.HIToolbox 0x96eb986a SendHICommandEvent(unsigned long, HICommand const*, unsigned long, unsigned long, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 498
43 com.apple.HIToolbox 0x96d30984 SendMenuCommandWithContextAndModifiers + 70
44 com.apple.HIToolbox 0x96d30931 SendMenuItemSelectedEvent + 268
45 com.apple.HIToolbox 0x96d307b6 FinishMenuSelection(SelectionData*, MenuResult*, MenuResult*) + 134
46 com.apple.HIToolbox 0x96f05e7e MenuSelectCore(MenuData*, Point, double, unsigned long, OpaqueMenuRef**, unsigned short*) + 623
47 com.apple.HIToolbox 0x96f06dc6 MenuSelect + 171
48 com.apple.HIToolbox 0x96ebcc16 HIMenuBar::HandleMouseEvent(OpaqueEventRef*) + 102
49 com.apple.HIToolbox 0x96ebca65 HIMenuBar::HandleEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*) + 165
50 com.apple.HIToolbox 0x96d419bf HIObject::EventHook(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 163
51 com.apple.HIToolbox 0x96eb99bb _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
52 com.apple.HIToolbox 0x96d41394 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343
53 com.apple.HIToolbox 0x96d40780 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
54 com.apple.HIToolbox 0x96d54655 SendEventToEventTarget + 88
55 com.apple.HIToolbox 0x96d745f6 ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 2188
56 com.apple.HIToolbox 0x96d4183f DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2538
57 com.apple.HIToolbox 0x96d40780 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430
58 com.apple.HIToolbox 0x96d54655 SendEventToEventTarget + 88
59 com.apple.HIToolbox 0x96eb90b7 ToolboxEventDispatcher + 82
60 com.apple.HIToolbox 0x96eb8f79 RunApplicationEventLoop + 240
61 com.apple.FinalCutPro 0x001539d1 KGMainEvent(void*) + 51
62 com.apple.FinalCutPro 0x002c1278 main + 54
63 com.apple.FinalCutPro 0x00002d5b _start + 209
64 com.apple.FinalCutPro 0x00002c89 start + 41
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x957fc9ae kevent + 10
1 libdispatch.dylib 0x97156c71 _dispatch_mgr_invoke + 993
2 libdispatch.dylib 0x971567a9 _dispatch_mgr_thread + 53
Thread 2:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x957fbbe6 __select + 10
1 com.apple.CoreFoundation 0x90cf5650 __CFSocketManager + 1632
2 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
3 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 3:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x0042911f DisplayQueue::Run() + 681
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 4:
0 libsystem_kernel.dylib 0x957fbc02 __select_nocancel + 10
1 libsystem_kernel.dylib 0x957fa67b select + 92
2 com.genarts.SapphireAE.plugins 0x27685721 DFTI_SET_VALUE_SGLVAL + 33127
3 com.genarts.SapphireAE.plugins 0x27677501 jpeg_stdio_src + 1793
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 5:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 6:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 7:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 8:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 9:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 10:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 11:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
7 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 12:
0 libsystem_kernel.dylib 0x957f98e2 mach_wait_until + 10
1 com.apple.CoreServices.CarbonCore 0x95559592 MPDelayUntil + 29
2 com.apple.CoreServices.CarbonCore 0x9556a8bd Delay + 90
3 com.redgiantsoftware.trapcode.Starglow 0x2eb634e0 RGS::SerialServer::ThreadProcess() + 54
4 com.apple.CoreServices.CarbonCore 0x95558a7b PrivateMPEntryPoint + 68
5 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
6 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 13:
0 libsystem_kernel.dylib 0x957f97ce mach_msg_trap + 10
1 libsystem_kernel.dylib 0x957f8cac mach_msg + 68
2 com.apple.CoreFoundation 0x90cabf79 __CFRunLoopServiceMachPort + 185
3 com.apple.CoreFoundation 0x90cb195f __CFRunLoopRun + 1247
4 com.apple.CoreFoundation 0x90cb101a CFRunLoopRunSpecific + 378
5 com.apple.CoreFoundation 0x90cc0ab1 CFRunLoopRun + 129
6 com.apple.DVCPROHDMuxer 0x2ecb998f AVS::DestroyAVCDeviceController(AVS::AVCDeviceController*) + 317
7 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
8 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 14:
0 libsystem_kernel.dylib 0x957f97ce mach_msg_trap + 10
1 libsystem_kernel.dylib 0x957f8cac mach_msg + 68
2 com.apple.CoreFoundation 0x90cabf79 __CFRunLoopServiceMachPort + 185
3 com.apple.CoreFoundation 0x90cb195f __CFRunLoopRun + 1247
4 com.apple.CoreFoundation 0x90cb101a CFRunLoopRunSpecific + 378
5 com.apple.CoreFoundation 0x90cb0e8b CFRunLoopRunInMode + 123
6 com.apple.CoreMediaIOServicesPrivate 0x0110eb76 MIO::DAL::RunLoop::OwnThread(void*) + 146
7 com.apple.CoreMediaIOServicesPrivate 0x0111106f CAPThread::Entry(CAPThread*) + 151
8 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
9 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 15:
0 libsystem_kernel.dylib 0x957f97ce mach_msg_trap + 10
1 libsystem_kernel.dylib 0x957f8cac mach_msg + 68
2 com.apple.CoreFoundation 0x90cabf79 __CFRunLoopServiceMachPort + 185
3 com.apple.CoreFoundation 0x90cb195f __CFRunLoopRun + 1247
4 com.apple.CoreFoundation 0x90cb101a CFRunLoopRunSpecific + 378
5 com.apple.CoreFoundation 0x90cc0ab1 CFRunLoopRun + 129
6 com.apple.qmaster.do 0x32cce460 swamp::CRAdReceiver2::ReceivingThread::runOnce() + 234
7 com.apple.AECore 0x3281a022 aecore::CThread::runThread() + 34
8 com.apple.AECore 0x32817fb9 threadProc(void*) + 17
9 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
10 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 16:
0 libsystem_kernel.dylib 0x957fbbe6 __select + 10
1 com.apple.AECore 0x3281a067 aecore::CThread::runThread() + 103
2 com.apple.AECore 0x32817fb9 threadProc(void*) + 17
3 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
4 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 17:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d09572 pthread_cond_timedwait_relative_np + 47
3 com.apple.CoreServices.CarbonCore 0x955856ad TSWaitOnConditionTimedRelative + 177
4 com.apple.CoreServices.CarbonCore 0x95585184 TSWaitOnSemaphoreCommon + 272
5 com.apple.CoreServices.CarbonCore 0x9558540d TSWaitOnSemaphoreRelative + 24
6 com.apple.QuickTimeComponents.component 0x979b823c 0x973c2000 + 6251068
7 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
8 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 18:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 19:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 20:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 21:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 22:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 23:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 24:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 25:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 26:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 27:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 28:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 29:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 30:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 31:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 32:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x97acf48e 0x973c2000 + 7394446
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 33:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 34:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 35:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 36:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 37:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 38:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 39:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 40:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10
1 libsystem_c.dylib 0x94d092e9 _pthread_cond_wait + 938
2 libsystem_c.dylib 0x94d96ae4 pthread_cond_wait + 48
3 com.genarts.SapphireAE.plugins 0x275ca7ff mp_main_thread_p_internal + 1631
4 libsystem_c.dylib 0x94d045b7 _pthread_start + 344
5 libsystem_c.dylib 0x94ceedce thread_start + 34
Thread 41:
0 libsystem_kernel.dylib 0x957fb8e2 __psynch_cvwait + 10Thank you Michael.
I was exporting a QT Movie and bringing into compressor but there was a further problem of Compressor greying out the "submit" button, so that option wasn't available when I posted.
Your solution led me in the right direction to fix my problem. The Digital Rebellion application is very good and when I ran the crash analyzer, it still said the CUDA plugin was the culprit. But when I tried looking at the available plugins, it didn't show up. I ran a search for the plugin and found that there was a folder under Library>Frameworks>CUDA.framework. I copied that folder into a folder I made on the desktop (because I didn't want to delete something that the computer needed to run) and then deleted it from the Framework folder. I knew that our third party graphics card we installed didn't support CUDA, so I thought I'd be okay risking this; I could also replace that folder from the desktop if something major happened. I restarted and then tried exporting using QT Conversion. It worked!
Next problem then was Compressor. I needed to find out why compressor's submit button was greyed out. The application seemed to work fine, the version of compressor and Q master were the same, 3.5.3, but it didn't allow me to submit anything. I ran compressor repair from the Digital Rebellion application and it didn't change things. I read up a while on why this was happening and found on a support community that had similar issues. Many people on it said this update for Pro Applications fixed their problems:
http://support.apple.com/kb/dl949
So I think, now my computer is running the same way as it was before (except for Sorenson Squeeze which I need to fix). Thanks for the help! -
Premiere CC to AME - H.264 nightmare rendering problems with CUDA on rMBP
I've been struggling for weeks trying to troubleshoot and narrow down my encoding nightmare on my own and I have finally succumbed to getting the forum's or Adobe's Help.
Problem:
Rendering a Premiere Pro CC project with via Export Media > Queue to AME in H.264 causes the encode to randomly fail on multiple projects.
I find it quite amazing that this error happens as I surely am not the only one rendering ProRes to H.264 on a new Macbook Pro!
Symptom:
Output preview starts to flicker then encoding stops randomly, preview window turns to a black screen or simply stalls while the Elapsed Time keeps rolling, PProheadless crashes in Console, encoding sometimes resumes after several minutes post the crash (but sometimes not) however the final output in such case is garbled before/after the crash. Computer is useable. All other software shutdown. Not using computer during encode. Can reproduce virtually every time.
Hardware:
Early 2013 Retina Macbook Pro
Processor 2.8 GHz Intel Core i7
Memory 16 GB 1600 MHz DDR3
Graphics NVIDIA GeForce GT 650M 1024 MB
Software:
Premiere 7.0.1 (105)
Adobe Media Encoder 7.0.1.58 (64bit)
Creative Cloud Latest Updates
Cuda 5.5.25 (latest)
GPU Driver: 8.12.47 310.40.00.05f01
OS X 10.8.4 (latest)
Project Details:
ProRes 4:2:2 or AVCHD sources
No nested sequences
Video track with image over whole sequence
Video track with text over whole sequence
Video track
Audio track
Sometimes video track with adjustment layer
Standard disolve effects between cuts
4 effects used: denoiser for audio, luma corrector and twice Fast Color Corrector
No third party plugins installed nor used
Sequence is set to Maximum Bit Depth / Max Render Quality / Linear Color
Use Previews off
Encode is set to Maximum Render Quality and always H.264 2pass VBR.
Errors in console:
8/27/13 12:38:01.144 AM PProHeadless[1389]: [CL_INVALID_OPERATION] : OpenCL Error : Failed to retrieve device information! Invalid enumerated value!
This is seen at multiple times while starting Premiere (no crash) and while starting the encodes and usually after/during the crash.
Crash report:
Process: PProHeadless [410]
Path: /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/PProHeadless.app/Contents/MacOS/PProHeadless
Identifier: PProHeadless
Version: 7.0.1 (7.0.1.105)
Code Type: X86-64 (Native)
Parent Process: dynamiclinkmanager [397]
User ID: 501
Date/Time: 2013-08-26 21:12:21.878 +0200
OS Version: Mac OS X 10.8.4 (12E55)
Report Version: 10
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGSEGV)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Full Crash report:
http://pastebin.com/a93cNVqk
Attempts to solve the issue:
Tried encoding without external montior
Tried encoding with source on internal HDD, output internal HDD, source exterbak RAID, output internal HDD
Tried encoding with AME while Premiere is open in the background and without it opened in the background
Uninstalled other software that could mess with the graphics: Colormunki, Parallels.
Software mode is fine on all attempts in AME however encoding takes 2-3x longer. On a $3000 laptop it's not really great.
Encoding directly via Export Media > Export without Queuing to Adobe Media Encoder seems to work fine. I have not tried this too many times because I need to render multiple outputs and doing it without AME means a lot of 'sitting and waiting' to click Export for the next format. This is not an option.
Tried deleting the Media Cache
Completely reinstalled OS X 10.8.4 from scratch with no other software running and tried to export. Same problem.
Performed Apple hardward test. No problems.
To Test:
I'm planning on installing Bootcamp so I can test the problem in the Windows version and I could pinpoint it to a hardware problem rather than a software problem.
Notes:
Problem happens with CUDA and Open CL modes although in Open CL mode, the whole computer tends to freeze intead of just 'stalling'.
Editing and playback inside Premiere is OK! Even encoding out of Premiere is OK directly but not useful for me as I need to render each project to 5 different H.264 formats.
I hope you guys or Adobe's Support can find a solution to this problem because I'm really stuck between a rock and a hard place.
I've submitted a bug report but their reply is not very comforting:
but their bug report says "Due to the volume of submissions we receive, responses to inquiries are generally not possible. However, we may contact you if we need clarification on your submission." Nice.Yes I considered your "solution" of just upgrading to Adobe CC but on principal I don't want to have to shell out more money to "fix" the problem. I was able to get an Adobe technician to view my screen in real time. He asked me where Prem Pro was after I opened it and my response was "precisely". The only evidence that Prem Pro is open is that there is the taskbar there with what appears to be fully functional drop down tabs but as far as the panels/workspace goes non-existent! He has "escalated" the matter I'll let you know what occurs next. I have tried using the software mode and there is no change. Like you I have wondered about a hardware proplem but I have checked via Disk Utility and there doesn't appear to be any? The CUDA issue well a) I am not sure how I would revert to previous drivers and b) when I re-installed Prem Pro from disc (that's version 6.0.0.) the only render option it gave me was Software only but that was also greyed out. Prem Pro still did not open up as it should!
I'll let you know what transpires. -
Sniffer Result Code: 3 / CUDA-Problems since Mavericks update
Hey Guys, first, thanks a lot for helping / or checking this out.
I have this problem since upgrading to Mavericks from Mountain Lion.
After upgrading I noticed there is a CUDA-Panel in my System prefs - which was new to me, having the classic onboard ATI Radeon of my MacPro.
Starting After Effects since then results in:
Last log message was: <140735271506704> <GPUManager> <2> Sniffer Result Code: 3
Generating crash log, which may take a few minutes.
then OSX tells me AE has stopped working.
System Specs:
MacBook Pro
15 Inch,
Late 2011,
AMD Radeon HD 6750M 512MB,
OSX 10.9.2 (13C64)
So it's the classic on Board graphics card and nothing NVIDIA/PC-fancy.
What I've done so far:
Installed newest CUDA-Version (even though, the system prefs plane tells me it needs an update, even when downloading the newest from NVIDIA)
Deinstalled and installed the whole CC-Suite, cleaned it, made a new admin-user, deinstalled again, installed on the news user (same problem), installed on the old one.
CUDA-drivers deinstalled from within the terminal (killing all relevant NVIDIA.kext and GeForce.bundle files), rebuild the extensions files with kext-utility.
Used disk-utility in the system and by rebooting with COMMAND+R, checked the volumen and the permissions, nothing Adobe relevant came back.
I'm kinda very stuck here...
Any help would be very welcome.
ThanksThe problem is that you installed CUDA software on a computer that has no CUDA-capable hardware. Don't do that.
You must remove the CUDA framework from your computer. See the last part of this article:
http://blogs.adobe.com/kevinmonahan/2014/03/19/avoid-installing-nvidia-cuda-drivers-on-com puters-with-amd-gpus/ -
Cuda is not working in CS6 with MacOs Mavericks, nvidia gtx 285
Will it be fixed? By whom? Apple, Adobe, Nvidia?
Hi,
I'll think it will be not fixed. But...
... take a look here
http://www.studio1productions.com/Articles/PremiereCS5.htm
http://forums.adobe.com/message/3936695#3936695
http://www.vidmuze.com/how-to-enable-gpu-cuda-in-adobe-cs6-for-mac/
Regards
Axel -
Hi,
i got a wired problem:
I am running PP 5.5 on a macpro with nvidia quadro 4000 with the latest nvidea driver for the quatro and the latest Cuda for Mac driver 4.0
But this didn`t get Cuda working in Premiere. I checked the forum and found an answer to this problem - i needed to instal Cuda driver 4.0.21, which seems to be a beta-version.
Nevertheless i now can choose Cuda to use as GPU accelerating and everything should be fine.
But after restarting the MacPro premiere says no Cuda-Board installed and checking the driver version: it`s 4.0 again.
After reinstalling the driver 4.0.21 Cuda works again.
Does anyone have a clou or the same problem?
Regards
JaskinaskaThanks for your second reply. The problem is apparently in the Firefox software, since it occurs with all Mac users even though their personal information is different. In other words, the problem follows the website.
I have been unable to find a systematic way to duplicate the problem. It initially occurred while I was changing user names and passwords. I didn't want to update some of the changes in the "saved passwords". My recollection is that I ignored the "Remember password" prompt. URL's were changed. The "Remember password" prompt no longer appeared, and did not reappear when returning the the web sign-in page.
For those web pages, there is no "Remember password" prompt. However, those pages are not included as exceptions to the "Remember passwords for sites" exceptions. Similarly, the sites do not appear in the saved passwords.
I have read the recommended reading; none seem to apply. For one of the sites, I was able to produce a pull down list for user name. However, the Shift + Delete action produced no change. -
Nvidia quadro 4000 for mac and os 10.6.8 on After Effects CS6 (11.0.2) Cuda don't work
Hi,
We bought an Nvidia Quadro 4000 for Mac for use RayTrace on After Effects CS6 (11.0.2) with our Mac Pro 5.1 on OS 10.6.8.
And the Mac lost the Cuda driver when we restart it.
We use the Nvidia driver 256.02.25f01 for Mac Os 10.6.8 and we made test on different Cuda driver (4.1.25, 4.2.10, 5.0.37 and 5.0.47).
When we install Cuda driver and start directly After Effects 11.0.2 it’s works (after effects see the GPU processor).
But when we restart the Mac and try to launch After Effects, AE doesn’t see GPU processor and ask to install Cuda driver 4.0 or later.
Do you know this problem ?
Do you have a solution ?
Thanks.
And sorry for my English !Hi All,
I'm having the exact same problem on 10.6.8 with a brand new Quadro 4000. My CUDA preferences are up to date, but After Effects CS6 is not seeing the card.
GPUSniffer gives me some really weird results, which I've included. Of particular note there is a repeated "just leaking" message, an "invalid drawable" and "Did not find any devices that support GPU computation."
Anyone have a fix for this? We just dropped a lot of money on this card so I could squeeze some more life out of this workstation (Mac Pro 4,1 dual quad 2.66 with 12GB RAM).
Last login: Fri May 31 10:20:47 on console
edit-e-room-20:~ johnlee$ /Applications/Adobe\ Premiere\ Pro\ CS6/Adobe\ Premiere\ Pro\ CS6.app/Contents/GPUSniffer.app/Contents/MacOS/GPUSniffer
--- OpenGL Info ---
2013-05-31 10:28:52.456 GPUSniffer[71708:903] *** __NSAutoreleaseNoPool(): Object 0x1046095a0 of class NSCFString autoreleased with no pool in place - just leaking
2013-05-31 10:28:52.458 GPUSniffer[71708:903] invalid drawable
Vendor: NVIDIA Corporation
Renderer: NVIDIA Quadro 4000 OpenGL Engine
OpenGL Version: 2.1 NVIDIA-1.6.37
GLSL Version: 1.20
Monitors: 2
Monitor 0 properties -
Size: (0, 0, 2560, 1600)
Max texture size: 16384
Supports non-power of two: 1
Shaders 444: 1
Shaders 422: 1
Shaders 420: 1
2013-05-31 10:28:52.467 GPUSniffer[71708:903] *** __NSAutoreleaseNoPool(): Object 0x10411d900 of class NSCFString autoreleased with no pool in place - just leaking
2013-05-31 10:28:52.467 GPUSniffer[71708:903] invalid drawable
Monitor 1 properties -
Size: (2560, 0, 1600, 1200)
Max texture size: 16384
Supports non-power of two: 1
Shaders 444: 1
Shaders 422: 1
Shaders 420: 1
--- GPU Computation Info ---
Did not find any devices that support GPU computation.
2013-05-31 10:28:52.471 GPUSniffer[71708:903] *** __NSAutoreleaseNoPool(): Object 0x1041234d0 of class NSCFArray autoreleased with no pool in place - just leaking
2013-05-31 10:28:52.471 GPUSniffer[71708:903] *** __NSAutoreleaseNoPool(): Object 0x1041236a0 of class NSCFArray autoreleased with no pool in place - just leaking
2013-05-31 10:28:52.471 GPUSniffer[71708:903] *** __NSAutoreleaseNoPool(): Object 0x10411c030 of class NSView autoreleased with no pool in place - just leaking
2013-05-31 10:28:52.471 GPUSniffer[71708:903] *** __NSAutoreleaseNoPool(): Object 0x10411c030 of class NSView autoreleased with no pool in place - just leaking
2013-05-31 10:28:52.472 GPUSniffer[71708:903] *** __NSAutoreleaseNoPool(): Object 0x10411b000 of class NSCFArray autoreleased with no pool in place - just leaking
2013-05-31 10:28:52.472 GPUSniffer[71708:903] *** __NSAutoreleaseNoPool(): Object 0x104110e00 of class NSCFArray autoreleased with no pool in place - just leaking
2013-05-31 10:28:52.472 GPUSniffer[71708:903] *** __NSAutoreleaseNoPool(): Object 0x10411ccc0 of class NSView autoreleased with no pool in place - just leaking
2013-05-31 10:28:52.473 GPUSniffer[71708:903] *** __NSAutoreleaseNoPool(): Object 0x10411ccc0 of class NSView autoreleased with no pool in place - just leaking
edit-e-room-20:~ johnlee$ -
How Do I Uninstall Cuda Driver from my Macbook Pro
Hi Guys,
I recently installed the Cuda Driver for my Mac because I was having problems playing Diablo 3, and later, working on Google Chrome.
The common problem is that I'll get a black screen, my music starts looping, there's nothing I can do but to hard reset my MBP.
It's a common problem as I've done my search online and always read about this happening on the MBP, so I've been desperately trying to find ways to stabilized the performance of my MBP.
I've got update combos installed, and checked for latest software updates and I read somewhere that you should not install other graphic drivers into your MBP and that is why I've opted to remove it. I simply went to my "System Preferences", right click on the Cuda icon and remove it from my "Preference Pane", does that mean I have successfully unistalled Cuda?
I wanted to ask your opinion on this as I've been experiencing these crashes alot more frequently lately. If I were to bring this in to a Mac Shop and get a diagnostics run, what could be the potential problem and how much may the repairs cost? Is this a Logic Board problem or a Graphics Card problem?
I've got a Mac OS X 10.6.8, running on an Intel Core i& 2.66 GHz chip, with 4GB 1067 MHz DDR3, I feel it's still good enough to use and I don't see the need to change to a brand new MBP.
Thanks for reading this and I appreciate any input or help you may offer me.
Regards,Open Print & Scan preferences. Select the installed printer in the list. Click on the Delete [-] button below the list.
-
Why is my DSLR playback so sluggish, even with CUDA?
Hello,
At work I'm using Premiere cs5.5 on a MAC Pro running osx 10.7.4, it's a 2x2.4 quad core xeon with 12gb of RAM. My primary edit drive is a RAID 0 and I have the NVidia quatro 4000 with CUDA enabled in premiere.
My main question is why my DSLR playback is still incredibly slow when trying to watch footage? I get maybe...4 seconds of smooth playback and then it gets choppy. Even at 1/4 preview quality. It's mostly when watching footage shot with Canon 5D Mark III.
I compared footage shot with my Canon 60D and with my Mark III and the 60D played back without any issue at all, smooth all the way through, with an avg. bit rate of 5.6MB. The Mark III, set on high compression (similar to that of the 60D) avg. bit rate of 3.7MB, gets super choppy within seconds.
Is there a known bug or issue with the Mark III files playing back in premiere? CUDA seems to make no difference in performance for this. It's no better at playing back Mark III footage then when I try on my 3 yr old Dell studio Xps laptop within Premiere 5.5. The laptop I understand, but a fully decked out Mac Pro with CUDA? It seems like something is up.
I don't think it's the video card (but I'm only guessing), as it only seems to happen with Mark III footage. When I playback this footage through quicktime or preview, it plays without issue.
I find in general premiere pro to be sluggish on my mac compared to my win 7 edit machine at home, is there any validation to that?
Thanks for any help you can provide, these forums are very useful.
JamesHi Jim, that helps with some general info, but it's the fact that it's all Mark III footage specifically that is giving me hassles, and the fact that is plays back without issue in quicktime or preview, makes me believe it's a premiere issue. I'm not running off an external drive or anything either, I've got a RAID 0 that's got some great performance and premiere still bottlenecks.
I've been reading about Open GL 2 (one of the system requirements) issues with this card on a mac, but I'm not really too sure what to make of it, or how to check what my system is running or how to correct any issues.
Thanks
James -
Media encoder cs 6 and cuda Ge Force gtx 780
HI
I have a new graphics card it is the Gigabyte GeForce 780
I have CC and CC 2014 and also CS6 I notice that if encode using AME
I can see Cuda enabled in the encoder window and the option to use software only as well.
I don't see that option in CS6 I have Cuda in project settings in CS6
I am wondering if CS 6 AME uses it in the background or something or not at all?
I am thinking of sticking with CS 6 for a variety of reasons and just wondered if the later versions
were better able to utilize the card?
Hope that makes sense.
Thanks in advance for any light shed on thisYes, Premiere Pro CC adds full GPU acceleration certification for the GeForce GTX 680 on Mac.
-
Premiere Pro CC CUDA rendering working with avi output only
Hello All,
on my system Premiere Pro CC is only using GPU rendering with AVI output formats.
All other formats like MPEG2, Quicktime, H.264 are unfortunatly fully CPU rendered (=slow).
I just upgraded from trial to payed mode and when Premiere started the CUDA was already enabled (might have activated it during trial already).
But anyway I checked if my card was in the support txt file and also used the cuda.zip auto tool to make sure I had no typo.I did this for Premiere Pro CC and also copied the list into the Adobe Media Encoder directory.
No matter what I did - no hardware rendering.
So I started playing with input and output formats.
It turned out that CUDA is currently only working with AVI output. I installed GPU-Z to check my GPU usage vs CPU usage in the task manager.
As soon as I pick any other output format than AVI - CPU usage during rendering is up to 80-90 and GPU at 0%.
With AVI output GPU ist around 30 and CPU in the 40ties or less as it should be.
What is going wrong here?
One of my old applications Cyberlink Power Produces 11 is doing the h264 rendering in half the time.
Any suggestions?
My System is running on:
Asus P8Z77-V Deluxe with 16GB Ram
Nvidia GeForce GTX 660 Ti (with current Driver - 332.21 )
Windows 8.1 Pro 64-Bit (with Media Center) and latest updates
Current entry in CUDA*.txt file (as printed by Adobe GPUSniffer):
GeForce GTX 660 Ti
And already tried:
GeForce GTX 660Ti
GeForce GTX 660
Best regards
Moongate
P.S. I already followed the instructions on this page http://www.studio1productions.com/Articles/PremiereCS5.htmI now understand that Premiere Pro CC is only using my GPU for accelerating complex effects during editing giving me the possibility of a live preview during editing?
From the editing in other apps I know that the final rendering can also eat up much time which is why they try to accelerate it via GPU rendering. I see that Premiere is "outsourcing" this task to the Adobe Media Encoder (AME) so that you can continue working during rendering.
But I believe what tricked me into asking this question is that in the AME there is also the option to choose between software and GPU assisted Mercury Engine. So there must be a purpose for it and it sounds resonable that it is for GPU assited rendering.
So when the encoder is not using the GPU to speed up completion of rendering - what is he doing with that option?
Would it not be clever to cut rendering drastically using the GPU - its hard to believe that Adobe is only using it for previews?
Maybe you are looking for
-
I purchased music on my iPad (and it works fine). It populated my purchased list on my home computer but will not download (purchase is no longer a given option) ?? when I access it in the iTunes store I can click on play but nothing happens-how do
-
How to Get User entered value in a text variable
Hi, I have made a text variable to show the user entered value in the column header. The user enteres value in a formula variable ABC whose default value is say '30'. I am using customer exit to capture this value in the text variable. The code is as
-
Running PS 7 on Windows XP. Is it possible to do a multipage scan in Photoshop 7 and to have all the scanned pages saved as one PDF file. At the moment I can only find a way that gives me the same number of files as I have scanned in. The reason I am
-
Impact on if you change in material group
Hi, Change in Material groups in Material master - System will not update the PR,PO,Stock Have to change all the documents to update the New Material groups. Update Material master by LSMW
-
I need to have a unique sequential number printed on each form that is printed. Like the way checks are numbered. Can anyone help? Thanks!