加快Premiere Pro導出速度的4個技巧



如果您不使用Premiere Pro的Smart Render,那是在浪費寶貴的時間。

查看深入的文章:https://blog.frame.io/2017/09/11/speed-up-premierepro-exports/。

45 comments
  1. I'm wondering why you are the first guy i learned this from? I mean others such as big YTbers they've only focused on export section only.

  2. this is interesting. But unfortunately a lot of these features have been removed in 2020 version. You can't seem to choose a codec any longer so it's hard to understand if it renders twice or if you decide to use pre-rendered previews.

  3. I'm finding that in/out rendering a nest takes massively longer than opening the nest and rendering the content. But then the internally rendered content doesn't work on the parent timeline.

    When I say longer- I tested on a 10sec portion; Open the nest and pre-render, I didn't get the chance to start a timer. Same 10sec of the compiled nest on the parent timetime, it's taking about 2 seconds on EVERY single frame.
    What's so different?

  4. Hope you can help me. I have a Mac with a i7 8GB ram setup . Works great but I have no idea why it takes ages to export my DJI videos. I use a 2.7k format. Trie everything including your suggestions , a 3:30 minutes clip takes 10-12 minutes to export and the same amount of time to render the sequence 「In and Out」. I have tried just about everything without success. Note: even the clip on the time line does not run smoothly. Runs choppy . Pls help. My computer is fine. Works great with other Adobe apps. Thanks

  5. Just a question, maybe dumb … but maybe you can answer it… if I used h.264 and export at 1080… and make a change and reexport with the same settings how much quality will I lose? (I』m still using CS5)
    Thanks in advance

  6. I have an opinion/question with regards to file size:

    While this does save on export time/prevent an additional encode, I've found over the years the trade-off in file size to be a separate issue itself. Most times, when sending a screener/review link to a client, having a smaller file (h.264) is advantageous. It can upload much faster to Frame.io through the extension this way too!

    Most clients are not able to perceive the quality loss from the ProRes timeline I'm working in to the h.264 screener. This also has the added benefit of not clogging up your data cap on Frame.io with bloated file sizes (beneficial for smaller teams such as ours).

    Regardless, editing with ProRes in a ProRes timeline (or any of the other mentioned codecs) is a HUGE lifesaver!

  7. Fantastic tips! Thank you for putting this out! More like this and other best practices is helpful especially for those of us on long-form projects where instability and crashes creep in if best practices aren't used. I don't find much support for those of us doing long-form/feature in Premiere Pro now, despite Adobe's NAB promise to do this. (Unless you are super famous of course 🙂 )

  8. I rendered my sequence and it took as long as it wud take to export. I thought ok it wont take time to encode. But now i satrted encoding and its taking the same ammount of TIME to ENCODE. NOW IVE WASTED DOUBLE THE TIME. i dont know why this happend can anyone help?

  9. Thanks sir yeah it's speed up like 10x I'm using dnxhd but the problem is the file size after export is more than 50gb 1hr 30min footage. How I decreased file size?

  10. Such ass-saver! However it only works for exporting using Pr Pro (not Media Encoder!) It's like 32 hours (what a hell) using Media Encoder vs 30min using Pr Pro when I use this trick to fix a tiny problem in the video.

  11. This was probably the most useful "render faster" video I've seen for a long time! Because it actually explains how the pipeline of Premiere Pro works and stuff 😀

  12. Great video, but for some reason i am kinda confused.. If i'm making my RAM Previews in QT proress 422 HQ, but i'm exporting in h.264 is that still going to help with the ecoding time and in the same time without any quality loss?

  13. I love this video and some of the tips I've been clued into in the past (thank goodness). I don't have the Apple ProRes 422 preview codec available to me within my 2018 Premiere Pro (although I do see it in the uber-buggy PrPro 2019). Seeing as you made this video in 2017, I'm wondering if you know of a way to import the codec settings?

    Maybe someone who knows more about this than I do can help me. I'm not sure if even finding/using the ProRes 422 codec is going to speed up my setup. I'm always in a sequence that is 4K, video previews in 4K, GoPro CineForm YUV 10-Bit. I then output in 4K and HD, using H.264 with a .mp4 extension.

  14. This didn』t work for me at all. I have a video with a 2 hour encoding time. Decided to render first. Took 2 hours. Moved to encoding. Took 2 more hour to encode using previews. Total time 4 hours. Twice as long as if I had just done it the normal way.

  15. Wow… I just subscribed… Help me to understand this… I make 10 hour long videos. Lets say I have a 5 minute long video clip. If I preview render it in the timeline and then copy and paste that EXACT same clip for the next 10 hours, and then final render and click the check box "use previews" adobe will then use the prerendered preview saved on the hard drive correct? And that should significantly speed up my render times? Instead of being over 10 hours long each time ?

  16. Another obvious one that people forget about is rendering and working from separate drives. I have One for cache files and one for my project file. I usually then export to my desktop. This speeds up rendering times massively. Compared to doing it all one one drive.

  17. This was super helpful, like time went from 11hrs to 36minutes do the pre-render. Have two vids to get up before halloween ia over I needed this boost

Comments are closed.