Skip to main content
T
TheKillaTapes
Participant
November 2, 2017
Question

Premiere Pro CC2018 keeps crashing

  • November 2, 2017
  • 2 replies
  • 675 views

I keep trying to edit an updated sequence, and every time I try to move a group of clips in the sequence all at once I get this error "TrackInfoChangedAction.cpp-88" and Premiere shuts down. Have tried restarting my computer and also creating a new sequence in the project and then pasting the footage into it and working from the new sequence but nothing has worked

    This topic has been closed for replies.

    2 replies

    E
    excited_Genie16B8
    Legend
    November 9, 2017

    You can try some basic troubleshooting, see if anything helps.

    Unofficial Premiere Pro Troubleshooting Guide

    T
    TheKillaTapesAuthor
    Participant
    November 15, 2017

    This didn't help. What it ended up being was that I had changed my sequence from 59.94 to 29.97 and that for some reason tripped up Premiere. I made a new 29.97 sequence and pasted the footage from the other sequence into it and it solved the problem.

    That being said, there are a lot of bugs with this version that make it extremely annoying, and I will be reverting back to 2017 version until they get it ironed out.

      O
      Outpost Magazine Inc.
      Known Participant
      November 15, 2017

      I believe this is the best solution. The 2018 version would have all the ram running at 100% and the CPU at 100%...when reverted to the 2017 version (same file, same settings, same everything) the ram is at 34% max and the CPU is at 45% max!

      I believe that the version 2018 is not ready yet.

      I don't know if this can help but I had a few settings that helped quite a few people...

      https://www.inspadesmag.com/single-post/Premiere-Pro-2018-Fix

      O
      Outpost Magazine Inc.
      Known Participant
      November 9, 2017

      I'm having tons of problems and crashes constantly. I think that CC2018 is not really ready yet. I know that this might be a huge problem, but I switched back to 2017 and (fingers crossed) it's working fine.

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