I thought I'd delete my previous and repost this IMPORTANT (at east to OUR company) question again –– since it received ZERO responses or help originally. Possibly I just posted at a bad time of the week, or when folks were busy. But I would be most appreciative of any assistance that can be offered in solving this GLITCH –– or in knowing that a FIX is soon to be on the way. THANK YOU...
In the video link above, I document how RENDERED frames in Premiere (version 13.1.2) suddenly REAPPEAR as UNRENDERED. This has ONLY started happening since I updated from Premiere 2018 to the current version. Entire timelines that rendered perfectly in 2018 without any issues, are now speckled throughout with UNRENDERED frames once opened, saved as new version file, and rendered in the current version.
In timelines of 20 minutes or more, this GLITCH can easily occur as many as 20+ times. It may happen during a few frames of a dissolve, or a during a layered effect, or simply where nothing whatsoever out of the ordinary is applied to a clip. PLEASE NOTE: In the video link above, the two clips with the "unrenderable" frames have NO EFFECTS and NO RESIZING!
All clips are RED R3D files in either 5K or 6K. We are running Premiere on a Windows 10 workstation.
Does anyone know of a cause? A workaround, until these bugs are FIXED?
This is just ONE of a frustratingly LARGE group of BRAND NEW glitches which have only occurred since installing version 13.1.2. Other GLITCHES include:
• Clip icons in project folder still registering as "?" and playback of timeline images (not sound, solely the picture) not appearing until long after the notification of "All Media Loaded"
• The cursor DISAPPEARING (though what it HIGHLIGHTS or AFFECTS on the screen is still seen)
* Entire timelines that HAD been rendered (though WITH the glitches of scattered unrendered frames), once saved and reopened appear as having not yet been rendered
• Constant crashes
• and much more...
Interesting ... and I can't replicate, but ... I would ask you to post this on the bug site UserVoice. Everything posted there goes directly to the engineers, and to the upper managers in collated form ... the folks that decide budgets & schedules. Adobe lives by metrics, give them some.
Also, that site is searchable by others having similar issues to gang up together. And I would further ask you after posting there ... whether you start a new one, or add on to another post ... to post a link back here for anyone with similar troubles to find.
Adobe UserVoice Bug /Feature form: https://adobe-video.uservoice.com/forums/911233-premiere-pro
Thanks so much for reviewing my post and for your suggestion, Neil.
I've done as you recommended, and here is the link to my "suggestion" to FIX this glitch, now found on UserVoice:
I added a comment. Thanks for posting there!
That may just be the nudge that's needed...
Sorry to hear that you are facing this issue. Have you tried using the Mercury Playback Engine Software Only as Renderer (FAQ: How to change the Video Renderer in Premiere Pro? ) and checked if it's rendering properly? This will help us in isolating if the issue is specific to GPU accelerated renderer. Also, have you tried clearing the cache (FAQ: How to clean (delete or trash) media cache files? ) and preview files (location for the preview files can be found under File>Project Settings>Scratch Disks)? Let us know, we’re here to help.
I am having the exact same problem with frames unrendering themselves. At one point I had it render eight frames and befoer the frames were completed rendering, it would recognize the newly unrendered frames and render them. and then they would unrender and it would just repeatedly render them forever in a loop. I have mercury set to software only.
I did find somewhat of a work around, however its kinda bull*#($ and involves adjusting the scale of the image a few degrees. Also it should be noted that I'm working in 4068 x 1716, square pixels. Never been a problem until this version of Premiere. After 17 years using it, I took 3 years off (video production n general) and came back to a glitchy platform apparently.