Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP

My recent update to Adobe CC 2014 apps has been an unmitigated disaster. Was running the 2013 version until last week and everything was just dandy. Very good performance and excellent render/encode times even for stuff with lots of filters and fx.
Since update 1-2 min videos with no fx or filters (or even transitions) have gone from exporting in under two minutes to well over 25 minutes. These exports are with the same presets I regularly use (Vimeo 720HD H.264).
I've been poking around the forums here for two days looking for answers and can't find anything that works. Tried the whole "App Nap" toggle as well as a few other tips. Didn't do squat. Looking for any hints/answers. Thanks.
Mac Pro Mid 2012
2 x 2.4 GHz 6-Core Intel Xeon
32 GB 1333 MHz DDR3 ECC
ATI Radeon HD 5870 1024 MB
OS X 10.9.5 (13F34)
System SSD 500GB
Cache SSD 500GB
Media HD 1TB

Hi MXSw,
MXSw wrote:
All right. More experimentation has been done. Seems like the renaming of Adobe folders fix prescribed in the link below might have helped a bit.
Premiere Pro CC 2014 renders are painfully slow.
You can rename folders, but I prefer to do it this way: Premiere Pro CC freezing on startup or crashing while working (Mac OS X 10.9, and later)
MXSw wrote:
Kicked out a 1 minute edit with some color/fx in under 10 minutes. Not as fast as in the past but at least the CPU seemed to be cranking at 500% and above per Activity Monitor. Its barely gone over 250% in previous attempts.
That sounds a lot better.
MXSw wrote:
Same 1 minute edit took 35 minutes however when I exported from a PP timeline using MXF clips instead of QTs. I assumed the QTs would speed up the process but in the past I've gotten great performance on big old RED raw files so still a bit of mystery why I can't approach the speeds I had prior to most recent CC update.
Maybe updating your project file has something to do with it. I'll keep my eye on this issue. Thanks for reporting.
Regards,
Kevin

Similar Messages

Media Encoder not starting from Premiere Pro

I'm having issues Exporting from Premiere Pro - I'd rather queue it through Media Encoder so I can move onto the next edit, but when I select Queue and Media Encoder opens, it doesn't do anything - simply sits there with "Not Currently Encoding" as opposed to importing the data to export.
Help?
Adobe Media Encoder, 6.0.2.81
Also installed other CC products Ps, Pr, Id, Lr, Ai, etc
I have run Adobe Updater but no updates available for Me.
Mac OS X 10.7.5 (Lion)
I am using Adobe Media Encoder through a Creative Cloud Membership subscription
Project is 6 minute film shot on Sony FS700 (AVCHD) and exports from Premiere Pro
No error message, just no action from the Application
Have not seen the problem before - most of my work is vi Canon 5D MK III, so maybe it's a Sony Codec issue? Though I have exported footage from this camera before though...
Apple MacBook Pro, 17",
I am using Mercury Playback Engine GPU Acceleration in Premiere Pro
Cheers

Finally got fed up and rang Adobe (if all else fails...)
Video Support Team Member opened my Library folder (Go\Go to folder...\~/Library/) then went into \Preferences\Adobe\Adobe Media Encoder\ and changed the folder called 6.0 to 6.0old (i.e. rename it to anything else), then hit Queue in Premiere Pro and the project successfully opened in Media Encoder and was able to start encoding.
Hopefully that helps someone else suffering the same issue!
Ollie

Slow render time in Premiere Pro CS4 (with fast computer?)

