Metadata writing in progress (n files pending).... error

I see this has been happening since 2012 (first post, dkitsov). It's still happening.

 Hasn't anyone from Adobe figured this out yet? Why is there no clear answer in this thread? I'd really like to know if there's any potential problems in simply ignoring the message...

This is happening to me as well and just started recently after an update to PPro CC 2022 (22.4.0)
Every time I open Premiere for the first time, and then open a project, not only does it take a while, it is re-writing all the peak files (.pek) files for each video clip. I am working with BRAW files from an Ursa Mini Pro G2, h.264 MOV files from a Panasonic CX350, and AVCHD files from a Sony NX5u. All of these A/V files are creating multiple peak files AND upon exit Premiere is showing the "Metadata Writing in Progress..." notice with the parenthetical total number of files still writing equaling the total amount of A/V files in the project.
Oddly this does not affect WAV files imported into the project. Just video+audio files.
Also, if I send the project to AME to render, AME will re-scan all the files again and create new ancillary files (.pek) files, as it most likely can't find the metadata for the imported files and is trying to re-create them for its purposes.

Any reason that Premiere Pro would not be able to write the metadata it needs?

So, just to clarify, things were functioning normally. Now they're not, with no change on my end. Nothing about my computer setup has changed, other than the updates to the adobe software.

Thanks for any insight. Questions are welcome, obviously. 🙂

Windows 10

32GB RAM

Guess I can't reply to last post but only the original.  Here it is 2019 and the error is resurfacing again, first recognized in 2012, then 2016 now in 2019.  And question is NOT ANSWERED.  Guess posting in forums doesn't really help much.  Where does Adobe post solutions for existing problems?

Well here it is August of 2016 with CC PPro version 2015.4 (v10.4 (30), Good Buddy) and the problem has resurfaced. For the first time ever, but since upgrading to this version, I'm getting the "Metadata writing in progress (n files pending)..." warning dialog on exiting PPro even when the project file has been saved a few seconds prior. It doesn't appear if the project file is simply closed first. So it happens when there is no active/open project file as well, but not if a file was never opened. Also, upon exit, when I go to restart PPro, it won't run (i.e., the splash screen never appears). I have to go to Task Manager and kill the PPro process first. It appears that a PPro thread remains running in the background on application exit, and blocks any attempt to restart it. Anyone else seeing either of these effects?  My rig is a Windows 10 64 bit machine with 32 GB DRAM.

All my audio WAV files were destroyed by this error. Does anyobody know how to fix this?

What happens if you select File and then Save as to a new Project file in the same location before you close?

Eric

ADK

dkitsov wrote: After updating to the latest version of the Premiere Pro last week, everytime I am closing the project I now get a "Metadata. Metadata writing in progress (n files pending). If you quit before writing is complete, data will be lost. Are you sure you want to quit? Yes/No" error window. Please see a screenshoot attached for one of such errors. What is interesting, is that no matter how much time i give it the process is never complete.

So the metadata writing in Premiere is fairly involved.

It tries to write metadata in the background asynchronously, but only when the file isn't being touched by something else in the application or by some other application.  What you're experiencing is potentially (I can't say for sure yet) where these 23 background metadata writing tasks never finished, or someone else never let go of the file.  If that someone else is Premiere, it is definitely a bug (which is my current guess).

Are you able to provide which file types these 23 files are, and what sort of drive/volume they're on (e.g. local/external USB/firewire/SSD/etc).

And since a number of other posters are mentioning that this started in 6.0.2 for them, is that the same for you?

Try going to Edit>Preferences>Media and uncheck Write XMP ID to Files on Import.

Seeing it here too. My "system" is really just my college laptop but was definitely excited about 6.0.2 due to GT 650M Mercury support (finally!)

Win 7 64-bit

i7 3610QM

8Gb DDR3 RAM 1333 Mhz

750 Gb hybrid drive (Seagate Momentus XT)

nVidia GT 650M Kepler as mentioned

Is it problematic to close the file anyway? I gave it maybe 2 hours and still no change.

Additionally, I receive errors in my Events log concerning files that were working correctly before the 6.0.2 update.