Premiere Pro CC 2014: nVidia GTX780 in SLI
Hello everyone!
I found these forums to be really useful in the past (read them as guest) - so I thought I'd post. For Premiere Pro CC 2014, is it worth having a rig with two nVidia 780 cards hooked up in SLI? I keep reading that PP will still only look at one card and not both of them. Thanks in advance for your help!
SLI is not used. SLI is for gaming display but of no use at all for PR. You can use 2 video cards, but SLI is irrelevant and can cause problems.
For 2 GTX 780's to be used effectively (not having one or the other used for less than 50%) you better have a monster of a machine with dual 10+ core CPU's, 128 GB memory and a raid array capable of more than 2000 MB/s transfer rate. Otherwise the GPU will be waiting all the time for the rest of the system to catch up. See Tweakers Page - Balanced Systems
Similar Messages
-
Premiere Pro CC 2014 with NVIDIA system freezes (Win7x64)
It appears after perhaps the last update Premiere Pro CC 2014 started freezing during editing. It appears to happen mostly with 4K material and using the Ultra key and alpha blending but may also occur with 4K titles. The sequences are 23.976 1080p, with mixed footage from the Sony A7S (50 Mbps XAVC-S/H.264) and GH4 (4K 100 Mbps H.264). There are also frequent crashes with GPUFoundation.dll (Mercury + CUDA). No freezing with software only rendering. I tried a variety of drivers when using a Quadro 5000 with no change in freeze behavior. I tried a new GTX 770 (clean driver install) and the freeze behavior and GPUFoundation.dll crashes are the same, however now even the mouse freezes. With the Quadro 5000, the entire Windows GUI would freeze (become inactive), however the mouse would still move. Thus, it appears there are issues with both NVidia drivers and Premiere Pro CUDA code path on Windows (app errors shouldn't be able to lock up the entire GUI). GPU Meter shows low GPU and GPU memory utilization during the freezes. The freezes typically occur when switching between clips during playback or scrubbing (more often with fast scrubbing). As a developer, it feels like some kind of semaphore lock / race condition, since during the freezes CPU, GPU, and memory utilization are very low. Additional hardware info: 2010 MacPro 12-Core, 24GB RAM running Win7x64 (with latest updates). Side note: PPro used to hang in memory on exit, but stopped after a recent Microsoft forced update (PPro now crashes sometimes on exit but no longer hangs in memory (used to have to kill it after exiting every time)). Has this been reported before? (A7S XAVC & GH4 4K footage is relatively new)
This crash occurred when dragging Black Video with Noise and other effects on top of alpha composited layers (+3 layers). CUDA turned the rendered area black, so I switched to OpenCL. This crash happened a few minutes later. While this would appear to be an Nvidia driver error (OpenCL), perhaps the developers can investigate. The system is very stable except when doing complex operations in PPro (and only PPro crashes). A tried and true Quadro 5000 crashed in the same way (totally different hardware and drivers).
The full debug info wouldn't post, edited shorter:
Application Specific Signatures:
Graphics hardware encountered an error and was reset: 0x0000001f
Process: Adobe Premiere Pro CC 2014 [380]
Path: /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Identifier: com.adobe.AdobePremierePro
Version: 8.0.1 (8.0.1)
Code Type: X86-64 (Native)
Parent Process: launchd [191]
Responsible: Adobe Premiere Pro CC 2014 [380]
User ID: 501
Date/Time: 2014-10-01 03:13:25.803 -0700
OS Version: Mac OS X 10.9.5 (13F34)
Report Version: 11
Anonymous UUID: 3E030FD4-F38F-857C-3EB9-85D10E36AB49
Crashed Thread: 11 Dispatch queue: opencl_runtime
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
Application Specific Signatures:
Graphics hardware encountered an error and was reset: 0x0000001f
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff8bcbfa1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8bcbed18 mach_msg + 64
2 com.apple.CoreFoundation 0x00007fff8bb10f15 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation 0x00007fff8bb10539 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation 0x00007fff8bb0fe75 CFRunLoopRunSpecific + 309
5 com.apple.HIToolbox 0x00007fff8d375a0d RunCurrentEventLoopInMode + 226
6 com.apple.HIToolbox 0x00007fff8d3757b7 ReceiveNextEventCommon + 479
7 com.apple.HIToolbox 0x00007fff8d3755bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
8 com.apple.AppKit 0x00007fff86c7424e _DPSNextEvent + 1434
9 com.apple.AppKit 0x00007fff86c7389b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
10 com.apple.AppKit 0x00007fff86c6799c -[NSApplication run] + 553
11 com.adobe.Frontend.framework 0x00000001000ca38d FE::MacApplication::RunSelf() + 45
12 com.adobe.Frontend.framework 0x000000010004898a FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 4058
13 com.adobe.Frontend.framework 0x00000001000cbc44 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 276
14 com.adobe.Frontend.framework 0x00000001000d2e25 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
15 com.adobe.AdobePremierePro 0x00000001000018ac main + 508
16 com.adobe.AdobePremierePro 0x00000001000016a4 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff8bcc4662 kevent64 + 10
1 libdispatch.dylib 0x00007fff8a0c2421 _dispatch_mgr_invoke + 239
2 libdispatch.dylib 0x00007fff8a0c2136 _dispatch_mgr_thread + 52
Thread 2:
0 libsystem_kernel.dylib 0x00007fff8bcc464a kevent + 10
1 com.adobe.dvatransport.framework 0x0000000100e294fc boost::asio::detail::kqueue_reactor::run(bool, boost::asio::detail::op_queue<boost::asio::detail::task_io_service_operation>&) + 236
2 com.adobe.dvatransport.framework 0x0000000100e291a7 boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock<boost:: asio::detail::posix_mutex>&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) + 375
3 com.adobe.dvatransport.framework 0x0000000100e28d18 boost::asio::detail::task_io_service::run(boost::system::error_code&) + 552
4 com.adobe.dvatransport.framework 0x0000000100e18157 SkyConnectionEnv::MainLoop() + 167
5 com.adobe.dvatransport.framework 0x0000000100e17c09 SkyConnectionEnv::StaticThreadFunc(SkyConnectionEnv*) + 9
6 com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
7 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
8 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
9 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff8bcc3716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8c0d0c3b _pthread_cond_wait + 727
2 com.adobe.dvacore.framework 0x000000010036a0ab boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock<boost:: asio::detail::posix_mutex>&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) + 139
3 com.adobe.dvacore.framework 0x0000000100369e18 boost::asio::detail::task_io_service::run(boost::system::error_code&) + 552
4 com.adobe.dvacore.framework 0x0000000100369bda boost::asio::detail::posix_thread::func<boost::asio::detail::resolver_service_base::work_ io_service_runner>::run() + 42
5 com.adobe.dvatransport.framework 0x0000000100e29bb3 boost_asio_detail_posix_thread_function + 19
6 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
7 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
8 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 4:
0 libsystem_kernel.dylib 0x00007fff8bcc3716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8c0d0c3b _pthread_cond_wait + 727
2 com.apple.CoreServices.CarbonCore 0x00007fff824bc800 TSWaitOnCondition + 108
3 com.apple.CoreServices.CarbonCore 0x00007fff824bc9ff TSWaitOnConditionTimedRelative + 172
4 com.apple.CoreServices.CarbonCore 0x00007fff8248d145 MPWaitOnQueue + 192
5 com.adobe.dvacore.framework 0x00000001003a359d dvacore::threads::ThreadSafeDelayQueue::PopWithTimeout(std::auto_ptr<dvacore::threads::Al locatedFunctionT<boost::function<void ()> > >&, int) + 141
6 com.adobe.dvacore.framework 0x00000001003a1500 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 160
7 com.adobe.dvacore.framework 0x00000001003919ac boost::function0<void>::operator()() const + 28
8 com.adobe.dvacore.framework 0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
9 com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
10 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
11 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
12 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 5:
0 libsystem_kernel.dylib 0x00007fff8bcc3716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8c0d0c3b _pthread_cond_wait + 727
2 com.adobe.GPUFoundation.framework 0x000000010941b8d6 void boost::condition_variable_any::wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&) + 70
3 com.adobe.GPUFoundation.framework 0x0000000109419705 GF::Device::AcquireExclusiveAccess() + 117
4 com.adobe.PlayerMediaCore.framework 0x0000000129518684 AdobePlayer::PlayerDisplay::UpdateWindow() + 372
5 com.adobe.PlayerMediaCore.framework 0x000000012952b2a5 AdobePlayer::PlayerMain::OnUpdate() + 21
6 com.adobe.PlayerMediaCore.framework 0x0000000129530501 PrPlayModule<AdobePlayer::PlayerMain>::PlayEntry(int, pmStdParms*, void*, void*) + 241
7 com.adobe.PlayerMediaCore.framework 0x0000000129530390 xPlayEntry + 16
8 com.adobe.PlayerHost.framework 0x00000001057238c4 ML::CallPlayerModuleGuarded(int (*)(int, pmStdParms*, void*, void*), int, pmStdParms*, void*, void*, int*, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 276
9 com.adobe.PlayerHost.framework 0x0000000105721669 ML::PlayerModule::CallPlugin(int, void*, void*) + 153
10 com.adobe.PlayerHost.framework 0x0000000105745c36 ML::VideoPlayer::CallPlayModuleSelector_Update() + 86
11 com.adobe.PlayerHost.framework 0x000000010573421d ML::VideoPlayer::ForceDisplayRedraw(ML::PlayerOutputQuality) + 205
12 com.adobe.PlayerHost.framework 0x0000000105728a34 ML::PlayModuleThreadQueue::ExecuteDeferredCall(ASL::ObjectPtr<ML::DeferredCallBase, ASL::AtomicValue>) + 340
13 com.adobe.PlayerHost.framework 0x0000000105727935 ML::PlayModuleThreadQueue::ServiceQueue() + 293
14 com.adobe.dvacore.framework 0x00000001003a159e dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 318
15 com.adobe.dvacore.framework 0x00000001003919ac boost::function0<void>::operator()() const + 28
16 com.adobe.dvacore.framework 0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
17 com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
18 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
19 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
20 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 6:
0 libsystem_kernel.dylib 0x00007fff8bcc3716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8c0d0c77 _pthread_cond_wait + 787
2 com.apple.CoreServices.CarbonCore 0x00007fff824bc9e7 TSWaitOnConditionTimedRelative + 148
3 com.apple.CoreServices.CarbonCore 0x00007fff8248d145 MPWaitOnQueue + 192
4 com.adobe.dvacore.framework 0x00000001003a359d dvacore::threads::ThreadSafeDelayQueue::PopWithTimeout(std::auto_ptr<dvacore::threads::Al locatedFunctionT<boost::function<void ()> > >&, int) + 141
5 com.adobe.dvacore.framework 0x00000001003a1500 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 160
6 com.adobe.dvacore.framework 0x00000001003919ac boost::function0<void>::operator()() const + 28
7 com.adobe.dvacore.framework 0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
8 com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
9 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
10 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
11 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 7:
0 libsystem_kernel.dylib 0x00007fff8bcbfa1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8bcbed18 mach_msg + 64
2 libcuda_334.01.03_mercury.dylib 0x00000001223f85a2 cuosEventWait + 210
3 libcuda_334.01.03_mercury.dylib 0x000000012233e922 intHandlerMain + 114
4 libcuda_334.01.03_mercury.dylib 0x00000001223f9479 cuosPosixThreadStartFunc(void*) + 41
5 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
6 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
7 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 8:
0 libsystem_kernel.dylib 0x00007fff8bcbfa1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8bcbed18 mach_msg + 64
2 libclh.dylib 0x000000011ae0fe19 0x11a800000 + 6356505
3 libclh.dylib 0x000000011a8c5df2 0x11a800000 + 810482
4 libclh.dylib 0x000000011ae10c69 0x11a800000 + 6360169
5 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
6 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
7 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 9:
0 libsystem_kernel.dylib 0x00007fff8bcbfa1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8bcbed18 mach_msg + 64
2 libclh.dylib 0x000000011ae0fe19 0x11a800000 + 6356505
3 libclh.dylib 0x000000011a8c5df2 0x11a800000 + 810482
4 libclh.dylib 0x000000011ae10c69 0x11a800000 + 6360169
5 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
6 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
7 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 10:
0 libsystem_kernel.dylib 0x00007fff8bcbfa1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8bcbed18 mach_msg + 64
2 libclh.dylib 0x000000011ae0fe19 0x11a800000 + 6356505
3 libclh.dylib 0x000000011a8c5df2 0x11a800000 + 810482
4 libclh.dylib 0x000000011ae10c69 0x11a800000 + 6360169
5 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
6 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
7 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 11 Crashed:: Dispatch queue: opencl_runtime
0 libsystem_kernel.dylib 0x00007fff8bcc3866 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff8c0cf35c pthread_kill + 92
2 libsystem_c.dylib 0x00007fff8c131bba __abort + 145
3 libsystem_c.dylib 0x00007fff8c131b29 abort + 140
4 libGPUSupportMercury.dylib 0x00007fff89db41ca gpusKillClient + 111
5 libGPUSupportMercury.dylib 0x00007fff89db4b51 gpusQueueSubmitDataBuffers + 155
6 libclh.dylib 0x000000011a90ee26 0x11a800000 + 1109542
7 libclh.dylib 0x000000011a8b104a 0x11a800000 + 725066
8 libclh.dylib 0x000000011a8b10a1 0x11a800000 + 725153
9 libclh.dylib 0x000000011a8b4394 0x11a800000 + 738196
10 libclh.dylib 0x000000011a910425 clhCtxSynchronize + 21
11 com.nvidia.web.GeForceGLDriverWeb 0x00001234402e627d gldFinishQueue + 234
12 com.apple.opencl 0x00007fff87917abe 0x7fff87911000 + 27326
13 com.apple.opencl 0x00007fff87931123 0x7fff87911000 + 131363
14 com.apple.opencl 0x00007fff8793414a 0x7fff87911000 + 143690
15 libdispatch.dylib 0x00007fff8a0c028d _dispatch_client_callout + 8
16 libdispatch.dylib 0x00007fff8a0c6a18 _dispatch_barrier_sync_f_slow + 460
17 com.apple.opencl 0x00007fff87933faa 0x7fff87911000 + 143274
18 com.apple.opencl 0x00007fff8792a202 clEnqueueMapBuffer + 631
19 com.adobe.RendererGPU.framework 0x0000000111714245 GF::ScopedRecordedHostMemory::Map() const + 133
20 com.adobe.RendererGPU.framework 0x00000001117685ea RendererGPU::PointwiseFilterHostNode::ApplyConcatenatedPointwiseFilters(ASL::InterfaceRef <MF::IVideoFrame, MF::IVideoFrame> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame> const&, boost::shared_ptr<RenderResults> const&, std::vector<RendererGPU::PointwiseFilter, std::allocator<RendererGPU::PointwiseFilter> > const&) + 826
21 com.adobe.RendererGPU.framework 0x0000000111767daf RendererGPU::PointwiseFilterHostNode::Process(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&) + 831
22 com.adobe.RendererGPU.framework 0x000000011171d2b8 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 1448
23 com.adobe.RendererGPU.framework 0x00000001117ad03c RenderNodeBase::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 76
24 com.adobe.RendererGPU.framework 0x000000011171d094 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 900
25 com.adobe.RendererGPU.framework 0x00000001117ad03c RenderNodeBase::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 76
26 com.adobe.RendererGPU.framework 0x000000011171d094 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 900
27 com.adobe.RendererGPU.framework 0x00000001117ad03c RenderNodeBase::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 76
28 com.adobe.RendererGPU.framework 0x000000011171d094 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 900
29 com.adobe.RendererGPU.framework 0x00000001117194d5 RendererGPU::CompositorNode::Process(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&) + 1413
30 com.adobe.RendererGPU.framework 0x000000011171d2b8 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 1448
31 com.adobe.RendererGPU.framework 0x000000011170f36f RendererGPU::(anonymous namespace)::RendererGPU::ProduceFrame(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, std::string*, ASL::ParamRect<int>) + 1279
32 com.adobe.PlayerMediaCore.framework 0x0000000129535bf0 AdobePlayer::RenderRequest::ProduceFrame(ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, RenderParams const&, std::string*, ASL::ParamRect<int>) + 96
33 com.adobe.PlayerMediaCore.framework 0x000000012951cefd AdobePlayer::PlayerDisplay::PresentRenderRequestImpl(boost::shared_ptr<AdobePlayer::Rende rRequest> const&) + 1901
34 com.adobe.PlayerMediaCore.framework 0x00000001295204db AdobePlayer::PlayerDisplay::PresentLastCompletedRenderRequestImpl() + 267
35 com.adobe.dvacore.framework 0x00000001003a159e dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 318
36 com.adobe.dvacore.framework 0x00000001003919ac boost::function0<void>::operator()() const + 28
37 com.adobe.dvacore.framework 0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
38 com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
39 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
40 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
41 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 319
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 56776
thread_create: 1
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=679.6M resident=223.0M(33%) swapped_out_or_unallocated=456.6M(67%)
Writable regions: Total=19.5G written=15.6G(80%) resident=14.2G(73%) swapped_out=3.0G(16%) unallocated=5.3G(27%)
REGION TYPE VIRTUAL
=========== =======
ATS (font support) 32.0M
ATS (font support) (reserved) 8K reserved VM address space (unallocated)
CG backing stores 23.8M
CG image 584K
CG raster data 48K
CG shared images 204K
CoreImage 8K
Foundation 4K
IOKit 78.3M
IOKit (reserved) 268K reserved VM address space (unallocated)
Image IO 1032K
Kernel Alloc Once 8K
MALLOC 1.5G
MALLOC (admin) 32K
MALLOC_LARGE (reserved) 512K reserved VM address space (unallocated)
Memory Tag 241 128K
Memory Tag 242 12K
Memory Tag 249 192K
Memory Tag 251 24K
OpenCL 1.0G
OpenGL GLSL 1664K
STACK GUARD 56.8M
Stack 113.7M
VM_ALLOCATE 52.6G
VM_ALLOCATE (reserved) 30.4M reserved VM address space (unallocated)
__DATA 71.6M
__IMAGE 528K
__LINKEDIT 225.7M
__NV_CUDA 456K
__TEXT 453.8M
__UNICODE 544K
mapped file 84.0M
shared memory 68K
=========== =======
TOTAL 56.3G
TOTAL, minus reserved VM space 56.3G
Model: MacPro5,1, BootROM MP51.007F.B03, 12 processors, 6-Core Intel Xeon, 2.93 GHz, 24 GB, SMC 1.39f11
Graphics: NVIDIA GeForce GTX 770, NVIDIA GeForce GTX 770, PCIe, 2048 MB
Memory Module: DIMM 1, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 2, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 3, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 5, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 6, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 7, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.7f3 14616, 3 services, 15 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: NVIDIA GeForce GTX 770, Display Controller, Slot-1
PCI Card: pci1095,3132, SATA Controller, Slot-2
PCI Card: NVIDIA GeForce GTX 770, NVDA,Parent, Slot-1
PCI Card: pci1b73,1100, USB eXtensible Host Controller, Slot-4
Serial ATA Device: HL-DT-ST DVD-RW GH61N
Serial ATA Device: WDC WD1001FALS-41Y6A0, 1 TB
Serial ATA Device: OWC Mercury Extreme Pro SSD, 240.06 GB
Serial ATA Device: OWC Mercury Extreme Pro SSD, 240.06 GB
Serial ATA Device: WDC WD4001FAEX-00MJRA0, 4 TB
USB Device: Scarlett 2i2 USB
USB Device: Keyboard Hub
USB Device: USB-PS/2 Optical Mouse
USB Device: Apple Keyboard
USB Device: My Passport 0741
USB Device: My Passport 0820
USB Device: USB3.0 Media Reader
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Logitech RumblePad 2 USB
USB Device: Mobile Keys 49
FireWire Device: built-in_hub, Up to 800 Mb/sec
Thunderbolt Bus: -
Adobe Premiere Pro CC 2014 compatible with Nvidia 970 GTX?
Good afternoon.
I'm an owner of a GIGABYTE Nvidia 660 GTX Ti OC 2GB. The card is detected by Adobe Premiere Pro CC 2014 (Even though,i think,it said that it's not listed or something but will work under my own risk..Is there a way to check if it's certified/supported via my own program and NOT the typical "This is the list of supported GPUs"?)
Anyways,i was thinking of buying one of the new 970GTX cards to game on better,but also to make full advantage of it's properties to do much more faster encoding/exporting (you know,create a H.264 MP4 720p@29,97FPS file) than my actual 660GTX card with Adobe Premiere Pro CC 2014.
The thing is,any owner of such card (GIGABYTE,MSI,doesn't matter) have tried to launch Adobe Premiere Pro CC 2014 and export stuff by using the GPU's full potential to make everything faster?.. Because i have this fear of "Getting the newest n greatest Nvidia card so far and in the end see/notice it'll not work with Premiere Pro CC 2014"
....Can somebody please help me with this big fear of mine,please?
Thanks in advance
DVLocked... duplicate discussion... see GTX 970 and Premiere Pro
-
New (8/14) Macbook Pro Retina - Premiere Pro CC 2014 spinning beach ball
Help! Seems my shiny new wiz-bang 4-core Macbook Pro with 16 GB of Ram and a 512 solid state drive works just fine with Adobe Premiere Pro CC 2014 until my project reaches a certain size, then it won't open the project and immediately gives me the deadly spinning beach ball. The only way to exit is to force quit whereupon I get the "Sorry, a serious error has occurred...". Aggravating beyond words.
Saw one forum comment where it was recommended to update to the 6.0 CUDA driver, but not even sure I have a CUDA driver. Plenty of space left on hard drive. In Premiere Pro preferences under the "Memory Tab" it doesn't seem to matter if it's set to "Optimize rendering for.... Memory or Performance." I've reinstalled the Premiere Pro App twice. Doesn't help.
Some specs:
Processor 2.5 GHz Intel Core i7
Memory 16 GB 1600 MHz DDR3
Graphics Intel Iris Pro
NVIDIA GeForce GT 750M GPU PCie
Intel Iris Pro GPU Built-in
8 GB DDR# 1600 MHz (x2) = 16 GB RAM
350 GB of 499 GB left on drive
Of the 16 GB of RAM I have 11 available for Premiere Pro and the other 5 GB allocated for other apps.
Any suggestions would be greatly appreciated.>NVIDIA GeForce GT 750M GPU PCie
>Intel Iris Pro GPU Built-in
Dual graphics adapters are a bane on civilization!!!
-http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
-http://forums.adobe.com/thread/1001579
-Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
-link to why http://forums.adobe.com/message/4685328
-http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2
-Mac Utility for dual adapters http://forums.adobe.com/thread/1017891?tstart=0 -
Adobe Premiere Pro CC 2014 Crashing very often! Please Help!
Hello,
I am currently editing my first feature on Adobe Premiere Pro CC 2014 and it is currently up to date.
I am editing on a iMac 27in, late 2013 brand new computer.
Processor: 3.5 GHz Intel Core i7
Memory 32GB 1600 MHz DDR3
Graphics: NVIDIA GeForce GTX 780M 4096MB
System: OSX Yosemite V 10.10.1
The project is located on a 8TB G Drive
7200 RPM
High Performance ThunderBolt drive.
Details of the project:
I am currently working on a fine cut of 5K Red Footage that is being cut in the RAW.
I work at 1/2 quality settings and have no lag.
The timeline includes limited stacked video files and various mp3 audio files.
The Problem:
Lately, the program will randomly quit or freeze up 4-5 times during an 5-6 hour edit session.
Many times it is random, however, it seems to happen often if I accidentally click on the end of a clip on the timeline and it goes to switch into trimming mode.
Also, it will randomly go into the "pinwheel of death" out of nowhere followed by "Adobe CC is not responding."
My project file is just about 15MB now.
What is causing this reoccurring problem?
How can I make it happen less? I have scoured the forums and found similar articles but no helpful solutions.
I have recently turned auto save on to save every 2 minutes because there have been more than one occasion where I lost A LOT of work because of this issue.
I am about two weeks out from picture lock delivery and this issue is driving me crazy and loosing me a ton of time.
Please help or let me know if any more additional information can help solve the issue.
I have sent in well over 25 error reports already.
Thanks,
Thomas.I think I may have found the solution...
I completely removed the Premiere Pro folder under User > Documents > Adobe and so far it seems to have solved the problem.
I of course backed up my projects and than deleted this folder. So far it seems it worked.
I'll know for sure in a day or two, but after constantly crashing, Premiere hasn't crashed for the last 4-5 hours of work.
Goran -
Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different. Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
It can occur even in the parts without filters !!! But no all time.
ver 2014.2 - win 7 - intel i7-4770 - gtx 770 - flicker!
ver 2014.2 - win 7 - intel i7-4770 - Intel HD Graphics 4600 - flicker!
ver 2014.2 - win 7 - intel i7-2700K - quadro 2000 - flicker!
MERCURY PLAYBACK ENGINE work fine! But still flickering in preview and render.
When waiting for fixes this bug?Hi Aleksey,
Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different.
Have you tried with the Mercury Playback Engine set to "Software Only?" More info please: FAQ: What information should I provide when asking a question on this forum?
Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
Is this a brand new project or one you updated from an earlier version? What kind of footage are you exporting? Which preset are you using?
When waiting for fixes this bug?
If I can repeat the case here with the same hardware, GPU, and drivers, that would be easier to fix the bug. Currently, I cannot recreate the bug. If you or anyone else can provide me with steps to recreate the bug, that would help immensely. It sounds like this will be the difficult thing.
Thanks,
Kevin -
Why does Premiere Pro CC 2014 renders incredibly slow?
Dear Premiere Pro experts
I created a movie with Adobe Premiere Pro CC 2014 and I have serious performance issues when it comes to export the movie.
The first 10% renders pretty fast and takes 1 hour. Then it takes for every additional 1% about 4 hours! (never rendered it to finish so far, 14% max so far)
Here are some facts that might help to isolate the problem:
Project:
Length: 24 minutes in total, splitted into several sequences (up to 4 minutes) and arranged on a "main-sequence"
Input: Cineform AVI files, 1080p, 59fps (I converted GoPro 3+ footage (3D!) using GoPro Studio to the Cineform format for further processing)
Desired Output: Same as input, preserving 3D (Render 3D Intermediate)
Effects used: Warp-Stabilizer (default settings) and Auto-Color (smoothing 1-2 sec) on almost every clip.
Hardware / Software:
i7-3770K @3.5 GHZ (Quadcore)
16 GB RAM
NVIDIA Geforce GTX 970 (also tried with a ATI Radeon R9 290X)
Windows 8.1
SSD for OS and programs, RAID 0 for media files and project, separate drive for rendering output.
Then I tried to render using AME using the same settings. The whole video rendered in about 14 hours what is acceptable in my case. There problem here is that the 3D gets lost, even if I selected "Render 3D Intermediate". The picture for the left eye is the same as the one for the right eye. This is not happening when I do a direct export. But the direct export get almost stuck at around 10%.
There is almost no difference in choosing Software-Rendering and GPU. Also, the GPU has almost no load. Premiere Pro uses the CPU for about 45% (total usage 65%) and takes up 5-9 GB of memory (total usage 65%). Disk usage at around 14b/s.
I think there are two problems. One is that AME renders differently (no 3D) and the other is that the direct export takes way too long.
Can someone help me with any of these problems?
Thank you,
MartinI did some additional research and found out, that the slow rendering happens with this combination:
- Auto-Color using Temporal Smoothing
- Render 3D Intermediate
Without rendering the 3D intermediate, Temporal Smoothing is not a problem. And without temporal smoothing, Rendering 3D Intermediate is not a problem.
Might this be a problem in the codec or in Premiere? -
ICanon C100 playback issue premiere pro cc 2014
I am having playback issues in Premiere Pro CC 2014 with footage shot on my Canon C100 (29.97 fps). It was happening after doing a straight import and creating a sequence using "new item". Then, after reading some other threads here and elsewhere, I interpreted the footage so premiere would see it as progressive (no fields) rather than interlaced, but that doe not seem to help. It is even doing it when I play at 1/4 resolution. The only solution seems to be to quit and restart and reopen the project. Then it works temporarily for a little while but not long enough to actually edit. I have done projects in Premiere with C100 footage in the past and have not experience this level of difficulty.
My Media Cache is not going to the startup diskc(it is gong to the right place)
I am on a Mac 2.66 Ghz Quad-Core Intel Xeon
OS X 10.8.5
10GB 1066 MHz DDR3
NVIDIA GeForce GT 120 512 MB
Please help - very frustrated. If the solution is to transcode, it sort of kills the value of premiere in many ways.Hi,
This might help :
Go to File > Project Settings > General and change the Video Renderer to Mercury Playback Engine software only. Click OK and select Delete Previews.
Thanks,
Rameez -
Can't Move Audio Clips in Timeline After Expanding to View Waveforms (Premiere Pro CC 2014.2)
So, this seems to be a bit of a weird one, and I'd be pretty stoked if it ended up being something silly that I'm doing wrong, but I can't for the life of me figure out what that might be.
As the title suggests, I can't use the mouse to move some audio clips in a timeline once I expand the track to view the waveforms. This appears to only happen with independent audio clips (WAV. AIFF, MP3, etc), and not with clips attached to video. Also, it's worth noting that I don't have track keyframes turned on. I was hoping that was it, but it wasn't.
So, what happens is this:
1) I drag an audio clip down to the timeline (I can drag it onto an existing track, or drag to the bottom of the sequence and create a new track. Neither option seems to get a different result.).
2) So long as the track isn't expanded and the waveform isn't visible, I can move the clip left, right, or up and down to a different track.
3) As soon as I expand the track to view the waveform this functionality goes out the window. When this issue happens I can use the keyboard to nudge left and right, but that's about all the movement I have.
4) It's almost as though the track becomes corrupt. The lanes for the track don't redraw properly, and the track is pretty much unusable. I can't put anything into it, and I can't take anything out. All I can do is delete the track and start again.
Complicating issues is that this doesn't always happen, but instead is one of those "vast majority of the time" issues. I can't see any rhyme or reason for why it works or doesn't. I seem to do the exact same thing, but occasionally get different results. It doesn't matter what type of file I'm using (WAV, AIFF, etc), and this only happens with independent audio clips.
Once again, I don't have track keyframing turned on when this happens. Believe me, I wish that was it.
I have already filed a couple of bug reports about this over the last month or so, but haven't heard anything yet. I was wondering if anyone else was having the same issue, and if so, whether they had any workarounds.
Mandatory system info:
Windows 7 Professional SP1 (64-Bit)
Intel i7-3820
32GB RAM
Nvidia GTX 980 (350.12)
Premiere Pro CC 2014.2Update:
I was just looking to post a screenshot of the timeline when I discovered something interesting. As soon as I use the vertical scroll bar to the right of the sequence, the tracks start to work again. Close off the waveform and the clip goes haywire. Move the scroll bar a tiny bit (or a lot), and suddenly the clip starts working.
Pretty bizarre.
The good news is that for the time being that could be a workaround, though it would be great for this to not happen at all. -
Premiere Pro CC 2014 and Media Encoder CC 2014 not completing encode.
This is a project that I have been successfully encoding in short segments until now. Now when encoding, session runs about 10-15 minutes and then ends without error messages.
Removing effects and changing to Mercury PB Engine SW did not help.
Also tried disabling metadata as suggested in another forum.
When CUDA used, logged as "Encoding failed." When Mercury SW used, logged as "File Successfully Encoded" even though video file is only 6 KB with no content.
Premiere Pro Build 8.1.0 (81)
Media Encoder Build 8.1.0.122
Windows 7 Professional
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
8 GB RAM
NVIDIA GeForce GT 610 (9.18.13.3788)I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out. -
Exporting to Media Encoder crashes Premiere Pro CC 2014
Greetings,
I am experiencing a problem with premiere off and on. Right now it is an on problem. When I am exporting from Premiere Pro CC (and CC 2014) it will intermittently crash Premiere. I have tried this with several different audio and video formats (AVI [Lagarith and uncompressed], WAV, H.264, MPG2, AAC, etc). At the moment, every time I go to export to queue it locks up and hangs on the "Preparing data for export..." Media Encoder Launches and then it just freezes. I get "Problem Even Name: AppHangB1" over and over. Sometimes a full restart will fix this temporarily and sometimes it goes away for a long while. I managed to get a few sequences exported and then it just kept freezing on every PP CC restart.
Here are my system specs:
Premiere Pro CC (up to date)
Win 7 64bit (up to date)
i7 970
24GB Ram
NVIDIA 470GTX (driver up to date)
3 x 1.5TB internal
4TB internal
3TB internal
12TB RAID 5 via USB 3.0
USB 2.0 and 3.0 drives
FireWire audio device (M-AUDIO FireWire1814)... although, I am not using it for playback. It is connected.
Footage is from C100 H.264 .MTS, H.264.mov from 7D, and H.264 .MOV from iPhone.
All stock video plugins with a few third party audio plugs.
This problem happens with and without third party plugs, but it happens that this project uses them.
I have chatted with Adobe help twice about the matter and nothing has come of it. Log out, log in = same. Restart = same (sometimes), create new user account = same, and so on. The only thing I haven't done is completely re-install premiere, which seems a bit overkill. One of the reps said he would get back to me in a few days after he watched the issue via screen share. Never heard back.
I get the sense that this has something to do with PProHeadless.exe not launching or not running properly. When the crash happens on a fresh restart of PP CC 2014 PProHeadless is not running. I can start PProHeadless and it will send sequence to media encoder. When I try to export another sequence from the same project it crashes and I see another instance of PProHeadless launched.
Also, once the projects are exported to Media Encoder, I can encode them to any format with no problem. The problem is getting the sequences there!
Is there anything that I am overlooking here?
Thanks for the help!Hi
Premiere pro cc 2014 8.0.1 (21) build
Encoder CC 2014 8.0.1.48
I use CC for Teams so it updates all the time.
Again when I tried to use it today by letting premiere open it by sending an output into Queue it crashed both Encoder and Premiere.
In order to shut down Encoder and Premiere I had to go into Task Manager and "End Process Tree" on everything adobe I could find because just ending Encoder did not work it would not close. I remembered that years ago when Premiere would crash we had to end a photoshop process. I found photoshop open even though it was not "alive" on my task bar. I had used it yesterday but had closed it. I also had to close dynamiclinkmanager.exe *32 as well as one of the three Adobe CDF Helper.exe*32. They popped back on but Encode closed and then I got a message that Premiere needed to close and did when I clicked the button to let it close.
After all this I re-opened Encoder by itself and checked the Preferences finding that Import Sequences Natively option was again checked.
By the way for me, "Launch AME manually, then drag the sequence from PPro's Project panel to AME's Queue (or to a preset in the Preset Browser). That uses a different code path than the File>Export>Media workflow." won't work most of the time because I do live events of panel interviews that may run 2 or more hours. I need to break them down to chapters for the web
Also I know this isn't part of this problem but I and many others would still love dynamiclink to work to Encore because the DVD is not dead yet. The current work path is a drag.
Looks like some programers and engineers have some work to do.
Thanks
Dennis
My computer:
Self built PC windows 7 Professional 64 bit Build 7601 SP 1 I use auto update so it is up to date.
ASUS P6x58D Premium Motherboard
Intel (R) Core i7 930 @ 2.80 Ghz
Installed Memory 12 GB
NVIDIA GeForce 9500 GT
NVIDIA GeForce GTX 580
2 Apple Monitors and a HP full HD Monitor
With a BlackMagic Intensity Pro Capture Card -
Premiere Pro CC 2014 very unresponsive while rendering on background with Adobe Media Encoder
Usually while I eddit videos on Premiere, I'm rendering on the background with AME. Or at least I used to. Some time ago, this process suddenly stopped working, as rendering on the background bagan to make Premiere really unresponsive, and quite impossible to work with. I couldn't think of any change I made other than switching my HDD, and I blamed it on that (it made sense because new HDD is one of those WD Green ones, a little worse than my old Seagate one). So I adapted to just queueing everything and start rendering when I was done edditing. But yesterday I installed a 240gb Kingston HyperX SSD, re-installed Windows and the main apps on it, and tried again, hoping to see an improvement. Now I was storing the original media on the HDD, running OS, Premiere and AME on the SSD, and rendering to the HDD. It did not work. Premiere still became slow while I rendering with AME. So I thought it might get better if the HDD was not reading and writing at the same time, and I switched the original media to the SSD, while still rendering to the HDD. Also didn't help. I don't know why this setup suddenly does not work, and I really need to fix it.
My setup:
Windows 7 Home Premium 64bit
Intel Core i7 2600 @ 3.4GHz
12GB of RAM
nVidia GeForce GTX 560 (yes, drivers are up to date)
Dual monitors (one for Premiere workspace and one for a bigger program monitor)
2TB WD Green HDD where I keep most of my junk (and media files)
240GB Kingston HyperX SSD where I run the OS and important apps (Premiere and AME included)
I'm running Adobe Premiere Pro CC 2014 (8.1.0 build) and AME CC 2014 (8.1.0.122 build)Hi chriscorrell,
Thank you for posting on Adobe forums.
Upgrading your OS might be a good idea because Premiere CC 2014's OS requirement is OS X 10.8.
See here: System requirements | Adobe Premiere Pro
Thanks,
Rameez -
Premiere Pro CC 2014 won't open "because it is not responding".
When trying to open Premiere Pro CC 2014 it won't open and I get the message "You can't open the application "Adobe Premiere Pro CC 2014" because it is not responding.
I've done my updates, uninstalled it, reinstalled it. Even did a clean re-install of the Yosemite OS but nothing. It opens up fine on my laptop.
I'm on an iMac 27, late 2009.
2.66 GHz Intel Core i5
16GB RAM
ATI Radeon HD 4850 512 MB
Really need this to work asap.
Thanks.
/CarlA variety of issues can cause PPRO to crash on launch. Here are some of them:
a problem with the Preferences, or some other pref-related file in the Profile-<USERNAME> bin.
the graphics driver
having an integrated graphics chip as well as a graphics card. Disabling the integrated chip often fixes this.
having Nvidia CUDA drivers installed on a system with an AMD card
third-party plug-ins
a problem with the cache files.
a problem with the project file (if you're loading a project...)
folders that Premiere writes to being set to read-only
the user not having administrator rights
a conflict/incompatibility with some OS setting
a problem on the licensing/authentication side.
The fact that you've done a fresh installation of 10.10 eliminates some of those possibilities.
After a crash on launch, does a dialog box eventually come up prompting you to submit a crash report to either Adobe or Apple? If so, please click "information" or the like to access the crash log and copy/paste the report here. -
Performance Issue Premiere Pro CC 2014 with Late 2013 Mac Pro
Hi all!
Im working Premiere Pro CC 2014 on a Late 2013 Mac Pro 6 core D700s and 32GB RAM on OSX 10.9.4
After the 2014 update i have experience some drop frames and hangs with a new 1080p timeline project.
And it later results in software hang and crashing . even after a quit (force quit) and re-poen, it seems to happen again and again.
Even after a system reboot seems to be fine at first, but it still crashes on the project.
Tired to render the timeline and still the same. Also tried to delete rendered file and play right with timeline with yellow bar, same.
Even drop the preview playback to 1/2 and still..
files are mixed 1080p footage from Canon 5d3, 60D, T2i.
I have 3 layers (interview video with different angles) and a title layer (hard subtitle)
had some light color correction with fast color corrector and a sharpening on the 5d3 layer.
Ive work with the CC premiere pro before with mac pro and everything is fine and never hand an issue.
All my memory setting are set for performance and i have open GL on my D700s
Im not sure if this a software issue or someone my hardware is not working right?!
Thanks in advance!I am having the same issues.
Im working on a late 2012 iMac, 3.4 GHz Intel Core i7. 32 Gb ram, NVIDIA GeForce GTX 680MX, OS X 10.9.4.
I'm editing RED footage, about 3 TB worth for this project from a Promise Pegasus drive.
The software really slows down when using the TYPE tool and also when scrubbing through footage.
When I attempt to quite the software and restart, the interface goes away but the app is still running but says "not responding" when I attempt to force quit.
If you've figured it out since then Id love to know what works.
Thanks!
G -
Adobe Premiere Pro CC 2014.2 (8.2) freezes up constantly on Mac OS X Yosemite
After the latest update (no idea which one but the latest update) Premiere Pro cc just keeps freezing up constantly. There's no indication what brings it up but after different periods of time I just get the apple wheel and the entire program freezes up. I force quit and get the "sorry, a serious problem has occured", blabla. Sometimes it's in the middle of cutting a clip, sometimes it's while trimming. There isn't a single indication what causes it. At first I thought it was only because of using a multicam clip, but that's not the case anymore. I tried reducing memory to other apps, deleting preview files, deleting autosaves, turning off autosave altogether, deleting Adobe Premiere 8.0 preference file, changing permissions, basically everything in this post: Re: Adobe Premiere Pro CC keeps crashing... (Which now also seems totally neglected by Adobe).
Believe me, there's hardly a thing I haven't tried.
It's getting REALLY frustrating now and it's time something is done about this. Yes I know, "don't just say it's frustrating, explain the problem", but that fase has passed now. I'm paying for this product and it needs to work like it should.
Also I know I'm not the only one who's having these problems.
My specs are:
OS X Yosemite 10.10.1
MacBook Pro (Retina, Mid 2012)
2,3 GHz Intel Core i7
16 GB 1600 MHz DDR3
NVIDIA GeForce GT 650M 1024 MBHi JJ,
JJ Millen wrote:
It is not about the past times you may or may not have participated, but about the latest message from rob654 and my last messages in that thread (which are clearly not about Windows).
One great reason to get a Mac only version of the post. It is never a good idea to post on a Windows post with Mac problems. And when threads get so long and unruly, the team can't focus on the actual issue so it doesn't get the attention it needs.
Now that we have that sorted out...
JJ Millen wrote:
I checked that and it says 8.2.0. (65) build.
Thanks for the verification. You are running Premiere Pro CC 2014.2 (8.2). It helps to have that absolutely clear.
JJ Millen wrote:
Here are all the checkpoints mentioned in that thread, applicable to my project:
- Version 8.2.0;
- My Creative Cloud says Premiere Pro is up-to-date;
- Operating system is OS X Yosemite version 10.10.1 (14B25);
Very well, did things operate any differently on Mac OS X 10.9.x? Or did you have the same problem?
JJ Millen wrote:
Type: MPEG Movie
File Size: 4,0 GB
Image Size: 1920 x 1080
Frame Rate: 25,00
Source Audio Format: 48000 Hz - 16 bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00:12:35:16
Pixel Aspect Ratio: 1,0;
So is this H.264? What is the camera that you are working with? DSLR?
JJ Millen wrote:
- I do not get any error messages, except for the "Sorry, a serious problem has occurred"-message after I have to force quit my Premiere because of the freeze;
What kind of drives are the media files stored on?
Are the permissions set correctly (as Read/Write) for the Mac HD and your media drives?
Are the permissions set correctly for all the Adobe folders as I outlined in my blog?
JJ Millen wrote:
- The problem mostly occurs when cutting a clip with the razor tool, regardless of the kind of clip;
When you import clips, are you using File > Import, or are you importing via the Media Browser?
JJ Millen wrote:
- Yes this has worked before, the problems started either after creating a submix (which I've deleted, without result) and/or after updating to a newer version of Premiere CC;
Definitely do not update Premiere Pro or OS X when in the middle of a project. Wait until it's complete. If you did either or both of these things, you can cause your project to become corrupt. After your current project is wrapped, test with a brand new project.
JJ Millen wrote:
- The only software I run actively besides Premiere is Apple's Mail program, Safari and/or Chrome, sometimes Wire, sometimes Spotify;
- I currently have no third-part effects or codecs installed in Premiere;
- I installed the latest CUDA Mac Driver, version 6.5.37 (release date 01/14/2015);
- The problem just happens while working in my sequence, not in any final output. I don't know what is meant by "previews", but I have the yellow bar indicator in my sequence, if that's info you need.
I have heard of others having issues with OS X 10.10 and NVIDIA GPUs. My advice is to consider downgrading your OS if you continue to have issues. I believe I have avoided a lot of trouble by sticking to OS X 10.8.5.
Previews AKA the Media Cache are your "render files." They can become corrupt, so it's a good idea to trash them when troubleshooting. You can locate them via your Preferences > Media. Click the Browse button.
JJ Millen wrote:
Okay I went through that menu (which I'm not eager to do, I prefer direct contact) and came across the CUDA setting inside the project settings. I've now enabled the "Mercury Playback Engine GPU Acceleration (CUDA)", which might help.
So were you set to "Mercury Playback Engine Software Only" or "Mercury Playback Engine GPU Acceleration (OpenCL)" prior to changing it to "Mercury Playback Engine GPU Acceleration (CUDA)?
JJ Millen wrote:
Testing with a brand new project is not an option. I have a deadline for my current project and it's impossible to start from scratch. What I did try is start a new project and importing the existing one, which didn't help so far.
I was just wondering if you experienced the same issues in a new project. Any project you update to a new version is suspect, in my opinion. In the future, try to avoid doing that. If your current project is corrupt, I could see why you are having certain issues.
For what it's worth, we had another user that exhibited similar issues until they started with a brand new Premiere Pro CC 2014.2 (8.2) file.
Since importing your 8.1 file to a new 8.2 project isn't working, make sure to triple check permissions on all the Adobe folders I laid out in my blog post: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
It's the #1 reason Mac users experience freezing and crashing. The other one I'd look at is that NVIDIA drivers are not working well with Yosemite. Finally, if you update a project across versions, it can become corrupt. Not much you can do about that except start a new project ASAP.
Thanks,
Kevin
Maybe you are looking for
-
Is there a way to speed up importing of songs?
When I am importing CD's, it seems extremely slow at times. The display shows 1.0X, and I am guessing that means if the CD is an hour, it is going to take an hour to import? Is there a way to speed this up? When I posted this question before, the onl
-
My laptop was stolen and now when I try to sync my music it wants to wipe my ipod touch 5th generation. How do I get around this ?
-
Why i am unable to catch the 'TAB' key press?
hi i have an application where i have 2 text fields and one button in order say t1, t2 and b1. on tabbing t1 cursor moves to t2 and on tabbing t2 cursor moves to b1 and on tabbing b1 cursor moves to t1. now when i press tab button on any of the compo
-
TS1398 I am traveling tomorrow and I have had trouble connecting to airport wifi...why?
I was at the airport in Atlanta and could not connect to the public wifi. I chose that one and the next page had no other info or entry...help!
-
Calculating stock on hand per material at bin level from EWM
Hi, I want to arrive at a report where i want to display the current stock(quantity) of a material at a particular bin. What are the EWM tables or Function modules or Methods that will give me that. EWM monitor (/scwm/r_wme_monitor) displays the same