Hello people on the Adobe Forums,
I hope someone can help me with this question, it's been bothering me a long long time now and this week i have to make a decision, or fix the problem and keep this configuration, or spend money for a new cpu (i5 750) and a new motherboard. But i think this computer should do better then it does. I have the following configuration:
AMD Athlon X2 4600+
Nvidia GeForce 7800GTX
2× 1Gb OCZ memory (DDR, PC2400, 250mhz)
Storage Disks:
Seagate 320GB SATA (7200, i think)
WD 74GB SATA (10.000RPM, OS)
Hitachi 500GB SATA (also 7200, i think)
WD 1TB USB (SATA) (extern hdd)
WD 250GB SATA (7200, i think)
So, i don't understand the problem, Premiere is running very slow on my computer.. The rendering of a 5min piece of just a random movie takes like 3 hours! Just right now i am rendering some things I filmed with my mobile, it does like 1 frame in 10sec!! On most pc's with this vice versa!
So the cpu is not that old, and neither is the videocard, meaby the memory is a little bit low.. Could that be the problem?
Hope you people can help me out, i searched Google and everywhere but can't find anyone with this problem..
List of software:
- Windows 7 Ultimate
- Adobe Premiere Pro CS4
Drivers are, as far as i know, all up to date, i updated the Adobe programs too..
Describe source material, Codec: XDCAM-EX Movie (mp4)
But like i said, it happens too avi too, it think that was DivX..
I bought this pc second-hand, so it could be that something in the processor is already broken and i didn't notice it at all.. i searched like everywhere and also tried too reinstall the program but that doesn't work either..
Some more info:
http://www.creadion.nl/premiere/info.jpg
http://www.creadion.nl/premiere/info.nfo
http://www.creadion.nl/premiere/DxDiag.txt
Ohye, and the PPBM: http://www.creadion.nl/premiere/Output_PPBM4.txt
With friendly regards,
Marinus

