Matrox Mojito Max with GTX 970 Premiere Pro CC 2014

Good day everyone,
I am building a workstation and I would like to ask, if I can use both of the cards, The GTX970 for rendering and Matrox Mojito MAX for monitoring? I know, that Matrox card is hardware accelerating h.264, but is it faster than GTX970? If i can use this combo, how can I set? If i set the Mojito to preview, can I set the Mercury settings in the project settings for GTX970? Will it work? Thank you for respond.

Ask in the Premiere forum.
Mylenium

Similar Messages

Incredibly Long Lag Time When Working With Effects in Premiere Pro CC 2014

I am having incredibly long lag times when working with effects in Premier Pro CC 2014. Like 60 seconds or more. This also happens periodically when I am doing something as simple as cutting into a timeline (just ripple deleting from and in to an out point).
I have a MacBook Pro running OSX 10.9.4 2 GHz Intel Core i7 with 16 GB 1600 MHz DDR3.
I have seen that some people are having different versions of the same problem. I do have RedGiant plug-ins, but I am not using any of them in this project. The Red Giant plugs (again, not being used in the project) include MOJO and Universe. The previous version most certainly did not work like this. Any ideas? I did try moving the Red Giant plugs out of the COMMON folder and "alt" starting up to reset preferences. Still having same problems.
A specific example is I have an interview shot. I add brightness and contrast. Just making a change to the effect (increasing brightness) causes freezing of the interface and long delays. I added a piece of transparent video on a top layer to add a CIRCLE to create a vignette effect. Same deal -- ridiculously long times for effect changes to take place.
Does anyone have any clues as to how to fix these problems?
THANKS FOR ANYONE'S HELP!!!!!!!

Got the same Error. Previous I worked with a GTX 760, and was hoping to get it fixed with using a GTX 780 6GB. But just as you, didn't solve the Problem.
Usually I got the Problem solved, with exiting Premiere, restarting it, reset my Workspace. Then the Problem of having the bugged Workspace was gone. And also the Problem of the missing Video Tracks.
At the moment I started on a new Project. Pretty simple, with only a 21 second DV footage. And here I was switching tabs with my Browser, came back to the Project, and the Video Tracks were gone. I saved, closed Premiere, restated and the Video Tracks are still missing.
So I made a new Sequence, voilá the Video Tracks are there. Thus I need to copy and paste the Tracks onto the new Sequence.
But that is not really a solution!
I was on the Phone with Adobe, and on Chat, but they couldn't help me. They suggested to get a Tesla or Quadro Card, or at least a GPU that got confirmed as working on their page. I did that, but obviously, that is not the issue.

GTX 770 - Premiere Pro CC 2014 CUDA Problem

My GPU: Asus GTX770 DirectCU II O.C. 2GB
My GPU Driver: 347.88 (up to date driver)
Premiere Pro CC 2014 (ver.8.2.0)
CUDA detected but CUDA rendering not work. Please Help me...

You have me confused, your GPU is working perfectly. Are you telling me that in your projects you do not see it being used? Then it is evident that you are not using any MPE accelerated effects or features. Unless you use some of these effects or features:
Here is a list of the effects and transitions that can be accelerated by CUDA in Adobe Premiere Pro
Alpha Adjust
Basic 3D
Black & White
Brightness & Contrast
Color Balance (RGB)
Color Pass (Windows only)
Color Replace
Crop
Drop Shadow
Edge Feather
Eight-Point Garbage Matte
Extract
Fast Color Corrector
Four-Point Garbage Matte
Gamma Correction
Garbage Matte (4, 8, 16)
Gaussian Blur
Horizontal Flip
Levels
Luma Corrector
Luma Curve
Noise
Proc Amp
RGB Curves
RGB Color Corrector
Sharpen
Sixteen-Point Garbage Matte
Three-way Color Corrector
Timecode
Tint
Track Matte Key
Ultra Keyer
Video Limiter
Vertical Flip
Cross Dissolve
Dip to Black
Dip to White
Directional Blur
Fast Blur
Invert
Additive Dissolve
Film Dissolve
Here are some features that also are CUDA assisted
scaling (details here)
deinterlacing
blending modes
color space conversions
Unless you use things off this list in your workflow you will not see GPU usage.
I am not sure this list is completely up-to-date, new functions are added frequently

Premiere pro cc 2014 crashing my system

