Skip to main content
Participating Frequently
April 17, 2024
Answered

Marker colors gone after closing Premiere

  • April 17, 2024
  • 12 replies
  • 1942 views

I made a bug report last week about this last week, but it hasn't been revolved so I'm hoping someone over here can help. 

I'm working on a 2021 MacBook Pro M1, and Premiere 24. 3.0.

For what I edit, I like to mark the source for my selects and color code them with notes so I can quickly & easily find what I need. For the last week, every morning I open Premiere to find that all of the markers set to green with no color coding, BUT the notes are still there. Screenshots showing before & after are attached.

I opened up a few older projects to see if it was a system wide problem, but my old projects have their old color coding, so I am not sure what is going on. This only started on 4/9 and nothing had changed with my system to precipitate this change. Since then, I've shut down, reopened, rebooted, upated Premiere & my OS and reset my settings, all to no avail. 

Please help!

This topic has been closed for replies.
Correct answer Ben Insler

Thanks for the assist @scottadderton!  Nice to see you.

 

@usconner7796 With "Write clip markers to XMP" enabled, Premiere Pro is going to attempt to actually add marker metadata to your source media files on disk when you add markers to clips in the source monitor.  If Premiere Pro determines that it cannot modify the source files of a specific type, it will write siedcare XMP files instead, but if Premiere Pro can modify these source files, it will actually change these source files on disk by inserting this metadata.  This is definitely an option/workflow that you want to explicitly enable if you intend to use this feature, and otherwise keep disabled.  XMP workflows can be extremely powerful for immediately sharing markers in certain environments, but they do run the risk of creating complications as the source media is altered.

 

In your case, there could be one of a few things happening.  You could have both markers that were saved into your project file (the ones that I'm seeing when I launch your project), and markers saved into the clip XMP data on disk (which I won't see since I don't have your media).  So on my side everything looks like it's working correctly when I open your project, but on your side, the clip XMP data is overriding the project XMP data... in which case we are not actually looking at the same set of markers at all.  This doesn't totally explain why the marker color is not sticking, even if it is being saved to XMP.  We could make some guesses, but I'm not sure that's helpful.  That said, it is totally possible that the XMP setting was not enabled for part of your project (which would initially keep markers contained to the project file itself), and then became enabled over the course of the project, creating a workflow branch where XMP markers were now being saved/used in the source media instead of the project.

 

First, please turn off "Write clip markers to XMP". 

Then, please open up a new clip (or import one) that has no markers on it.  Try to add markers of different colors.  Save, close, and re-open Premiere, and launch that project.  See if the marker color now sticks.  If it does, this is definitely related to the markers being written down to XMP.

Finally, writing markers to XMP only impacts source media clips.  Regardless of the two steps above, you should always be able to add markers of any color to sequences.  Please also confirm that sequence markers do hold their color after saving and relaunching Premiere.

 

The above will confirm whether or not XMP is creating your problem.  Unfortunatley, if it is, there's no quick way to convert all XMP markers to Project-centric markers.  It'll just be a manual process to fix... or avoid on the next project.

12 replies

Participating Frequently
April 22, 2024

Thanks for getting back to me.

  • This started in 24.2.1, then I updated to 24.3.0 to see if it would fix the problem, but it didn't. 
  • This is happening in all of my projects created since April 8th. It was the morning of April 9th when I opened my April 8th projects to find all the colors gone.
  • On projects created before the 8th, the marker colors are still there, however over the weekend I ran a test and put a marker in an old project, saved it, closed the project, then closed Premiere. When I reopened Premiere and the old project with the new marker, all of the markers had reverted to green.
  • I don't use the hotkey command to change the color, just the window because if I change the color, 99% of the time I am also adding a note.
  • Haven't had any error messages. All of my systems have been running fine. No changes at all before this.

I can send you a "failing" project file. I can evenn send you a non-failing one to compare, if you'd like. Where do I send it?

Community Manager
April 19, 2024

Hi @usconner7796 - I am not able to reproduce this in 24.3.0.  Are there any more specific details you can share, particularly the exact process where you see this happening, and can predict the behavior?  For example:

  • This only happens in projects that I created in 24.3.0.  Any pre-existing project don't have the issue even when I create new markers in those old projects.
  • This happens when I change a marker to a new color.  Existing markers don't change color simply by saving the project, but if I try to change the color of an existing marker, the color change won't save.
  • This only happnes on markers that are created with the "Add *color* marker" hotkey command.  If I create a default (green) marker and then double-click on the marker to change the color by clicking on the swatch in the Edit Marker window, the new color does save correctly.

Any specific info on the exact steps you're taking to reproduce this issue would be helpful.

 

Also, any chance you'd be able to send me one of your project files where this is failing?  Just the .prproj itself, no media.  If you can, we might be able to detmine if there are any breadcrumbs we can follow in your project specifically to find the issue.