Well, I'm helping other people too here on some dutch foras and i hate how people say things like "Doesn't work. Help" and just wait and wait for someone to answer. Plus i want to order my new hardware this evening (10:27pm now here), so meaby that's a 'cause' too, to make you people answer fast! (and it worked! hehe)
So, what i am thinking of right now is to upgrade the motherboard, cpu and ram.. The videocard can wait a little more:
- Motherboard: MSI P55-GD65 (not sure of this one, good reviews&tests, Asrock P55 Extreme is an option too.. be my guest to do another recommendation) (Asus P7P55D seems like a good option)
- CPU: Probably an I5 750 from Intel, heard good things about this one.. Although i've always used AMD..
- RAM: I really don't know, don't see many differences between the RAM sticks.. But yeh: OCZ Gold OCZ3G2000LV4GK
Sorry for no links to product pages, you have to do a little search, i only got some dutch websites, and i know for sure that you all having you're own comparing/specs websites (which i don't know) .
Thank you very much untill now, meaby i get another reply tonight.. Ohye, plans changed, i'm not ordering tonight anymore.. I'll do that tomorrow morning (I'll do a few calls to a view webshops and see if they got in stock, if so, i'm gonna drive (or go with bus) to one of them.. I need it really really quick, need to submit a project from school August 30
Thanks everyone!
Just took a look at the links you gave me, the Asus P7P55D is an option too!
Took a look at the links, added the "Asus P7P55D".
What i forgot to mention: I got a budget with a max of like €400,- (That's like 510usd, I don't even really have the money) so I can't buy a whole new pc..

Long render time with premiere pro CS5 lately, help!

lately my premiere pro CS5 render extremely slow
i have a 6GB ram 64bit windows 7
is it normal to render a 10 minutes quicktime/h264 codec in 5 hours?
please take a note that this happened recently, so i think my pc spec. should not be the problem
thanks in advance

You start off with the wrong sequence settings. To resolve that, right click on a clip in the project panel and select 'New Sequence from Clip". That will give you the correct sequence setting for your source material.
When exporting, never use QuiRcktime, since it is a 32 bit application, plagued with numerous severe problems, hence the name. Use plain 64 bit H.264 codec for exporting. If you use Maximum Render Quality, your export can take many times longer than without that checked.
Your memory and presumably the rest of your system (please give details) is not up to this task, especially not when you start with the wrong sequence settings, export with a 32 bit codec and have MRQ turned on.

Encoding for Encore from Premiere Pro - File Size

I'm working on a Blu-ray project that contains four separate tutorials, each with several individual clips. I exported each clip (chapter) out of After Effects CS6 using the standard H264 preset. The tutorials range from 2 to 5 hours each. After all was said and done, the total file size of all H264 video clips was just under 25GB, perfect for a Blu-ray burn.
I created four sequences in Premiere Pro, one for each tutorial. All of the H264 video files were brought into Premiere Pro, chapter markers were added, ready to rock.
When I attempted to export each sequence using the H264 Blu-ray preset, I found that using that preset would result in a grand total of about 75GB worth of data. So I selected the MPEG2 Blu-ray preset, and it was almost the same. I manually adjusted target bitrate settings, dropped quality to as low as it would go, and still the estimated file size far exceeded the 25GB I had available.
All tutorials total about 15 hours of 1280x720 30p content. I realize that's a ton of data, but AE exported all of this content using H264 and the grand total file size was under 25GB. But bringing those very same video clips into Premiere Pro, assembling them, and exporting them results in much, much larger files. I even attempted to import the AE exports directly into Encore to avoid having to re-encode anything, and still it estimated that the project's file size exceeded 75GB, even though the source footage of H264 video was less than 25GB.
Right now I'm down-rezzing all of the footage to 720x480 and the file sizes are smaller, although I'll still need to decrease the bit rates significant if I have any shot of dumping all of this onto a single 25GB Blu-ray.
I do realize that 15 hours is a lot for a single disc, but what I don't understand is how I can have 15 hours of H264 exported out of AE result in less than 25GB, but using that exact same footage in PPro/Encore results in over 75GB of footage.
Any insight would be appreciated.
Windows 7 64-bit
Adobe Creative Suite Production Premium CS6
(After Effects/Premiere Pro/Encore)

The thing is, the AE exports look just fine. (The tutorials are just a bunch of screen capture/software stuff.) I didn't mess with any of the default preset settings for H264 out of AE, but yeah, they must've been encoded at pretty low bitrates.
I wasn't aware that BD specifications have minimum bitrate requirements, so that would explain why I'm unable to decrease the bitrates within PPro or Encore. Thanks for the info on that. I just figured as long as the footage was at least 720P with square pixel ratio encoded in H264 or MPEG2 I'd be fine, but apparently not!
The tutorials are for my own personal use, so I'm not too concerned about decreased resolution if I am able to make the SD content fit. Otherwise, yeah, burning multiple discs is my only option.
Thanks for the prompt feedback.

I am trying to export a video from Premiere Pro. I have both audio and video checked and the sequence is active but only the audio exports. There is no video at all. Can anyone tell me how to get the video to export. It was working fine until today.

Premiere Pro CC has been working fine until today. I have completed my sequence and it is active. I have both audio and video checked when I am exporting using H.264 with Match Source Hi bitrate. I am choosing entire sequence. The audio exports but the video and title does not. Can anyone tell me how to troubleshoot this so I can complete this project? Please!

Greetings,
I've never seen this issue, and I handle many iPads, of all versions. WiFi issues are generally local to the WiFi router - they are not all of the same quality, range, immunity to interference, etc. You have distance, building construction, and the biggie - interference.
At home, I use Apple routers, and have no issues with any of my WiFi enabled devices, computers, mobile devices, etc - even the lowly PeeCees. I have locations where I have Juniper Networks, as well as Aruba, and a few Netgears - all of them work as they should.
The cheaper routers, Linksys, D-Link, Seimens home units, and many other no name devices have caused issues of various kinds, and even connectivity.
I have no idea what Starbucks uses, but I always have a good connection, and I go there nearly every morning and get some work done, as well as play.
You could try changing channels, 2.4 to 5 Gigs, changing locations of the router. I have had to do all of these at one time or another over the many years that I have been a Network Engineer.
Good Luck - Cheers,
M.

Render times in Premiere Pro CS6

In this otherwise very helpful article (link below) can anyone tell me if the numbers referred to in this table are hours: minutes, or minutes: seconds? In other words, by 8:16, do they mean 8 hours and 16 minutes, or 8 minutes and 16 seconds?
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/products/creativesuite/produ ction/cs6/pdfs/adobe-hardware-performance-whitepaper.pdf

minutes & seconds.

How to increase render speed in premiere pro

Hey Everyone,
Is there a way to speed up the render time in premiere pro? I do realize on my mac the processor isn't the fastest. I have 8 gigs of ram and But, I have all other programs closed, I only have premiere running and I don't have a lot of special effects. I only have some keyframes but nothing complex. Does anyone know what is going on? Every time I make a small change it takes hours to render a small section. When I started this project it didn't take as long. I only select the option to render the change I just made and not the whole video. Does anyone have any suggestions? Thanks in advanced and an intel core 2 duo processor which sin't the fastest but for a small change and a simple video 4 hours to render a section is ridiculous and frustrating and this didn't happen before.

There are two primary things you can do to speed up rendering.
1. Get a faster CPU
2. Turn on hardware acceleration. (Or if already turned on, get a faster GPU.)
There are some secondary actions you can also do.
1. Add more memory.
2. Get more/faster hard drives.
And finally a third method which may have some limited application.
1. Avoid QuickTime.

Exporting from Premiere Pro CS4 using Media Encoder gets stop error

I am trying to export my timeline from Premiere Pro CS4, using the Adobe Media Encoder CS4 to export my timeline as an MPEG2 HDTV 1080 24, and it goes for about fifteen minutes then I get the blue screen and my computer restarts, telling me the program had a stop error. Is there a way to go around this step? Another method to get the mpeg2 without losing quality? Anything I can do?
Please offer any knowledge you have before I scream at my computer again.
Thank you

as I know Adobe products are buggy no matter what hardware you have.
I am sorry, but my experience has been the absolute opposite of what you have heard, or experienced. I have used many, many Adobe programs for almost 2 decades (maybe even more than 2 decades?), and have never observed such. I do have to admit that over those many years, I have always had a "state of the art" computer, but have made plenty of $ using Adobe software. Even with my now aging workstation, things work great. Time to upgrade though.
When troubleshooting issues, they shake out like this:
1.) system
2.) Assets
3.) Project
4.) OE
5.) Bugs
This is after troubleshooting Adobe issues from almost the time that PS hit the PC, when they were only NNTP, in what, 1985?
Now, I am not saying that your issue IS hardware, but only that that is the most likely issue, given a BSOD. Also, system is the #1 cause of issues, so that is where I start.
Good luck,
Hunt

