BUG Rendering a timeline on a Mac in 12.1.1 is freezing with ProRes as the video preview codec
Updating from 2015.2 to 2018.1.1 on macOS. Rendering a timeline is freezing with ProRes422 selected as the video preview codec (as I always done in the past). Tried it with multiple machines with various GPUs, it freezes faster if a Lumetri Color effect is applied. Premiere hangs (with the color beachball). Actually, the renders keep on rendering in the Video Previews folder until the end of the timeline, but Premiere itself is frozen, which cause to force quit and lose all the renders. It works fine with the DNxHD and AVC-Intra 100 codecs, but not ProRes422.
Hunter Haines commented
I have this issue as well, Prores 422 HQ is seqeunce codec. mixed Prores and r3d files in timeline. I am still on 12.1.1 can anyone confirm it is fixed in 12.1.2?
Ryan Fritzsche commented
I've switched to i-mpeg instead of Quicktime (QT > DNxHD was actually having the same issue as the ProRes Proxy) and everything is now working fine. Rendering long sequences without failures. So it's definitely a quicktime or ProRes issue. It's still a big problem, b/c being able to render into ProRes in preparation for expedited export of ProRes (or DNxHD for that matter) masters is a key issue.
Ryan Fritzsche commented
I have a large documentary project which I was working on in CC2017 without issue. After moving to CC 2018, renders seem to seize up the program after 5 or 10 minutes, virtually without fail. It means that rendering any long timeline is virtually impossible. There is no freezing or issues exporting these sequences thru media encoder. I have tested in various projects with a wide variety of timelines, running off different drives, writing to a high-speed RAID system, all incorporating different footage, so I know it's not corrupt media, and the fact that Media Encoder handles it fine suggest to me that it's not a hardware issue. Mac Pro 6,1, dual D700, 6GB VRAM, 64GB RAM. Same experience as above - seems to keep rendering but the project loses track of the render files when I have to force-quit. I have to assume this is a result of Adobe having to rewrite the code for ProRes after eliminating legacy 32-bit Quicktime support in CC2018, but it's a huge problem and DESPERATELY needs to be fixed ASAP. My render codec is always ProRes Proxy, but as noted here, I will attempt with DNxHD or some other codecs and see if that's a sufficient workaround. My source footage is a mix of Sony A7S .mp4s, various iPhone, Canon 60D, Canon 5D, and other misc.
John Twigt commented
Same here, constantly rendering small pieces now, but it's a huge nuisance. In some toime sensitive cases (deadlines breathing in my neck) I resorted to importing the rendered files themselves into the project and using them, because PP actually renders the whole sequence but the freeze causes them not to link to the sequence, aaargh (I experience this since the update to 12.1.1 (build10)
I've been experiencing the same thing as well. I've had some luck rendering in smaller chunks. Thanks for starting this thread.
I'm having the same issue. Premiere Pro (same version as OP) freezes inconsistently. Sometimes it will render fine and then other times it hangs after rendering a few frames. Using ProRes 422 as preview codec as well. This is really embarrassing when I have a client in the room. I'm running a 2013 Mac Pro w/ dual D700.
Marc Trojanowski commented
Yes, having the exact same issue too, come on adobe can we get better testing before you roll out updates?