Premiere Pro CS3 Issue with nVidia 182.50 GeForce Driver?

I recently updated the driver for the GeForce 8800GTS on my other editing workstation because it would sometimes BSOD when preparing to standby with a fault in the nvidia minidriver being reported. I updated to the current version as of today, 182.50 from nVidia's own web site.
After the driver update, I could swear I am seeing more frequent lockups of Premiere when jumping from clip to clip on a timeline of many clips. I can jump maybe half a dozen times and then Premiere will stop responding. Task Manager reports Monitor.exe 'not responding' and a few seconds later, Premiere.exe stops responding and I have to kill the app and start over. I can get it to hang within 20 seconds by just paging down through a few clips on the timeline now. The problem has existed prior, but usually after flipping though several dozen clips, not just a half dozen.
Is anyone noticing problems with more frequent lockups with the 182.50 driver?
SYSTEM CONFIG
Gigabyte GA-P35-DQ6
XFX PVT80GTHF9 GeForce 8800GTS 640MB
Intel Core 2 Quad Q6600
Mushkin Hp2-6400 Ddr2 4gb Kit
4 Western Digital Caviar HD 500G|WD 7K 16M SATA2 WD5000AAKS
SILVERSTONE TEMJIN SST-TJ06S-W Silver Aluminum
Seasonic S12 Energy Plus SS- 650HT Power Supply
LG GGW-H20L Blu-ray Burner
HP LP3065 30" LCD Display
Turtle Beach Montego DDL 7.1 Dolby Digital
Pioneer DVR-112D
NEC Beige 1.44MB 3.5" Floppy Drive Model FD1231H
ZALMAN 9700 LED 110mm 2 Ball CPU Cooler
Contour Shuttle-Pro

Hi Mark I'm running the 182.50 no problem now! I was having problems moving clips as the timeline would double in size and distort and not run correctly. The way I solved it was to to tick "disable display scaling on high DPI settings" in the compatibility section of the Premiere CS3 properties (right click on the icon for CS3 and then choose properties) this may help because with a 30" screen you're sure to have a high DPI setting. Terry

Similar Messages

How does premiere pro CC work with nvidia GT 630M (2GB) vega???!

how does premiere pro CC work with nvidia GT 630M (2GB) vega????!

That will work. I would just not expect major performance with a heavier load on playback.
Eric
ADK

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:

Premiere Pro CS6 Issues with AJA and Black Magic

Has anyone had any issues outputting via AJA and Black Magic cards?
I have 3 Macs using Black Magic Intesnsity Pro HDMI cards and 1 Mac using an AJA IO Express. On all the machines, i get weird audio issues intermitantly. I press play, no audio comes out. I stop, press play again, no audio comes out but the PP VU meter is registering. I stop, and press play again, and i hear distortion coming from my speakers, i stop and play again, and everything is fine. These issues are consitantly happening, but not necisarily in that order. I also get out of sync audio, then stop and press play again, and its all good.
I fell as though i have narrowed it down to being between PP and the IO cards, because if i turn the cards off in PP, my audio is fine everytime.
I have the propper Premiere Pro drivers (for AJA) and all the latest firmware and drivers for black magic. I am playing Quicktime media, usually Apple Pro Res hq or 444. IO and data rate with same codecs works perfectly in FCP. I have also tried using media that is local as opposed to on our server.
Has anyone had issues with this? Is this a known bug with in PP? Will it ever get fixed???
Thanks.

I have expereinced this issue on my Mac Pro right before I switched to a PC.
Call AJA Support. They are there to help you!

Premiere Pro CS6 issue with AME/Dynamic Link

