Premiere Pro update problem and AME bug

After renaming the folders and emptying the Media Cache database in the Preferences I thought everything was working, that is until I exported my project to the updated Adobe media encoder. There was no audio playing back from the rendered file and my clips from the Canon 5d were missing which are not acvhd. This is a multi-cam project and the audio that was used was from the acvhd clips. Pretty weird..... So I tried exporting the project from within Premiere to bypass the AME and it worked perfect.

In AME, please go to Preferences>General and disable the Import Sequences Natively option. Then export the sequence from Premiere Pro to AME and see if the problem persists.
If this change resolves the issue, then we'll be interested in getting a copy of the project, if possible, to test with.

Similar Messages

Premiere Pro CC 2014 and AME using only 25% of CPU

Hello all,
I've been having this problem with Premiere PRO CC 2014 and that when exporting it uses only 25% of my CPU thus taking 4 times longer than CS6 to export the same file project. I read a couple of forums with people having the same problems, I tired disabling CPU parking, disabling "Import sequences natively" in AME but no result.
Quick PC specs:
i5 4670
16GB of RAM
GeForce GTX 760 4GB DDR5
Everything for Adobe including the video files in use are of Samsung's SSD drives. Using CUDA as the render engine.
Currently one hour and 4 minutes clip in 4k takes about 52 hours to encode in Premiere CC 2014 and 9hr to encode the same project in CS6. Any ideas?

Take a look at your GPU usage with something like GPU-Z to see if both Premiere versions are using the same amount of MPE GPU hardware acceleration. Actually with CC 2014 it might work faster because Adobe added in more 4k effects/features for GPU acceleration.
You might want to download our Premiere Pro BenchMark (PPBM) and run it on both versions. The H.264 very complex timeline has 4K material in it and usually shows Premiere Pro 8.xxx take about only half the time that Premiere Pro CS6 take to export that same timeline.

Premiere Pro Update Problem

Hi there,
after having installed the latest Premiere Pro update some media files are suddenly offline and when I try to relink them I get the message "Method of compression not supported". Can You please help me or tell me how to downgrade to the previous version of Premiere Pro?
Thx

@simon:
I don't think so:
http://forums.adobe.com/thread/1061692
Meanwhile found this useful guide:
http://www.mediacollege.com/adobe/premiere/pro/troubleshooter/media-offline.html

Premiere Pro audio problem and crash

Yesterday I got an error multiple times which then led to PP crashing.
I imported an audio track, placed it in my time line, and when i went to adjust gain is when it would freeze/error/crash.
The error i got was:
[/Volumes/BuildDisk/builds/MightySilt/shared/adobe/MediaCore/ASL/Foundation/Make/Mac/../.. /Src/Mac/MacFile.cpp-1104]

In AME, please go to Preferences>General and disable the Import Sequences Natively option. Then export the sequence from Premiere Pro to AME and see if the problem persists.
If this change resolves the issue, then we'll be interested in getting a copy of the project, if possible, to test with.

Premiere Pro 2.0 and Windows 7 - Direct Sound Input soundcard driver problem

My XP machine crashed, I reinstalled Premiere Pro 2.0 with Windows 7, and I got the following error: 'The Currently installed soundcard driver does not support Direct Sound Input. Recording audio is not possible.' The soundcard drivers are updated. Any ideas? Here's what I have: AMD Phenom II X4 965 Processor 3.40 GHz 8 GB, 64 bit. Thank you for looking.

Thanks! Though I upgraded to solve the problem, this is good to know.
Bob
Date: Wed, 9 Nov 2011 04:45:42 -0700
From: [email protected]
To: [email protected]
Subject: Premiere Pro 2.0 and Windows 7 - Direct Sound Input soundcard driver problem
Re: Premiere Pro 2.0 and Windows 7 - Direct Sound Input soundcard driver problem created by Steve-Italy in Premiere Pro CS4 & Earlier - View the full discussion
VERY VERY VERY EASY (now, when I solved the problem, not before...!!!)
Insert Micropone or any jack in Micropone Input or Aux Input, on your sound card or motherboard !
AND NOW YOU CAN USE PREMIERE PRO 2.0
Enjoy
Steve - Italy
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4015730#4015730
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4015730#4015730. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Premiere Pro CS4 & Earlier by email or at Adobe Forums
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

