My original link showing the Adobe Forum posts going back to 2016 reporting this problem no longer works in my original Bug Report post above because of site changes.
I've had this issue for a while now, and now that I thought it through, I dont think its a bug...
The problem is that we've been mistaking the idea of a nested sequence with the idea of merging or join clips... the way to solve this issue is to render and replace rather than nest.
Nesting is the process of putting a few clips under one tab in order to perform edits collectively however this doesn't apply to time remapping or warp stabilising.
I had an outsourced support guy tell me "audio sync is hard, maybe look up some youtube videos", it was absolutely the most condescending support experience of my life.
It really comes down to frame holds and time remaps being janky as **** in nested sequences. Unfortunately we have no choice as nested sequences are the only good way around things like "remap + warp stabilizer" or "Premiere is barfing all over itself on the last frame because the clip has a different framerate than the sequence".
POSSIBLE FIX: I'm in PPRO 15.4.1 and I was trying to speed ramp two clips joined together (approaching a doorway, and going through the doorway) and the second clip was going black when speed ramping the nested sequence. I then nested both clips individually, then nested the individual nests and speed ramped that.
Hey guys, been a few months but I have some new insight on this: Clearly if you do anything significant with frame holds, time remaps, stabilization, etc. then you are expected to use Adobe After Effects.
For a couple years I was getting by just fine on premiere pro and only very rarely needed to do any advanced editing, and so I didn't have After Effects on my subscription. I encountered many many many many bugs regarding frame holds, time remapping, framerate mismatch, etc.
Recently I upgraded my license and it turns out After Effects doesn't have any of these bugs. The implication is clear: The large majority of professionals using these tools are not complaining to Adobe about this because the "standard" workflow through After Effects (using Premiere Pro just to stitch things together) is actually working pretty much fine. Even the Warp Stabilizer gets ASTONISHINGLY better results than the one in Premiere Pro, with exactly the same options.
The consequences of this are equally clear: Adobe is never going to fix this because it already "works" for enough people. Your options are to live with awkward workarounds and bugs, or suck it up and shovel more money at them for an upgraded license.
Quand je fait du montage sur première pro je passe plus de temps sur les forums à chercher comment contourner les bugs que finalement faire mon montage. Ca commence sérieusement à me casser les couilles!!!
Another workaround, which worked for me: Go to the source of the nested sequence. Select all tracks; enable multi-cam; disable multi-cam again. After that, the track containing the nested sequence did not show black screens anymore...
QUICK FIX: Select all clips that you would have tried to nest. Right click and select "Replace With After Effects Compostion". Export it from AE, import it back to PR and time remapping should work. (follow last steps if you don't want a dynamic link muddying up your project speeds)
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).
77
Replies
AdChoices