Media Encoder crashes when exporting from Premiere Pro

Media Encoder crashes when exporting from Premiere Pro. I am queueing multiple files for export and Media Encoder will crash. The computer system has 32GB of RAM and the videos export fine in Premiere, but that requires exporting each one individually. Each video file is being down converted and some can be quite long (upwards of 3-5 hours). Nothing else is running on the computer that would take up memory.
Any idea why Media Encoder will crash?

Try turning off GPU acceleration.

Is there a way to set a default "Source Range" in AME when exporting from Premiere Pro CC?

When exporting a sequence from Premiere Pro CC, you are able to toggle between 4 drop down options within Adobe Media Encoder on what Source Range you'd like to export (Work Area, Sequence In/Out, Entire Sequence, Custom) as seen here:
Is there a way to set the default Source Range to something besides Sequence In/Out?
My reason for asking is that sometimes I export multiple sequences at once using AME's Queue. I add my custom presets to each Sequence and hit export, but SOMETIMES I may have accidentally marked an in point on my timeline and by default it's set to export only that In-to-Out part of the sequence.
I know what you may be thinking...well, just don't add any In/Out points to your sequence on the timeline or clear them first. The trouble is that I often don't see them or catch them when working quickly. In Premiere Pro CC, I use the "Lighter Brightness" Appearance setting because it's easier on my eyes after editing 10 hours a day, 6 days a week. Sure, darker looks cooler, but it kills my eyes for some reason. Anyway, PPro CC has a troublesome appearance issue in CC where it's not "optimized" for editing when you change it to a lighter appearance like it was in CS6. I've already contacted Adobe about this and another appearance issue (involving highlighted clips when in Lighter Appearance setting) and they are "actively working on fixing this appearance issue asap".
For reference, here's Premiere Pro CC in/out points in default dark appearance (notice the slightly lighter grey area):
Now here's that same in/out in "Lighter Appearance":
Not exactly optimized. Can hardly see it. Good luck spotting that little guy on a long timeline. Sadly, this affects in/out points in the Source Window as well. Really hard to see.
Conversly, CS6 looked the best (the blue REALLY stands out making things easy to see):
So my question again...is there a way to set the default "Source Range" to something else besides Sequence In/Out so that I don't end up doing what I just did and leaving for several hours while batch exporting only to come back and find that I exported only a "portion" of one of my big sequences?
Thank you!