Hello,
I'm having a quite frustrating problem with Premiere PRO CS6. Let me tell you my configuration first:
Intel i7 860, 8Gb Ram, 2x1Tb HD in Raid 0, GeForce GTX570 Ti 2Gb DDR5, Windows 7 Ultimate 64 bit, Adobe Creative Cloud subscription.
When I try to put in the AME's queue any Premiere's composition, I can see the window saying "Exporting...." but then nothing happens. AME doesn't start or, if it's already open, it doesn't receive anything on the queue.
I've tried to import the timeline's directly from AME, but it doesn't work either.
It has been a few days I'm fighting with this problem and I already have done this:
1) Uninstall/Clean Install all the software inside the Creative Cloud subscription and all updates applied.
2) clean any preset both in Premiere and AME by keeping down Alt+Shift when starting the applications.
3) disable/enable antivirus software (Microsoft Security Essentials) and firewall (default windows 7 firewall).
4) disable/enable the CUDA Mercury engine.
None of this solved the problem.
However I've noticed that each time I try to send something from Premiere to AME appears a general error in notifications saying just "invalid menu operation".
Since, as I've said, I tried also a clean installation, right now I'm really out of options and I would really appreciate any suggestion how to fix this problem. Thanks.
Martin

That has solved a few annoying Dynamic Link problems for me.
As a point of interest, the connection between Premiere Pro and AME isn't a Dynamic Link. It's more of a 'static' link. The point of a Dynamic Link is that any changes made in the original program will show up in the secondary program. That does not happen here. The sequence is 'saved' from PP as it is at the time the export is started and AME works off of that saved sequence. Changes made after that do not show up in AME automatically.
So whatever the error, it is not related to Dynamic Link.

Adobe Premiere Pro CS3 compatibility with Windows 8.1

Is Premiere CS3 and Encore CS3 compatible with Windows 8.1 64 bit?

I rather doubt it. CS3 was released back in 2007. You might try it.

Premiere Pro CS6 issues with .MOV files

I am having problems with .MOV files from my Nikon 5100.
They play very choppy. Multicam REALLY has issues with the .MOV files as it will play ten frames and freeze. Usually crashing Premiere altogether.
Anyone know how to optimize my system to play these .MOV files so the can be worked with? I've updated my videocard firmware and Quicktime.

Anyone know how to optimize my system to play these .MOV files so the can be worked with?
The logical steps would probably be:
Get a better PC
Don't use QuiRcktime but rename the .MOV file to .MPG
Tune your system. Also for Win7: Adobe Forums: Guide for installing and tuning a Vista...

Premiere Pro CS3 crash with many video files

Hi
I got back from my Ski vacation with many short (few minutes) videos which I took on Canon P&S camera, about 50 files.
I imported the 50 files to Premiere and tried to work on a movie, but everything works slow and every few commads the premiere crashes.
I notice that for each new file I add to the project 20K of rams are used - 1G for 50 files. I also get message of low resources from premere which recommend to save my works.
The video are standard video (not HD) 30fps, and the project is also standard.
Why is this happening?
Does the premiere have a limitation for number for files to be imported?
Does it have problem with the video format?
How can I overcome this and get a stable editing environment?
Thanks

Sorry for the CAPS Lock, I was writing from my mobile, and for some reason it was locked
so you do not recommend any of those codec package. How are you dealing with all video and audio formats, and subtitles? ffdshow does all for me.
dont' worry I dont have Klite installed
so you belive that if one of two codecs you recommened installed well and working it will solve my problem and work much better then FFDSHOW
I also have the option for converting the file to another format. under what name will I found a sutible format in the conversion software?

Premiere Pro CS3 Issue- Cross Dissolve Transition creates random frame insert

Hello,
I have had this issue for a long time, and whenever I render a cross dissolve transition, once in a while, it inserts a random frame from either the prior or latter clips that I apply the transition effect to.
I don't know how to solve this issue and could use help as soon as possible.
Thank you,
Th3On3Fr33man

I agree with Harm.
This happens when one does not have enough Frames (Handles), beyond the Out-Point, or before the In-Point, to accommodate the Duration of the Transition.
For some more info on Handles, these might be useful:
In the days of A-B Roll editing, or with film, Handles were an easy concept to grasp. With current NLE's, it's more abstract.
Good luck, and do not forget to read through the Help files. In the days of manuals, this concept was covered pretty well. Curt Wrigley covers it in his Classroom in a Book PrPro.
Hunt

Audio balance greatly different in Encore CS3 after encoding 5.1 master track in Premiere Pro CS3

