Participating Frequently

Answered

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

Forum|Forum|13 years ago
November 12, 2012
23 replies
35664 views

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!

This topic has been closed for replies.

Correct answer Kevin-Monahan

Hi Athenikos,

This is an older thread, but to wrap things up, the Project Manager has been completely rebuilt in Premiere Pro CC 2014. It should function without errors, but if you are still experiencing issues, please file a bug here: http://adobe.ly/ReportBug

Thanks,

Kevin

R

rolin75

Participant

After going through all the suggested workarounds and ways to get rid of or avoid this error

(exclude audio conform and preview files, avoiding mp4 audio, avoiding different fps rates) and

still having the same error on numerous projects I found one file (from a client) that had a special character in it.

I got rid of it in Premiere, ticked “Rename Media Files to Match Clip Names” in the PM and

everything worked.

So why isn't it possible to phrase this in the error message or

why is it an actual problem if Premiere handles the file without moaning in the first place.

We wouldn;t name any files with special character ourselves

but I guess everyone here knows what clients sometimes throw our ways.

And if Premiere doesn't complain, why would the PM have a problem?

This has cost me a lot of time and nerves, so thanks Adobe.

rebeccaa34772112

Participant

I FEEL YOUR PAIN. Same thing happened to me. A client audio file had a slash "/" and Premiere Pro CC was reading it as ":".

Of course it is a good practice to rename files and pay attention to naming conventions...especially when it comes from clients because we all know that most of them are not the most tech savvy. But at the same time, can't we be prompted to locate file or just ignore that ONE file and not get rid of the entirety of the Media Managed files? thanks adobe in deed.

mikeyp69524842

Participant

So on Aug. 4th 2015 this same problem was driving me crazy and burnt a full 12 hour for me but i found a fix!

DON'T check the preview files!! After i finally found a forum that had that info i could finally work again!

DON'T check the preview files!!

uk_richlester

Participant

I also found the same issue. If working on a Mac you can watch the files populate your destination folder and as long as you don't click on 'ok' when the error message pops up, you can see what the last file was that corrupt the process.

I had an animation file with an alpha corrupting mine so I encoded it to prores4444 and export at 32bit out of premiere and that fix that issue. I also found in another sequence the previews folder was the issue.

BRT_LovesSushi

Participant

Still having the issues though, I understand Project Manager has been rebuilt but I think Apple and Adobe aren't the best of friends and it gets a little tired watching each blame the other. I had this same issue, fortunately I'd already sent the project off to Color and received a PRORES 422 HQ back, so the only thing I was trying to consolidate was the ProRes, Audio, and all the Dynamic Linked AE title work into one archive file. Project manager failed for me several times until I turned off previews & renaming clips (something I never do anyway, because that tends to create it's own mess). On a side note, CC 2014 seems more unstable in general from cs6 with Yosemite, last time I called into Adobe, they stated that Mavericks and Yosemite where built differently and Adobe is playing catch up trying to correct for Apple's changes... Odd since Mavericks and Yosemite are still build on the 10.x platform, but that might just be inside baseball... I wouldn't think they'd change much core structure till they hit 11.x whenever that may be.

I do love the Creative Cloud, but it doesn't work half as well as it should on mac... everything they fix seems to break something new, I can't even get Media Encoder to work without crashing after 20min - granted these are large files that I'm playing with, but I expect this stuff to be fixed sooner then later for a subscription based service!

My two cents.

michaelp2453689

Participant

FIX: Try exporting without the preview files..

Kevin-Monahan

Correct answer

Community Manager

Hi Athenikos,

This is an older thread, but to wrap things up, the Project Manager has been completely rebuilt in Premiere Pro CC 2014. It should function without errors, but if you are still experiencing issues, please file a bug here: http://adobe.ly/ReportBug

Thanks,

Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

F

FPS_Fish

Inspiring

Hi...it's 2020 here and I'm having the same problems when I choose "exlude unused clips". Nothing seems to work with this checked on. Which kind of makes the function of "consolidating" pretty useless, no?

N

nogueli

Participant

Worked very well for me:

I create the project manager and put the original project file inside the folder with the manager, lots of c300 footage, 5D Mark III footage and a lot of still images, just put original project file and opened him.

C

caffesse

Participant

Did you simply consolidate the entire project or have Project Manager trim and transcode the clips?

It is the trimming that seems to be the problem.

N

nogueli

Participant

Just project manager trim, seems the project trim is the issue, i have opened the original project in 5 machines, pc and macs, and worked very well.

M

mike_buckhout

Participating Frequently

De-selecting 'Include Preview Files' worked for me, with Premiere Pro CC - 2014.2 Release, 8.2.0 (65) Build.

And this is with a lot of XAVC (Long-GOP) MXF files from a Sony PXW-X70, mixed with AVCHD footage too.

It did not work on the first try with 'Include Preview Files' turned on.

One thing that can cause problems are assets located on a network drive, just another thing to check if you're still stuck.

Julien.karmad

Participating Frequently

Hey Mike, (and everyone else)

Did you find the resulting project after managing your sequence?

I'm experiencing issues after a consolidate of my sequence, all the files seem to get consolidated and transcoded to MXF into the new location but I can't find the resulting project with the newly consolidated sequence.

Any idea where that one went?

M

mike_buckhout

Participating Frequently

No issue finding the resulting sequence, sorry. It should appear in the same root folder as all the other assets.

L

littleluce

Participant

Is this thread still only referring to CS6? I'm pretty sure that it's been resolved with Creative Cloud

A

Anonymous

I'm running creative cloud and am still getting the same issue. Thanks for clarifying. I had not noticed this was the wrong thread. Any clues?

Sent from my iPhone

A

Anonymous

Exact same issue. This thread started in 2012 and people are still having the same issue? Not being able to make this important function work is the difference in mailing a SD card versus a hard drive on this project. Eager to find out this has been solved and I missed it somehow. Adobe? You still with us buddy?

APB_Post

Participant

Any fix for this yet? I am pretty sure my problem is the issue with long GOP structures, but if Adobe knows this why hasn't it been addressed? It's been two years since this poster started this thread and still nothing? I have a feature doc that I need to media manage down to be a backup and every time I try to do it it fails with the same error message Athentikos had nearly 2 YEARS AGO. The word was that this last update a few weeks back was supposed to have major advancements to the Project Manager feature and yet it looks like they STILL haven't fixed this issue?! Come on Adobe...

A

AKChannel

Participating Frequently

APB Post,

I had a recent problem and found the solution for myself. It requires 2 parts.

1. I would render and replace all clips in my timeline to a ProRes 422 (Right click on clips)

2. Even after I did this I had the problem. I watched the files Premiere was writing over and I located a specific file that was corrupted on my timeline. I simply dragged and dropped the file back in and it worked fine after that.

So render and replace if possible, and then see if it's a specific file giving you trouble.

Edit on friend,

-AKChannel.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded