Skip navigation
Currently Being Moderated

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

Sep 11, 2012 10:08 AM

Tags: #premiere_pro #cs6 #metedata

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.Metadataeroor.PNG

 
Replies
  • Currently Being Moderated
    Sep 12, 2012 1:51 PM   in reply to dkitsov

    Ditto here.  We have multiple Windows machines and are getting the same thing.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 12, 2012 1:54 PM   in reply to Kevin B Good

    On an HP Z820 running 6.02. Never have seen that screen.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 12, 2012 4:49 PM   in reply to dkitsov

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

    Adobe Premiere 6.0.2 Metadata Errors.jpg

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 12, 2012 5:09 PM   in reply to TJImbroDC

    I have also been having this error non-stop during the last couple of days, it started happening almost right after my 6.0.2 update. I'll post screenies of it tommorow. I wasn't really sure if it's a bug or something else wierd going although I'm starting to believe it's most likely a a bug. My system is also Windows 7 64-bit here are the specs of my work system where I've been having the issue.

     

    Intel 2500k

    16Gb DDR3 RAM 1600Mhz

    240Gb SSD OS drive

    Nvidia GTX 570 GPU (MSI)

     

    Then I have several other HDD's one that is a RAID-5 but that info shouldn't really be causing any issues. (At least I think)

     

    Honestly though in my experince the bug hasn't really caused any actual problems for me, although I am curious as to why it happens. It's really just more annoying than anything.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 13, 2012 3:35 PM   in reply to dkitsov

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 13, 2012 5:48 PM   in reply to sachind1231

    From what I can tell it doesn't actually cause any issues, it has popped up for me about 10 times in the last 3-4 days. At first it worried me but I've closed several times even though it said "progress will be lost" and I haven't ever suffered any consequences.

     

    I reported it as a bug today, I'd suggest everyone else do so as well so hopefully it can be fixed, the problem is though I can't reproduce it consistently. It seems to happen randomly.

    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 13, 2012 10:05 PM   in reply to dkitsov

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

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 14, 2012 7:12 AM   in reply to dkitsov

    I think we have another moderator now 

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 14, 2012 7:35 AM   in reply to dkitsov

    As I have asked you earlier

     

    I usually don't pay attention to who's asking, only to what's being asked.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 14, 2012 9:08 AM   in reply to dkitsov

    Even if Jim's suggestions don't help you personally, they may be of benefit to other users who may experience the same or similar problems. It is inappropriate for you to attempt to censor his input unless his posts violate Adobe's Terms of Use or Forum Guidelines. Even then, it is up to the moderators to deal with such situations.

     

    Jeff

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 14, 2012 10:15 AM   in reply to Jeff Bellune

    dkitsov - "Oh wow.  What a shocker - now a trio of serial posters polluting the thread instead of of just one. How unexpected."

     


     

    Its probably not a good idea accusing participants of polluting the thread. At the very least its kind of insulting.  

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 14, 2012 12:26 PM   in reply to dkitsov

    I have haven't exported anything as a XML in around a month, so it's very possible it might cause issues with that. I just wouldn't have experienced them yet since I don't do this very often, I basically only do it when I'm working with a FCP user.

     

    It does make since though that it would show that type of error message since the problem seems to be related to .xmp's which can hold that type of info. I'm assuming if you're not using your .XMP's for anything then the error that occurs doesn't actually hurt anything. The strange thing is though I haven't been getting the error all day... (Hopefully it will go away although I doubt it)  In the past I would get the error about 50 percent of the time when I would go to close my projects.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 14, 2012 2:54 PM   in reply to lasvideo

    Another point, that probably should be made right now is that Jeff Bellune is one of the MOD's of this forum, plus a valued contributor.

     

    What Jeff is pointing out is that there are basically three "lives" for a forum thread:

     

    1. A poster poses a question, or lists a problem, and other users (occasionally an Adobe employee) respond.
    2. Subscribers with a similar problem, will ideally use Search, to find threads, that might apply to their problem, and hopefully a solution.
    3. Subscribers pick and choose threads to read, based on their interest, or to expand their knowledge, though they might not have a problem.

     

    At the end of the day, Jeff decides what stays, and what goes.

     

    Hunt

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 15, 2012 5:45 AM   in reply to dkitsov

    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.Metadataeroor.PNG

     

    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?

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 8, 2012 8:35 AM   in reply to dkitsov

    I hope another bit of info helps track this, I have recreated this issue three times consistently; here is what leads to it in my case:

     

    Using Win 7 x64 Ultimate, Premiere Pro 6.0.2 (creative cloud subscription)

     

    I am working on an edit using all CineForm HD footage (in Premiere 6.0.2).

    I used the "Replace with after effects composition" command on a clip in a sequence. This, of course, then loads After Effects. Often, when I use this dynamic link feature, I find that my After Effects composition becomes complex enough that it won't play smoothly in Premiere in realtime, so I go ahead and render it from After Effects as a video and just imort that into Premiere.

    Thus, I render from After Effects to a new CineForm HD encoded file.

    I import the new CineForm footage into Premiere, delete the automatically imported After Effects composition and replace the AE comp in my Premiere sequence with the rendered CineForm footage.

     

    When I close Premiere, I now have the "Metadata writing in progress..." dialog box with 1 file pending. I've repeated this process with two other clips and get the exact same result (now I have 3 files pending). I have several other dynamic linked AE comps in my sequences as well.

     

    I'm guessing the issue is only related the CineForm video file rendered from After Effects in my case (and not the use of dynamic link / imported AE compositions), but I wanted to explain who I got it to happen.

     

    As a random side note, my Premiere seems to post-close-crash everytime I close it. The window closes all the way, then about five seconds later, I get a report that PPro has crashed.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 8, 2012 9:20 AM   in reply to ComputerNovice25

    Here is the picture I said I would post awhile back, I hadn't seen the error occur in a couple weeks until today. Anyways here it is.

    pending error.PNG

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 15, 2012 8:23 AM   in reply to ComputerNovice25

    I am on OSX Lion and it also started to happen to me after the update. This is not an OS based issue. It is an Adobe Premiere issue. I hope it gets fixed soon on their part.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 15, 2012 8:28 AM   in reply to dkitsov

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

     

    Eric

    ADK

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 15, 2012 8:42 AM   in reply to ECBowen

    Nothing happens, it works fine. However it gives me these errors on certain projects. I suspect that it has something to do with RED footage since after the update, Premiere started to give me these errors as well as corrupted file errors on some of the RED clips. It is certainly possible that the RED clips do contain write errors and that caused Premiere to lock up and fail to write metadata, furthermore, such files would cause havoc for Premiere if it were trying to read corrupted RED preview files in the media browser.

     

    I spent an entire week converting each RED clip on a particular project into 4444ProRes format to prevent further data degradation. I hope this has stopped the bleeding. It seemed to get worse as the weeks passed by.

     

    But in regards to the metadata error as mentioned in this thread, Premiere gives this error on some files and no error messages on other files. The only suspect would be RED video preview data. Anyone getting errors with RED files here?

     

    VT

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 15, 2012 8:44 AM   in reply to matreyia

    What happens if you go into your Media Cache Directory and select all to manually delete and then open one of those projects?

     

    Eric

    ADK

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 15, 2012 9:11 AM   in reply to ECBowen

    Hmmmm, I am trying to reproduce the phenomenon, but to no avail. When the error occurs again, I stop what I am doing and post it here. Meanwhile, I must finish this project..due today.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 19, 2012 3:13 PM   in reply to matreyia

    I did this:

     

    Edit -> Preferences -> Media

     

    uncheck: Write XMP ID to Files on Import

     

    restart Premiere, and no more this warning.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 22, 2012 7:30 PM   in reply to Rafal1911

    HI.

    I experienced the same: I upgraded from CS5 to CS6 a fortnigh ago and tried some random projects to open. All was fine than.

    Today I started to edit on a project (in the mean time, Premiere and whole CC was updated several times) I experienced SAME "metadata pending" issue.
    This was regardless if I openend CS5 created project or create new one to test. I do use Cineform too. In another project I've got "pending" message even when I tried to export via Media Encoder.

     

    Pressing NO at the dialog, HAD consequences: Every time I re-opened same project, Premiere recreated media cache for some files (not all). I have 252 files in project, 30 files was pending: It recreated that much media cache files everytime (and multiplying them in mediacache folder). After I deleted all media cache, premiere recreated them and different number of "pending" was shown (12 in this case). After hitting NO and reopening Premiere, media cache was rebuilt for exactly 12 files (now, 264 files in media cache folder).

     

    Workaround with "unticking" XMP ID write uppon import, helped. Premiere recreates media cache and closes normaly. Uppon reopen, it does not recreate cache files any more.

     

    But this issue can be 100% repeated. If I tick XMP ID again, it will behave the same again and again found 12 files pending. Since I do not know what that XMP is doing I reckon I don't need it. But I doubt it was designed to work like that or to be designed with no meaning at all. I did not use dynamic link before but I would like in the future. I hope there will be solution for this, or I will be able to do dynamic links anyway?

     

    Regards to all.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 23, 2012 5:18 PM   in reply to Snemanje poroke

    I had the same issue.  i figured it might be a ram issue cause my sequence was getting massive.  I thought if i forced it to clear ram in a different way it might get over the issue.

     

    i saved,

     

    then created a new project. (didn't do anything with it)

     

    then exited no problem, no error message.

     

    deleted dummy project.

     

    worked for me,  anyone?

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 23, 2012 5:30 PM   in reply to CaeTzar

    In my own experince the issue can't be recreated. It's totally random for the most part. It hasn't happened to me in about 2 weeks and my work flow is basically exactly the same thing over and over again. Day in and day out so it appears to be a totally random issue. (In my case at least) Anyways though it has happened to me inside extrmely small projects so I don't think it's related to large projects.

     
    |
    Mark as:
  • Currently Being Moderated
    Calculating status...
    Nov 13, 2012 12:28 AM   in reply to dkitsov

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

     

    error.jpg

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 13, 2012 6:27 AM   in reply to josurf15999

    HI josurf15999.

     

    Your audio FILES are most likely NOT destroyed. Listen them from HDD/SSD using Windows explorer.
    But in Premiere AUDIO CACHE get screwed. Maybe waveform is not showing, maybe audio is not playing (al the time, or at all), maybe audio have bits from other tack shatteren randomly...

     

    Very likely solution will be to delete media cache files and let Premiere create new ones. This happens more if Premiere was crashed, or when a lot of external modification is done to already cached files. Find out WHERE Premiere stores them.

     

    How to delete media cache files: Go to EDIT > PREFERENCES > MEDIA and see what folder is set. Close Premiere, go to that folder and delete everything. I have media cache files on a SSD, because they are small and Premiere depend on them a lot when scrubbing. It speeds up audio conforming/indexing/peaking files significantly. Ma first 32GB SSD was bought just for that reason. Do not have everything on System folder. C partition could get filled up, caousing another pile of problems.

     

    Try out and report if it helps.

     

    Regards, MIHAEL

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 13, 2012 10:06 AM   in reply to Snemanje poroke

    Unfortunately this did not help. I deleted all the files in that folder and waited for Premiere to reconstruct new files but it did not fix the problem. Any more ideas? At this point I'm willing to try anything.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 13, 2012 11:07 AM   in reply to josurf15999

    Ok josurf15999.

     

    As it seems you have WAV file on timeline. Is this ST-000.WAV plays from explorer? Is this file OFFLINE if you look at it among other files in premiere project (files windows)? You can see that if you right-click on file (on timeline) and choose "reveal in project". That will place highlight on file in project. You can see if it is online or not. On that file you can right-click again and choose "reveal in explorer". It will open windows explorer and point to that file. If it's there it must play in windows media player (or any other). If does not play, problem is in source file.

     

    Please tell more, detailed, to enable me giving some more hints.

     

    Regards

    MIHAEL

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 13, 2012 11:37 AM   in reply to Snemanje poroke

    Thanks for the help Mihael but unfortunately this method didn't work either.

     

    It is definitely online. I did the reveal in explorer and it plays in windows media player. The actual audio files are fine in that I can pull the original audio files from the project side panel into the sequence and it will be fine and play perfectly but for some reason this particular sequence as it is has the audio files muted.

     

    I am running Adobe Premiere CS6.03 which is the most current update I believe. I am running Windows 7 64bit with 16GB RAM 3.60 GHz quad core. Originaly when I tried to save my project I got the error "Metadata writing in progress (2 files pending). If you quit before writing is complete, data will be lost. Are you sure you want ot quit? "   I waited 30 minutes but nothing changed. So I just accepted and exited. Then when I reopened the project all the sound looked like this.

     

    This is frustrating because I spent so much time putting all the sound files together. It would take forever to redo it. Here's a screenshot of when I click on it:

     

    error2.png

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 13, 2012 12:01 PM   in reply to josurf15999
     
    |
    Mark as:
  • Currently Being Moderated
    Nov 13, 2012 12:28 PM   in reply to Jim Simon

    YES! Thank you so much, that worked.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 13, 2012 12:29 PM   in reply to josurf15999

    You're welcome.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 13, 2012 3:01 PM   in reply to josurf15999

    I'm glad you found solution.

    Thanks to Jim Simon for pointing to the solution, which even I could need someday.

     

    regards,

    MIHAEL

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points