WRT the issue with large stills . . . I'm now on 5.5 and it still occurs. This has been a defect since at least CS4. I wonder why Adobe can't fix it? If it's some "software architecture" issue, they could at least prohibit you from importing a still that's too large.
Thanks for the detailed report, David. I hope you reported all this to Adobe.
I've also gotten errors trying to export a sequence with nested sequences, and used the same workaround to get the job finished.
I'm hoping for great things from CS6.
What I'm wondering is... well, I can see why someone might want to shoot an promotional video in standard high-definition video (720 or 1080), because yeah, that's where so much video is going anymore. But... why would someone go to the trouble of renting and setting up a 4-5K camera if the material isn't being made for the movie screen?
I was having a similar problem.
I shot on a Scarlet and I found I could initially import and edit the r3d files just fine, also I could render them without any problems.
But as soon as I saved it and re-opened the project I'd get the 'Error compiling movie: unkown error" dialogue.
If I rescaled it, it went just fine.
However, I found that if I went into sequence settings, and changed the preview format - or even just the codec, it would work again.
Hope this helps someone else out, because I nearly lost my mind.
So, I ran into this the first time recently. I discovered it when I copied an adjustment layer for quick grading with an RGB Color Corrector and Color Balance effects in it from a rehearsal cut of a short film.The effects worked fine and rendered out without issue. I imported the sequence into my 'final' cut so I could reuse the titles and adjustment layer. I copied the adjustment layer to the new rough cut of the final sequence and ran into this error when I tried to render it, but only after applying the adjustment layer. I found that if I turned off the Color Balance, the sequence rendered fine. I found that if I moved the Color Balance above the RGB Color Corrector, the effect of the RGB effect completely disappeared AND it rendered correctly (both effects turned on) - so reversing the order worked, but effects were weird. I also found that if I added ANY non-GPU accelerated effects to the RGB Color Corrector that I'd get the same compile error (unknown).
I went through and deleted clips until I got to 0 on the timeline, added a new one back on, and it still wouldn't render. So, I created an entirely NEW sequence, copied all video and audio (not adjustment layer) from the original failing rough cut of the final sequence, and pasted it into this new sequence. I also copied the adjustment layer again from the rehearsal cut into this new sequence and it is rendering just fine.
HOURS WASTED DOING THIS! It would be awesome if Adobe actually tested their products before releasing them instead of forcing us to do it for them. My project consisted of about 30-40 different clips and audio, all from the same DSLR (Nikon D810), nothing fancy, two effects in an adjustment layer applied to the entire sequence, and Premiere couldn't handle it. Given this and some of the comments I read while troubleshooting this on this forum, gives me pause in trusting Adobe products for any real work that has a deadline (unless, of course, you build in the required Adobe testing time into your budget).
So, just another data point; something else to try. Create a new sequence, and copy everything from your non-working one to it, and see if this will jump-start Premier. Worked for me. Good luck.
Error compyling movie can be anything; clips, stills, effects, adjustement layers, keyframes, scaling, speed, nesting, you name it.
Best way to solving this is to export the sequence in small portions
In AME open the Preview window and watch the export and see where it stops.
Error compyling movie has been around ever since I can remember back to Premiere 6.5.
I just spent all day trying to figure this one out. Same issue as mentioned above. Tried all kinds of things. I finally stumbled onto another post because I had a hunch that it had to do with "Temporal Smoothing". Sure enough. I turned off all instances of "Temporal Smoothing" and was able to render without a problem.
There is another solution.
I have a Sequence "A" with a Multi Camera Sequence "B" inside. When you use some Audio Effects (like a Compressor) inside the Multi Camera Sequence "B", there will be the "Error compiling movie" if you export Sequence "A". When you take the Compressor on the Multi Camera Sequence in the Sequence "A" the export is fine.
I hope you understand me.
Hi, I have the same issue and i don't know what to try anymore.. clips, stills, effects etc..
But I found something shocking:
Same sequence split in 2, 1st half and 2nd rendered fine individually, but all together Failed!
I've got a sequence consisting of 1 (one) png sequence at 1280p and 1 audio file. Can't render. Unknown error. Premiere: I'm sick of your ****.
Just for testing purposes I've tried just rendering a short png sequence to h.264. No go. WHEN ARE YOU GONNA FIX THIS ADOBE????
Adobe is not going to fix this. As its an unknown error.
Have you tried making a new project and importing the old one into?
Adobe is going to fix the H264 error Its effecting to many users since there last update. Ann is just another MVP that doesn't help anyone with there comments.