shooternz wrote:
Here is the solution: Slow down. Give your project some love. Smell the roses.
Agreed about the roses but alas my next project always calls. Actually, I think what happens is I give each project SO much love that when it comes to exporting, I've run out of time.
shooternz wrote:
Then it would not be a default...it would be an option and you already have that option.
Semantics aside, I would love to be able to have it at least default to whatever option was last chosen. Or, perhaps I shouldn't use the word default again...I'd love it to simply remember my preferred setting. That's all.

Pushing and pulling from Premiere Pro CS 5

Hi,
Recently, I came across a problem and I was wondering if you could confirm this is a limitation within Production Premium CS 5 or whether I am doing something incorrectly?
If I render a sequence within Premiere Pro and push it to Encore via Adobe Dynamic Link, the rendered sequence correctly shows its rendering within Encore. However, if I render my sequence, save, and exit from Premiere Pro and then start Encore and pull the sequence from Premiere Pro via the Adobe Dynamic Link, I don't necessarily keep the rendering. I know that this has happened when using a 64-bit plugin from a third-party. The sequence shows with a watermark as if it had never been registered. The problem further manifests itself by, when I restart Premiere Pro, while the rendering looks intact, if I click on the third-party plugin as if to modify it, it won't let me make changes until I delete the already rendered sequence. It seems like somehow, the sequence has become corrupted.
Any thoughts - is this a known problem? Has this been addressed with CS 5.5? Are there plans for this to be addressed? Is there a workaround?
Thanks,
Steve

JSS1138 wrote:
The pros are faster encodes with superior quality. I use the free HC Encoder for MPEGs. You'll also need Avisynth to use it. The process is somewhat cumbersome, but if you have the time and want the quality, it's noticeably better, in my opinion.
To add to this, I've been producing commercial blu-rays using the free x264 encoder. The quality is unmatched by any commercial encoder, however there are some features absent that some commercial producers need (such as the ability to directly place I-frames, re-encode a section of GOPs with different bitrate targets, etc. which commercial encoders like CineVision can provide). If you don't have any need for those, x264 is the way to go. As quality is more important to me than bitrate, I use the single-pass constant ratefactor "--crf" mode with something better than the default, like 18 or 16, and it has never let me down.
Just be prepared to wait a while if you have a longform project. x264 is very fast, taking advantage of multi-core machines, but it cannot utilize the GPU/CUDA for encoding. A 3.5 hour 720p60 project (over 750,000 individual frames) at maximum quality takes a full 24 hours to encode on a 3.2GHz core i7, with all hardware threads at 100% (so make sure your machine is stable if it is overclocked!).

Premiere Pro CC 2014 keeps freezing when loading projects from Premiere Pro CC

Hi everyone,
I'm reporting this issue in case someone else would have the same problem.
I just downloaded the 2014 version of Premiere Pro CC, and when I'm loading a project from Premiere Pro CC into CC2014 I have the software freezing and being unable to even play the loaded sequences. It seems that dynamic link is having trouble linking the CC and the CC2014 version of Premiere Pro.
Until now the only solution I found was to kill the process of the software and start it again, after 8 times I got my sequence loaded alright, then sometimes it is freezing again, killing process, starting software again, and so on. Does anyone has the same problem ?
I'm running a Windows 7 Ultimate PC with 12Go RAM dedicated only to Premiere Pro.
Cheers,
Vincent

