Been struggling with this exact issue (4k nested footage blacking out), spent a while redoing the work, then looked up a bunch of tutorials to find out what I was doing wrong. Nothing I found told me to do anything different so just googled the error and this is top result. As usual with most Premiere Pro problems, I find it to be a years old bug that has never been fixed.
Already started learning Davinci Resolve. I've decided that every time I hit an Adobe bug / issue in future, I will watch 1x YouTube tutorial on Davinci. That way, I figure it's in Adobe's hands how quickly I move away from Premiere Pro!
@baarokun by virtue of it not having been fixed, I'd have to disagree with you there. Rather, my experience as a software dev leads me to suspect that Adobe's products are incredibly laden with technical debt, rendering even "simple" changes nearly intractable. For example, the integration of keyframes and time remapping is also jank (as well as leaving extraneous transforms after enabling Bezier curves (e.g. my footage is moving vertically when literally no keyframes change the Y coordinates, because in the past there was a keyframe doing so)).
Hi, @Elaskanator, Welcome to Adobe forums. I hope I can assist. Sorry about your issue. I'm not on the Premiere Pro staff—I'm in support. I'll see if I can reproduce your error and file a report here.
Providing a project file and a short sample of media from that project is the ultimate test. If possible, upload it to Creative Cloud, Drop Box, or whatever you like. You can follow up with me via PM with the link. I will deliver the assets to the product team.
In the meantime, give us the details about your computer, including the GPU and driver (if on Windows). Give workflow steps and information on how to re-create the bug.
I can help more by receiving sample files from you or after learning more details about your setup and media.
To work around any GPU issues, you might reduce the need for GPU interaction. Sounds like you have many things going on there! Try working with "optimized" media instead of native camera files. Editing codecs like ProRes (DNxHR or Cineform OK) files are superior in effects creation, as there is no H.264 decoding trying to compete with the Mercury Playback Engine. When you take H.264/HEVC decoding out of the chain, you can handle effects creation more nimbly. Please try this out. Let me know if this works for you.
Sorry for the issue you're having. Give us computer specs, footage details, and any workflow steps you took so I can reproduce the bug (currently, I cannot). PM me a link to your project file and source files if you like, and I'll pass them on to the Premiere Pro product team (I am an employee but not a developer).
Hi @Kevin-Monahan I'm happy to help provide anything you need to look into this, maybe you could ping me a message or use my adobe registered email address. I don't really want to provide stuff in a forum because it's quite time-consuming and I've been down that road before - with this bug. I'm happy to invest the time if I know it's actually going to get looked at, and not dismissed as what my Mrs calls "idiot user error"
I'm having the same problem. I have 3 videos having 3 seconds each that are inside a NESTED. When I try to apply a speed ramp in the middle of the sequence, the video turns black.
I've been going through this for several years and today I came here in the community to research
I found a work around. The problem dosn't accure then ther is only one video nested. As soon as I place two or more video's in the nested sequence the black video's apear. It works when you nest eatch video file separate.
The new update has been released and the problem continues. In Brazil, see with each update video editors abandoning the program and switching to DaVinci Resolve
Hello is there any news on a fix for this @Kevin-Monahan - I have a 15second edit with 8 time-remapped nests in it. The nested shots are A/B cameras and the ramps applied at the edit points.
The second shot in every nest is showing as black in program monitor and render.
Is there any workaround other than export the nests as a solid clip and applying the time-remapping to the new clip?
63
Replies
AdChoices