True Snap Toggle in Premiere Pro CC 2014
Hello there,
As many of you, I've been a Final Cut Pro 7 user for many years, and am making the migration to Prem..
and there's one Final Cut feature that I miss so badly...
It's the snap toggle. I know in Premiere, you press 'S' to turn snap on, and 'S' to turn it off again.
However in Final Cut, you can keep your timeline on "Non-Snap", but whilst your moving your clip in the timeline,
you can toggle 'N' and it will snap into place. but as soon as you drop your clip on the timeline, it will revert to "Non-Snap".
This the way I like to work.
Now I know it's just one more keystroke to do it in Premiere, but I felt this true-toggle option to be the most brilliant workflow.
It would be most appreciated if someone knows how to turn this on in a setting, or perhaps we can request it in the next soft update.
Thanks so much for your help people!
- Josh
Also, while we're at it..
I was wondering if there was a way to reduce the amount of snap, because it seems way more 'snappy' than FCP.
thanks! : )
Similar Messages
-
Premiere Pro CC 2014 and Medie Encoder CC 2014 problem
Hello there,
Every time that I am willing to export my project my Premiere Pro CC 2014 stop responding all together. I tried the short cut (Commend+M) or going through the Manu bar. the result is the same, Premiere Pro CC 2014 just freezes and does not respond to anything till I force quit it and restart it allover again. I tried exporting from Premiere Pro it self, without using Media Encoder, but the problem remains the same.
I am using the new Mac Pro. I heard Adobe Premiere Pro is experiencing problems with the New Mac Pro. Is that true? Or is there other issue?
Thank you and looking forward to hear back,
MarufI 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. -
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: -
Exporting from Premiere Pro CC 2014
Hello there,
Every time that I am willing to export my project my Premiere Pro CC 2014 stop responding all together. I tried the short cut (Commend+M) or going through the Manu bar. the result is the same, Premiere Pro CC 2014 just freezes and does not respond to anything till I force quit it and restart it allover again. I tried exporting from Premiere Pro it self, without using Media Encoder, but the problem remains the same.
I am using the new Mac Pro. I heard Adobe Premiere Pro is experiencing problems with the New Mac Pro. Is that true? Or is there other issue?
Thank you and looking forward to hear back,
MarufHi Maruf,
Maruf Noyoft wrote:
Kevin,
I reset as you suggested and it took care of it.
Great!
Maruf Noyoft wrote:
So, if you don't mind explaining me the cause of the problem that I had? Or
an article about it. It is just for me for getting to know better the program and the system.
Thank you very much and appreciate your help enormously.
Since preference files get touched by the application frequently, there is always the possibility of their corruption. When this happens, you start to see what we call "unexpected behaviors" from Premiere Pro. This problem happens infrequently, but it is a good first troubleshooting step to try on your own. This is the case with most every non-linear editing application I have used over the years (Final Cut Pro, Avid, Media 100, etc.).
Thanks,
Kevin -
H.264 encoding issues with Premiere Pro CC 2014
After updating to Premiere Pro CC 2014 yesterday, I see encoding artifacts on my H.264 exports.
Same source video imported into CC v2014 and v7, and exported using the YouTube 1080p 29.97 fps settings. The artifacts manifests itself as softness/blurriness in parts of the image every few seconds, especially notice the area with a red circle below.
Here are the source file (GoPro HERO3 Black Edition), the v2014 render and the v7 render.
Original: https://drive.google.com/file/d/0B2rJe0xgMTxFYXJiMjZpZ0stUzQ/edit?usp=sharing
CC v2014 render: https://drive.google.com/file/d/0B2rJe0xgMTxFQ1B0Z09GS3I0a1E/edit?usp=sharing
CC v7 render: Premiere Pro CC.mp4 - Google Drive
[Version numbers corrected.]
Message was edited by: Jim SimonMark Mapes wrote:
This is a known issue introduced in CC2014.0. Some h.264 encodes have blurriness or noise periodically in some areas of the frame. The problem is most pronounced in regions of the frame with very little detail, like grass or pavement--or the T-shirt in the sample frame. We are working on a fix. Before you ask when the patch will be forthcoming, I'm not authorized to even hint at the timeframe.
Unfortunately, the only real workaround is to export to a format other than h.264. If that's not an option for you, then your best bet is probably to keep working in CC7.2.2 until the patch is released.
Sorry, but thats not completely true and by far not the correct answer:
The problems with random artifacts occurred with the introduction of a new version of H264 in CS6 but there you still had the option to export with the previous H264 Version via Media Encoder.
Since the previous H264 version is not available in CC, using CC7.2.2 is not a solution either.
BTW
Updating to CC and using the new Mac Pros with Mavericks is currently a total mess - no open cl rendering, random crashes, no usable h264 ... thanks adobe!!
... but we can track masks in premiere now ... wow! -
My recent update to Adobe CC 2014 apps has been an unmitigated disaster. Was running the 2013 version until last week and everything was just dandy. Very good performance and excellent render/encode times even for stuff with lots of filters and fx.
Since update 1-2 min videos with no fx or filters (or even transitions) have gone from exporting in under two minutes to well over 25 minutes. These exports are with the same presets I regularly use (Vimeo 720HD H.264).
I've been poking around the forums here for two days looking for answers and can't find anything that works. Tried the whole "App Nap" toggle as well as a few other tips. Didn't do squat. Looking for any hints/answers. Thanks.
Mac Pro Mid 2012
2 x 2.4 GHz 6-Core Intel Xeon
32 GB 1333 MHz DDR3 ECC
ATI Radeon HD 5870 1024 MB
OS X 10.9.5 (13F34)
System SSD 500GB
Cache SSD 500GB
Media HD 1TBHi MXSw,
MXSw wrote:
All right. More experimentation has been done. Seems like the renaming of Adobe folders fix prescribed in the link below might have helped a bit.
Premiere Pro CC 2014 renders are painfully slow.
You can rename folders, but I prefer to do it this way: Premiere Pro CC freezing on startup or crashing while working (Mac OS X 10.9, and later)
MXSw wrote:
Kicked out a 1 minute edit with some color/fx in under 10 minutes. Not as fast as in the past but at least the CPU seemed to be cranking at 500% and above per Activity Monitor. Its barely gone over 250% in previous attempts.
That sounds a lot better.
MXSw wrote:
Same 1 minute edit took 35 minutes however when I exported from a PP timeline using MXF clips instead of QTs. I assumed the QTs would speed up the process but in the past I've gotten great performance on big old RED raw files so still a bit of mystery why I can't approach the speeds I had prior to most recent CC update.
Maybe updating your project file has something to do with it. I'll keep my eye on this issue. Thanks for reporting.
Regards,
Kevin -
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 -
What is the problem with Adobe Creative Cloud Premiere Pro CC 2014, why it freezes often?
I Purchased the Adobe Creative Productive Premium Suite CS5 in early 2010 and I was very satisfied with it all this time, I can say that I never had a problem while using any of the Production Premium applications. Few weeks ago, I asked Mr. Philip Bloom about a technical issue regarding the best method to use a 50 FPS clip with a 23.976 FPS project, and I got his kind help but he recommended me too that I should upgrade to the latest Adobe Cloud CC 2014 which has many new features added to the different programs. I took his kind advice and downloaded a trial version of all the Adobe Cloud CC programs which I use for my filmmaking business.
Today is the 20th day of my trial period and I have 10 days left to take the decision of continuing with CC 2014 or not. The past 20 trial days were not very pleasant. I want you to share with me the following details which I'll list them as bullet points and I would appreciate diagnosing the problem if you can and suggest a solution for it to re-try the Adobe Cloud CC 2014 for the 10 remaining days with no further problems.
I used to have the Gigabyte graphics card GTX 470 for about 4 years and it malfunctioned last year and I replaced it with a humble Geoforce GT 610 card, but it worked fine with the Adobe Suite CS5 programs.
My system configuration is Intel Core I7 950@ 3.07GHz , installed memory 12 GB. , Windows 7 Ultimate, 64 bit Service pack 1, 3 hard drives 1TB. each (one of them is dedicated for Adobe asset files and the editing work)
For the first 2 or 3 days I used mainly the Premiere Pro CC 2014 establishing short projects for a max. of 5 minutes each and it was working normal. But, later, as soon as I started to build a project which reached about 24 minutes of length and I began to edit those before I add more clips to the timeline, unfortunately, the PrPro CC 2014 started to freeze on any of the frames every time I try to edit normally as I used to do with the CS5, so, I had to wait for 2 or 3 minutes every time it freezes, then it works for seconds then freezes again!! and during the 20 days mentioned above it crashed once.
The movie files of my project are the Nikon's .Mov files and the editing work which I performed included effects such as Color correction (levels) color correction (fast) color correction (Auto) sharpen effect, and stabilizing effect.
I installed the Magic Bullets Suite trial version, and the Neat Video trial version, aiming to purchase either the DeNoiser or the Neat Video (but I tried their effects without saving them to the project).
I used to export parts/ or whole project before finalizing the editing process to be able to monitor on a TV screen (mp4 file format) some of the changes I made in PrPro before being freezed.
Based on my previous 5 years experience using the CS5 Suite I have a strong trust in Adobe, I never thought the problem was in the PrPro application, but rationally I thought it was the graphic card (GT610), and accordingly I purchased yesterday a new Zotac Geoforce GTX 770 (listed by Adobe as an approved card) and I installed it and checked that it is running fine and I checked the processor temperature which was within the normal level.
Only today, I began to think that it might be something wrong with the Adobe Cloud CC 2014 ( a bug or something) and as a result of searching on the internet I could see lot of users since 2014 who were having freezes and crashes with the CC and the CC 2014 versions. That was a shock for me, could it be that until Feb. 2015 the same severe problem still occurs???
Sorry for any inconvenience, looking forward to seeing a solution for that serious problem.Hello Ashraf,
Sorry you didn't get any help on this post. In the future, please contact Adobe Support for 1-1 assistance on issues like this: Contact Customer Care
Thanks,
Kevin -
Multi Cam Flicker Issue - Premiere Pro CC 2014
Multi Cam Flicker Issue - Premiere Pro CC 2014 can any one help me pls
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 -
We are working on a film project on Adobe Premiere Pro CC 2014. Two editors are working on the same film project (same pproj file ) on two machines. As a result the bin structure and the file structure is exactly the same. We even bought two licenses for the respective machines to make matters simple (at least we thought it would).
Now when we share a sequence between the two machines, every time we have to import and re-link media. Also each sequence import comes with its own set of files, which are actually already present in the project. Basically the new sequences are looking to re-link the media to the original/ source files only and are completely ignoring the file structure present in the project.
In all editing softwares, timeline/ sequence sharing is a very common practise when working on multiple machines. Why is it so tedious in CC 2014? Every time we share a sequence between the two machines the media gets doubled and tripled in the project. As a result the project file size is increasing perpetually. Already Premiere CC 2014 is extremely laggy and slow, and this stupid bug is making it more difficult for us to finish our work on time.
Has anybody ever faced this issue? How do we solve it? We are willing to try out any workflow that you can suggest.Concurrently working on the same project it requires a specific implementation in all editing programs like Avid's Unity/ ISIS shared storage. That's what you are simply not considering. none of your issues would be any problem if your projects resided on a commonly accessed server or something like that. Check respective hardware solutions.
Mylenium -
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 -
Premiere Pro CC 2014 crashes when loading project file
Hi guys, any help on this is much appreciated as I have a job due in 18 hours and I'm in big trouble if I can't fix this.
I've been editing a project in Adobe Premiere Pro CC 2014 (updated to the latest version) and when I tried to access the same file today it is giving me the error message:
'Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project.'
I had saved other version files and they all seem to be working properly so I know it's not my HD that is corrupt. In fact my suspicion is that it has something to do with a blur effect i'm using. The only problem is, I can't even access the file to delete the effect as the project file won't open.
Information about my computer:
I am using a Macbook Pro
OS X version 10.9.4
2.6 Ghz Intel Core i5
Memory 16 GB, 1600 MHz DDR3
Any suggestions/comments would be appreciated.Guys I solved my own problem - thought I'd share with you how in case anyone else is having this problem -
I came across this thread
Premiere Pro CC error message and crash
which had the suggestion -
"Do tou have after effects installed? If yes, please try to import the main sequence into it and then export it as premier pro project from file/export ootion and then try to open that in premiere pro."
This didn't work for me too but I did try and import my existing project into a new project and copy all the files over. Works fine now.
I don't know if I will have the same issue again tomorrow so I'm going to render out a super high res video before I close premiere just in case -
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? -
After upgrading to Premiere Pro CC 2014, I can't change the render preview location
Ever since I downloaded Premiere Pro CC 2014, I cannot re-route my render preview files. I have two internal hard drives and I need the files to go to my secondary one. With CC, it did this just fine, but since I've upgraded to 2014, it will not do it. I've set it the same way I did before in Preferences/Media, then set the Media Cache Files and Media Cache Database to the new hard drive. It's eating all my hard drive space and I cannot render or export a large sequence. Is there a trick to this I'm missing that has changed?
Thanks Neil! I'm actually wondering how to change where the preview files go. I've attached two screen grabs. Right now my media cache is going to my SATA drive (my smaller of my two internal hard drives and the drive where Premiere Pro is located.) I want to re-route my render files to go to my Macintosh HD drive which is much larger and gives me more breathing room. I could do that before but since I've upgraded to 2014, even though I have it set in preferences, it STILL goes to my SATA drive. So annoying! I'm wondering if I'm doing something wrong or if it's a bug. I'm still running Mountain Lion (getting ready to finally upgrade, I've just been needing to backup my computer), could this be the reason? Any ideas? Thanks so much for the help!
Maybe you are looking for
-
my smaprtphone is Xperia x10
-
Unable to pass parameters in Report Bulder due to single quotes
Hello, I have a problem with parameters in Report Bulder. This is the query: where task.closed_at between (@Per) Then I need have to pass following value to @Per : DATEADD(month, -5, getdate()) and getdate() to get following: where task.closed_at bet
-
Okay, I've never used the support forum before, so go easy on me... Here's the deal...I built a website using iWeb for my business. I basically took a template and started used the features that come out of iWeb. No editing HTML, just doing everyth
-
When I perform a search on our Intranet it shows a displayed of Correlation ID: 29cb4bfc-421e-42be-9fe4-50a5c686fec4 I have researched the problem and it seems to be something to do with a service application but which I have created a new one but th
-
How do I open hotmail messages, delete, compose, etc. ? It has stopped working since May 31st.
On May 31st , 2010 my hotmail stopped working properly with Firefox. After logging in to my account, I see that I have new messages, but cannot read them, or read the old messages. I cannot delete, compose, or do anything with my messages. I can acce