General Error Out Of Memory Final Cut Express
Please enter a title. You can not post a blank message. Please type your message and try again. imjtblanton Level 1 (4 points) Notebooks Q: General Error, Error: Out of Memory I'm editing a video in Final Cut Express HD 3.5 on a 10.6.8 Mac OS X. When I try to view one of the clips final cut pro 7 general error from the browser window by double clicking on it I recieve a message that says "General Error" final cut pro disk full and then a second one that reads, "Error: Out of Memory." I still have 54 GB of memory left so I don't beleive it's a memory final cut pro not enough disk space problem.Here's the info about the clip I am using. Friend A made an original video that I needed some shots from. I don't understand the online video sharing process very well so I had him send it to friend B. Friend B larry jordan then downloaded it as a .mp4 file and gave it to me on a flash drive. I can play the clip just fine on my computer through Quicktime. So why am I recieving this error? Any help would be much appreciated.Also, under the information about the video, it says, "Codecs: H.264, AAC." Posted on Jan 1, 2014 10:43 AM I have this question too Close Q: General Error, Error: Out of Memory All replies Helpful answers by Meg The Dog, Meg The Dog Jan 1, 2014 10:45 AM in response to imjtblanton Level 6 (11,168 points) Video Jan 1, 2014 10:45 AM in response to imjtblanton FCE does not directly support mp4 video.Download MPEG Streamclip (free)http://www.squared5.com/svideo/mpeg-streamclip-mac.htmland convert the file to an FCE friendly format - if HD, then Apple Intermediate Codec, if SD then DV.MtD Helpful (0) Reply options Link to this post by imjtblanton, imjtblanton Jan 1, 2014 11:07 AM in response to Meg The Dog Level 1 (4 points) Notebooks Jan 1, 2014 11:07 AM in response to Meg The Dog I did that and have run into another problem. When I try to convert the video I get a message that reads, "Error: Can't Prepare the Movie."I downloaded MPEG Streamclip and hit "Export to MPEG-4." Under the window that pops up I selected "Apple MPEG 4 Compressor." Frame Rate was set to 29.97, 1280x720, Interlaced Scaling checked, Frame Blending unchecked, Better Downscaling unckecked, Deinterlace Video unckecked.Also, for future reference, what video formats is Final Cut Express capable of using? It seems like it's not capable of using anything that's convenient. Helpful (0) Reply options Link to this post by Meg The Dog, Meg The Dog Jan 1, 2014 12:15 PM in response to imjtblanton Level 6 (11,168 points) Video Jan 1, 2014 12:15 PM in response to imjtblanton In MPEG Streamclip, you want to use the Export to Quicktime option, then set the desired format and framesize there.As stated in my previous post, you do not want to convert the file to M
Gigs are full of a lot of things other than cached files, so the actual number is even a bit smaller. The only thing that you can do to prevent the error is actually to use less memory. Thankfully, here are a bunch of tips on how to do that. 1) NEVER edit in h.264 or any other compressed format. It will add a little bit of transcoding time to the beginning, but it will prevent a lot of rendering and rerendering once in the edit. 2) Make your sequence settings (ideally) prores, and make sure that all of your footage is transcoded to the same flavor of prores (LT, HQ, 4444, whatever) This applies to framerate as well! 3) Ensure that your audio is aiff (not mp3) and at the https://discussions.apple.com/thread/5734780?tstart=0 same settings as your timeline. 4) Resize all stills to rough video sizes. 30,000 pixel wide files will bog down fcp immediately so crop or scale it down to something closer to your timeline resolution. If photoshop does this once, then fcp doesn't need to do it a million times. 5) Flat stills are easier than layered files. FCP doesn't have to deal with the precomp that psds or layered tiffs come in as. 6) Close unneeded tabs in the timeline and canvas. So that's basically it. Pre-process your footage to http://blog.youdownwithfcp.com/2012/07/17/how-to-fix-out-of-memory-error-in-final-cut-pro-7/ be 100% the same as your timeline and work with as few sequences open as possible. In my experience it seems that once things start erroring there is very little that helps outside of a restart. ~ by ross on July 17, 2012. Posted in FCP, glitch 5 Responses to "How to fix "Out of memory" error in Final Cut Pro 7" Thanks for the list Ross. I keep coming up against that wretched message all the time even when using ProRes… Then again I've been working on some pretty hefty HD projects recently. Have found that if you get the message, flushing some render files using Tools->Render Manager can free up enough memory to get you going again. It's only a temporary fix since the cache will fill up again but it keeps you going when the deadline looms. J John Weeks said this on July 24, 2012 at 4:01 am I am editing a LONG piece (trt 5 hours) and have a TON of footage - all h.264 clips. I created a ProRez seq, and the render time was over 20 hours. Seriously. Also, the render took about 100 GIGS. And this is just an hour long seq. I have 4 more to go! Plus, if I turn a layer on/off, it needs to render again. Time is an issue here, as well as space. (I don't have 500+ gigs just to use for render!) Now I'm conforming all the clips to ProRez, and the estimated render time is 30 hours! Is there any way around this?? Tammy said this on November 20, 2012 at 10:15 am Thanks! T sai
Final Cut Pro "Out of Memory" Error…FIXED! Booyah Final Cut! Take that! I dont know if anyone who reads this uses FCP7 but if it even helps one person with this INCREDIBLY annoying problem https://hiddenmoonproductions.wordpress.com/2012/02/01/final-cut-pro-out-of-memory-error-fixed/ then its worth confusing some readers. Every once and a while https://larryjordan.com/articles/fcp7-general-error/ I'll be editing a project and go to render and see this. I know I'm NOT out of memory… In fact, I am currently only using 30% of my RAM. What the hell Final Cut? In searching the web I found a couple solutions that worked for final cut some people but I figured out one that has worked every time this pesky error shows up. Here is a simple timeline where the error popped up. Nothing special. Just some opening graphics, interviews strung back to back with supers. How could something this simple cause any problems? The sequence settings looked like this. Here's the solution: - Click final cut pro in the timeline. - Select all (Command+A) - Copy (Command+C) - Right-click in the Browser window and make a "new sequence" - Right-click on the new sequence go to settings. - Manually set the settings to match the original sequence (if it is using Compressor settings of either HDV or H.264 you might want to change this to some form of ProRes) - Paste the previously copied timeline in the new sequence. (Command+V) - Render! I bet you've never been so happy to see a progress bar have you? Now go get a beer and celebrate while your sequence renders and you feel that warm feeling of relief come over you… Unless you're at work. In that case, GET BACK TO WORK. You've wasted enough time searching the web for this article! Rate this:Share this:Share on Facebook (Opens in new window)Click to share on Twitter (Opens in new window)Click to share on LinkedIn (Opens in new window)Click to share on Google+ (Opens in new window)Click to share on Tumblr (Opens in new window)Click to shar
ContestFree ResourcesLARRY RECOMMENDSRelated WebsitesRelated BooksFavorite ArticlesLEARN FROM LARRYFree Step-by-Step TutorialsArticles / BlogFree Weekly WebinarTip of the DayOTHER RESOURCESForum (beta)Editing as a BusinessNewsletter ArchivesSocializeStoreSupportGeneral FAQSupportFCP 7: Fixing a General ErrorPosted on April 28, 2012 by LarryProbably my least favorite error in Final Cut Pro 7 (or earlier versions) is a General Error. It has one of the least helpful warning dialogs and is frustratingly difficult to solve. However, I've learned that when a General Error occurs it is almost always related to a bad clip, or a bad render file, in your sequence. Maybe not always, but this should be the first place to check.General Errors most often relate to render problems; either when you are rendering directly during editing, or rendering as part of an export. While there isn't a fast way to fix this, it can be fixed. Before you attempt to fix a General Error, it doesn't hurt to reset your system by doing a Safe Boot.NOTE: Here's an article that explains how to do a Safe Boot: Trouble-Shoot in Five StepsTHINGS TO CHECK1. While Final Cut SHOULD be able to work with video of different frame rates, it can often have problems when a clip with a faster frame rate (say, 30 fps) is put into a slower sequence (say, 23.98 fps). Disable clips with different frame rates and see if the General Error goes away when you render.NOTE: To disable a clip, select it and type Control+B. A clip changes color when it is disabled.2. It is possible that a specific render file became corrupted. This isn't your fault, every so often it just happens. Delete all render files and see if the error goes away.NOTE: To delete all render files associated with a track, turn off the green visibility light, located in the track header on the left of the Timeline, then turn it back on. This is just a quick click - click. If you don't turn the visibility light back on, all clips in that track become invisible.3. Sometimes clips downloaded from stock image houses are corrupted during the transfer. Disable any stock shots (select the clip and type Control+B) and re-render.4. If these first three suggestions don't work, you will need to get a bit more methodical by rendering your project in sections until you finally isolate the clip(s) that is causing a problem. To render just a portion of your seque