Skip to main content
Inspiring
May 28, 2014
Answered

Premiere Pro CC refuses to render sequences

  • May 28, 2014
  • 5 replies
  • 52227 views

I have a project in Premiere Pro where I have a lot of footage that needs to be rendered for editing. Lots of red here! However, any time I try to render by hitting Enter or even selecting a few bits to render in pieces, the rendering window comes up and sits at 0.01% and won't render any frames at all. If I try to cancel it gives a "not responding" message and I have to force close the app. I have tried clearing the media cache and even uninstalled and reinstalled but it still won't render. This isn't a problem with this one project either, but some of them get about 70-75% done before they stop. By the way, these projects were started in CS6 (which I don't have any more) and converted by Premiere Pro into a CC project. I'm running on a Windows 7 Professional 64-bit machine with the Intel i5 2.67GHz and 8 MB of RAM.

Please help! I can't edit if I can't see it!

This topic has been closed for replies.
Correct answer benlawsonphoto

I have the ATI Radeon HD 5700 video card which I just updated to the latest drivers 14.10.1006-140417a-171099C (which helped a little, as went from stopping at 0.01% to getting almost half way). I do not have GPU acceleration enabled, and the sequence has the "Composite in linear color" unchecked.

All footage was shot on the Canon 7D (MOV files). The project was created originally in CS6 with the HDV option, and the sequences used the DSLR 1080p24 preset with no modifications (although the "Composite in linear color" was unchecked recently). When I replaced CS6 with CC, I opened the project and let Premiere Pro convert it to a CC project.

As for the sequence itself, it has two video layers and five audio layers. I use Red Giant Color Suite II, and all of the clips have Denoiser II and Magic Bullet Looks filters applied. Some of the audio just has fades and blends applied.

I have been loathe to start from scratch considering the time I've already invested. However, if I do would it make a difference if I simply imported the old project or would I need to just import the footage only and start over?


I tried creating a new project and importing the relevant sequences from the original project. So far, it seems to render completely without stopping or crashing. This saved me time for sure, and I would definitely say that Premiere Pro CC's conversion process is flawed if this is the how it works. In any case, thank you all for the attempts to help. I appreciate the guidance.

5 replies

Participant
July 15, 2022

East fix. Create a new sequence, and select DSLR as the format. Change the dimensions of the projects to 1080X1920, or whatever aspect you desire. Change the FPS to 30 and voila, all solved! You will have to import all your source files again, but that's not a problem. And all new source files will have the new sequence settings. And oh, you will have to change the scales of each segment in your video. Hope this helps! 

Known Participant
August 4, 2023

That was an overcomplicated way to tell someone to just rebuild their project.

Participant
July 12, 2020

Try selecting the timeline track first! Then Crtl M or File -> Export -> Media. Do this each time that you want to export and it went straight to Media Encoder. Wait until your exported timeline shows up (sometimes 15 or 20 sec.) and hit the green start button!

Participating Frequently
October 4, 2017

Well, here I am on Oct 2017 struggling with the same issue, but in my case it is the CS6.

Render work area is ALWAYS stopping at some point, it is driving me crazy.
I had switched scratch disks, created new project, new sequence...nothing can make it render again.
SHould I delete the preview files? All of it? WOuld it help?

Please help, I'm really in need. TKS!

laaron53566804
Participant
January 23, 2017

I was having this problem as well.

As I recently migrated to Windows from Mac, I have had to learn my way around lots of little idiosyncrasies. In the case of this problem, I noticed that my sequence codec was set to QuickTime Animation. That was not intentional on my part. Never do I need a virtually lossless codec like animation. Subsequently, any section of the render that was resulting in a file greater than 4gb in size would cause the render to stop.

In my case, I fixed the problem by using a different codec.

Cheers!

Luke

Legend
May 28, 2014

Are you able to export?

Inspiring
May 28, 2014

Yes, it seems to export just fine. I have one sequence chugging away in Media Encoder as we speak, and it seems to have all of the unrendered changes.

Legend
May 28, 2014

There are no settings in the Sequence Settings that I can control. Unless there is something I'm missing...


Yeah, those are pretty standard.  I don't expect that to be an issue.

Unfortunately, with the data supplied, I just don't have any other ides about why it will export but not render.