Hi Vincent,
I feel your pain, you are not alone. Here are my machine specs and my very frustrating situation, if anyone has any idea as to how I should move forward, I would really appreciate the input/advice...
iMac - 27" Late 2013
Processor 3.4 GHz Intel Core i5
Memory 12 GB 1067 MHz DDR3
Graphics NVIDIA GeForce GTX 780M 4096 MB
Software OS X 10.9.4 (13E28)
I'm having similar issues that began when I installed Premiere Pro CC 2014, and actually got worse with the latest update/release. The majority of my projects worked fine at first, but the update last week ended that quickly. I did what I know I never should do and updated Adobe CC while completing a project on a deadline. I thought some of the fixes would help me complete the project sooner. Needless to say, the deadline has passed, my client is pissed enough to not pay me or hire me again and I'm stuck with an almost-there version that I can't export correctly because of this software. This is my problem, not Adobe's, but I didn't expect such a detrimental update to halt my operation.
After doing some research, I found that some plugins could be the cause of some specific editing issues, mainly due to incorrect or inaccessible folders - who knows if its Dynamic Link, CC apps or 2014 apps. I concluded that my issue at the time was a plugin permissions issue on the Adobe "Preference" Folder, so I reset the permissions on the folder so that CC and 2014 apps would be able to access its contents without any problems. This was the wrong decision. For some reason, resetting this folders permissions also effected the main HDD, it's Kernel Text files and their respective permission. I could not boot my machine, just got the Apple and spinning wheel until I had to power down. I ended up on the phone with 3 different AppleCare reps who helped me at least be able to turn the machine back on and access my desktop/files, apps, etc. Outside of this, no one could offer anything other than "Uninstall the problematic application, reboot, reinstall, etc..." or "Backup your files and reimage the HDD." When I mentioned the recent CUDA driver update for my graphics card (NVIDIA GeForce GTX 780M 4096 MB now running CUDA Driver Version: 6.0.51), it was like they had never heard of graphics cards being used in their machines.
Resetting permissions on Adobe Preference Folder...
This is what I read would get the CC and 2014 apps communicating correctly so that they could utilize my plugins. There is a problem, I believe, in that their are TOO MANY locations where Adobe folders/components live. There are 3 "Preferences" folders that I found, and I don't know which effects what process, but the folder I changed permissions on clearly effects the operation of all of the CC & 2014 apps I had installed, as well as my HDD. Kernel Extensions and the entire system.
Based on my perceived effects of the Preference folder, I needed to uninstall everything, run the Adobe CC Cleaner Tool, download/install just the 2014 releases and see if that resolved the issue. I'm not downloading CC apps, the 2014 releases should run fine on their own. I've yet to confirm this with Adobe, as what I've read has simply said to install the new release next to the CC apps, rather than on top of, as traditional update releases work. Anyway, one by one, I reinstalled the 14 apps that I use on a regular basis on a "clean" machine with no trace of previous Adobe apps.
After reinstalling (without any plugins), I was at least able to open Premiere Pro from the Application folder and work for a few minutes before both Program and Source monitors froze and had to force quit the app. If I try to open the Project File by double clicking it in the Finder, SpeedGrade opens up instead of Premiere Pro - never seen that before. I also had to force quit to end that process and reopen in Premiere instead of SpeedGrade.
So back to Premiere, if I do have success in opening a project in the right application, Premiere freezes - if not immediately, eventually it will just stop responding. The video clips, sequence segments and UI freeze, but the audio will keep playing until I force quit. When I force quit, Premiere Pro doesn't close entirely. The UI closes, but the process still runs. I've even force quit from Finder, force quit again from the Dock, Shut Down the machine, restarted and Premiere Pro will still be open, but "Not Responding", so I force quit again and open the project. Just now, I opened PP, made minor edits to a sequence, sent it to Media Encoder, exported, but the video I tested exported without audio. I force quite PP twice just before that and it is still running now, but again, it is "not responding".
Ultimately, none of this works, nor have my attempts at resolving these many issues. One thing I know is that there is something VERY WRONG with either the latest release/update to 2014 apps, the Preference folder or the permissions that were changed.
As I mentioned previously, and what I think is a major oversight by someone at Adobe, is that for some reason the permission changes to ONE Adobe folder also effected my entire system and Macintosh HD. Some Kernel Extension files went missing, which is never good and should not happen when resetting folder permissions, so I believe my issues are far greater than the faulty Adobe CC 2014 applications, and is the cause of many of my problems right now. If I can't get things sorted soon, I'm going to reimage my HDD and start from scratch. As much as I would like to avoid this, I really have no choice if I want to get back to work and not lose clients over inexplicable technology issues.
If I find a solution, I will repost, but I think Adobe has to make some serious fixes on this release before anything is resolved entirely. I pay them monthly and rely on their software and platform to work without issue, which is foolish - I know, but I've used CC since it was introduced and it has work well enough until now.
Is there anyone at Adobe that can offer some advice??

Exporting from Premiere Pro CC 2014

Hello there,
Every time that I am willing to export my project my Premiere Pro CC 2014 stop responding all together. I tried the short cut (Commend+M) or going through the Manu bar. the result is the same, Premiere Pro CC 2014 just freezes and does not respond to anything till I force quit it and restart it allover again. I tried exporting from Premiere Pro it self, without using Media Encoder, but the problem remains the same.
I am using the new Mac Pro. I heard Adobe Premiere Pro is experiencing problems with the New Mac Pro. Is that true? Or is there other issue?
Thank you and looking forward to hear back,
Maruf

