Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Premiere Pro CC Rendering incredibly slow, almost impossibly slow

Scott Welsch

Scott Welsch

Well-known member
Joined
Apr 11, 2015
Messages
350
Reaction score
0
Points
0
System Specs:
32GB DDR3 18000 HZ RAM
GTX 780Ti SuperClocked 3 GB RAM Video Card
Intel 6 Core Processor
C:\ is Samsung SSD
Other drives standard 7200 RPM HDD's

Video is stored on 7200 HDD
Edited on C:\ SSD read and write around 400/525 mb/s (give or take)

I am using the .r3d files on my 7200 RPM J:\ drive, Premiere Pro CC is installed on my SSD (c:\) and exporting to C:\ I have also tried exporting to another HDD but no major differences.

I've cleared cache and even tried clearing it manually as well (didn't affect speed of renders or previews for that matter.)

I can watch the video in full resolution without much effort for the most part with few effects applied and I don't have issues, but when it comes to rendering, it takes a very long time.


I've tried changing from "memory" to "performance" but literally no difference.
http://imgur.com/5Df3lnY

Color FX I've used
http://i.imgur.com/h4x1seA.jpg

How I'm using my GFX card:
http://i.imgur.com/s2skmqh.jpg

The render time will start at 15 minutes then ramp to voer 60+ hours when I let it run over night.
http://i.imgur.com/w9Zq5Ac.jpg

Sequence settings:
http://imgur.com/FksOOR5

Render time: (process spiked to 33% it runs around 20% when rendering) [I got a lot of other processes running in the screenshot but I tried restarting my PC as well and removed items from startup, no viruses, no malware, etc... I doubt that'd even play a role in this]
http://imgur.com/iFBNZgD



I cannot figure out why I am being bottlenecked here... :emote_headwall: Does anyone have any solution as to why?
 
Phil Holland said:
Try removing Unsharp Mask and see what your result is.
Click to expand...

I removed all effects then tried different ways to CC it seemed to help, but for some reason a lot of the resources still weren't being used.

Now when I try to export larger than 2k I get this error.
http://imgur.com/iYyR0D5

Edit:

They are HDRx files, I tried a single 30 second clip that isn't HDRx and it rendered just fine at 4k.
 
Last edited:
Are your drives full?

First thing I'd try is a Software only Render.

Also, try sending out to AME and then closing the Premiere project before starting rendering.

Another thing to try is sending out a FCP XML to resolve and then rendering a DPX or cineform sequence out of Resolve.
 
Rendering r3d directly to h264 have always been slowvresults for me. Try to render to a master format and use ame to spit out your h264 from there.
 
PPCC15 is buggy as fuq. It's not you or your settings - it's Adobe shipping a Beta then the entire engineering and support staff taking a couple weeks off on a company retreat. As it is today = unusable
 
I converted all the .r3d files to apple prores, then replaced those in my timeline and rendered with all the effects and it took around 15 minutes to render and it worked just fine.

I'm not sure how to export full res 6k video as of yet though, are there are certain formats that are best for exporting 6k video?
 
Thats why I found the whole subscription model from Adobe disturbing.
They don't have a clear inceptive to ship production ready products.
If this was the old days, no one would pay for an upgrade once the word gets out that its faulty.
Paying a monthly fee to be a beta tester is a concept only the software industry finds plausible.
Its like if we released a feature film where part of the dialog is missing, and FX shots have green screen in it.
Charge audience to watch it, and say we are fixing the bugs as we are getting audience feedback.
Next version will be more complete. Thank you. Lol. ; )
 
Premiere... but sorry, really... Have a hard time being enthused by that.
Have to use it, though. And Warp Stabilizer is great.

But still...
 
Want to add that I have rendering problems with premiere 2015 too.

When Rendering to "Black magic avi file, uncompressed 10-bit yuv" i get the "Error compiling movie. Uknown error" message.
The same goes for Animation, dnxHD and h264. All giving me the error message in premiere 2015.


But I can send it to AME and write it out in "Black magic avi file, uncompressed 10-bit yuv"
 
I switched from Sony Vegas to Premiere over a year ago to leave the growing bugginess in Vegas... Premiere started far more solid (than Vegas), but the last two CC releases have been worse and worse. I haven't 'upgraded' to the 2015 release yet, as my current projects are working fine with my current version.

Whenever I encounter problems with Premiere, I usually try two things. First, disable the GPU and use 'software only' rendering. That usually solves the infamous unknown error during render bug. If extreme unusual slowness is the problem, a reboot will often solve it. Your machine can certainly handle Epic and Dragon footage.
 
Michael Gyori said:
I switched from Sony Vegas to Premiere over a year ago to leave the growing bugginess in Vegas... Premiere started far more solid (than Vegas), but the last two CC releases have been worse and worse. I haven't 'upgraded' to the 2015 release yet, as my current projects are working fine with my current version.

Whenever I encounter problems with Premiere, I usually try two things. First, disable the GPU and use 'software only' rendering. That usually solves the infamous unknown error during render bug. If extreme unusual slowness is the problem, a reboot will often solve it. Your machine can certainly handle Epic and Dragon footage.
Click to expand...



My trick is to render previews. Use gpu accelerated. When the render crash it will tell you where the problem is. Usually :)
 
Just wanted wine about how much work there is to render out now days with premiere 2015.2 compaired to 2014. I wish I could still render directly from premiere, but its a no go. If an render goes super slow in AME, it helps to restart the workstation...but Im never close to using 90% of the cpus! Its camping 20-30%. I think, if 50% is the best i can go if everything is just clips, with no effects or graphic.

I have started little to getting used to the thougt of switching nle. Davinci could be cool, but I think they even have less support than adobe. Smoke could be cool, but I dont like to spend money on a new mac (pc now). Same goes for fcpx...and I would never trust apple again to use it as a main editor...

So Its not that many left. Vegas is no optio for me, and avid feels like they are behind the rest at the moment (don't quote me on that one=) ).
 
James Falco said:
Thats why I found the whole subscription model from Adobe disturbing.
They don't have a clear inceptive to ship production ready products.
If this was the old days, no one would pay for an upgrade once the word gets out that its faulty.
Paying a monthly fee to be a beta tester is a concept only the software industry finds plausible.
Its like if we released a feature film where part of the dialog is missing, and FX shots have green screen in it.
Charge audience to watch it, and say we are fixing the bugs as we are getting audience feedback.
Next version will be more complete. Thank you. Lol. ; )
Click to expand...

I agree. The subscription model enables shabby software development. The incentive to build sturdy and attractive enhancements to encourage a license holder to "upgrade" is gone and we're hostages as we need to subscribe to work on our own projects. I find that repugnant. I like PP and AE and held a perpetual license for years. My work pays the subscription but I am working towards an alternative solution.

On topic, the rendering is really slow especially to H.265
 
You must log in or register to reply here.
Back
Top