Premiere Pro CC 2014 (trial) interpreting XAVC S as AVCHD, is it normal?
Hello all,
Since PP CS6 doesn't support natively XAVC S and buying a codec pack is quite a few $$$, I decided to try PremierePro CC 2014.
Now, it can import the files fine. (XAVC-s 1080-60p) but...
However if I make a new Sequence from footage it makes the sequence a AVCHD format. Is that for export purposes only?
My problem is that as I go from frame to frame I am only getting 30 doubled frames, that is frame 1 and 2, 3 and 4, and so on, are identical. Both in the Sequence Monitor window and in the source window, so Premiere is not displaying the 2nd frame... just repeating the 1st...
The same files play well in Cyberlink Power Director (auch!) that is 60 unique frames.
Is this a limitation of the trial? It is pretty useless to shoot in 60p if premiere is only going to interpret it as 30p.
Elsewhere in the forum it just says that Premiere Pro is compatible with XAVC S but no where in the program or the help you can find anything about XAVC S and there are not Sequence presets for XAVC S.
Maybe there are some settings to be changed but Premiere does interpret the footage as 60p but it doesn't show the codec used (or better said, I can't find where it sees which codec
If any of you have any answers, please help!!!
Otherwise it looks like PowerDIrector is a better investment !!
Attentively
Javier Velazquez
stevemctee wrote:
I appreciate the sidebar conversations, and it is valuable information, but I am really hoping to hear from Adobe about why this card is not listed as supported by AE.
Oooh, I can answer this one too!
As of the development and release of CC, they're not working with the ray-traced renderer at all (other than to bring it into each version for compatibility reasons), so no more cards have been (or are going to be) tested and added to the white list.
It may be a bit before someone with the official A logo comes in. This is a user-to-user forum. We are grateful that Adobe folks poke their heads in a lot (seriously, the AE forum gets a lot of love considering how tiny the AE team is), but sometimes it can take a while for them to appear. (Especially if some of them are on holiday.) That's why they have folks like us around; we may not have A's, but we do have M's, V's, and P's
Speaking of the C4D integration: When I visited the Adobe team's offices recently, I got to have a look at some of the new technology they're working on for future versions. I am very excited about the future development of AE. The lines between 3d and compositing are really starting to blur. Some of the things that we are currently missing (expressions to control animation of C4D models, for example) are going to be addressed!
Now, if you are planning to do a lot of 3d work that is mostly titles and that sort of thing, I would suggest seriously looking at Element 3d or Zaxwerks 3d Invigorator. Element's latest version renders extremely fast considering how beautiful it can look. It's mind-blowing, really. (And it uses the GPU!)
Similar Messages
-
Premiere Pro CC / 2014 - Sony f5 XAVC - Codec Missing?
Hi,
I'm trying to import footage that was shot on a Sony F5 camera at 2k 24p with the XAVC codec at various frame rates.
I've tried this on both Premiere Pro CC & Premiere Pro 2014 - both say 'Import failure - codec missing or unavailable'
From what I can find, premiere should support these files?
Adobe Premiere Pro Help | New features summary
(Support for new camera formats)
Sony RAW (F65, F55, F5, FS700)
Any help / suggestions much appreciated
Thanks
Screen shot of my mac setup below.You can try to convert your files into other format then load them into your premiere. The xavc may be a hard codec to handle with.
-
I'm using premiere pro CC 2014 (trial version) for 4k editing.
but I saw the play sequence problem.
whenever I play the sequence cut off only window (premiere pro cc 2014).
but mac was fine.
I can't using realtime play.
my sequence setting information
sequence > sequence settings
editing mode : custom
timebase : 59.94 frames/second
video
frame size 3840*2160
pixel aspect ration : square pixels(1.0)
fields : no fields (progressive scan)
display format : 60fps
audio
sample rate : 48000 Hz
display format : audio sample
video previews
preview file format : quick time
codec : Gopro Cineform
Maxium bit depth : uncheck
Maxium render quality : uncheck
composite in linear color : check
check it please my workstation spec.
1. HP Workstation (Z840)
* CPU : Intel Xeon E5-2690v3 2.6Ghz
* RAM : 128GB
* Graphic Card : Quadro K5200Now I see is fully integrate with the OS preference. If you change the scale in windows resolution Preference, Premiere Pro scale too.
Thanks. -
Hi guys,
I believe this is just a bug in Premiere Pro CC 2014 (and other versions in the past), but I wanted to make sure it was on the PP team's plate for the next update, since it's detrimental to a workflow that include more than one computer or more than one editor on a project.
My team shoots a lot of footage in slow-motion (for instance, 59.94 for 23.976). Premiere's process to conform this footage is great. Modify -> Interpret Footage -> Assume this frame rate: "23.976".
Unfortunately, when we move this project file to another system, even if we are using a hard-drive that is synced to have the exact same source media files with the exact same file structure, we lose the footage interpretation metadata. Premiere Pro CC thinks this footage is 59.94 again, and our sequences are in shambles. All clips where the interpretation metadata is lost have "zebra pin stripes" on them wherever they exist in our sequences.
We have to manually re-interpret the footage, and then sometimes manually re-select in and out points. This is a work-around that enables us to push forward, but it's a barrier that makes collaborative editing extremely challenging and opens up rampant possibility for error. It's hard to locate every clip we need to re-interpret in some of our more complex projects, and even harder to avoid re-interpreting the wrong clips.
Looking forward to a resolution to this problem.
Daniel Lichtenberg
[ad/link removed by moderator]Guys I solved my own problem - thought I'd share with you how in case anyone else is having this problem -
I came across this thread
Premiere Pro CC error message and crash
which had the suggestion -
"Do tou have after effects installed? If yes, please try to import the main sequence into it and then export it as premier pro project from file/export ootion and then try to open that in premiere pro."
This didn't work for me too but I did try and import my existing project into a new project and copy all the files over. Works fine now.
I don't know if I will have the same issue again tomorrow so I'm going to render out a super high res video before I close premiere just in case -
Adobe Premiere Pro CC 2014.2 Trial Version - Error when importing mts and mp4 video files
First time using Adobe Premiere Pro (and I'm using the trial version). When I try to import an mts video file (and tried to import an mp4 file as well), I get the error: Adobe Premiere Pro CC 2014.2 has stopped working. And then the program crashes. Please help.
My computer specs: Windows 7 with Service Pack 1,Processor: Intel(R) Core(TM) i5-4570 CPU @ 3.2GHz, RAM: 4.00 GB, System type: 64-bitHi Catherine,
Welcome to the Adobe forums.
Please try the steps mentioned below and check if it works for you.
1. Launch Premiere Pro and create a Project, go to File menu>Project Settings>Renderer and change the Renderer to Software only mode, delete previews if you get a prompt and then try to import the clip.
2. If step 1 fails or the Renderer is already on Software only mode, go to Start Menu and search for Device Manager, go into Display Adapters and Right click on the Graphics card to select Update driver software option, on the next screen choose "Browse my computer for driver software", then choose "Let me Pick from a list..." option and from the list select "Standard VGA Graphics adapters. You might need to change the screen resolution of your screen and once done restart the machine again.
Launch Premiere Pro and import the clip to check.
Regards,
Vinay -
My Premiere Pro CC 2014 has finished its trial
My Premiere Pro CC 2014 has finished its trial and I have already payed for the creative Cloud in order to get the Premiere Pro CC 2014 and Creative Cloud only let me download Premiere Pro CS6. Why??? Can the newest CS6 version open CC' files?? What can I do? Help me please, I MUST finish an important project.
Thank you.
SunGironaHi SunGirona,
I have verified your account and everything is okay in our end.
Can you please try the following steps:
Solution 1: Sign out and Sign back in
http://helpx.adobe.com/creative-cloud/kb/sign-in-out-creative-cloud-desktop-app.html
Solution 2: Clean up cached user login information - Step 2 from the link
http://helpx.adobe.com/creative-cloud/kb/unknown-server-error-launching-cc.html
Solution 3: Reset your Hosts File - Step 3 from the link
http://helpx.adobe.com/x-productkb/policy-pricing/activation-network-issues.html
Please verify the Hidden folders for the Solution 2 and 3
http://helpx.adobe.com/x-productkb/global/show-hidden-files-folders-extensions.html
http://helpx.adobe.com/x-productkb/global/access-hidden-user-library-files.htmlg
Thank you.
Arnaud. -
Transcription Not Working in Trial of Premiere Pro CC 2014
I'm currently in a trial of adobe premiere pro cc 2014 and adobe media encoder. I am trying it specifically for the audio transcription and analysis featureset that final cut pro x lacks.
However, when I go to the metalogging workspace, right click on a clip and under the rename - there is no dropbown for analyze.
Also, when I select a clip and go to the window > metadata and under speech, there is no "analyze" button either. I can't get the transcription featureset to work - and I have used it before on a friends premiere pro cc....
Can someone help me understand what is going on and how I get the transcription working in premiere CC ASAP?
Thanks! - CI believe that feature is now defunct
Look here Update on Speech to Text functionality in video tools | Premiere Pro work area -
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 -
ICanon C100 playback issue premiere pro cc 2014
I am having playback issues in Premiere Pro CC 2014 with footage shot on my Canon C100 (29.97 fps). It was happening after doing a straight import and creating a sequence using "new item". Then, after reading some other threads here and elsewhere, I interpreted the footage so premiere would see it as progressive (no fields) rather than interlaced, but that doe not seem to help. It is even doing it when I play at 1/4 resolution. The only solution seems to be to quit and restart and reopen the project. Then it works temporarily for a little while but not long enough to actually edit. I have done projects in Premiere with C100 footage in the past and have not experience this level of difficulty.
My Media Cache is not going to the startup diskc(it is gong to the right place)
I am on a Mac 2.66 Ghz Quad-Core Intel Xeon
OS X 10.8.5
10GB 1066 MHz DDR3
NVIDIA GeForce GT 120 512 MB
Please help - very frustrated. If the solution is to transcode, it sort of kills the value of premiere in many ways.Hi,
This might help :
Go to File > Project Settings > General and change the Video Renderer to Mercury Playback Engine software only. Click OK and select Delete Previews.
Thanks,
Rameez -
Upgrading Premiere Pro CC to Premiere Pro CC 2014 in the middle of a project
Hi guys!
I was working through a project with Premiere pro CC until I checked my creative cloud app and realised there was an update for the software, Premiere Pro CC 2014. I thought great, I'll download it straight away.
It's a great bit of software and it does seem to be faster, however, whenever I play a sequence everything is fine and working as expected except the sequence monitor, which constantly freezes while trying to edit. Quitting the application and re-opening it is my only real solution so far as it's fine once I do this for a good couple of minutes until the sequence monitor freezes again
I was wondering whether I could get any help with this problem? I am using Yosemite as my OS and I have read up on many issues that have come about with adobe applications since the launch of Apple's new OS update. Someone recommended going back to the older version of Premiere Pro CC, but I've done a serious amount of work on the newer version now so going back is out of the question really.
I've spoken to quite a few people about the issue, like you do, and they are also a bit unclear of a solution. Some say its the graphics card. Some say I need to buy a new computer (I have an imac mid 2010 intel core i3). And most say to downgrade to mavericks again as adobe and Apple are still working on a solution for the near future.
I was thinking of re-installing premiere pro cc 2014 altogether but I am a bit worried that work may go missing if I did?
Any suggestions would be greatly appreciated!
TomThere is this offer of a trial version FC Pro X with 30 day runtime:
http://www.apple.com/final-cut-pro/trial/
Too bad you didn't have a complete backup that could run the previous OS X
and then you could resume using an earlier Final Cut Pro (10) or (7) since a
clone would have been a means toward that position.
http://www.apple.com/support/finalcutpro/
http://www.apple.com/support/pro-apps/
This appears to be another good reason to check out all the reasons why one
would want or need to upgrade a working OS X version, since these kinds of
events are known to happen as a direct result.
Sorry to not have an answer to this, other than try & use the Trial version...
Or see if someone at Apple sales/support can field your issue w/ an answer.
Good luck & happy computing! -
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: -
Hello,
I just installed Adobe Premiere Pro CC 2014 as trial to see if its working on my system but as soon as i launch it, it crashes with the following errors on splash screen: Adobe Premiere Pro CC 2014.0 has stopped working followed by Adobe QT32 Server CC 2014.0 has stopped working.
System Info:
Windows x64 bit
16GB RAM
Intel Core i7-4770 CPU @ 3.40GHz 3.39GHz
NVIDIA GeForze GTX 660 (fully updated)
I turned off Windows 7 Sync Center (suggested in adobe forums) but it didn't help.
I tried running it as administrator, and playing with the permissions but nothing helped.
Please help me with my problem.
Thank you,
JamesI have the same problem too.
I try format pc ans reinstall win7 64 bits totally clean, but nothing...
Drivers are update, intel i7,nvidia gtx 760,all works fine in all aplications and games.
When open media encoder or premiere or after effects crash is startup and show message adobeqt 32 stoped.
The sp1 are install too.
I think what adobe cc 2104 fails hards and adobe needs fix this.
The solutions how reinstall or update drivers not work, fix a problem please. -
Adobe Premiere Pro CC 2014.1 (graphic adapter problem)
"Adobe Premiere Pro CC 2014.1" but I downloaded the trial version; When I run the program, "Adobe Pro could not find any capable video play modules. Plasa video display drivers update ans start again" as a window opens.
Then the program shuts down.
I need your help in solving the problem.
Goodbye ..
"Adobe Premier Pro CC 2014.1" deneme sürümünü indirdim ama; Programı çalıştırdığımda, "Adobe Pro could not find any capable video play modules. Plase update video display drivers ans start again" şeklinde bir pencere açılıyor.
Daha sonra program kapanıyor.
Problemin çözümü konusunda yardımınıza ihtiyacım var.
Hoşçakalın..Dual video problems - Do you have dual graphics adapters?
Go to the Windows Control Panel and select Hardware and Sound and then select Device Manager... In Device manager you click the + sign to the left of Display Adapters... and see if 2 are listed
IF YES, read below
-http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
-http://forums.adobe.com/thread/1001579
-Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
-link to why http://forums.adobe.com/message/4685328
-http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2 -
Premiere Pro CC 2014.0 has stopped working
I have Premiere Pro CC 2014.0 installed
I can't install 2014.0.1 because it's simply not available despite being told the contrary from Adobe Communities moderators.
I'm using Windows 8.1
There is no actual error message from premiere, the message comes from Windows Problem Reporting which states: "Adobe Premiere Pro CC 2014.0 has stopped working... A problem casued the program to stop working correctly. Windows will close the program and notify you if a solution is available."
This error occurs during the launch of Premiere Pro.
This problem began to persist yesterday. It occurs while no other programs are running. I am running no third party codecs or add-ons to Premiere Pro.
Here is the AMT3 log file:
It's not letting upload this information.
The contents of this file suggest premiere pro is trying to return values in regard to license keys... So, I signed out and signed back in. I started Premiere and it asked me to sign in, I clicked sign in and it logged me in automatically... its said thanks then disappeared... It then brought up a dialogue saying I had 00 days left on my trial. It then went away and asked me to sign in again... I signed in and it said thanks and went away and started to load... Then the same thing happened : I get a white screen and a Windows Problem Reporting that Premiere Pro has stopped working.I have an enterprise subscription through Tulane University. Here is the amt3 log if it lets me upload this time.
09/11/14 14:53:15:976 | [INFO] | | | | config | | | 7956 | Using default media policy RET
09/11/14 14:53:15:979 | [INFO] | | | | AMT | | | 7956 | AMTImpl::AMTRetrievePersonGUIDWithAuthSource PersonGUID is : 48AD623B4FA80E1B0A490D44@AdobeID
09/11/14 14:53:15:979 | [INFO] | | | | EULA | | | 7956 | 48AD623B4FA80E1B0A490D44@AdobeID
09/11/14 14:53:15:979 | [INFO] | | | | EULA | | | 7956 | V7{}PremierePro-8-Win-GM
09/11/14 14:53:15:980 | [INFO] | | | | LicenseAgreementLog | | | 7956 | Called GetLicenseAgreementDetails
09/11/14 14:53:15:980 | [INFO] | | | | LicenseAgreementLog | | | 7956 | Called IsLicenseAgreementAccepted
09/11/14 14:53:15:980 | [INFO] | | | | LicenseAgreementLog | | | 7956 | passed type in IsLicenseAgreementAccepted 1
09/11/14 14:53:15:980 | [INFO] | | | | LicenseAgreementLog | | | 7956 | passed dguid in IsLicenseAgreementAccepted 48AD623B4FA80E1B0A490D44@AdobeID
09/11/14 14:53:15:980 | [INFO] | | | | LicenseAgreementLog | | | 7956 | passed driverleid in IsLicenseAgreementAccepted V7{}PremierePro-8-Win-GM
09/11/14 14:53:15:981 | [INFO] | | | | LicenseAgreementLog | | | 7956 | passed version in IsLicenseAgreementAccepted 1000
09/11/14 14:53:15:982 | [INFO] | | | | LicenseAgreementLog | | | 7956 | Successful in searchDocForAgreement, returning the child element
09/11/14 14:53:15:983 | [INFO] | | | | LicenseAgreementLog | | | 7956 | foundXmlElement in IsLicenseAgreementAccepted
09/11/14 14:53:15:983 | [INFO] | | | | LicenseAgreementLog | | | 7956 | outstatus being returned from IsLicenseAgreementAccepted is 0
09/11/14 14:53:15:983 | [INFO] | | | | LicenseAgreementLog | | | 7956 | return status from IsLicenseAgreementAccepted is 0
09/11/14 14:53:15:983 | [INFO] | | | | LicenseAgreementLog | | | 7956 | return status from GetLicenseAgreementDetails is 0
09/11/14 14:53:15:984 | [INFO] | | | | uiswitch | | | 7956 | EULA has already been accepted.
09/11/14 14:53:15:984 | [INFO] | | | | AMT | | | 7956 | This is a subsequent launch. Deferring services.
09/11/14 14:53:15:984 | [INFO] | | | | performance | | | 7956 | AMTObtainProductLicense took 95.203712 ms
09/11/14 14:53:15:984 | [WARN] | | | | AMT | | | 7956 | AMTGetParentLEIDLicenseStatus called.
09/11/14 14:53:15:985 | [INFO] | | | | SLCoreService | | | 7956 | Starting up SLCore 2.0 Release (build 2.0.1.360321).
09/11/14 14:53:15:985 | [INFO] | | | | SLCoreService | | | 7956 | Service construction took 0.1 ms and succeed.
09/11/14 14:53:15:985 | [INFO] | | | | AMT | | | 7956 | Parent LEID not passed Relying on Licensing LEID V7{}CreativeCloudEnt-1.0-Win-GM
09/11/14 14:53:15:985 | [INFO] | | | | SLCoreService | | | 7956 | Syncing to license store...
09/11/14 14:53:16:049 | [INFO] | | | | SLCoreService | | | 7956 | Found server mkey.
09/11/14 14:53:16:066 | [INFO] | | | | SLCoreService | | | 7956 | Loading license references...
09/11/14 14:53:16:068 | [INFO] | | | | SLCoreService | | | 7956 | Found 2 license file(s)
09/11/14 14:53:16:083 | [INFO] | | | | SLCoreService | | | 7956 | Parsing license file [10436989.lc2] succeed.
09/11/14 14:53:16:099 | [INFO] | | | | SLCoreService | | | 7956 | Parsing license file [243157053.lc2] succeed.
09/11/14 14:53:16:099 | [INFO] | | | | SLCoreService | | | 7956 | License store synchronization took 114.5 ms and succeed.
09/11/14 14:53:16:101 | [INFO] | | | | SLCoreService | | | 7956 | Query license: type = 5, duration = 1122 days, remaining = 1121 day(s) 14803 seconds.
09/11/14 14:53:16:101 | [INFO] | | | | PCCheck | | | 7956 | Royalty Bearing found.
09/11/14 14:53:16:101 | [INFO] | | | | PCCheck | | | 7956 | Protected Content found.
09/11/14 14:53:16:101 | [INFO] | | | | PCCheck | | | 7956 | Breaking Out!
09/11/14 14:53:16:101 | [INFO] | | | | AMT | | | 7956 | Return Code 3
09/11/14 14:53:16:101 | [INFO] | | | | performance | | | 7956 | AMTGetParentLEIDLicenseStatus took 117.028931 ms
09/11/14 14:53:32:720 | [WARN] | | | | PCDService | | | 7956 | Failed to remove key [LD_SESSION] in hive [976087041428704252227960]from cache : 769
09/11/14 14:53:32:721 | [DEBUG] | | | | PCDService | | | 7956 | No value for key [AdobeUpdaterCodeV2] in hive [{07BE616F-9E42-4C90-AF4F-0F32A5B088E7}] in master : 10
09/11/14 14:53:32:721 | [DEBUG] | | | | PCDService | | | 7956 | No value for key [AdobeUpdaterCodeV2] in hive [{07BE616F-9E42-4C90-AF4F-0F32A5B088E7}] in master : 10
09/11/14 14:53:32:721 | [DEBUG] | | | | PCDService | | | 7956 | No value for key [Updates] in hive [{07BE616F-9E42-4C90-AF4F-0F32A5B088E7}] in master : 10
09/11/14 14:53:32:721 | [DEBUG] | | | | PCDService | | | 7956 | No value for key [Updates] in hive [{07BE616F-9E42-4C90-AF4F-0F32A5B088E7}] in master : 10
09/11/14 14:53:32:721 | [WARN] | | | | AUMService | | | 7956 | config: No AdobeUpdaterCode found in configuration; AUM will be disabled.
09/11/14 14:53:32:721 | [DEBUG] | | | | ServiceLoader | | | 7956 | looking for library C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\updaternotifications.dll
09/11/14 14:53:32:722 | [DEBUG] | | | | ServiceLoader | | | 7956 | Found library C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\updaternotifications.dll
09/11/14 14:53:32:722 | [INFO] | | | | SLCoreService | | | 7956 | Shutting down SLCore 2.0 Release (build 2.0.1.360321).
09/11/14 14:53:32:755 | [INFO] | | | | SLCoreService | | | 7956 | Service destruction took 32.8 ms and succeed.
09/11/14 14:53:32:755 | [INFO] | | | | performance | | | 7956 | AMTReleaseProductLicense took 35.584194 ms
09/11/14 14:53:32:755 | [INFO] | | | | AMT | | | 7956 | END SESSION. -
I just downloaded the trial for Premiere Pro CC (2014), and the program keeps crashing every time I open or create a new project. I can idle at the "Startup Screen" but as soon as I open a project the program closes without warning. I've re-installed all Adobe products I have, re-installed the Microsoft Visual C++ Redistributable 2012 and 2013 to get new MSVCR110.dll files (which seems to be the file causing the crash) but nothing is helping. I've also looked in every thread I've found on this forum and a lot of people seem to be having the same problem, but no one had got any answers for how to solve the problem.
Anyone have a clue on what to do? According to others formatting the hard drives don't seem to solve the problem either.
Here's the crash log:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Pro.exe
Application Version: 8.0.1.21
Application Timestamp: 53c7b17f
Fault Module Name: MSVCR110.dll
Fault Module Version: 11.0.51106.1
Fault Module Timestamp: 5098826e
Exception Code: 40000015
Exception Offset: 00000000000740da
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1053
Additional Information 1: dac8
Additional Information 2: dac844fabf0ae09d193ac750f70263ad
Additional Information 3: 6e8b
Additional Information 4: 6e8b89b059d1639bd5ba176e9f652c56
I'm running a:
Intel i7-3770K, not overclocked
ATI Radeon 7850, not overclocked
16gb RAM
64-bit Windows 7 Professional with Service Pack 1Me too with this one have it randomly when just opening the same project and begining to edit
had it happen about 4 times now.
Latest update
Microsoft Visual C++ Runtime Library
Program C:\Program Fi...
R6025
- pure virtual function call
[ok]
Adobe Premiere Pro CC 2014.1 has stopped working
roblem signature:
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Pro.exe
Application Version: 8.1.0.81
Application Timestamp: 5426694c
Fault Module Name: MSVCR110.dll
Fault Module Version: 11.0.51106.1
Fault Module Timestamp: 5098826e
Exception Code: 40000015
Exception Offset: 00000000000740da
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: a22a
Additional Information 2: a22a26525c716a6a7fdf0a84944bf385
Additional Information 3: 9245
Additional Information 4: 9245cf38809b383bd6a86e3f052c9114
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Maybe you are looking for
-
Given iPod touch is not showing up on my iTunes when plugged in.
I got my brother's old iPod touch and am trying to sync in music from my iTunes. However, when I connected it to my computer, it won't show up on my iTunes as a plugged in device. I reset this device's settings and even removed it from my brother's a
-
Unable to edit "calendar" field of events with invitees
I am having a couple problems with the "calendar" drop-down field on calendar events. This is on a 4S, iOS5, syncing calendars with iCloud. If I create an event with an "invitee" (or add an invitee to an existing event), I can no longer change the "c
-
How to highlight a specific element of an array
I'm having some trouble selecting which element in an array has key focus. I want to be able to selectively highlight individual elements in an array of strings and set the key focus so that the user can immediately enter the text into that specific
-
Error on uploading EBS - Natwest UK
Hi Gurus Need some help on EBS Electronic bank statement, we are banking with Natwest - UK, Now I've done all the config work when I try to import the file FF_5 (RFEBKA00), I got an error Termination in statement no 00000 of acct closing record 62F m
-
Material doc, accounting doc, and profit center doc in vl03n
Hi All, In VL03N how can i see Material doc, Accounting doc, and Profit Center doc. thanks in advance, kumar.