Hi Maruf,
Maruf Noyoft wrote:
Kevin,
I reset as you suggested and it took care of it.
Great!
Maruf Noyoft wrote:
So, if you don't mind explaining me the cause of the problem that I had? Or
an article about it. It is just for me for getting to know better the program and the system.
Thank you very much and appreciate your help enormously.
Since preference files get touched by the application frequently, there is always the possibility of their corruption. When this happens, you start to see what we call "unexpected behaviors" from Premiere Pro. This problem happens infrequently, but it is a good first troubleshooting step to try on your own. This is the case with most every non-linear editing application I have used over the years (Final Cut Pro, Avid, Media 100, etc.).
Thanks,
Kevin

Big problems exporting from Premiere Pro CS3

Hey all.
Would be massively grateful if anyone here could help me out. I'm in the process of trying to export a 23 and a half minute project from Premiere Pro CS3. I've tried exporting to different formats, (Quicktime, MPEG2, etc..) but keep arriving at the same conclusion. The process will freeze midway through, and I'm greeted by the following error messages:
"premiere pro debug event
premiere pro has encountered an error
[..\..\Src\PPixHandleUtilities.cpp-114]"
When I close that, another window pops up saying;
"export error
application failed to return a video frame.
cancelling the operation."
I'm not really sure where to go from here. Previously during the process of editing this project, I would occasionally get a message telling me that premiere pro was "running low on system memory". Fearing this to be the problem I was having while exporting, I attempted to export an extremely low quality version of the project, but arrived at the same conclusion. I also wondered if there was a corrupt frame or clip somewhere that was causing the issue, so I overlayed one whole transparent clip over the whole sequence and tried to export, but again, the same result.
I now have to put all my faith in you Adobe Wizards! Please ask me any questions that might help you to arrive at what may be causing the problem, I'll answer them the best I can
Many thanks!
Andy

>13.4GB free
FAR too small !!!
The program itself uses more than that for temporary working files
Also, unless you already have a 2nd hard drive or eSata external, you are below specification
Trying to use only ONE Hard Drive for Video Editing
You are a music conductor, with a baton that you use to point to various parts of the orchestra... this is like Windows pointing to various parts of the hard drive to do Windows housekeeping or to load program segments for various functions
Now, at the same time and with the same hand... while still using the baton to conduct the orchestra... pick up a bow and play a fiddle... this would be doing something with your video file at the same time as all the other work
You as a person cannot do both at the same time with the same hand
A computer is a LITTLE better, in that it can switch from one kind of task to another very quickly... but not quickly enough for EASY video editing
You need AT LEAST two hard drives (separate drives, never a partition http://forums.adobe.com/thread/650708 for more) with Windows (or Mac OS) and software on your boot drive, and video files on a 2nd drive so the boot drive is not slowed down by trying to do everything
Partition = Crash http://forums.adobe.com/thread/957286
I find that the three drives I use work very well for me, for editing AVCHD video... some people use a 4th drive, so video INPUT files are on drive three and all OUTPUT files are on drive four... I only bought a mid-tower case instead of a full tower case (my bad... but had to fit in the space available on my office desk!) so I use the three drives that will fit
Depending on your exact hardware (motherboard brand & model AND USB2 enclosure brand & model AND external hard drive brand & model) AND the type of video file, you may... or may NOT... be able to use an external USB2 hard drive for SD (Standard Definition) video editing
Steve Grisetti in the Premiere Elements forum http://forums.adobe.com/thread/856208 and Jim Simon in the Premiere Pro forum http://forums.adobe.com/thread/856433 use USB externals for editing
A USB3 hard drive connected to a motherboard with USB3 is supposed to be fast enough for video editing (I don't have such, so don't know) but eSata DOES have a fast enough data transfer for video editing... I have not used the eSata Dock below... for reference only, YMMV and all the usual disclaimers
http://www.amazon.com/Thermaltake-BlacX-eSATA-Docking-Station/dp/B001A4HAFS/ref=cm_cmu_pg_ t

Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP

Similar Messages

Maybe you are looking for