-
Premiere Pro CC Sequence Rendering Issue
Has anyone ever experienced rendering a sequence (in to out) and having the progress bar get up to the early to mid 90’s only to have it constantly go up a percent…stop and start at a slightly higher percent.. hundreds of times in a row? Started at about 93%.. and for 30 minutes worked towards 100%.
Never had this happen before in all my rendering.
All the videos in the sequence are .MOV files (1920 x 1080) with a frame rate of 23.976. I have 2 Dynamic links – same resolution and frame rate.
I am running Premiere Pro CC (2014) on a Windows 8 platform.
Thanks,
Shawn -
8 Replies
-
Because of recent personal experience, I’d first ask whether or not you have used Magic Bullet Looks on any of the clips.
Asus P6X58D Premium * Core i7 950 * 24GB RAM * nVidia Quadro 4000 * Windows 7 Premium 64bit * System Drive – WD Caviar Black 500GB * 2nd Drive(Pagefile, Previews) – WD Velociraptor 10K drive 600GB * Media Drive – 2TB RAID0 (4 – WD Caviar Black 500GB drive) * Matrox MX02 Mini * Adobe CC
——————————————-
“98% of all computer issues can be solved by simply pressing ‘F1’.”
Steve Brame
creative illusions Productions -
I have not used any effects at this point. I was merely in my rough cuts phase..
-
I have discovered that sometimes when you have AE open with Premiere and you are rendering the linked comp, it freaks out, so I close AE and Render.
Neal Bilbe
Production Technician
City of Fayetteville Media Services Division
Fayetteville, AR 72701 -
Yup, I have ran into issues using MBL too. Anything that you have noticed that triggers the problem with the looks plugin?
-
I ended up sitting with Adobe Tech.. They had me try all sorts of things, none of which worked. We eventually created a new project and imported the original project in, which then allowed me to render the main sequence, problem is, the new project is currently starting to experience the same issues. So not really a fix.. more like a temporary patch.
-
Shawn,
Surprise, surprise: CC 14 is Beta!
I had your issue along with some unknown compiling errors today.
What I have figured out, in my situation, is that CC 14 (I am on a Mac with Mavericks 10.9.4) seems to have a bug wherein the audio and video preview folders (Project Settings: Scratch Disks) revert to an alternate drive that is low on space. This happens every time I close and reopen Premiere.
I have to manually rest the scratch disk folders for audio & video previews every time I reopen the project. But then the rendering is fine. Check your scratch disks designations under Project Settings and see if they are full or have been diverted to the wrong drives.
MORAL OF THE STORY
As I am between big projects, I took the opportunity to finally upgrade to Mavericks from Lion. While I religiously waited to upgrade the OS 3 to 6 months after its debut, I wanted to clean install CC and figured I might as well just implement CC 14 and installed it like you.
I think we are being ‘rewarded’ for jumping prematurely into a new release with the Beta Kiss of Death.
I still have a Lion partition with the old CC but I noticed that once again, Adobe is making the current Premiere Project non-backwards compatible with previous projects.
So either we don’t start any more new projects in CC 14 and continue to work in our old CC installs for the next few months, or we bite the bullet and ride out the Beta Bugs. I’m not sure yet in my case.
Why do I feel like a three year old again, having to touch the stove to see if it is hot or not?
Good luck and hope that helps in your situation.
PS: Other issue could be still images or video with larger than HD resolution.
-
I was experiencing something similar — rendering out w/ an AE dynamic link. I found that Get Info on the AE & PR (and others) and checking the Prevent App Nap seemed to fix the problem. As I understand it, if the DL program is in the background, it can go to sleep (to save power, possibly), this messes up the render.
My 2 cents.
Good Luck,
Jim
-
Joshua,
Yikes. I wish I would have known that prior to install. I suppose I got giddy and overlooked the ‘beta’ portion of the notification.
That being said, thank you for the insight regarding scratch disks. I initially thought that was the problem, but didn’t see anything out of the ordinary. I didn’t dig too deep into it though. I will be now.
What’s funny is that I tried to revert back to the previous version of CC and realized it was more work to do that than anticipated. It looks 25 links just to find the previous version, which is then broke into 4 separate files to be downloaded. It was a mess. So I opted out.
All in all I appreciate your reply and will look into right now.
Thanks again!
Reply to this Discussion! Login or Sign Up