[Chris Wright]

are you exporting directly from quicktime? try exporting the master from media encoder.

[Chris Wright]

it actually only takes 2 hours, but your asking your computer to render it twice. try constant bitrate next time.

here’s some other thoughts to speed up renders:
https://forums.creativecow.net/readpost/351/1918

[Chris Wright]

before you go down the route of the log to linear nightmare, do they accept EXR? its much easier to work with(and newer). you can do half float which is lossless 16 bit images which is really nice or full 32bpc that can hold RAW’s latitude. That being said, most DPX stuff is full range unless specifically told otherwise(and its in LOG) and 8 bit log losses quality. You can go 10 bit DPX if you go LOG. You can go linear DPX if it is 16 bit or you lose precision. DPX is old and the production pipeline can get muddled if you don’t have a vfx supervisor as all composites have to be converted from log to lin first. This is why most small studios go EXR. It came from ILM and way simpler to use. ie. not mess up as often.
Helpful ?

[Chris Wright]

For hardware, take a gander at:
cpu speed:
https://www.pugetsystems.com/labs/articles/Premiere-Pro-CC-2017-AMD-Ryzen-7-1700X-1800X-Performance-909/#Exportto4KDNxHRHQ8-bit

storage speed:
https://www.pugetsystems.com/labs/articles/Adobe-Premiere-Pro-CC-2015-4-Storage-Optimization-854/#MediaImporting

cuda speed:
Here’s a list of things that Premiere Pro can process with CUDA:
– some effects
– scaling
– deinterlacing
– blending modes
– color space conversions
https://blogs.adobe.com/creativecloud/cuda-mercury-playback-engine-and-adobe-premiere-pro/?segment=dva
https://blogs.adobe.com/creativecloud/scaling-in-premiere-pro-cs5/?segment=dva

1080 ti cuda speed:
https://www.pugetsystems.com/labs/articles/Premiere-Pro-CC-2017-GeForce-GTX-1080-Ti-11GB-Performance-912/#Conclusion

for software speed:
– The Super Fast Premiere Export Guide –

1. run creative cloud software update
2.launch media encoder before opening premiere(there’s a single core bug if its opened after)
3. cleane the cache setting, delete temp files
4.update neatvideo and run its optimize tool.
5. check if cpu’s are parked. The utility is called ParkControl
or select High Performance profile in Control Panel-Power management
6. change available memory by changing the rendering optimization preference to Performance from Memory or visa versa if you have large image formats.
7. shrink large images to sequence size before importing into premiere, stay away from PNG, they are not thread safe!
8. don’t use lumetri
9. enable smart rendering 4x-12x faster render
https://blogs.adobe.com/kevinmonahan/2012/10/11/smart-rendering-in-premiere-pro-cs6-6-0-1-and-later/
10. don’t use adjustment layers
11. don’t use 64 cube luts
12. don’t use dynamic link with AE projects. render them out first, expecially warp stabilized shots. you can run multiple warps at same time.

[Chris Wright]

aw yes, just set AE to none. not only will it work faster, but you won’t have to worry about it. AE will passthrough your monitor’s color profile which is sRGB or rec. 709(0-255). The FS5 uses slog 2/3 and S-Gamut3.Cine/S-Gamut3 luts which you would use the special lut to rec. 709 to normalize both gamma and color to your monitor. Both are wider colorspaces than rec.709 so unless you have a P3 or rec. 2020 monitor, there’s no point in staying in that colorspace for a master. besides, youtube only supports rec. 709 anyway.

[Chris Wright]

i can tell you right now that premiere coloring is only in rec. 709 0-255. if you want other colorspaces, you’ll need to export xml to davinci.
youtube and vimeo only use sRGB anyway which is just rec. 709 with 0-255 instead of 16-235 which is legal rec. 709.

[Chris Wright]

you can use auto ingest proxies then render out original footage; or if your hard drive is fast enough, go full offline with cineform, prores, dnxhd. trying to multicam edit with h.264 is very hard for cpus.

[Chris Wright]

keep in mind, 1070/1080gtx will only output 10 bit in directx. premiere uses opengl so only 8 bit in there, in case you’re wondering.

[Chris Wright]

if you enable the hidden text layer and scroll Gamma Clamp in control layer at gamma*10 so that the text box reads 25, it will
fix timelapse and old movie’s flicker.

[Chris Wright]

here’s an oldie in the expressions forum.
https://forums.creativecow.net/thread/227/14016