Hello! I'm wondering if anyone can offer some advice for my DVD audio problem.
I have a Premiere Pro CS3 project with a 5.1 master track that appears to behave correctly judging by the meters when I play it in PP. It also sounds reasonable (in a mixed-down fashion, I guess) on my PC system's speakers (L,R,LFE), and all rebalancing and panning seems to work well. However, once I export the master track to Encore using PP's SurCode Dolby Digital codec, the resulting audio mix is totally off. Here's what I get: both front channels play mainly out of the right front and center speakers, and the rear channels play mainly out of the left front speaker. I've tried all different settings, but I can't seem to change this. Well I've read that Encore just sends the audio mix straight through (the DVD trancode status is "Don't transcode"), but when I build the DVD and play it on both of my 5.1 surround systems, the results are just as bad as what my desktop PC speakers were hinting at. [Actually all DVDs that Encore builds are UNSUPPORTED on one of my set-top DVD players and they're both Panasonic! So first, I first have to copy the DVD using Nero and then the copy is accepted by all. That seems to have no bearing on my audio dilemma but I thought I'd mention it. I would love to know what Nero is doing right that Encore is doing wrong!)
Anyway, here's some background: I began to notice this problem with the audio balancing whenever a .wav music source is imported into PP as a stereo source. [A side issue here - I don't seem to be able to explain - or control - how one .wav file gets imported as stereo while another is imported as 5.1!] Anyway, as one would expect, since my master track is 5.1, the stereo track is automatically set up with a rebalancing tray with the puck set in the middle. The meters show that the source is stereo and the sound has been rebalanced across the master track. If I drag the puck around, the master meters behave accordingly. Then I import my video (.avi video clip) and that sound is imported as a stereo track. For that track, I drag the puck to the rear. Again, the master meters respond correctly. So far so good. But when I export to Encore, the resulting audio mix so completely wrong it can't even be explained as a 5.1-to-stereo downmix situation. The sounds that were supposed to come out of the rear channels are in front left and center (and deafening), overpowering the music that is only coming out of front right. And the rear speakers are silent unless I turn on Pro-Logic on my amplifier, which just confuses the issue. I didn't bother to check LFE as things were bad enough.
Where I DO NOT have the problem is when the audio file is imported as a 5.1 source (although it is just a stereo CD track ripped using Sony CD Architect). In that case, there is no rebalancing tray and the track meter shows only the L and R channels active, as expected. Ditto for the master track. Now if I go ahead and send the music to a stereo submix track and let that rebalance to the master, I see all channels active. But that results in the problem above after exporting to Adobe Media Encoder using SurCode and then importing the audio into Encore. If I don't remix to 5.1, the audio on the DVD is OK. But I would like to have the music come out of all speakers when there isn't a video soundtrack as there are many still pictures in the presentation.
So the question is, if I can rebalance and pan channels in PP CS3, why are the results coming out all wrong in Encore using SurCode? And how can I hear my project on DVD the same way I mixed in PP?
Any help would be greatly appreciated!
Doug Herbst
Holmdel NJ