I have a new Mac book pro (2014) 16 gbs ram.. everything is upgraded to max. downloaded the new premiere pro CC 2014. and it's crashing my system every time.
it takes about 4 mins. with the spinning ball. Then all the processes and plugins load in. Then it says "premiere pro couldn't find any capable video play modules. Please update your video display drivers
and start again" WHICH IS FREAKING IMPOSSIBLE SINCE I AM ON A MAC BOOK PRO. So sick and tired of companies not working out glitches in this crap. Could someone please help. I am so
angry and frustrated here.
Sean

Somewhat figured it out and extremely frustrated.
I created another new user with administrative privileges. When i did this i got AE CC 2014 and Premiere Pro CC 2014 working. However, they will not work in my regular main account which has
administrative priviledges. On the phone with ADOBE they told me that it was a permissions issue and that it was Apple's Problem. Which I CALL B.S.!!!
I tried to repair permissions in disk utility knowing full well that it wouldn't fix the issue. How on earth would apple know what the permissions errors in folders or files are for Adobe products!!
I was very angry and upset with the Adobe technical support for this issue.
On the new mac pro i am using i was able to create the new administrator account and erase the old administrator account since i have 0 documents or old data that i have on it other than programs.
However, on my mac pro. I have well over 15 years of data on it including 100 GB of music, etc... that i simply can't just erase away. Not too interested in working on 2 different accounts either.
Not sure what to do now and i am extremely frustrated.

NEED HELP ASAP Updated to Premiere Pro CC 2014 and now .MTS files are unsupported/unrecognized

I Have Windows 8
3.4 Ghz 8 Core Intel i7
32 GB Ram
PPCC2014
I was using Premiere Pro CC for the last year or so and .MTS Files have worked fine. Since I upgraded. I can no longer use .MTS Files.
I sync all of my footage using Plural Eyes. I updated plural eyes so that it would work with the New Premiere Pro CC 2014 update.
I tried going back to Premiere Pro CC; however, that was updated as well. It does recognize the .MTS files there, but it doesn't import the new .xml correctly created from Plural Eyes 3.5
If anyone knows any help or workaround so I can complete my TV episode. That would be great.
Also, I would prefer not to have to Transcode anything. Hours and Hours and Huge files won't really work.
I've also looked in to Re-wrapping. I understand Clipwrap is great for that; however, I have Windows not Mac. Other options look way too involved. I'd really just like my Premiere Pro to work the way it's supposed to,.
Does Adobe Media Encoder Rewrap?
Anyway, any ideas would be helpful.
Thanks

Thank You, Thank You!!!! That worked. I had to "Link Media" to the new file path, after I renamed the parent folder; however, it's working!!!! Hopefully there will be a fix for that soon!

Nvidia GTX 970 and Matrox Mojito MAX Premiere Pro CC 2014

Good day everyone,
I am building a workstation and I would like to ask, if I can use both of the cards, The GTX970 for rendering and Matrox Mojito MAX for monitoring? I know, that Matrox card is hardware accelerating h.264, but is it faster than GTX970? If i can use this combo, how can I set? If i set the Mojito to preview, can I set the Mercury settings in the project settings for GTX970? Will it work? Thank you for respond.

The Matrox hardware has nothing to do with the Mercury settings. When you go to File > Export > Media, you will have options for "H.264" and "Matrox H.264" - choose the Matrox option as "Format" and then you will see dozens of presets to choose from. These will use the Matrox Max hardware acceleration. You can do your own test between similar presets (Adobe and Matrox) and decide for yourself which works better for you. Again, this only affects EXPORT and not "editing" in Premiere.
Thanks
Jeff Pulera
Safe Harbor Computers

Adobe Premiere Pro CC 2014 compatible with Nvidia 970 GTX?

