Skip navigation
Currently Being Moderated

Premiere Pro CS6 Project Manager gives error & will not manage project - OS X Lion 10.7.5

Nov 12, 2012 10:09 AM

Tags: #avchd #premiere_cs6 #project_manager

Premiere CS6 project manager reports  an error and will not manage my project. I have tried several times with both "Create New Trimmed Project" and " Collect Files and Copy to New Location". I have also tried to manage the project with options checked and unchecked (Include Preview Files, Include Audio Conform Files, Rename Media Files to Match Clip Names). Every time I try to manage the project, the process takes a few hours and then gives an error asking me to try again.

 

The project is 90 minutes long and uses multiple footage formats:

Sony FS100

Sony NEX7

Sony NEX-5n

Canon C300

Canon 5DmkII

Panazonic HVX200

 

My computer is:

 

Processor  2 x 2.66 GHz 6-Core Intel Xeon

Memory  12 GB 1333 MHz DDR3

Graphics  ATI Radeon HD 5770 1024 MB

Software  Mac OS X Lion 10.7.5 (11G63)

 

Is this a bug, or are there specific things I can do to troubleshoot the problem? I have read of issues with AVCHD. I have confirmed all of my AVCHD folders are intact. Any other Ideas?

 

THANKS!

 
Replies
  • Currently Being Moderated
    Nov 12, 2012 10:14 AM   in reply to Athentikos

    Honestly, I'd advise you to skip this feature.  File management is best done using a proper File Manager (like Finder), not an NLE.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2012 10:20 AM   in reply to Athentikos

    First I'd ask why are you copying the files?

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2012 10:25 AM   in reply to Athentikos

    only the files used in the edit.

     

    That's the part I'd recommend against.  Keep all files in all folders intact and unaltered.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2012 12:25 PM   in reply to Athentikos

    If it's a corruption in your project that's causing it, you could try opening a new project and then importing just your master sequence into it. Hopefully whatever is causing the issue won't come through and you might find that you're then able to do a project manage from the new project. That's what I'd try anyway.

     

    I honestly think advising people not to use Project Manager is misguided. It's an essential feature. There's a whole bunch of professional workflows that aren't possible without it.

     

    I have heard of people cracking open the project file with a text editor to find the links to all the media, but have no experience with such myself. Hope you manage to get something worked out.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2012 12:48 PM   in reply to Athentikos

    What exactly does the warning say?

     

    FYI: the Project Manager won't trim Long GOP footage, like the 5D footage. That is a limitation of the Project Manager. Are following all the recommendations from the Help article?  Trim or copy your project.

     

    Also, check out the video tutorials at the bottom of the Help page for more details.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 14, 2012 5:04 PM   in reply to Athentikos

    I'm having the exact same problem on 2 different machines.  Media Manager was an essential part of our archive process when we were using FCP.  To move a project onto a different drive, that you can return to any time and not have to search to reconnect media and that only has a fraction of the media footprint of the original project is incredibly important for us.  All of our raw media is saved somewhere else, but the point is that the final show is saved with only the media associated with it in a different location for storage sake.  I've been fully on board with a lot of the Adobe features, but this issue really hurts our process.  And the fact that the feature sits there taunting us makes it hurt a little more.  I can't even figure out a good workaround.  Please fix this feature.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 17, 2012 7:17 PM   in reply to Athentikos

    I too am having this problem. I have a 45 min project and have tried 5 times to media manage. It always fails and kills the program. I'm using Sony XDEX .mp4 files mainly with some ProRes files as well. Also some GoPro video. I also used to use FCP and this is a must in my workflow. If there is a fix, I would love to find out as much as you!   Hopefully they will find a fox for this. I intend on calling them Monday morning to get a human to see the problem with me.

     

    Good luck!

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 26, 2012 1:08 PM   in reply to Athentikos

    I did a Collect and Copy function for a number of different projects and footage types and the Project Manager seems to be working fine for that. Again, it won't trim Long GOP footage, but should be able to manage it otherwise. You might try it on clips using a different codec to see if the functionality of the Project Manager is broken or the footage is the problem.

     

    If you are still having trouble, please file a bug report: http://www.adobe.com/go/wish

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 20, 2012 8:36 AM   in reply to Kevin Monahan

    It doesn't work for me either in long projects.  I narrowed it down in my project to MXF files from a Canon XF300 by breaking out my different sources into different timelines.  Other sources (5dMKIII, AE Renders, QT transcodes) work.  MXF files do not, giving same error as OP.  Filing a bug report.

     

    EDIT: Should have specified I'm doing the "collect and copy" function.  Not attempting a trim which I know doesn't work.  I have to resort to hand copying files from their original reel folders, which is a pain.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 15, 2013 11:25 AM   in reply to Athentikos

    Also having the same issue. Just upgraded to CS6, running OSX 10.8.2. The project has 2TB worth of video and stills, and Project Manager will run for ~2 hours and then give the "Unknown Error Occured, please save your project and then try again." This has happened 3 times now. Attempting to manage 10 sequences, which have 3 streams of 1080 Pro Res LT, but XDCAM footage that is imported, but not used in the timeline. When I Calculate the size, it actually increases the resulting project size by ~500GB.

     

    Has anyone had any luck in figuring out this problem?

     

    Justin

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 2, 2013 1:24 PM   in reply to Kevin Monahan

    New problems that have come up outside of unknown errors:

    • The trim goes through ok, but then when opening the trimmed project, there are \\\\\ lines through the footage, making it black in the program and     nonexistent audio. There is no pattern to it, part of the clip will be fine and the other part is basically non-existent. Check Enable, locking and all that it's     not any of those. Some of it happens to Pro Res LT footage, and some to the XDCAM EX 35mb/s footage, so it's not codec specific.

    • Project manager says that there isn't enough space to trim to on a volume, but the original project is under 1.2, and the drive I'm trimming to is 2 TB, so the     project is getting bigger, not smaller.

    • In some trims, the clips aren't actually trimming. I'm getting the trimmed clips, as well as the raw source, significantly increasing my project size. This happens with all Pro Res LT footage.

     

    Kevin do you or does anyone else have any suggestions?

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 7, 2013 9:46 AM   in reply to Filmhooligan8

    I think the issue is the C300 footage. We've not been able to use the Project Manager with any project that contains footage from our C300. P2, AVCHD, other formats seem to work fine. Love for this to get fixed as it would help us archive our projects much more effectively.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 12, 2013 7:10 PM   in reply to Filmhooligan8

    Wow, I just got back from NAB 2013 and met with the Adobe staffers and told me to simply use the Project Manager+Collect Files so I can move my project to a bigger and faster machine to complete the task. Like the others in this section, here, I cannot copy the files manually one by one as it is nearly an hour long, with numerous files and formats. I get the same errors as the other posters and I'm told to try again. What???? This is a feature?  We need a fix now. It worked fine in Final Cut Pro and I am not going to start all over and cut this on FCP 7. I came back from NAB ready to finish this task and that simple commnad craps out? I do realize that a small minority of users actually write in. I guess this is ready for a recall. Fix this!

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 14, 2013 12:16 PM   in reply to JimmyFunGuy9

    Adobe definately need to fix this promtly. The Project Management function is absolutly crucial for pro workflows! And Canon MXF is a widely used format. Adobe - you got a fix it!

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 14, 2013 12:20 PM   in reply to Kevin Monahan

    Hello Kevin.

    The this doesn't solve the problem when Canon MXF files is involved (As C300 in files) Adobe really need to fix this - An actually I would say - as I migrate form FCP - that Adobe needs to get the core functions in Premiere 100% solid before new features is introduced. I would pay a full update price - If just CS 7.0 will be functioning as Cs 6.0 was supposed to.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 14, 2013 8:06 PM   in reply to Athentikos

    I'm having a similiar problem managing a current project. As part of the job scope I need to hand over rushes to the client. I've cleaned my shots up and attempt to copy the trimmed timelines into a new folder and get the same error (Premiere has encountered an error, will close now..), regardless of whether I'm reducing or just copying the media. Material is a mixture of 60D and Sony FS700 both in native form, so there is some long GOP material in there but I still don't understand why it crashes when I simply try and copy.

     

    My workaround to meet this deadline is to individually nest each clip in the timeline then send the nests as a batch through AME. A little tedious, but it has to be done somehow..

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 14, 2013 10:02 PM   in reply to PaulM-Aus

    To be clear from my post above I was only trying to "collect and copy" the entire project, not trim the clips, as I knew there were issues with that. Really need this to work for archiving and transferring projects.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 26, 2013 6:23 AM   in reply to Athentikos

    Hi - Has any progress been made on this? I've filed a bug report but not heard - It's massively important to us to be able to archive projects that use Canon MXFs from the XF305  and every time we try, we get the unknown error....soon as we manage a project without this kind of footage, it works...It's pretty frustrating.

     

    Thanks

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 10, 2013 5:16 PM   in reply to Athentikos

    Same exact problem.

    (Interview/Doc style project with a lot of subjects)

     

    Settings: "Collect Files & Copy to New Location" selected - "Rename Media Files to Match Clip Names" is UNCHECKED.  The project contains about 200GB of H.264 footage from Canon 5D MK II's with dual system audio (audio in MOV files Replaced via DualEyes/PluralEyes) and my workflow involved creating ALL subclips for each usable soundbite. I get the same message, "An unknown error has occurred during the Project Manager operation. Please save your project and retry the operation."

     

    I noticed  in the Finder it has nearly QUADRUPLED the collective size of the media compared to the "Resulting Disk Space" estimated within the Project Manager. Is this a direct result of using subclips? In the Finder (before hitting "Ok" to the unknown error dialog box) I see the same clips duplicated up to 10+ times in some cases, filenames being appended sequentially with 001, 002, etc.

     

    Archiving this project for my [former] employer to hand off to the next editor is the only thing standing between me and my new job! :/  Please, ANY HELP would be very, very appreciated!

     

    Thanks,

    - FCP Veteran gone Adobe

     

    Screen Shot 2013-07-10 at 7.12.53 PM.png

    Screen Shot 2013-07-10 at 7.15.10 PM.png

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 20, 2013 11:51 AM   in reply to DentalSuccess

    Yup, having same issue here, with Premiere CC. For me the issue was trying to export sequences previously imported from FCP XMLs that contained "slugs" which were black sections of video inserted at beginning and end. Seems as though Project Manager doesn't know how to handle those.

    Screen Shot 2013-07-20 at 11.27.25 AM.png

    I filed a bug report.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 24, 2013 2:04 PM   in reply to Athentikos

    I have recently this issue with the project manager both in CC and CS6.

     

     

    1. I get an error "An unknow error occurred during the Project Manager operation. Please save your project and retry the operation." while trying to collect all files and copy all the media in my final sequence to an external drive. If I choose to use trimmed project I had a bunch of clips get messed up and are out of sync. Frozen frames, wrong part of the media. Overall just broken.

     

     

    2. While trying to troubleshoot and fix this issue I have had 3 clips go from working to offline because they were now corrupt. Very concerning. Could have been outside issues but strange that it happened while I was trying to media manage.

     

    I am using 100% prores media transcoded mostly from Red R3d files.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 12, 2013 2:03 PM   in reply to Athentikos

    I had the same problem. But when I deselect the option to copy the preview files, it suddenly works.

     

    The previews seem to be the cause of multiple problems. They also prevented me from opening a project before.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 18, 2013 9:18 AM   in reply to Athentikos

    I have this same problem on a Mac with CS6. I was simple trying to archive a project using the "collect files" option. After five or six hours of troubleshooting (Thanks Adobe) I have narrowed it down to MXF clips that came over in a Final Cut EDL (Projects created in PP with MXF files seem to be fine).  In other words, as I was transitioning from FCP to Premiere Pro, I sent four or five projects out of FCP as an EDL, opened them in PP and continued to edit.  It seemed to work really well until I attempted to archive my media.  If there was a single raw MXF file in the timeline (Not the project panel for some reason) the Project Manager would give me the standard error:"An unknown error occurred during the Project Manager operation. Please save your project and retry the operation.".

    I have found two solutions that seem to work, both of which are a pain in the ax. 

     

    Option 1: Save the original project file only to an archive folder.  Then delete all the old timelines from the project, and save the project with a new name.  Create a new timeline and just drag all the raw video and audio into it. (Project Manager needs a timeline of some sort to archive) Then use the Project Manager to archive the modified project.  If I need the project in the future, I'll need to open the original PP project and relink all the media from the archived "media only" project folder. 

    Unbelievably, if you were to take this route and then re-edit the project in the future, it looks like you would run up against the same archiving issue AGAIN next time (At least using CS6). You'd have to go through all the steps above to archive it a second time. Depending on the size of your project, you may want to take option 2 and get the pain over with once-and-for-all.

     

    Option 2: If you only have a couple of MXF files in the timeline (in my case I had mostly renders from AE by the time I was done and THAT raw project had archived in AE just fine) you can export the raw MXF files to another format, then replace the media in your project panel.  Finally, use the Project Manager to archive the project like you should have been able to in the first place if Adobe had written the code well in the first place!

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 13, 2013 3:56 AM   in reply to RocklinDavid

    This sucks big time. Same problem here. A 2min video compillation and I cannot move the project without spending time afterwards re-connectng all the file references. Is this a joke, Adobe? And nothing is being fixed?

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 11, 2013 3:00 PM   in reply to Athentikos

    I was having this same issue, but for some reason it seemed to work when I unchecked certain timelines so that Premiere Pro would only try to collect the clips from a single timeline instead of multiple timelines. This would be a weird workaround, but I hope it helps!

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2014 9:22 AM   in reply to Athentikos

    I would first like to say that it takes twice as long to fix a problem when half the posts on the forum are simply complaining about the problem.

     

    Next, I would like to say that copying the folder structure containing the media was my first instinct but not possible due to the difference in version updates.

    We could not copy from a newer version of adobe CC 7.1.something to version CS6.

     

    That is when I looked into Project Manager. The first time I exported through PM it worked. I "collected files and copy to new location" and "included preview and audio conform files." The folder was 6GB. I then completely rendered my project and tried to export again with the same settings. The estimated file size was 69GB and this is when I encountered the same errors as the OP. I then deselected  "included preview and audio comform files" and worked again. Like post #28 CS Mic, I assume the problem is with the preview file sizes. I did have over 1.5TB available on hard drive.

     

    Fix: Try exporting without the preview files and audio conform files. I will be much quicker with smaller folder size. The receiver of the new folder structure will have to rerender. I did have to relink like 2 files but it is quick and clean and simple because it takes you to the folder. Just choose the file real quick and its done.

     

    I am using CS6 v6.0.5.  Exported 2 sequences in 1080p24 AVCHD. 1st seq is 30 min. 2nd seq is 5 min. RAW footage in bin is 1 hr with a few video effects, transitions, photos, and titles.

     
    |
    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