Problem solved everyone!!!
Rebecca of Adobe support helped me identify the root cause: project was originally set up as standard (2-channel) and although it had evolved to a 5.1 project over time, it could never grow up to be anything other than a standard audio project. After you set up the new project, the setting that controls your audio is buried in the project somewhere. Changing your project settings to set up new 5.1 audio tracks for new timelines does NOT make the project 5.1! The real audio identity attribute set at birth is not alterable OR EVEN VISIBLE (even as a grayed-out project setting) although PP will allow you to set up and mix 5.1 audio tracks at will. So you may think you're working on a 5.1 project now, but you're only fooling yourself and PP goes right along with it. Even the .ac3 files you create via export are 5.1! But dare to build your DVD in Encore and all of your timelines are transcoded back to 2.0 instantly. Resistance is futile.
A new feature in PP CS4 will allow you to view, and even CHANGE, your project's audio identify from standard to 5.1. How sweet!
Well, I've devised a way to dig out myself out of this deep hole in CS3 and it worked, but I can't promise that it will work for everyone. (This assumes you own the Dolby Digital 5.1 codec from Minnetonka.)
1. Create a new Premiere Pro project as 5.1 audio from the get-go.
2. Import your suspected 2.0 project into this new 5.1 project and click each sequence to flesh out the timeline.
3. Re-export all audio as elemental streams using Adobe Media Encoder. Make sure you export the audio component of each timeline as Dolby Digital 5.1 and exactly - and I mean EXACTLY - the same way. To deviate the audio settings for each timeline is to ask for trouble, so I recommend setting up an audio pre-set that you can just click when you need it.
4. Create a new Encore project and import all original video assets and your new replaced and, hopefully, 5.1 audio assets into it.
5. In Encore, create a separate timeline for each pair of assets (.m2v and .ac3 for example). DO NOT ATTEMPT TO PLACE MULTIPLE PAIRS OF ASSETS ON THE SAME TIMELINE! For some unexplained reason, the build process will transcode the audio back to 2.0, and if you continue pack new 5.1 audio assets on the same timeline, you will get an error message "an input contract violation has occurred" because you now have 2.0 and 5.1 assets on the same timeline, even though you really don't know that and didn't ask for that to happen anyway. (Thanks to Bill Hunt who mentioned his habit of keeping the asset pairs on separate timelines in another thread - that suggestion was absolutely essential to the solution here.)
6. In Encore, check to make sure that all of your original video sychs up correctly with the new, true 5.1 audio. Link the end actions of each timeline with the next timeline to play in the correct sequence. Check your project for orphan timelines and other errors. Then, before you start building menus and start getting fancy, build a DVD and make sure it plays as 5.1 on your system.
Tip #1: while you're re-exporting and replacing the audio files, don't have Encore running. I've seen it gracefully and automatically re-import the replaced file once the export is done, but I have also seen it choke with the terribly descriptive "Encore has encountered a problem" message upon discovered the asset is not available while it is being replaced. Encore then continues to mark the asset as offline.
Tip #2: when re-exporting and replacing files, always select audio and video separately. For some reason, Encore will allow you to replace an .ac3 file when you perform an elemental audio export, but when you try to combine video and audio and both files exist, Encore will prompt you to replace the video, but immediately abort with an error that it cannot replace the .ac3 file, thus forcing you to delete the .ac3 component manually before trying again.
Doug

Premiere pro CS3 with Nvidia GTS 250

Hi,
I just installed the Nvidia GTS 250 1GB graphics card to my system & the system config is - AMD Phenom X2 555 Black Edition, ASUS M4A785TD-V EVO,
8GB DDR3 Cosair, 1TB X 2 WD HDD with 64MB Buffer, Sony DVDRW, Samsung 24" FullHD LCD.
I use premiere pro cs3 to edit marriage videos. If I add a Hollywood FX 3D effect in between two clips when I play the clips in timeline with the Hollywood FX the video not smooth it jarks, so what the use of this GTS 250 Graphics card?
Is there any way to smooth playback in timeline with the Hollywood FX?
Thanks in advance

1-do you render before trying playback
2-what kind of video?
Read Bill Hunt on a file type as WRAPPER http://forums.adobe.com/thread/440037?tstart=0
What is a CODEC... a Primer http://forums.adobe.com/thread/546811?tstart=0
What CODEC is INSIDE that file? http://forums.adobe.com/thread/440037?tstart=0
For PC http://www.headbands.com/gspot/ or http://mediainfo.sourceforge.net/en
3-what is your drive setup?
My 3 hard drives are configured as... (WD = Western Digital)
1 - 320G WD Win7 64bit Pro and all programs
2 - 320G WD Win7 swap file and video projects
3 - 1T WD all video files... read and write

Premiere Pro CS3-CONSTANT Memory issues when editing/rendering/exporting

Alright, as said in the title I am currently using Adobe Premiere Pro CS3, and my issues are horrendous
No matter what, within 10 minutes of editing, Premiere will warn and then crash because of memory issues, starting with the message:
"Adobe Premiere Pro is running very low on system memory; please save your project and proceed with caution"
Also, whenever I try to export this project, within 800 frames of a 7000 frame project (currently), it displays the message:
"Error Compiling Movie", and then the previous message above if that hasn't already happened before
And eventually, the program will crash out of nowhere, with random windows errors
Here's my specs:
Intel i7 920 Processor
6 GB DDR3 RAM
Nvidia 480 GTX
750 watt power supply
24" Dell Ultrasharp Monitor
Now, I've noticed that whenever Premiere is getting close to crashing, my RAM gets up to around 4.7 GB being used, and then it crashes.
I have already gone into Edit-Preferences and tried switching from Performance to Memory; that hasn't fixed anything
I noticed that when I was just running my video over and over again, it stayed stable at 4 GB or so, so maybe its a rendering issue?
I have already tried lowering my number of processes running at any given time, including my antivirus program (Kaspersky) and even explorer, but it still crashes no matter what.
========================================================================================== ========
This is a SERIOUS issue for me, as even with all the normal crashes I could finish the video; but now I cannot even export my video at ALL without it crashing, and I have a plenty strong-enough computer to handle this, so what gives?
Please help

Ok, well this has been getting me nowhere
I tried importing (both my CTRL-X method, and literally importing the project), and now the program won't even RENDER the footage, it just errors out at 800 frames (just like exporting)
What is going on???
I used to use Premiere Pro 2.0 all the time, on a separate computer, but I have 6 GB of RAM, is this really impossible???
EDIT:
And now, even after finally getting it to render (by saving after rendering before what crashed, and then starting it up and rendering again), all my footage looks like crap XP

Encore & Premiere Pro CS3 with Photoshop CS5

Hi,
I have the CS3 suite on Vista 32 bit. I was wondering if I can keep the Premiere Pro CS3 and Encore CS3 and only upgrade Photoshop to CS5. Has anyone had any compatibility issues using this combination? Can Encore CS3 menus be easily edited in Photoshop CS5?
Thanks

Welcome to the forum
You cannot upgrade to a standalone program from a Suite.
But to answer your question: yes you can edit Encore CS3 menus with Photoshop CS5.

Premiere Pro CS3 Importing Issues

Hi all,
I'm new to Premiere, and I've been having issues with a project that I am trying to start. I am running Adobe Premiere Pro CS3 on Windows Vista. I want to import a file that was originally a .mkv file. Because Premiere does not use .mkv files, I simply changed the file extension to .avi. The file is about 1.42 GB. But whenever I try to import the file as a .avi, my program freezes and I get a (Not Responding) error on the dialog box at the top of the program. When this happens I am always forced to close the program. Am I experiencing this simply because the files I am attempting to import are too big? Or is it something else?
Also, if it is indeed because the files are too big, how can I get around this problem? I have tried using software such as VirtualDub and SolveigMM Video Splitter to cut the AVI files into smaller parts, but they do not seem to be working. Any help would be greatly appreciated! Thanks a lot!
(By the way, I attached a JPEG file of a snapshot of what happens when I try to import into Premiere.)

This is because you cannot simply rename a file's extension to "look like" a different format. An .mkv is as similar to an .avi as a goat is to an iguana. First, you may want to try something like this.
You can also try opening your MKV in VirtualDub (without renaming it ".avi"), which may work. I have read that recent releases of VirtualDub can handle (more or less) MKV files, but I have no experience with this myself. If this works, you can save it as an AVI from VirtualDub.
As for the AVI format, it is really just a "container." What matters more is the codec with which the AVI is compressed. A good choice is often DV (and here is a good free DV codec if you need one). However, DV only works with videos of certain resolution and framerate, so you may want to convert to an uncompressed AVI or use a codec like Lagarith.
Assuming you are able to find a decent MKV -> AVI converter, could you please post more details on your video, such as its resolution. It would also be helpful to know what format you plan to output your edited video as.

HT203254 My MacBook Pro 15-inch with NVIDIA GeForce 8600M GT graphics processors just failed. Do you guys know if apple still fixes them?

My MacBook Pro 15-inch with NVIDIA GeForce 8600M GT graphics processors just failed. Do you guys know if apple still fixes them?

I tried last week. The best I could get was a discount on the repair, but the damage to my logic board by the GPU caused it to no longer boot. The program ended in December last year, but it has been extended in the past.
If you have no other damage you might be able to get a flat rate tier 1 repair if you are in the USA.

Premiere Pro CS3 Issue with nVidia 182.50 GeForce Driver?

Similar Messages

Maybe you are looking for