I just updated to Premiere Pro CC 2014 and it can't start up

I just updated to Premiere Pro CC 2014, and now I am seeing an error message saying it cannot find any capable play modules. I updated the driver for my graphics card (Firepro), and tried running as administrator with no change. I am running amd fire pro control center which doesn't have the speed settings that is suggested for this problem. For some reason, the original Premiere Pro CC can still open (luckily). I looked up this problem on the on the support page, and it is listed, but when I click the link it redirects me to the start of the troubleshooting questions. I hope there is an answer to let me use the latest version of Premiere!
[moving to Premiere Pro... JTS]

Same here! Screen shot attached. I'm running the latest MBP with max specs. Anybody there @ Adobe.......?
***UPDATE*** - it's pretty easy to fix yourself. Just follow these helpful instruction on Creative Cow: Re: CC 2014 startup issues : Adobe Premiere Pro

Premiere Pro CC's Warp Stabilizer BUGS...see for yourself. (7.0.1 & 7.1)

I'd love to hear from Adobe Staff on this one. Hopefully they can focus on fixes over features for the next update, especially for one it's most touted effects.
Warp Stabilizer works great at stabilizing clips in Premiere Pro CC...but I'm beginning to learn that it's quite buggy. The two bugs below simply cripple the user experience when you use the effect a lot like we do. Here's a link to a sample project with just 2 clips (around 1 minute in length each) on two separate timelines with each clip stabilized using the Warp Stabilizer effect. It's only a sample/test project meant to show the issue which can be MUCH larger in a longer/bigger project. Relink to any longer media and you'll quickly see what happens when you have multiple warp stabilizers applied to a Premiere Pro CC project and how problematic it can be.
https://dl.dropboxusercontent.com/u/105331144/Warp_Stabilizer_SAMPLE_Project.prproj
See for yourself.
Two VERY Annoying BUGS and One Unfortunate Feature:
BUG #1: (It affects 7.0.1 and the new 7.1 Release/Update)
1) With GPU Acceleration Enabled and both sequences open, once the timeline render bar has turned yellow, hit save.
2) Now toggle to the 2nd sequence and you'll notice a delay/freeze as the render bar switches back to red and then yellow again.
3) Now toggle back to the other sequence and you have the same thing occur. Then, you can toggle back and forth with no delay...until...the project saves (or auto-saves) again...and then the delay/freeze will happen all over again.
4) Side Note: Even when you right-click on the sequence in the Project window, there's a delay. Right-click on a sequence with no Warp Stabilizers and the drop down list pops up immediately.
What's the Big Deal?: When you have tons more warp stabilizer effects applied to multiple sequences, not only does it take a while to save, but when it does, you are forced to wait while Premiere Pro freezes momentarily. This affects AUTO-SAVE too!!! The more warp stabilizers, the longer the wait. Our sequences have delayed up to 30-40 seconds depending on how much we've used warp stabilizer in each sequence. Imagine if you have Auto-Save set to every 30 minutes or less, well that means that every 30 minutes or less you'll be forced to stop while premiere freezes up for 30-40 seconds or so (depending on how much this effect is used). Other effects do NOT have this issue.
BUG #2: (It affects only the new October Release/Update of Premiere 7.1...this issue is NEW and does NOT occur in 7.0.1!!!)
1) Take the above project into Premiere Pro CC 7.1 (again, this does NOT occur in the previous 7.0.1 release) and hit FILE>EXPORT>Media.
2) You'll notice a delay while the EXPORT SETTINGS popup opens.
3) Toggle to different "FORMATS" in the export settings window and there's more delays every time the format is switched.
What's the Big Deal?: Again, this is a small sample project. When you have a much bigger project with lots more Warp Stabilizers applied to many more clips this "delay" can extend up to several minutes!!! Yes, on a recent project over an hour with MANY warp stabilizers applied to lots of clips, it took 7 minutes for the Export Settings window to pop up after hitting EXPORT>Media. And there was about a one minute delay now when switching formats. This occurs whether GPU Accleration is enabled or not. It ONLY occurs on Premiere Pro CC 7.1
UNFORTUNATE FEATURE #1:
We obviously use Warp Stabilizer A LOT. It's a great effect. The above bugs cripple the user experience. This last issue isn't a bug, but rather a default setting on Premiere Pro's warp stabilizer that should be changed. Within the settings of Warp Stabilizer there's a section called "Method". The default setting is "Subspace Warp". That sounds pretty cool. But in practice, and we have had lots of practice (eg. THOUSANDS of clips stabilized in just the last few months alone (no exaggeration)), we've found that switching the default method to "Position, Scale, Rotation" is a MUCH more effective way to stabilize a clip. Most of the time it cuts down on that "wobble" that you might see in complex moving clips...but more importantly, 9 out of 10 times it crops the video either the same or less than when you use the default method. By "crops less" I mean that the "Auto-Scale %" is less. Of those 9 times, I'd guess 7 or 8 of them would crop in on the video less while the other 1 or 2 times there would be no change to the Auto-Scale %. Less scaling = better.
What's the Big Deal?: Well, as cool as Subspace Warp sounds, our numbers don't lie. Again, we use this effect on HUNDREDS of clips every week. When you have to go into hundreds and hundreds of clips every week and keep switching the setting so the effect will work better, it gets old real fast. We end up wasting so much time doing this but it's worth it because the results are undeniable. Why not create a CUSTOM PRESET???! Well, that'd be nice if it worked...but it doesn't. The problem with a custom preset like that is that when you drop it on a clip, it doesn't activate/analyze the clip automatically so you have to manually go into the settings and hit analyze which negates any time saved. It's be great if the default "method" was simply changed to Position, Scale, and Rotation. Or at the very least, it'd be great if one could create a custom preset that would automatically activate/analyze the clip it's dropped on (just like the original effect does).
(BONUS FEATURE: It'd also be nice to have the ability to set a "max scaling %" too so you never crop in more than a preselected amount...but first things first...fixes over features.)
NOTE: I'm on a 2011 suped up iMac running OSX 10.8.5

[r]Evolution wrote:
Would it help to Render these Warp Stabaliized clips instead of leaving them in the sequence w/ the Effect applied?
Any way to "Batch" Warp Stabalize your media before editing so the effect is not needed during the edit?
Sounds like you guys could benefit from having your shooters use a "Stabalizer".
Thanks for the rendering tip rEvolution. Rendering the clips does help with BUG#1, however, I'm not sure if it would truly save us any time because of the constant need to render and rerender tons of very short clips with this effect as we make adjustments to the edit. Warp Stabilizer is GPU Accelerated so playback is really smooth which is great but why does saving a project have any effect on this and cause it to freeze up? And then it works great...until the next time the project is saved. Using any other effect, there is no issue (that I've found) when a project is saved or auto-saved.
Rendering unfortunately has no effect on BUG#2 in Premiere 7.1 (again, this bug/issue did not occur in Premiere 7.0.1)
Regarding "batch" stabilizing...I'm not entirely sure what you mean. We do stabilize dozens of clips at a time before editing because it's imperative for us to know which clips (the sections we've pulled) will stabilize effectively. And then once the longer edit is complete we end up pulling all the best shots from that long sequence and copy/paste it to another sequence to make a 2nd shorter edit.
To say we've gone back and forth about the use of stabilizers would be an understatement. The fact is that we've spent almost 4 years creating a unique way to shoot based almost entirely around the effectiveness of warp stabilizer. It's taken years of trial and error but our style of shooting effectively allows us to mimick and thus replace the need for stabilizers, sliders and cranes. The extra freedom allows us to get MUCH more varied coverage of live events. It's different, I know, but it's fun and rewarding having a unique style. Granted the extra work is passed on to the editing side, but it's worth it IMO especially if these issues were addressed/fixed.
Regarding the "unfortunate feature" I mentioned, I would be satisfied knowing the default method works great for others if one were simply able to apply a custom preset of the clip with the adjusted method and it activated automatically and began analyzing the clip without the need to manually go into settings and hit analyze. That would be nice.
Thanks again for your input.

Why are Adobe Premiere Pro CS6 source and program monitors playing each others footage?

Why are Adobe Premiere Pro CS6 source and program monitors playing each others footage? I import my footage into the project like normal. I drag it to the source monitor on the left hand side to set in and out points then I drag it to the time line. The footage drops into the time line with no problem but when I go to play the footage in the time line it plays back on the source monitor and not on the program monitor like it is suppose to. Other times ill drag the clip to the time line and trim it there and it will be fine and show up on the program monitor. Then ill go try to set a clip to have in and out points (which is suppose to show up in the source monitor) but it shows up in the program monitor. The clip is not even in the time line it should not be on that monitor! I have updated the program to the late update. I have re installed the program numerous times and I have even ran the Adobe Clean up program. Couldn't find much on this problem. Please help thank you! I have a PC. My computer is also way over the recommended minimum specifications to have the program installed on.

Definitive Answer (I believe): It's all about this setting, "Write XMP ID To Files On Import" - which confirms that Adobe Premiere Pro is deliberately modifying the .mov file: http://helpx.adobe.com/premiere-pro/using/preferences.html#WSE3BD4A43-7022-4fe6-97F5-95313 935347B
These posts give some background as to why having this setting enabled would be beneficial: one benefit being to be able to skip conforming files by matching the conformed file with the original using the embedded XMP tag :-
http://helpx.adobe.com/premiere-pro/using/preferences.html#WSE3BD4A43-7022-4fe6-97F5-95313 935347B
http://www.dvinfo.net/forum/adobe-creative-suite/498627-why-premiere-modifying-video-files .html
https://forums.creativecow.net/thread/205/876064
(Found using Google search term "adobe premiere pro date modified")

Crash on launch with 4/10/14 Premiere Pro Update?

I just did the Premiere Pro update and now it's crashing every time I try to launch my project file. Is anyone else having this problem?
Edited by: Kevin Monahan
Reason: changed title for searchability purposes

Hi Patsy,
A few things to try for your crash on launch issue:
Change Preferences to Write: When you upgrade a Mac OS (as opposed to installing the new version fresh), Mac OS can set permissions of folders and files incorrectly. To fix this in the case of Premiere Pro, go to the preferences folder and set the entire preferences folder ( /Library/Preferences/Adobe/Premiere Pro/7.0 ) and all of its contents to be writable, not read-only.
Trash preferences
Make sure the System Preferences > Language & Text is set to English
Have an AMD GPU? Certain applications, like DaVinci Resolve install CUDA drivers, even if you have AMD GPUs. This can cause issues with Premiere Pro. See this blog post.
Sign out from the Creative Cloud application and then Sign in
If you have a NVIDIA GPU, update CUDA drivers in System Preferences > CUDA
These are things that have solved similar issues for other customers. If none of these things work, send me a PM and I'll escalate your issue.
Thanks,
Kevin

Why is Dynamic Link between Premiere Pro CC 2014 and After Effects CC 2014 not syncing audio changes?

When I try to use a Dyamic Link between something I've cut in Premiere and a composition in After Effects, if it is simply an audio level change it will not update in AE. Only if I alter the Video track does it then take the changes reflected. Any suggestions as to what is causing this?
Running Adobe Premiere Pro CC 2014 and After Effects CC 2014.

As Dave alludes, AfterEffects is all about the visual changes ... or at least, mostly. For changes to the audio outside of PrPro's internal controls, highly suggested you use Audition instead. It is all about the sound ... and yes, will update PrPro when used correctly.
Neil

Premiere Pro update failed - error code U43M1D206

Hi,
Premiere Pro update failed - error code U43M1D206
Windows 7 64 bits
All other apps were updated.
I tried all theses steps :
Solution 1: Restart your computer and try again.
Solution 2: Download the update from Adobe.com.
Solution 3: Uninstall and reinstall the Adobe Creative software you are facing difficulties applying the update too.
Avast Antivirus :
Infection MSIL:GenMalicious-ML [Trj]
Please look at the picture below :
Thank you for your help ;-)
Gilles

Hi Gilles V,
Please try: Error downloading Creative Cloud applications
Thanks,
Atul Saini

I need to create DVDs but Premiere Pro requires Encore, and Encore is no longer available

I had Encore installed, but it gave me error messages when trying to import a Premiere Pro CC 2014 file. Following the advice from the support listings, I uninstalled Premiere Pro, then downloaded and ran the Adobe cleanup file, which removed my copy of Encore. Now I can't find a way to download it again because it's only available if I download Premiere Pro CS6, and there's no way to find and download PP CS6.
I'm in the middle of a project for the Library of Congress, that requires me to send a DVD. Adobe should recognize that DVDs are still important for some applications, and should be making Encore as available as all the other applications in Creative Cloud. This has become a very frustrating process when it should be getting easier.

Are you sure? CS6 still shows up in my Creative Cloud app (which I upgraded moments ago, by the way).
Your point is that PR/EN CS6 is still available, and that is true.Your list is of the "installed apps" section and indicates that it is already installed. The poster indicates it was uninstalled and he should be looking in the "find new apps" area. Many users appear to be continuing to install PR CS6 with EN CS6. But others are having problems (as some have all along).
A new problem appears to be that users seem to believe they have to uninstall PR CC in order to add PR CS6. And some odd errors have added fuel to the fire.
The errors referred to by this user were probably no more than trying to dynamic link from PR CC to EN, which, of course, does not work.

How to work with Premiere Pro cs5.5 and After Effects cs5 together?

I have edited my movie in premiere pro cs5.5 and made the rough cut. In premiere, i have edited the video, put in soundtrack and foley. Now, i need to add muzzle flashes & blood splatters in some scenes and final color correction using After Effects cs5.
When i import the premiere project in AE and make the changes, and then i export it back as premiere project. When i open this prmiere project, it shows vaious kind of errors and no changes are retained that i did in AE. Also, when i import the premiere project (which has 4 different sequences) in AE, all the media that has been imported in the premiere project also opens in AE making it difficult to organize the media.
How should i work now so that i add vfx and color correction using AE cs5?
I thought of exporting the video from Premiere pro and then open the video in AE and add vfx to some scenes and color correction to the full video and render it out again. But, this is the first time i am using AE and i am not sure if this is the best way. PLEASE HELP.
Or, i could import the whole project in AE, add vfx, do color correction AND then export to video from AE. But i think, it will be better if i export the video from Premiere as it has loads of options to choose from while exporting to a movie.
The dynamic link does not work between Premiere Pro Cs5.5 and After Effects cs5. Even if it does, its not working on my pc.
All the footage is in HD and i want the final result in best quality HD too. PLEASE Help!

If you are working between After Effects and Premiere Pro but with versions that are not the same number, you need to just work with movies rendered and exported as intermediate, lossless files.
Dynamic Link only works between After Effects and Premiere Pro of the same version number, and only when they are installed as part of the same suite.

Premiere Pro 2.0 and Windows 7

Is Adobe Premiere Pro 2.0 (and other software included in ProductionStudio PRM 1.0) supported by Windows 7?

Harm,
Is it really that easy? So, there is no need to download Windows XP Mode and Windows Virtual PC (http://www.microsoft.com/windows/virtual-pc/default.aspx)?
Of course I would prefer to upgrade to at least Adobe CS4 Production Premium, but the best price I could find was $400 on studica.com. Or I could upgrade my Adobe Production Studio Premium to CS5 Production Premium for $800. But, these are not options for me right at this moment.
Thanks so much,
Angela

Premiere Pro CC Source and Program Playback Controls not working.. help please.

Hi,
Need your help to find out why none of the Premiere Pro CC Source and Program Playback Controls are working.. I can do playback using spacebar, but not clicking on the controls... same goes the rest.
Thank you,
Mauro

Dear Mark,
Thank you for the hint/link, reseting the toolbar did the trick.
Regards,
Mauro

Premiere Pro update problem and AME bug

Similar Messages

Maybe you are looking for