Skip to main content
T
TheEditWolf
Participating Frequently
May 5, 2025
Answered

Sync Lock not respected during Ripple Delete

  • May 5, 2025
  • 3 replies
  • 2213 views

Hi everyone,
I have encountered what I believe might be a bug or at least inconsistent behavior in Adobe Premiere Pro regarding Sync Lock and Ripple Delete.

Here's the situation:

When Sync Lock is enabled on multiple tracks, everything works as expected. Using Ripple Delete removes content across all synced tracks, while tracks with Sync Lock disabled remain untouched - which is correct.

However, here's the problem:
If I perform a Ripple Delete on a track where Sync Lock is disabled, Premiere still removes content from other tracks where Sync Lock is enabled. In my understanding, this should not happen. If Sync Lock is disabled on the track I'm editing, the delete operation should not affect any other tracks, regardless of their Sync Lock state.

To be clear:

 

Ripple Delete on Sync-Locked tracks works fine.

Ripple Delete on Sync-Unlocked tracks should not affect Sync-Locked tracks, but it currently does.

 

This behavior seems inconsistent with how Sync Lock is supposed to work - essentially breaking the very concept of protecting track sync through Sync Lock.

 

To be absolutely clear:

Try using Ripple Delete to cut out a middle section of music on a track where Sync Lock is disabled. You'll find it's impossible without disabling Sync Lock on all other tracks - which defeats the purpose of the feature.

 

Has anyone else experienced this? Is this a known issue or am I missing something?

Thanks in advance!

    Correct answer ScottSimmons

    Good, I’m very glad that you understood my suggestion so well, and I appreciate that Premiere has its own unique approach, even if it differs from what I expect.

    As someone who works with both Avid and Adobe, I would love to see this function behave consistently across both platforms. In my experience, Avid handles this aspect quite elegantly - especially when sync lock is actively used.

    I hope more editors like Ali Jaber and sabine_7781 share their perspectives as well, as it could be valuable feedback for future improvements. After all, small workflow adjustments - like not having to disable sync lock on all tracks just to work on one - could really enhance the professional experience in Premiere.


    I don't disagree that that would be a useful change. You could file it as a feature request, but honestly, I feel like it probably wouldn't get much traction. Partly because there is, I would guess, a tiny percentage of Premiere users who actually actively use Sync Locks. And partly because it's such a niche, more "pro" feature. I don't feel like that's Adobe's focus right now. 

     

    A number of editors have been actively lobbying Adobe to fix one of the most annoying things: where it will automatically add tracks in the timeline if you've got more tracks in the Source monitor. It has been discussed over and over. I even ended up writing a post called My single most hated feature in Adobe Premiere Pro as a way to articulate the issue outside of multiple forum posts and Twitter threads and things like that. All we ask is a simple checkbox like is available in AVID and Resolve. It's been discussed ad nauseam for years, but never addressed. 

    3 replies

    S
    sabine_7781
    Participant
    May 7, 2025
    I understand exactly what TheEditWolf means. You have to laboriously de-sync all other tracks before you can work on just that one track – without affecting the others. That's not time-efficient, to say the least. Especially if the timeline contains many tracks. Workarounds like completely locking the other tracks are just as impractical. I'm used to working differently with the other NLE (Avid), just as TheEditWolf described. And the Avid way simply makes sense. If a sensible solution could be found, I'd be more than happy.
      A
      Community Expert
      Ali JaberCommunity Expert
      Community Expert
      May 6, 2025

      I did some tests and I agree, when turning off sync-lock of a certain track, ripple edit operations should not affect other tracks.

      The current behavior should be treated as a bug to be fixed.

        jamieclarke
        Community Manager
        jamieclarkeCommunity Manager
        Community Manager
        May 5, 2025

        HI @TheEditWolf -  If you’re using the Ripple Delete keyboard shortcut, make sure that sync lock is turned off and the track is not highlighted otherwise, it may affect unintended tracks.

        If you’re trimming instead, only sync lock needs to be turned off to prevent that track from trimming along with others.

          T
          TheEditWolfAuthor
          Participating Frequently
          May 6, 2025

          Hi jamieclarke,

          Thanks for the quick reply. There might be something in your answer that I wasn't aware of yet. Unfortunately, I still don’t quite understand it correctly, it seems.

          I’m aware that there are two main ways to use Ripple Delete:

          1. I select a clip and press Ripple Delete. In this case, I don't need to highlight any track.

          2. I use Mark In and Mark Out to define a range I want to delete. For this, it's important to highlight the specific track where I want to apply Ripple Delete.

          So far, so good.

          Now imagine a simple sequence: an interview with video on V1, corresponding audio on A2, and music on A3.
          If I want to delete parts of the interview but keep the music untouched, I disable Sync Lock on the music track A3. That works perfectly.

          However, if I want to cut part of the music instead, just disabling Sync Lock on music track A3 is not enough - I have to disable Sync Lock on all other tracks as well. With just three tracks, that’s manageable. But when editing larger sequences with 20 tracks, this method becomes extremely cumbersome.

          There’s also no real benefit to disabling Sync Lock on a single track if all other tracks still get shifted during a Ripple Delete or Insert Edit.
          Please don’t hit me for bringing up Avid Media Composer - but in Avid, Sync Lock works as it should: I disable Sync Lock on a single track (let’s say music on A3), and I can work freely on that track without affecting any of the others.

          I really believe Sync Lock is not functioning correctly in Premiere Pro in this context. I’ll have to live with it, I suppose - but it does feel like a clunky workaround is needed to compensate for what seems to be a design flaw.

          That said, maybe you’re on to something with your suggestion. I’ve experimented again a lot with highlighted tracks, but Premiere still doesn’t behave the way I’d expect it to.

          If you’d be willing to think through this with me again - which I’d truly appreciate - it’s important to understand exactly where I see the problem:
          I want to unlock a single track and work freely on it without endangering the sync of all other tracks.

          Thanks so much in advance for your effort.
          Michael

          jamieclarke
          Community Manager
          jamieclarkeCommunity Manager
          Community Manager
          May 6, 2025

          Hi @TheEditWolf - I really appreciate the level of detail you’re providing.

          Based on what you’ve described, it sounds like the key issue may be that the A1 source patch (the blue box in the track header) is still active when you’re performing the Ripple Delete. For Sync Lock to behave as expected especially if you’re trying to exclude a track like music from being affected you’ll want to disable Sync Lock on that track and also make sure the A1 patch isn’t active (i.e., the box isn’t blue). If the source patch is active, Premiere will still include that track in the operation even if Sync Lock is off.

           

          Some users also get around this by simply locking the track they don’t want to be affected, which can be more reliable when working with complex timelines.

           

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