Crop effect causes error compiling movie

when we render a timeline, every time it gets to a title that has a crop effect on it - it causes the rendering in the media encoder to stop because "error compiling movie". Definately it is because of the crop effect - since when removed - everything is OK. There is enough memory, disk space... Does anyone have a solution or an idea?
Thank you.

Dear Bill,
So we figured it out how to solve it.
The problem was that this problem occurred when implementing it on track num. 30. From track 30 and higher, the crop effect causes this problem. when we took the same titles, in the same sequence and lowered it to, say, track (video track) 25 - everything rendered OK.
Have you ever encoutered such a phenomena?
Best,
Oded

Similar Messages

One cause for "Error Compiling Movie: Unknown Error"

I just finished a huge promotional video project, one which was fraught with problems.
To start out with, most of my interview footage was RED Epic material, and my b-roll was comprised of a combination of RED Epic (some at 4kHD and some at 5k), RED ONE (some at 4k, some at 3k), XDCAM-EX 1080p, HDV 1080i, Sony AVCHD 1080p, previously exported Vimeo HD h.264 material, and still shots. Needless to say, quite a mess of codecs and odd file types to combine into one project.
Since much of my b-roll was 1080p, I decided to do my entire edit on a 1080p timeline; however, since all my interview footage was RED, I decided to use a RED Epic 1080p timeline. In doing so, I discovered something important about Premiere, and I don't know if this is a bug, or if it's meant to work this way: when you put 5k RED Epic material on a 1080p timeline and use the zoom controls in the motion effects panel to bring it to size, and attempt to export, you'll get the "Error Compiling Movie: Unknown Error" every time. This may happen with other types of footage that's too big for the timeline too, i'm not sure. However, when you instead right click on the clip and use the "scale to frame size" command, it exports just fine, with no errors.
I also discovered that (at least with my setup), PrPro can't handle large stills on the timeline; I contiually got OpenGL crash errors until I resized all my images in Photoshop to be no more than 1920px wide.
The promo video is 11:30, and comprised of five segments. I edited each segment (interview and b-roll) in it's own sequence, and then nested the sequences along with the transition/motion graphics/title slides between them on my master sequence. However, I kept getting crashes and freezes when attempting to export that master sequence which I couldn't explain. Ultimately I had to export each of the individual sequences as a Lagarith UT AVI file, and then import that file back in and place it in the master sequence where the nested sequence had been. Once that was done it exported fine, so I'm still not sure what the problems were, since each individaul sequence exported okay, and the master exported just fine after replacing the nested sequences with the Lagarith clips...
Anyway, I think I've got a pretty good promo done, and it's definitely a TON better than our last one. When I get it online I'll post a link over in the Lounge and ask for feedback...

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 compiling movie 'unknown error' premiere elements 11, tried every troubleshoot, what now?

I'm trying to export a video and I keep on running into this error message, which stops the export process. I've already visited and tried the troubleshooting suggestions on this page and this page, and this page, and none of those suggestions have worked. Here's a list of what failed:
Export in various file formats, every single one failed
I removed each asset individually and tried to export the video after each removal (100+ assets, imagine how long that took) and I got the error after every single time
I removed the front half of the video and tried exporting, still failed.
I removed the back half of the video (because if it failed if I removed the front, the problem asset should be in the back, right? nope.) and tried exporting, it still failed.
I don't have any Auto Color, Auto Contrast, Auto Levels, or Shadow/Highlight on any of my clips, although if I did, I'd try removing them.
All of my video files are the same format, so it's not a mix of formats in my timeline which is causing the problem.
I tried disabling auto-save, but it already tried to auto-save during the first 20 times I've attempted this, so the damage might already be done.
I obviously didn't use any other programs during this process
I moved all my assets to a different location on my harddrive, then reopened the project and refound the assests one by one, each of which had no problem getting into the timeline. I tried rendering after this, and the render bar sailed along until a certain point, where it got stuck indefinitely. I cancelled the render, which froze the program. I had to close it and re-open the project, and re -link every asset again. Once again there were no problems adding the assets. I saved the project before the next render, so I wouldn't have to do this a third time, and it was a good idea I did, because the program froze again during the subsequent render.
My computer didn't go to sleep or hibernate during the first 5-10 times I tried various methods for exporting. It has slept in some of the 10+ times I've tried it since, because I don't have the patience to sit in front of my screen and watch it fail again and again and again and again and again and again and again and again and again and again and again and again and again and again and again and again and again and again and again. CAN YOU TELL THAT I'M FRUSTRATED???
The first thing I noticed that was wonky with this project was when I first tried to render my sequence. The render window chugged along just fine until it got to a certain point (can't remember the %), at which point it got stuck indefinitely. I had to cancel the render, and then render other parts of the sequence bit by bit, avoiding what I thought was the problem part. I tried rendering the problem part, and it got stuck again, so I eventually just decided that that clip didn't need to be in this movie, so I deleted it from the timeline. All should be good at this point, my whole timeline is green from being rendered. But, when I tried to export the video, I started down this tourtuous path of failed exports and frustration, and now here I am, posting in the forum, hoping someone can help me out.
The problem asset (if that was the problem in the first place) isn't in the timeline any more, but I'm still having issues exporting the movie. The fact that rendering still gets stuck after re-linking assets, and after getting rid of the first problem asset, makes me think that there is some bigger underlying issue, but I have no idea what that could be. I followed these instructions and re-opened the project, tried to export, and still got that 'Unknown Error'.
Please assist before I put my fist through this company computer.

maxlong99
Thanks for your update. Let us go through it.
You wrote
During one of my isolation tests, I stripped the timeline off all assets except clips from the same footage and I also removed that New Blue effect, and the project exported without issue.
Did you run a control which included "with the New Blue effect" in this isolated test which does not sound like the "Full Project" as suggested in what you wrote next?
You wrote
Could multiple renders and project files be part of the problem? I've created many, many different versions of this project to test and see where the problem is, which in turn means I've created many different render files for each different project. If this could be part of the problem, should I keep the original project and delete all my test projects and associated render files therein?
Each of the projects should have its own name which will be applied to its files. And each project should have rendered files specific to it (for SD project whether video or still clip = DV .avi file; for HD project whether video or still clip = MPEG2.mpg file). Are you naming these different projects with distinctive names?
Have you expanded the Timeline with the -+ slider and closely inspected the track content for
a. leftovers such a very thin vertical black lines scattered about
b. gaps
c. transitions, and especially audio placement
You have probably seen the following, but I will post the link just in case. I suspect you have been there and done that.
http://helpx.adobe.com/premiere-elements/kb/error-error-compiling-movie-render.html
Please let us know what the closer inspection of the Timeline content (as mentioned) revealed.
Thanks.
ATR

"Error Compiling Movie: Unknown Error" or program crash when rendering

I just built a new PC because my Macbook Pro couldn't render fast enough. Now that I have built this brand new computer, I can't render at all! I render once and get the "Error Compiling Movie: Unknown Error" and if I try to render again, the program crashes.
My files are not corrupt as I can render them without problems on my laptop (just slowly) and on a friend's PC. I can export fine but the project I am working in is currently very small. I have 450gb of space and when using After Effects, rendering is a breeze. I have restarted, uninstalled and reinstalled and nothing seems to be doing the trick.
I feel like this must be a bug in Premiere Pro CC. Has anyone had this problem and/or come up with any solutions?

You may have more luck getting help with this kind of problem on the AME forum. Or at least have a look at this page from the AME forum prompting you for the information that can help in isolating the cause of this problem: http://forums.adobe.com/thread/1011883.

"Error compiling movie"!?! error message

Hey,
I've finished editing my film, all the effects are in, the final cut is just about there and when I try to render it gets half way through then stops and brings up this message:
"Error compiling movie" with nothing else.
I edited each scene in its own sequence. Then used one separate sequence to put all those scene sequences together as one whole movie. So basically I have a sequence that has lots of little sequences in.
I tried to export this big sequence (the whole film) and that message just keeps coming. I tried cutting it down and doing like the first half of the work area then the second. The first half worked okay but the second half still brought up that message.
Aspect ratio: 720x576
Format: Microsoft DV Avi
Compression: DV Pal
Frame rate: 25fps
Length of video: 25minutes
and it's in Pal wide screen.
Finally, free space on the hard drive I'm burning to is 63.7GB so that should be plenty of space, right?
I can't think of any other information to put here but if you need any just ask and I'll put it up. It's really stumped me this and with my premiere coming up in 20 days it's not really helpful at all.
Any help at all would be much appreciated.
Thank you,
Ben Derrick.

Often these errors are caused by some black space between clips or troublesome effects on a single clip.
Your first step was quite good to locate the problem. Now repeat that for the last 25 minutes. Split it again into two parts, each 12.5 minutes, find the part that exports OK and focus on the troublesome part. Divide it into two equal parts, etc. until you find the culprit.
An alternative might be to set the CTI to the beginning of your time line and hit page down to go to the next edit point, until you find the troublesome spot. It may mean hundreds of page down's but it is a relatively sure way of finding the culprit.

Error Compiling Movie: Unknown Error - Simple Solution in Premiere

ADOBE PREMIERE EDITORS: Be forewarned about the infamous "Error Compiling Movie: Unknown Error." It usually doesn't happen unless you're editing a big project like I am and then it screws with you because you've been editing fine until it's time to export and you can't even make your project into a movie, which defeats the purpose of all your hard work. I looked up forum after forum and finally there were a-few solutions that worked for some and not for others. (Adobe said they will get their team on this case right away.) Let's just say I do not have Final Cut Pro, so I cannot export to XML and then import into FCP to do the exporting like some people found helpful. Nor do I have the time to import my Premiere project into After Effects only to manually create all of my "dip to white" transitions. But I would have had to do that if nothing else I tried worked and thankfully, I was able to trick Premiere. It's so simple, it's stupid. Just open a new project in Premiere. Then "import" the project you wanted to export. For some odd reason, without changing anything of substance or in other words, doing practically nothing about the issue, it exports now. Just because I opened a "new" project and "imported" my old project. Of course, this may not work for others, but please try it and then reply your results. Me and I'm sure Adobe would find it very helpful to see if that worked for most people. It worked for me.
[Profanity is not permitted. Removed. Please keep your language family-friendly.]

I agree, Jim, but my train of thought was that a lot of people were changing and replacing and taking out effects and clips from their sequence to see if it was the components in the sequence that was causing the "unknown error." However, I had the same "unknown error" and was able to export in Premiere anyway by just practically "telling" Premiere that it's a new project, when I'm importing an old project to do the same task. Which makes me think that maybe Premiere doesn't have a problem exporting the specific files that most people thought were the problem, maybe it was just a glitch somewhere in Premiere that made the software think there was a problem after a certain amount of time, when there really wasn't. I don't know, I'm not a coder so that's just my layman guess. I did notice that Premiere was exporting/rendering fine when I was just beginning my project, but after it got to a certain length, that's when I couldn't render or export anymore. It honestly baffles me too. It would be useful to see what the results are if other people tried this simple switch-a-roo so possible issues can be narrowed down.

Error compiling movie: unknown error & Mercury Playback GPU acceleration

Hardware
2014 Mac Pro, 12GB RAM, 3.7 GHz Quad-Core Intel Xenon ES Processor, duel AMD FirePro D300 2048 MB graphics cards
Software
Mavericks (10.9.4)
Premiere Pro CC2014 (8.0.1)
I'm attempting to render out a moderately complex sequence. Raw footage was dslr h.264 MOV files. 30fps 1920x1080 from canon. It has some clips that are pulled from multi-cam sequences and a few that have warp stabilizer applied. 4 total audio tracks with some linked comps from audition. Whole thing is about 14 minutes. It should be noted that I render out similar sequences regularly without issue. However on this occasion whenever I tried to render out using media encoder ( for web h.264 MOV 720 30fps) I was getting an error at the same clip every time. Error Compiling Movie: Unknown Error. So I checked out the clip. It was one of the ones with warp stabilize. I turned that off and sent it out again. Render got further this time but hit a different clip with warp stabilize (after getting through like 2 other clips with warp stabilize enabled) and gave me the same error. I tried getting rid of cache files, saving to a local drive instead of a network drive, uninstalling and re-installing premiere even. (which btw if you check remove preferences then reinstall it def still has preferences so that's a total load.) Anyway I was doing some forum surfing and found several people going all the way back to PP 5.5 saying that the only solution they found was to turn off the Mercury Playback GPU acceleration. Tried that and it's currently rendering just fine but taking roughly 4X longer than with acceleration. The GPU acceleration is a big deal for me since our company relies on putting out a lot of volume quickly. Has anyone else experienced this problem and is it something you were able to fix without turning off GPU acceleration. Grateful for your input.

sorry I actually wrote that wrong. I am using the H.264 setting 720 30fps to create a web friendly .mp4. Alternately though I decided to watch and see if it was the same clip failing every time. It is. I went into the project and did a match frame for the offending clip. Dragged the a new version of the same content onto the timeline and copied the warp stabilize effect onto the new version. Well this time the encode got past the clip with the issue, however the next clip it hit with warp stabilize caused another error compiling movie: unknown error. I guess at this point my options are to turn off the GPU acceleration and wait for a render that takes more than 3x as long to render with software only, or to go through the whole timeline and replace the clips with warp stabilize (there are a bunch, the shooter wasn't having a great day on glidecam). Not a great solution on either end. Please let me know if I should file this as a bug report. Though it seems people have been having the same issues since version CS5.5

Error compiling movie: out of memory !!! Premiere CS3

Hey every1 --- desperate need of some guidance here. I've been all over the internet and these boards --- have seen this come up with a lot of people but no real solid answers that I'd seen or that have helped.
First off, my comp is an imac 3.06 Ghz Core 2 Duo, 4GB memory. (just bought the computer last year)
I'm shooting with a canon 7d in HD (1920 x 1080p) and I'm editing using Premiere CS3. I've noticed that editing has become very difficult since I started using HD; playback is very choppy and the 'quality settings' in the preview monitor are a joke and do absolutely nothing whether it's on draft or automatic.
Anyway, despite the choppiness and slow editing, I was able to get a 3 min clip completed. These are my export settings:
Export > Movie
H.264
960 x 540
23.976 fps
Square pixels,
100% quality,
recompress: unchecked.
Once exported (I was able to export smaller timelines previously--- say, 50 secs of footage or so) the files look AMAZING and from there I use them for online video via vimeo -- stuff looks really awesome.
Anyway, recently I'm getting: 'Error compiling movie. Out of Memory. Change optimization preferences to memory', etc. etc. Well, I did as it asked and that did absolutely nothing.
So, I decided to open up my activity monitor and watch what's going on with my memory while premiere is exporting. I also closed ALL unused applications. System runs at about 2.16gb free memory before I start exporting. Memory seems stable during export UNTIL around the 50% exporting mark, and then its starts climbing like crazy and my memory just gets eaten up --- finally resulting in a crash at about 70% render.
I really don't know what else to do. Does my computer not have the power to export 3 min of HD footage??? This seems surprising to me ... I don't know what else to try.
Thanks for any help !!!
-Mark

Hi Mark,
Hope you are having a wonderful day.
Sorry to hear that you are having such a hard time. Although I did not specifically get the out of memory error, I can only be convinced that that is the problem.
Although I am not a computer whiz, I have learned my share of things. I have been troubleshooting a video all this week (really, a couple of months), but I had to put it aside and come back to it.
I tend to be talkative; so I will get back on topic or at least try to stay on topic, so bare with me. Smile....
Here is what I have learned and maybe it will help you with yours if you have not found a solution already.
Based on your hard drive specs and ram, I was thinking the same thing e.g. hard to believe that you are not able to render 3 minutes of video in HD. I primarily work in HD/1080p.
The place where we are similar is that I eventually could get the video to render by reducing the workspace that is rendered piece by piece until I was able to render the entire file. When I tried to encode the video, I kept getting error compiling messages. I tried different codecs, deleting xmpses, not rendering xmpses, etc. I could not figure out the keyframe trick so I just put in a black video from after effects. By the way, all of my videos intro the same and no problems with the other videos fading from black to a still photo.
Here is the problem from what I could gather.
Simply, out of memory. I was rendering and trying to encode a 45 minute video with after effects compositions and the dynamic linking kept timing out once the file reached a certain size. There were no other true fancy effects. I do alot on the green screen and just use after effects to make a white background. Smaller videos, rendering has been slow, but doable. This massive video would never compile. I won't bore you with my system specs, but know that similar to your situation, the system in theory should have been adequate.
Work around...
I ended up exporting the video as 3 separate 15 minute video clips. I could not get them to encode as .wmv files so I encoded them as .mp4 files. By the way, I still encoded in HD.
Here is the kool stuff.
After what seems like forever, I found a converter that could convert .mp4 to .wmv and rejoin the files to play as one large file with the same quality as my source file and no audio synching issues. By the way, I do not work for this company. I just found this encoder at 4 o'clock this morning after trying all of these other converters that were straight garbage or were free to try and not really free if you wanted quality. By the way, the conversion tool is not only user friendly, but free which is awesome.
The name of the software is Media Cope. Just visit www.mediacope.com.... Be sure to send the owner an e-mail to thank him and let him know that Mark sent you. I just sent him an e-mail earlier to let him know that I was going to post on Adobe what a wonderful software he created. I just needed something free, quick, easy, and user-friendly.
Whoops... got off topic....
I'll do a summary at the end for my recommendation to you.
Here are some other tidbits that I learned as well that may save you some time.
When editing this is what I do now...
1) I use CCleaner from www.piriform.com to quickly clean my system especially temporary files before I start editing and if I am switching from project to project.
2) In all of my troubleshooting this week, I found a kool little software call Smart Close. (Just google to find this one.) It closes all of your non-critical background files in order to maximize system resources. (When I am done editing, I just reboot and all of my background programs start up again. You do not have to do it that way, that's just how I do it. The nice thing is that it is a wizard interface; so you do not have to try to figure out if a process in the background is critical or non-critical.)
3) Depending on my mood and if I did not forget, smile.... I change the priority to high for the adobe products in the task manager.
More things that I learned...
1) We are not able to change the temp file for how Adobe encodes. My logic was if I could change the encoding to a hard drive that was simply empty so Adobe can render there, then I would be good. Wrong.... Adobe does not allow you to change the temp location. (Note: This is what I discovered in the different forums; so encoding to an external hard drive is not the best move. Read more to se why.)
2) It is best to have your scratch disks as your internal disk. If you have multiple internal disks, then you shoud check some other forums for the best way to set up your scratch disks. When I was just starting out, I bought an external hard drive enclosure with the thought that I would work primarily off of those external drives with the option of doing some RAID work. Bad idea... Even the simplest of tasks took forever. It was best to work off of the internal drive. By the way, I still use the enclosure hard drives for backups in order to allow me to free up some space on the primary hard drive. When rendering, it is truely a use of the RAM and the hard drive space in the editing process.
I'll leave you with this...
I take back what I said earlier, you do need a new computer with more RAM. If you can get 16 GB, great. The primary reason is that if you are editing in Premiere and if you do anything with dynamic linking into your after effects, it will cause your ram to climb as the file gets larger. Of course, be sure to get the largest hard drive possible as an internal drive, the maximum on processor speed, 64 bit operating system, etc.
I know you are like by now, Mark, what is the point of all of your gibberish... Really, it was to share with you and others on some really kool work arounds.
My recommendation for you are as follows.
1) You have already proven that you can render and encode 50 second clips and you are very happy with those clips, so create separate smaller clips for this particular project.
2) Once you have the final clips outputted, then use Media Cope to rejoin the files as one large file and you are done.
(Note: The one thing that I did notice is that there is a small break right between where the files are merged. The nice thing is that as a video editor/film maker, you will be the only person likely to notice it because you know where the breaks are. The other nice thing is that the untrained eye will not notice it and if you had to submit your work to a television station especially on DVD, the video system should recognize the file as one large file and play all the way through. Note: For the last sentence, I said 'should play all the way through' as I have not had a chance to check this one yet as I just finished this project today and still have to turn in all of my videos. I still have some more videos to merge.)
By the way, the only specs that I will share are that I work on a PC and it has 8 GB of ram.
The summary of the summary is that sometimes an error compiling message could simply be that your system does not have resources to render and the encode that large of a file. At least that is what I learned this week or at least my specific situation. The confirmation is that I just finished shooting a documentary which was one hour and some change and was able to render and encode to .wmv with no problems. Of course, I was not using after effects for this particular project.
In either case, hope all the information helps you with your project.
Have a wonderful day and happy holidays everyone.
Mark

Error compiling movie during export

I'm using Premier Pro CC 7.0.1 (105). I have exported a couple films before, but am unable to export my current project. When I try to export the film as an MP4 to my desktop, PPr spends about 3 minutes encoding the movie, but only makes it to 19% before "Error compiling movie. Unknown error." pops up on my screen.
I have also had issues with a "low-level exception" occurrence when using the "shadow/highlight (AEVideoFilter)" effect. I don't know if the two are related, but have had many crashes with this current project (I'm currently working on the fifth PPr generated copy of my project).
Any advice would be great!

And that's why it's nearly impossible for us to help with Unknown Errors. The causes are varied and, as the name implies, unknown.
Unfortunately, the best option for anyone encountering this error is to simply experiment and hope to find the issue, as you did.

"Error compiling movie. Unknown error" - my solution

I was trying to encode a project to mpeg-2 DVD yesterday, when I repeatedly received the message "Error compiling movie. Unknown error." I had had this happen before and I can't remember what hoops I jumped through to fix it. But yesterday, I found a simple solution that may work for someone else in the future should they ever search for this problem in our forum.
The problem turned out to be with some .wmv files mixed in with all the other .avi files I was using. And the solution was to right-click on the .wmv clips in the project bin, choose "modify," then choose "interpret footage. From there, I changed the frame rate choice from "Use frame rate from file" (which was 30.00) to "Assume this frame rate" and entered a value of 29.97. Voila! Everything rendered without a hitch!
Hope this helps someone.
J. D.

I agree, Jim, but my train of thought was that a lot of people were changing and replacing and taking out effects and clips from their sequence to see if it was the components in the sequence that was causing the "unknown error." However, I had the same "unknown error" and was able to export in Premiere anyway by just practically "telling" Premiere that it's a new project, when I'm importing an old project to do the same task. Which makes me think that maybe Premiere doesn't have a problem exporting the specific files that most people thought were the problem, maybe it was just a glitch somewhere in Premiere that made the software think there was a problem after a certain amount of time, when there really wasn't. I don't know, I'm not a coder so that's just my layman guess. I did notice that Premiere was exporting/rendering fine when I was just beginning my project, but after it got to a certain length, that's when I couldn't render or export anymore. It honestly baffles me too. It would be useful to see what the results are if other people tried this simple switch-a-roo so possible issues can be narrowed down.

"error compiling movie: unknown error" in premiere cs3.2 / win8

This happens during both Export and Render Work Area, as soon as the renderer hits one of my assets. Initially, this asset was an uncompressed AVI with an alpha channel, over another uncompressed AVI. You can see the Progress bar suddenly get extremely slow when it hits that point, and then it gives the unknown error within about 10 frames. As far as I remember, this NEVER happened when I was rendering on my laptop, running Windows 7 (a former temporary setup while I was waiting to get a new workstation).
I've tried taking some pressure off Premiere... I rendered the sequence in AfterEffects, so Premiere didn't have to deal with the compositing. I also wrapped the asset in a MOV container, with PNG compression, so the files weren't so large. This seemed to help in certain cases -- using this method, I can get through some of the biggest assets. It still happens a bunch of times throughout my sequence, though.
I have the rendering optimized for "memory" in the project settings. I also have more than enough hard drive space on the drive I'm exporting to.
My instinct and limited powers of observation suggest to me that this is a memory problem. This computer's not exactly a world-class production system. However, there are other clips -- mostly HD footage directly from the camera (HVX200) but also some shorter-duration uncompressed AVI's -- that seem to render fine. Plus, even some clips already recompressed to MOV's in AE are causing the same problem. I don't want to have to fiddle with this on every project til I can afford Adobe CC... has anyone else seen problems like this, and found some kind of broader solution to them?

If you have not seen this Adobe KB article on Error Compiling Movie, it might also be helpful: http://helpx.adobe.com/premiere-pro/kb/error-compiling-movie-rendering-or.html
Good luck,
Hunt

My specific "error compiling movie" situation

There are a few threads in this forum relating to "error compiling movie" messages, but none relate to the problem as it manifests itself on my system.
First of all:
CS 5.5.2
Windows 7 64-bit
Nvidia GTX 460
16 GB memory
i7-2600
Now, I have a project which has a wide variety of media, from AVCHD to iPhone video. It's about 17 minutes long, and I can output the entire project as a Windows Media file with no problems. But if I try to output an Mpeg-2 DVD file from within Premiere, I get an "Error compiling movie. Unknown Error" message. If I try to output a Mpeg-2 DVD file in AME, it will lock up at different points each time. But, if I use dynamic link to bring the project into Encore, it renders fine.
What might be causing this? I've read on this board that down converting AVCHD footage to SD using Encore does not produce a video that looks as good as doing it from within Premiere, so I'd like to be able to do this.
J. D.

I can't say why it's happening. But you can install a free, lossless codec like Lagarith or UT and export out an lossless AVI file. Then you can use AME to create the MPEG form that AVI Master.

CS 5.5 Export - Error Compiling Movie - Unknown Error

I am running CS 5.5 and every time I export in Premiere or in Media Encoder - I get this message:
Error Compiling Movie - Unknown Error
I have tracked it down to a video clip with alpha channel. I have some animated overlays - If I turn off this layer it exports fine, but unfortunately I need the animated video with alpha in the exported file.
The video is using the Lagarith Codec. I have updated the codec and still getting the error. I have also tried using other codecs that support an alpha channel, like the Matrox IFrame with Alpha codec and the same problem exists.
These are TV shows and I need to get this resolved if anyone has any suggestions. I've done hundreds of these same formatted shows in the past, so it is not my system, drives, cpu, etc. This did not happen on previous versions of Premiere Pro.

Hm-m,
Obviously, you are using the Alpha Channel for some Transparency. Are there any other Effects applied to that problem Clip?
If you could post a screen-cap, showing that Clip Selected (and probably the Effects Control Panel also), plus the underlying Clips on the Timeline, perhaps someone can see an issue there.
You do have the 64-bit version of Lagarith installed, don't you?
Good luck,
Hunt

"Error compiling movie. Unknown error" while rendering a .PSD or .PNG

Hi,
I have this problem: When I try to make a "Render Selection" or export my video, everything is ok until I reach a .PSD file I've placed almost in the end of the clip.
The same is for .PNG file, a dialog appears saying "Error compiling movie. Unknown error".
I've tried to delete the effects, but it's the same. To be more specific, I've applied a simple "Cross Dissolve": Until the transition is working, and the picture is not entirely visible, the rendering works. When the picture is "complete", the render stops and the error appears.
When I tried to delete the transitions, the error appeared in the beginning of the .PSD picture.
Any help?
Thanks

Are you stills in RGB format? what pixel size are they?

PP CS4: Error compiling movie. I/O Error

I get this incessant I/O error any time I try to export a movie, regardless what format or
codec I am exporting to. I've tried this on a BRAND NEW Project with the same result.
I'm almost convinced that it's a problem or issue with Adobe Media Encoder? I tried to
export a GIF image with the result of:
Error compiling movie.
Unable to create or open output file.
Just five seconds ago, this is seriously driving me up a wall as I have my projects due
very very soon. ANY help would be greatly appreciated.
-jd

@ Harm Millaard
I'm not really sure what you mean by OE? Are you saying that its something to do with my hardware?
I had this running great in the past, before we changed buildings, I fired it up today to do some work
and no dice.
I insert a video, drag it to my time line, file > export and any option therein is wrong. The only thing I've
been able to export as is a static GIF, no AVI or etc....?
@ the_wine_snob
Actually I already did check out my Event Viewer prior to post, it came out with a clean bill besides
a few issues with my network not being able to update its dynamic ip (does not effect, has been doing
it for ages.) I used to be a computer tech so it was the first thing that I looked at. As for addressment
errors with hardware issues I'll have to wait until I get back to work tomorrow in order to check those
and make sure that I'm still running a tight ship.
I can tell you BOTH though that I am running a custom built Graphics Workstation put together by
me with no expense spared. I am running a Quadcore w/ 4gb high latency ram, and a 10k rpm hdd.
I believe that if there's a problem it would show itself in my other Adobe apps, and PS and AI seem
to scream, as well as After Effects, EnCore and other resource intense Master Suite apps.....?
This really has me scratching my head, I'm wondering if a full reinstall might be in order......

Crop effect causes error compiling movie

Similar Messages

Maybe you are looking for