Copy link to clipboard
Copied
Welp.
I dont wan't to have to render/nest the clip every single time I change something. Unreal that this has been going on since November 2019. I would ask for quick solutions but I know that there arent any.
Final Cut looking awfully tempting right now. How has this not been fixed let alone adressed at all?
Unreal.
Copy link to clipboard
Copied
I feel you,
I was tired being a "beta tester" as well. I took a decision last year, to be 1 major release behind, and haven't regreted it since.
Seems to be the perfect balance for pro work. 🙂
Copy link to clipboard
Copied
Please share more details of the type of footage you're experiencing problems with as well as your sequence settings and details of your hardware.
That way, we can eliminate whether or not this is due to other sources than Premiere Pro.
Copy link to clipboard
Copied
I get the error with the following media files:
1. Long GOP 4K h264 files (Sony A7S)
2. Long GOP 1080p 50fps h264 files (Sony A7S)
As soon as I time ramp or speed change a clip, it will randomly crash on play (sometimes not on first try)
As a solution, I make prores 422 LT proxies to bypass the issue.
With 2019 release which I currently work, I get no issue with speed on the same clips.
Working on a typical 1920x1080 25fps sequence (Pro Res 422 Previews)
Mercury Engine CUDA playback engine, with high quality playback off
I'm on Windows 10 Pro 1909 with the latest drivers.
CPU: i9-7960X 16 core
GPU: Nvidia GTX 1080 Ti 11GB
RAM: 64GB
DISK: Promise R6 (~600MB r/w) / CACHE: M.2 SSD (2.000+MB r/w)