Skip to main content
G
getho
Inspiring
November 19, 2017

P: Nested sequence time remapping bug

  • November 19, 2017
  • 50 replies
  • 26092 views

I've submitted this bug several times now.  2 things: how do we know if adobe has acknowledged a bug? do they respond to let you know?

2nd thing, the bug itself:

 

take a nested sequence, insert it onto timeline.  Add another layer in the nested sequence, apply time remmapping.  Sequence will go black before it reaches the end of the sequence. This vid below demonstrates that it is not the normal behavior of a time remmapped clip.  Most of the time when I encounter this bug it is when the original footage is not the same res as the final sequnce.

 

[hyper link removed by author request]

 

[Typo removed from title. — Mod.]

    50 replies

    Show previous replies
    Kevin J. Monahan Jr.
    Community Manager
    Kevin J. Monahan Jr.Community Manager
    Community Manager
    June 10, 2024

    Hello @jmvdigital,

    Thanks for the message.

     

    quote

    It seems really disingenious to chime in after this post being live for over 7 years, and now stating that you need more info to reproduce it?! Crazy.

     

    This bug report was carried over from User Voice a long time ago. It was then migrated to these forums and has not been picked up by the product team.

     

    Recently, the product team has asked my team (support) to come into these bug forums to triage legacy bug reports. I didn't intend to be disingenuous. I'm only trying to help here. I hope I can help. I am unsure why the product team did not respond to this bug. I'd ask them to comment, but even so, they do not comment on every bug report. Sorry about that.

     

    I tried to replicate the issue and saw some black frames when attempting to get a high percentage of speed in the nest. I suspect that the effect is out of additional frames to affect. I will ask the team to respond to see if the issue is expected behavior or a longstanding bug that needs action.

     

    Thanks,
    Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
      jmvdigital
      jmvdigital
      Known Participant
      June 10, 2024

      Add a few clips together in a nested sequence. Place said nested sequence on a timeline. Use keyframe within timeline to adjust speed ramp... notice how the footage disapears (black frame) randomly depending on speed ramp keyframe settings.

       

      It seems really disingenious to chime in after this post being live for over 7 years, and now stating that you need more info to reproduce it?! Crazy. 

      Kevin J. Monahan Jr.
      Community Manager
      Kevin J. Monahan Jr.Community Manager
      Community Manager
      June 10, 2024

      Hey @jmvdigital, Hi @getho, @Odobe, @Águia Films and @Isra Velzen,

      Thanks for the message. This bug report requires more information for the team to reproduce the bug. You can also send me a private message with links to files that produce this error. See: How do I write a bug report?

       

      The behavior may be "as designed," but we need more info to determine that.

       

      I hope we can help you.

       

      Take Care,
      Kevin

      Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
        R
        RodHarlan
        Participating Frequently
        January 24, 2023

        Only work-around seems to be to switch to "Mercury Playback Engine Software Only" which is brutal with 4K nested sequences.

        This has been discussed for years on the Adobe Forums
        https://forums.adobe.com/search.jspa?q=time%20remap%20nested%20sequence

        but I did not find it listed here, so I am posting it now.

         

        Mod note: The title was changed slightly.

          F
          FeedbackCommunityMember
          Inspiring
          January 24, 2023
          Please fix this issue, it makes it very hard to get the job done right and promptly. .
            iFleeter6237826
            iFleeter6237826
            Participant
            January 8, 2023

            January 2023 - This bug is still an issue. 

            Would be great if an Adobe employee on the bug team could share where this bug is in the queue. 

            There is certainly a Jira board or Project/Prod manager that's sole purpose is to make sure bugs are getting solved, daily, weekly, and monthly. With daily stand-ups, with the devs. Is this Bug stuck as a blocker and lost in the queue?

            This was logged back in 2015 from what I've seen. It's almost been a decade since this bug has been resolved. 

            If the Adobe team simply shared the internal bug board it would eliminate a bloated support forum from duplicate posts spanning years. The work is already being done and managed. Just share what is being worked on and where in the roadmap we are. 

            If this bug roadmap already exists please link me.  

              G
              gethoAuthor
              Inspiring
              January 9, 2023

              I've had direct contact with adobe about this bug - they failed to acknowledge it as a bug (because they didn't try hard enough!)

              I'm so used to it now I have 2 main workarounds:
               If a nested sequence includes a cut/more than one layer and you need to do a speed ramp on it in another timeline you can:

              1. render it out. I now have a "bump" folder for every project for such things. Re-import it into premiere.

              2. turn off cuda in prefferences, nest the ramped sequence and render that out as above

              I've also got used to just avoiding it: for instance for doing property boundaries instead of using paths I used lumetri plus masks to do the same thing.  

              The more people complain about this, the more likely it is to be addressed. 
              There used to be a lot of uservoice stuff about this bug, but I believe thats been deprecated or removed. I'm not sure at the mo how you even report bugs.  TBH I'm in  aholding pattern until I have the time to start using that Davinci Resolve licence I bought a year ago 

               

              Here's the uservoice page:
              https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/34384855-bug-report-time-remap-of-nested-sequence-results

               

                P
                Pim5C1F
                Participant
                December 23, 2022

                December 2022, bug still not fixed

                R
                Romulus22
                Participant
                September 1, 2022

                Version 22.5.0 (Build 62) still contains this bug. It has been almost 5 years now.

                 

                And it cost me more than an hour to find the workaround (Software instead of CUDA).

                  P
                  Peter24170174dlfj
                  Participant
                  August 10, 2022

                  This bug is really causing me a lot of pain right now. The fact that this only happens when using GPU acceleration makes it extremely clear this is a bug. Please fix this, or if it's not possible to fix please just remove time remapping from premeire entirely. 

                  M
                  Mikael23718359fyps
                  Participant
                  March 23, 2022

                  Changing rendering settings to software-only worked for me.

                   

                   

                    L
                    larrypizza69
                    Participant
                    March 29, 2022

                    Mikael237...... HAS THE FIRST HELPFUL ANSWER!  So glad I read this thread all the way to the end. 

                     

                    File > Project Settings > Video Rendering and Playback > Mercury Playback Engine Software Only

                     

                    The problem is the default "Mercury Playback Engine GPU Acceleration (Metal ) - (Recommended)" renderer with multiple layers of time remapping breaks for some reason.... A BUG PERHAPS!

                     

                    I remapped 2 different clips so the timing matched in a picture in picture, then nested and attempted to apply new time remapping keyframes to my nested sequence. I got the black screen error. Software only seems to be working!

                     

                     

                      C
                      Clemens5C68
                      Participant
                      May 15, 2021

                      Just encountered this bug too. Really frustrating! What is the best working workaround? 

                      C
                      Clemens5C68
                      Participant
                      May 15, 2021

                      Ok DanCoes method works:

                       

                      "I nest the sequence and then increase the speed duration of the nest (to say 200%) . I then create the time remapping and slow down the first part of the clip. Effectively creating the same result. I don't know why this works, but simply ramping the speed up from 100% speed duration doesn't?"

                        Show more replies
                        Terms & ConditionsAccessibility statement
                        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices