Premiere CS6 Unknown Error in Rendering & Export

Question

Hello,
this is an ongoing problem that persisted on any version of Adobe Premiere Pro I worked with, including CS5,5.5 and the latest 6.
I am stuck with a feature film on a CS6 Timeline, getting an Unkown Error during rendering and Media Encoder exports. 
I get the same error if I attampt to create a new trimmed project with Project Manager.
I am aware that this is one of the most common problems in this forum, and before opening a discussion I tried everithing I could:
- Replace the media at the point of the error/crash (even though the error seems to happen randomly in dirrerent portions of the timeline)
- Disable MPE
- Reset Secutity and permission on files
- change hard drive
- Create a new sequence
- Disable second monitor
I have to bring an export of my film and a new trimmed project by tomorrow to a color house and I am currently stuck.
I managed to render the entire timeline before exporting. Redering would stop randomly, generating the same "Unkown Error in Copiling Movie".
Although I rendered the entire timeline by creating different IN-OUT with the work area selection.
After a long and tetious rendering process I managed to have the entire timeline "green" and ready to go.
I figured that this way the exporting process would have been successful. Unfortunatelly not.
I switched to Premiere Pro for its ability to edit R3D media, but what's the point if we cannot export the project? And neither trimm it to a file that I can give to a colorist?
Here some details of my workstation and source media:
- MacPro 12cores 64Gb ram
- Internal 6Tb raid for source media
- 4Tb Dulce Scratch drive
- Editing 4K and 5K R3D Media natively
If anyone found a solution to this problem, please help.
Thanks

Answer 1

Hi Neonhigh,
If you are going to color correction, why do you need an output? Aren't they color correcting the native files?
I need an output as reference for the VFX department, I need an output for the sound designer, I need an output for the producer, I need an output for myself and to send to my girlfriend. The question I should ask you is, why shouldn't I need an output?
What's wrong by exporting my timeline in a format that is not r3d files for reference and production management?
I was talking about color correction only, as they usually only need the native files. Of course, an output would be necessary for all the other things you mentioned. Nothing wrong with that.
Neonhigh wrote:
If you need an output for some reason, why are you rendering at all?
As I explained I simply rendered because the software was having several random "Unkown" problems in exporting. I though rendering and exporting a file matching the timeline settings would have solved those annoying Unkown Errors, giving me at list an export based on the render sttings.
Problem is that PPro CS6 fails also to render the timeline, and I needed to break the process in 30-40 segments in order to achieve a complete rendering.
Rendering in Premiere Pro is primarily for playback, and not necessary for output. In fact, it's a waste of time in most cases. Render files are typically not used for an output unless you explicitly want to do so. Typically they are lower resolution "preview" files that you don't want to use.
Regardless, you should have no trouble rendering sections of your Timeline. Are you updated to Premiere Pro CS6 (6.0.2)?
Can you try an export without rendering?
I wish PPro CS6 was reliable enough to allow me to simply export.
I still did not solve the problem. Several people from the redusers forum are trying to help me as and they all ran into the same issue.
Currently this are the issues:
- PPro does not render the entire timeline
I'm trying a test project right now and so far it is rendering OK. Can you point me to the reduser forum post where people were giving you assistance?
- does not output the entire timeline (if not chopping it in 12-15 parts)
I'll test that, as well. You should not have to segment the sequence in order to get an export.
- Project Manager does not trim the project to pass it to over post prod facilities.
Sorry, the Project Manager will not consolidate every media type. It will copy, however. This would be a feature request or bug report: http://www.adobe.com/go/wish
Beside questioning me with why I want to render or export my project,
Not questioning your capabilities or talents, I just wanted to know what you wanted to do, and why. Typically, most people don't render as much in Premiere Pro as they do in other NLEs and I was wondering why you needed an export to go to color correction. That's all.
Many users in this forum (as well as on the entire internet) experienced th same Unkown Problem:
http://forums.adobe.com/message/4661398
There could be many different variables which can cause that error. The troubleshooting doc you found addresses many of those. I will add the "Unknown Error" warning to the document.
There is no "single fix" for this problem, I'm afraid, and these are our opinions and solutions on the matter.
A legitimate gripe would be that the error is too generic, and I would agree with you there. The error should contain more details about how to remedy your issue. Please make a feature request for more descriptive error dialog boxes: http://www.adobe.com/go/wish
I will also mention it to the product team.
I understand that, being an "Unkown Errror" Adobe does not have a iniversal fix, but please don't ask me why I want to output my timeline.
Again, I was only asking in the context of color correction. Of course, you want an output for various reasons.
I've written up your bad experience in my case notes and I'll do my best to get you some better answers to your questions. You definitely should not have to jump through hoops to render or export a .R3D sequence.
Neonhigh wrote:
Here is a temporary fix for who runs into this problem:
Yesterday, after trying everything I could think of I simply exported an XML, opened it in Final Cut Pro and exported all the files and formats that I needed. No Unknown Errors.
Thanks for the workaround. I'll add it to my notes.