After 2 years of using project manager to consolidate and back up my projects, it is now giving me constant grief.
On almost every project (mainly promos) it is unable to calculate project size og unable to back up my projects.
Every time giving me "unknown error", asking me to try again. Not even once, has this improved anything. I keep getting "unknown error"
It does not work and I've tried many combination of settings.
I will have to stop using Premiere as my editor if this keeps up. I cannot keep backing up by copying 100s of GB of assets for a each 30 sec. spot.
What is going on?
Has a bug been introduced in the last few versions?
Does anybody else have these issues?
What could be the possible cause?
Yeah, Im ending my subscription effective immediately. 2021, same issue, classic unkown error. Test your software.... Im out.
Yup. Im done wiht Adobe. This is inexcusable.
What I finally did was create a new project, copy just the seq I want and then project manage. That worked for me. 🙂
Didn't work for me... this is absolutely ridiculous.
Hasn't worked for me. The post facility I'm working with won't even accept premiere projects so I have to output it myself. It should not be this difficult or such a scavenger to figure out what "Unknown Error" is.
Sorry, I just did this and it still resulted in the unknown error. The problem is still a problem
No luck, in 2021. Cool.
SOLUTION SOLUTION SOLUTION: Uncheck the box "Include Prevew Files" when you getting ready to start the media manage
I did the same, I also unchecked the box for renaming files to match clip name.
This did not work for me 😕 Adobe its been years, we shouldn't still be having this issue.
Did you also uncheck the checkbox for Audio Conformed Files ?
Did you try to copy the timeline into a new project ?
That's the kind of things which generally work for people having issues like this.
If you still have troubles, you can use the third party plugin "PlumePack". It's not free, but it's a good alternative to the Project Manager. There is a "Trimming" feature also, which cut your files without re-encoding.
When i faced this issue in 99% cases it was solved by unchecking "Include Audio Conform Files"
Hi there I just had the same issue here. And what I have found is try to include the Unused clips and even the audio previews.Then once collected redo one more time without the unused clips. I know this is a double process but I would rather do that than getting stuck for several figuring it out. Hope this works for all of you.
I cant believe this error is still not fixed or the error message to have more information in 2020. Adobe, you have a lot of competition out there now, you are going to lose a lot of subscribers if you cant fix errors like this.
Hi, I'm sorry but this proposed solution is anything but. What if you have dozens and dozens of filenames in what you call "special characters", from your own language? And why should that be a problem? This needs urgent fixing, please. I'm running CC 13 0 3.
That is a specific thing if you mean the language characters of a different language are causing the problem. And it would need to be brought to the attention of the developers.
This forum is primarily user-to-user, they have a different forum for communicating with the devs ... their UserVoice system. I've talked with one of the engineers tasked with reading every post filed there. He wants MORE DETAILS. Please! Some people just say "x is broke fix it" ... but if they can't replicate the broke, they can't have any idea what to fix.
Click on that link, and search that forum for similar posts to your problem.
Either 'upvote' a similar post, or create a new post. Give full details, including the language and characters that are causing problems, then post a link to that back here. Others can see it and go upvote it.
Been smashing my head against the wall for an hour on this. Turns out Project Manager doesnt work if you have braw (blackmagic raw) files. This is in 14.1.0. Luckily my project isn't huge and it'll only take me another hour or so to copy everything manually ...
What specific thing is happening with Project manager with your BRAW files?
This is the sort of thing that should be filed in detail with the developers, which is done by going to the UserVoice system and searching for similar issues, adding details and upvoting ... or filing out a new post.
I've talked with one of the engineers who reads every flipping post filed, and his main complaint is they don't get nearly enough detail with most posts to be usable. System hardware/OS version, Premiere version, media used, part of the app with problems, and a description of what you're doing when X unfortunate thing happens. And what X is compared with what you expected.
One of the issues is that as users we don't get any sort of error message or log to help with the issue so we can send to the engineers. It's just a plain error message for this project manager issue. FYI, I cannot use Project Manager with BRAW files either.
If your engineers main complaint is they dont get nearly enough detail with most posts to be usable, maybe they should reply to these messages if he is reading them all and ask for the detail they need. The end-user doesn't know what details they need to post to help engineers with the errors. In most of the posts here there are only 2 parts of what you are requesting missing, System hardware/OS and Premiere Version. The rest of it is detailed in many posts. This sounds like engineers blaming the end users for their errors. By the way what is a "flipping post"??
And since your engineers is reading this, can he/she please respond to this message with the exact details they need to fix it. Let's get this sorted out so the project manager starts working again.
BTW for all those who wish to upvote this in Uservoice as Neil suggested here is the link to the specific problem. Please upvote it so we get an issue. No engineers have responded in uservoice either.
Having same issue here with BRAW files.
ERROR! an unknown error occurred during the project manager operation.
Using premiere pro 14.0
MacOS Mojave - 15 Macbook 2019, 32GB 2400 MHz DDR4 Ram. 2.3GHz intel core i9, Radeon Pro Vega 20
I expected the project manager to complete the operation. It failed about half way through the operation with the above error message. It appeared to be copying the files and then failed.
Sorry for the frustration. Keep in mind that Neil is a volunteer and a user like you. He does not work for Adobe. If you are having any specific trouble with a feature or have a feature request, as Neil suggested, let the product team know over at User Voice.
"And since your engineers is reading this, can he/she please respond to this message with the exact details they need to fix it. Let's get this sorted out so the project manager starts working again."
Engineers actually do not read these forums, they do read the posts at User Voice, however. Keep in mind that they do not always respond to posts, but they do tabulate the upvotes and will respond if need be.
These forums are run by users like you with some participation for support staff like myself. We are here to help users fix issues, we cannot address bugs or feature requests here.
Anything releated to product improvment must be addressed to developers over on User Voice, not here. Sorry about that. I do understand your wanting to have Project Manager working for BRAW. Unfortunately, that is expected behavior as BRAW is not yet a format Premiere Pro supports natively.
Great! That's a clear answer. Premiere pro does NOT support BRAW files. Thank you for the clarification. However this issue has been going on since before BRAW was introduced by Blackmagic. So there are other issues going on too. But, its good to get an answer, we won't be able to project manage with BRAW files. So we can stop trying to find work arounds like changing file names.
Neil said the engineers read "every flipping post", he must have been referring to the posts at User Voice.
Got it, clear as day. Thanks for your response. If anyone wants engineers to know of issues, post it over on User Voice. Not here. AND, include your specifications as Neil suggested.
Thanks for your clear response Kevin.