Good afternoon.
I'm an owner of a GIGABYTE Nvidia 660 GTX Ti OC 2GB. The card is detected by Adobe Premiere Pro CC 2014 (Even though,i think,it said that it's not listed or something but will work under my own risk..Is there a way to check if it's certified/supported via my own program and NOT the typical "This is the list of supported GPUs"?)
Anyways,i was thinking of buying one of the new 970GTX cards to game on better,but also to make full advantage of it's properties to do much more faster encoding/exporting (you know,create a H.264 MP4 720p@29,97FPS file) than my actual 660GTX card with Adobe Premiere Pro CC 2014.
The thing is,any owner of such card (GIGABYTE,MSI,doesn't matter) have tried to launch Adobe Premiere Pro CC 2014 and export stuff by using the GPU's full potential to make everything faster?.. Because i have this fear of "Getting the newest n greatest Nvidia card so far and in the end see/notice it'll not work with Premiere Pro CC 2014"
....Can somebody please help me with this big fear of mine,please?
Thanks in advance
DV

Locked... duplicate discussion... see GTX 970 and Premiere Pro

Can't get GeForce GTX 560 Ti card CUDA to work with new Premiere Pro CC 2014 version

In the past I've been able to get CUDA on my GeForce GTX 560 Ti card to work with Mercury Playback engine by adding "GeForce GTX 560 Ti" to the cuda_supported_cards.txt file. But with the new CC 2014 version of Premiere, that file isn't in the Premiere Pro directory anymore. Is there a way to get my GTX 560 Ti to be listed as a CUDA-supported card with CC 2014?

Okay, I figured it out. I installed the latest graphics driver and then opened the NVIDIA control panel. In there I selected "Manage 3D settings" and went to the "program settings" tab. I selected Adobe Premiere (adobe premiere pro.exe) from the list and under the "CUDA - GPUs" feature, I changed it to "Use these GPUs" and selected my GTX 560 Ti (which was the only one listed).
After doing that, I opened Premiere Pro CC 2014 and selected "Project Settings - General" and was then able to choose "Mercury Playback Engine GPU Acceleration" under Renderer (which had previously been unavailable).
Hopefully this will help someone else if they encounter the same problem.

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

Premiere Pro CC 2014 very unresponsive while rendering on background with Adobe Media Encoder

Usually while I eddit videos on Premiere, I'm rendering on the background with AME. Or at least I used to. Some time ago, this process suddenly stopped working, as rendering on the background bagan to make Premiere really unresponsive, and quite impossible to work with. I couldn't think of any change I made other than switching my HDD, and I blamed it on that (it made sense because new HDD is one of those WD Green ones, a little worse than my old Seagate one). So I adapted to just queueing everything and start rendering when I was done edditing. But yesterday I installed a 240gb Kingston HyperX SSD, re-installed Windows and the main apps on it, and tried again, hoping to see an improvement. Now I was storing the original media on the HDD, running OS, Premiere and AME on the SSD, and rendering to the HDD. It did not work. Premiere still became slow while I rendering with AME. So I thought it might get better if the HDD was not reading and writing at the same time, and I switched the original media to the SSD, while still rendering to the HDD. Also didn't help. I don't know why this setup suddenly does not work, and I really need to fix it.
My setup:
Windows 7 Home Premium 64bit
Intel Core i7 2600 @ 3.4GHz
12GB of RAM
nVidia GeForce GTX 560 (yes, drivers are up to date)
Dual monitors (one for Premiere workspace and one for a bigger program monitor)
2TB WD Green HDD where I keep most of my junk (and media files)
240GB Kingston HyperX SSD where I run the OS and important apps (Premiere and AME included)
I'm running Adobe Premiere Pro CC 2014 (8.1.0 build) and AME CC 2014 (8.1.0.122 build)

Hi chriscorrell,
Thank you for posting on Adobe forums.
Upgrading your OS might be a good idea because Premiere CC 2014's OS requirement is OS X 10.8.
See here: System requirements | Adobe Premiere Pro
Thanks,
Rameez

Premiere Pro CC 2014 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:

Performance Issue Premiere Pro CC 2014 with Late 2013 Mac Pro

Hi all!
Im working Premiere Pro CC 2014 on a Late 2013 Mac Pro 6 core D700s and 32GB RAM on OSX 10.9.4
After the 2014 update i have experience some drop frames and hangs with a new 1080p timeline project.
And it later results in software hang and crashing . even after a quit (force quit) and re-poen, it seems to happen again and again.
Even after a system reboot seems to be fine at first, but it still crashes on the project.
Tired to render the timeline and still the same. Also tried to delete rendered file and play right with timeline with yellow bar, same.
Even drop the preview playback to 1/2 and still..
files are mixed 1080p footage from Canon 5d3, 60D, T2i.
I have 3 layers (interview video with different angles) and a title layer (hard subtitle)
had some light color correction with fast color corrector and a sharpening on the 5d3 layer.
Ive work with the CC premiere pro before with mac pro and everything is fine and never hand an issue.
All my memory setting are set for performance and i have open GL on my D700s
Im not sure if this a software issue or someone my hardware is not working right?!
Thanks in advance!

I am having the same issues.
Im working on a late 2012 iMac, 3.4 GHz Intel Core i7. 32 Gb ram, NVIDIA GeForce GTX 680MX, OS X 10.9.4.
I'm editing RED footage, about 3 TB worth for this project from a Promise Pegasus drive.
The software really slows down when using the TYPE tool and also when scrubbing through footage.
When I attempt to quite the software and restart, the interface goes away but the app is still running but says "not responding" when I attempt to force quit.
If you've figured it out since then Id love to know what works.
Thanks!
G

Premiere Pro CC 2014 ram preview or MPEG2 output is clipped with black on lower third

On my System Win 8.1 X64 Premiere Pro CC 2014 ram preview or MPEG2 output is clipped with black on lower third.
Premiere Pro CC had no problem, but as I upgraded to CC 2014 this problem revealed.
I clean installed Win 8.1 and Premiere Pro CC 2014, but the problem exist.
Please Help me reveal and solve the problem.
Thanks in advance.
System Configuration:
Mainboard: Supermicro X9DAE
CPU: Dual 2690
Graphic: Geforce GTX 780 Ti
RAID: Areca 1880

Does Anybody know the answer?

Where is a link to the Premiere Pro CC 2014.1 (8.1) update? - Can I get help with the ticktime.cpp-290 error?

Ola to precisando do premiere versao 8.1 caravan consegue o link?
Message was edited by: Kevin Monahan
Reason: needed better title

Hi Kevin,
I posted about the same problem (TickTime.cpp-290 error) in another thread, but since you're asking here specific questions to resolve it, I'm answering it here.
Re: Debug Event: [...\ ...\src\TickTime.cpp-290]
What were you doing when this error started to occur?
          Nothing special I remember. The only thing I do recall, is:
          I was working with Premiere Pro (where the main project is), After Effects but rendering some PNG sequence, and Adobe Media Encoder. I sent from AE to AME a project to render. Configured 2 outputs (PNG & MP4). The same way I sent from PP a project to render and one error occured. Unfortunately I didn't write down the error, but it was like a path C://AME_64/something. But the AME queue updated and everything seemed OK. I close AME to be sure that the error wouldn't be the source of future error during rendering, and relaunched it. And at that time I couldn't open it. I got the error "Adobe Media Encoder has encountered an unexpected error and cannot continue". The only way I found to resolve this is to remove the directory /Users/%USERNAME%/My Documents/Adobe/Adobe Media Encoder/8.0/". The problem seems to appear when I save the queue. And since that time, Premiere do the TickTime.cpp-290 error.
          Another thing I noticed, don't know if it was there before, is, the AEP file in AME queue setttings displayed framerate as "25 / 29.97 / 30 / ...", a 2 digits number for the framerate. But suddenly (I thought first it was because of the Premiere Pro file being added to the queue, but no because it appended after without it), it was displayed as "25 000 / 29 970 / 30 000", a 5 digit number.
          After that, the TickTime.cpp-290 appeared. Sometimes when opening project, sometimes and resetting or changing the workspace (because it was messed up), sometimes when closing.
Do you have iCloud installed?
          No.
Is this a Premiere Pro CC 2014.0 or Premiere Pro CC 2014.1 project that was updated to Premiere Pro CC 2014.2? If so:
          It started long time ago a draft in CS6, but since I reopen the project, I saved new versions in Premiere Pro CC 2014.2 (not sure if I have other version like 2014.1 or 2014.0). Is there a way to know which 2014 version are my files? If I look into the XML I only saw Version="28"
Do you have a copy that can be opened in an earlier version?
              An old draft version in CS6. But that version has footage in different framerate and not all be interpreted at the timeline framerate.
Do you get the same error in that earlier version?
               No error here, the file opens properly.
              Additional info: I tried to open the 2014.2 file on another computer (where PP 2014.2 is installed) and same problem (this computer is on Win7 64-bit)
Did you use any unusual footage types in your project?
     I used MOV (Animation), MP4 (H264), and PNG sequence. The framerates of the footages are 24,25,30 and 60fps (but everything has been interpreted in 30fps)
If you remove them, do you still get an error?
              When I had the error, but not when I open the project file, I resave the file removing anything not interpreted in 30fps (because at that time I still had footage interpreted in their original framerate). I was able to work for some time, but now I can't open it anymore despite that.
Was the fps interpretation changed in any of the clips?
     Since the error appeared, and because I saw in another thread that it could be related to footage of different framerate, my timeline is now in 30fps and all the footage have been interpreted in 30fps. Footage are MP4, MOV, PNG sequence in 24, 25, 30 & 60fps.
If so, restore them to their original fps and see if you still get the error.
              Unfortunately, since I can't open the project anymore, I can't test that.
Did you use Warp Stabilizer?
          No.
Do you have any browser plug-ins?
          What do you call browser plug-in in Premiere?
Are there any third party plug-ins used?
          I have Magic Bullet Looks 2, and I'm using it on this project.
If so, remove the effect from those clips and see if it improves the situation.
              Unfortunately, since I can't open the project anymore, I can't test that.
Some additional infos on my computer.
I use Windows 8.1 (64-bit), all Adobe softwares installed have the last update (for video apps, it's 2014.2)
The language settings are configured in French, but Windows and CC apps are in English.
If needed the 2014.2 project file is here:
https://dl.dropboxusercontent.com/u/68413846/showreel19_30fps.prproj
Thanks in advance to help us to resolve this weird bug.
Christophe.

Audio-Problem with Adobe Premiere Pro CC 2014 by using long Clips in AVC-Intra Codec (4Gb Border)

Hello
We own a Panasonic camera (AJ-PX5000G) and we film in 1080p50 with the AVC-Intra100 Codec. When importing longer clips in Premiere Pro, the video is fully loaded, but the waveform of the sound ends at the Time Code 00:02:28:35.
Sometimes the sound could be played after this Timecode but otherwise there is no audio. Even if we use the same clip several times we see that it works sometimes and sometimes not. It looks random.
We also tried to import the Clips with Adobe Prelude directly from the P2-Card but there are the same problems.
The Clips in 1080p50 AVC-Intra100 have a bitrate of 227Mbps. After 2 Minutes and 28 Seconds 4Gb are written on the P2-Card and the Camera starts a new picture file and 4 sound files..
It looks like Adobe Premiere Pro has problems with the correct relation of the files that all get together to one clip.
Is there anybody who can confirm this problem? Can anybody help me with this Premiere Problem?
Dennis
(Workstation: Dell Precision T3600, Intel Xeon E5-1620 @ 3.60 GHz, 16 GB RAM, Windows 7 Professional 64-bit, Service Pack 1, Premiere Pro CC 2014.1 (Build 8.1.0)   )
Mediainfo of the P2-Cards:
General
Complete name                            : \CONTENTS\VIDEO\0068T7.MXF
Format                                   : MXF
Format profile                           : OP-Atom
Format settings                          : Closed / Complete
File size                                : 3.92 GiB
Duration                                 : 2mn 28s
Overall bit rate                         : 227 Mbps
Encoded date                             : 2014-10-15 13:33:41.000
Writing application                      : Panasonic P2 2.0
Writing library                          : Panasonic P2 2.0
Video
ID                                       : 2
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High 4:2:[email protected]
Format settings, CABAC                   : No
Format settings, GOP                     : N=1
Format settings, wrapping mode           : Clip
Codec ID                                 : 0D01030102106002-0401020201323104
Duration                                 : 2mn 28s
Bit rate                                 : 227 Mbps
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 50.000 fps
Standard                                 : Component
Color space                              : YUV
Chroma subsampling                       : 4:2:2
Bit depth                                : 10 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 2.193
Stream size                              : 3.92 GiB (100%)
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Mediainfo Audio-Datei P2-Card:
General
Complete name                            : \CONTENTS\AUDIO\0068T700.MXF
Format                                   : MXF
Format profile                           : OP-Atom
Format settings                          : Closed / Complete
File size                                : 13.6 MiB
Duration                                 : 2mn 28s
Overall bit rate mode                    : Constant
Overall bit rate                         : 770 Kbps
Encoded date                             : 2014-10-15 13:33:41.000
Writing application                      : Panasonic P2 2.0
Writing library                          : Panasonic P2 2.0
Audio
ID                                       : 3
Format                                   : PCM
Format settings, Endianness              : Little
Format settings, wrapping mode           : Clip (AES)
Codec ID                                 : 0D01030102060400
Duration                                 : 2mn 28s
Bit rate mode                            : Constant
Bit rate                                 : 768 Kbps
Channel(s)                               : 1 channel
Sampling rate                            : 48.0 KHz
Bit depth                                : 16 bits
Stream size                              : 13.6 MiB (100%)

Hi,
we have the same problem!
It is not possible to play audio with the AVC-Intra100 Codec fluently.
Can anybody help?
Thanks,
Anja

Matrox Mojito Max with GTX 970 Premiere Pro CC 2014

Similar Messages

Maybe you are looking for