1 Reply Latest reply: Oct 16, 2014 12:14 AM by Mark Mapes RSS

    Rolling Edit Tool bug?

    nathangrubbs
    nathangrubbs Oct 14, 2014 11:27 AM

      It seems as though the latest update for Premiere Pro CC 2014 has a bug with the Rolling Edit Tool. I am working on a project that has been running great so far up until this update.

       

      My project is 24 angles of 4k REDraw multi-cam live music. I am not editing with the Multi-Camera preview window open, only cutting with the Blade Tool, Rolling Edit Tool, and custom keyboard shortcuts to switch angles. This had been working great, but now the rolling edit tool is lagging a ton when trying to fine tune a cut. Is this a bug, or am I missing something? I have edited for years using this method with no problems.

       

      -Nathan

      • 50 Views
      • Tags:
        • 1. Re: Rolling Edit Tool bug?
          Mark Mapes Employee Hosts
          Mark Mapes Oct 16, 2014 12:14 AM (in response to nathangrubbs)

          Several customers have reported performance issues while editing projects that were created in an earlier version or Premiere. Here's the thread that sounds closest to what you describe: https://forums.adobe.com/thread/1595448. Two others with somewhat different symptoms reported that clearing their preferences improved performance.

          Did you assemble the sequence in Premiere or use a third-party tool like PluralEyes?

          If you're willing to try something, we'd be interested in knowing whether you have similar problems with a project originating in CC2014.1. I'm not suggesting that you start over from scratch and build up the full complexity of your sequence. Rather, import a subset of the same clips and throw together a simpler MC sequence. This obviously won't provide a full apples-to-apples comparison, but it could still be instructive.

          Also worth trying as a potential avenue to actual progress is to create a new project and use Media Browser to import the sequence from your old project.

           

          In general, I recommend finishing projects in the version in which you created them before upgrading. The greater the complexity of the project, the higher the risk of updating mid-project. That is not to suggest that these issues are your fault. It's simply an acknowledgement that issues with backward compatibility are at the root of many of the problems reported when a new version is released.