'out of memory' error in rendering

I'm preparing a series of sequences that i want to output in uncompressed 10-bit PAL (720 x 576) for a high quality wide-screen projection display. The bulk of the footage was acquired on uncompressed 10-bit and edited (along with other clips imported from other formats) in that format. Almost all the sequences have worked fine and look great. I'm stuck on one that includes a clip which is made up of a layered compilation of five still images which I have imported from JPEGs (varying resolutions, up to 3000 pixels wide). I'm having trouble rendering this composite image. Every time I try to render the clip, the render dialogue comes up but, after a few minutes, is replaced by a message saying 'out of memory'.
The sequence presets are Blackmagic PAL - 10 bit. The system is based on a Mac Pro 3.0G Quad Core Intel with 2G RAM and a 2T RAID array for media storage. I'm using Final Cut Pro 6.0.3

You might also try resizing the images to the smallest size you can get away with, regarding your 720x576 frame size and any movements you put on them.
tim

Similar Messages

  • CS6 Running out of memory Error while rendering

    Hey everyone,
    I recently upgraded to After Effects CS6 thinking it would be a great investment. So far, I have been horribly wrong!
    Here's my computer's specs: (this is a huge upgrade from the computer I was running 5.5 on without any problems other than it being slow)
    Intel i7-3615QM 2.3GHz Ivy Bridge processor
    8GB GDDR5 RAM
    NVIDIA GeForcs 650M w/ 2GB GDDR5 dedicated RAM
    Here's what's happening:
    I've been doing recording for my job at 1080p in front of a green screen. I record 16 minute sections. I use Keylight to replace the background with a still picture, and then export the video at half resolution, with audio as H.264 (.mp4) files. Normally I would set up the 16 minute sections to render in queue, but it kept having the "out of memory" error shortly after starting the one second in line. So then I started just doing one at a time... and now it won't even make it through one!
    I have noticed that even after rendering is done, AE is still using 6 gigs of RAM! Usually I can purge the ram, but now even doing that doesn't change anything - I have to close the program to get my RAM back. I have tried enlarging my page file, I've tried rendering in different resolutions and file types - I feel like I've tried everthing. I've looked all over the internet and I haven't found any real solutions (just talk from 2008 about "secret" menus that I can't get to work).
    Please help!!
    Thank you!!
    Dominic

    I wouldn't mind getting more RAM except that the computer I used to do this very same work with (except with 5.5) only had 6GHz of RAM and a pathetic processor and GPU in comparison.
    I've tried doing the same editing in PrP but it just doesn't have enough tools . Changing my output format hasn't helped either unfortunately. I think the program has a memory leak.
    I really think I might just go back to 5.5. I called support today and it took forever just to get the poor girl helping me to understand my name has an "m" in it. She wasn't really able to understand the problem. As far as I can tell, CS6 has been a 100% downgrade.
    Thank you both for the help!
    Dominic

  • Out of memory error when rendering.

    I edited a 40 minute show (25P) using Aspect 3.4 codec. When I export to DVD in low quality 1 pass everything is okay. However, when I export to DVD in High Quality 1 pass or low quality 2 pass I get an error half way through the rendering (out of memory error). What's the story?

    Try:
    Error:Out of memory
    Cheers
    Eddie
    PremiereProPedia   (
    RSS feed)
    - Over 300 frequently answered questions
    - Over 250 free tutorials
    - Maintained by editors like
    you
    Forum FAQ

  • Out of memory error while rendering

    Trying to render a 1 minute comp and part way through it tanks out with a "7::66 Unable to allocate enough memory" error. I watch the RAM usage indicator at the bottom of the render screen and it just gradually climbs until it hits 100% and crashes.
    System is a 2013 Mac Pro running latest version of Yosemite and latest version of CC. I have 64GB of RAM installed so at this point I'm going to disregard AE's advice that I bump this up.
    Also using Element 2 in the comp so that may be a culprit.
    Anyhow, if anyone has any advice on how to troubleshoot this I would greatly appreciate it.

    When you say latest version of CC, do you mean version 12.2.1.5?
    What is in your comp besides the layer with Element on it?
    Have you used a minute-long comp with Element 2 in the past?
    What are the rest of your system specs?
    Have you tried the "secret" preferences setting to purge after a certain number of frames?
    Another suggestion would be to render an image sequence. Then, if it crashes, you can just pick up the render from where it left off.

  • Rendering Out of Memory Error

    Why when I render large parts of sequences do I get "Out Of Memory Errors". This bombs out my render.

    & Uh, I know there's a "chalkboard" font. My question was more to the point of how to "animate" it properly.< </div>
    Not really, that's just the error message that FCP pukes up for you. FCP has no intelligent diagnostics and the errors are totally misleading and inaccurate.
    the other boys are trying to help you using verbal shorthand that not all newbies understand. That's one of the may ways in which we figure out they're new.
    bogiesan

  • Constant out of memory errors

    I am consantly receiving out of memory errors in fcp 5.1. Now when rendering I have to split it up into sections to render so I dont get the error (eg - render 5 seconds of footage at a time)
    My rendered files folder contains 203 files and I was wondering whether I could just delete all the files and then just re-render the project in one go - or will this just screw up the project?

    If I delete all the rendered files, when I re-render will it make just the one render file? If so does this mean everytime I make a change in the project it will take longer to render as Final Cut will have to re-render the whole file?

  • Another version of 'out of memory' error

    Hi all
    I have a colleague who is getting the following error message.
    As discussed...when I attempt to render a clip on the timeline, once it
    gets to the end of the rendering process and attempts to play the clip, an
    'out of memory' error message box appears on the screen.
    Then when I click on 'OK' to close this box, the canvas window turns to red
    and the following message displays in the canvas window...'Out of memory.
    Free up memory and window will redraw.'
    He is using HDV footage captured with the "HDV" codec [not the intermediate one], and editing it into HDV1080i50 sequences.
    He has a G5 DP 2 GHZ machine running Tiger 10.4.2 and 2 GB of ram.
    He has approx 80 GB free space on Mac HD and approx 400 GB on external Lacie HD. He is running only FCP HD 5 at any one time.
    I have sourced some previous posts which speak of corrupt graphics, clips, sequences and trashing fcp prefs.
    Does anyone have any other suggestions for him?
    [He is quite new to macs and FCP especially].
    I am going to send him an email to subscribe and create an account for this forum, his name is AGebhardt.

    Hello,
    I had the same issue last night, when a render (only 15 min., so not THAT big) completed and would not play and the canvas turned red and said I was out of memory.
    This is different than a general error! out of memory warning, which I have seen happen. Some of the answers in linked threads seem to be pointing to this other situation.
    I have plenty of space and plenty of RAM and was only running iTunes. I quit iTunes and it worked, almost to my disappointment because in the past I have had many apps working at a time with no problems,
    I would be pretty bummed if I could only have FCP open all of a sudden.
    I will try going through my clips to check for corruptions as suggested just to be on the safe side, but have a question;
    What good is it to throw out your render files if you have already checked to see if you have enough storage space? I can see the good if a file is corrupt, but with every project a new render folder is created and unless there is a limit on these folders that I'm unaware of I can't see the sense in trashing the folder.
    Am I missing something?
    Thanks,
    Jesse
    733 G4    

  • HELP out of memory error message

    I'm using fcp 7 with 10.6 on a macbook pro.
    I just finished editing a 16 minute photo montage with about 100 stills. The pictues all of movement.
    I used some of the pictures in photoshop and AE.
    When I try and render I'm getting "out of memory" error. All of the footage is on my 1 tb external hard drive with
    450 gig not used. I've done more layered ones before with no issues.
    I tried to render indivdual clips and several clips. It worked fine for a while. The render files are about 7 gig
    so it's not much. I also tried to output the whole sequence instead of rendering and I'm still getting the
    "out of memory"  I need to output by tomorrow.
    Thanks,
    Michael

    I have done some Google searching, and FCP 7 is a 32-bit application.  So it is my guess that whatever you are currently doing has FCP 7 wanting to use more than 4 gigibytes of Virtual Address space, and it cannot grow expand any further because it is a 32-bit applications.
    This is my best guess as to why you are getting "out of memory" errors.
    I am not an FCP user so I cannot suggest any tricks to get this to work.  The only other suggestion is to get newer version of FCP which is 64-bit capable, but that might also require upgrading to a newer version of Mac OS X, so going down the upgrade road can get involved.

  • Out of memory error when exporting to QT self contained movie

    When I export to QT self contained movie the program runs for about an hour then brings an "out of memory" error. My project is 1hour 10 min. I have 650 GB on the external drive I'm saving to and another 145 GB on my imac's drive. There are also photographs I've included in the sequence but I have removed them all from the sequence to see if the format was the problem but the error still comes up. I would appreciate any help.

    Well I don't have to render as I go, it is just a choice. I checked to see if all the video and stills were rendered. I re-rendered after making sure all of the options were checked, removed all of the stills from the timeline just in case the still format was the problem, then attempted to export again. It took about 2 hours. I watched with activity monitor and it took almost all of the available disc space then my computer shut itself down. When I rebooted there was a Quicktime file 320 GB in size but would not open. I got an error message that it was not a mov. file.
    But to answer your question:
    Video is 29.97fps DV/DVCPRO
    Frame size is 720 x 480
    3.0 mb/sec
    16 bit Integer
    Aplha= None /ignore
    Composit is Normal
    NTSC-CCIR 601
    Stereo
    Stills are at 25.0 fps JPEG

  • Out of Memory error after upgrading to Reader X

    We have several PDF documents that work fine on Reader 9.  But after upgrading to Reader X, the files will not open.  Instead, they report an Out Of Memory error and a blank document opens instead.  Removing Reader X and re-installing Reader 9 corrects the issue. This has been reproduced on 3 different PCs running both Windows XP and Windows 7.
    Any suggestions?

    Just to throw in my 2 cents... Adobe has known about the out of memory bug at least since 01/12/2011 because that is when I reported the problem to them.  I even had an escalated support case #181995624 and bug#2800823.  Our problem comes from a EFI Fiery E7000 attached to our Lanier LD460c Copier.  Any pdf's made from that copier will not open in Acrobat X, although they will open in lower versions of Acrobat just fine.  Our only workaround is to keep Acrrobat 9 on office computers, or you can open the offending pdf in Acrobat 9 or earlier and print it to pdf, and then it will open in Acrobat X!!!  They acknowledged that this was a bug, see my email chain below.  This was the last update I received from Adobe, very frustrating...
    From:
    Sent: Wednesday, February 09, 2011 9:12 AM
    To:
    Cc:
    Subject: RE: Case 181995624; Unable to open PDF
    Hi Phil,
    We do not have this information or estimate time by our Engineering team yet.
    Regards,
    Neeraj
    From:
    Sent: Monday, February 07, 2011 8:19 PM
    To:
    Cc:
    Subject: RE: Case 181995624; Unable to open PDF
    Next major release as in the next patch for Acrobat X, or as in Acrobat 11?
    From:
    Sent: Saturday, February 05, 2011 4:31 AM
    To:
    Cc:
    Subject: Case 181995624; Unable to open PDF
    Hi Phil,
    You can get back to us with the Bug Number provided you earlier based on which we will give you the update by our Engineering team. However, the update for now is that it is decided to fix in our next major release.
    Regards,
    Neeraj
    From:
    Sent: Thursday, February 03, 2011 1:33 AM
    To:
    Subject: RE: Case 181995624; Unable to open PDF
    Can you send me a link to where I can find information on the bug?
    From:
    Sent: Tuesday, February 01, 2011 10:14 AM
    To:
    Cc:
    Subject: Case 181995624; Unable to open PDF
    Hi Phil,
    Hope you are doing well.
    I have researched on your issue and found that it is a BUG with Acrobat X. I have logged it on your behalf so that our Engineering team can have a look on that. Please find the Bug Number #2800823 for any update on this in future. I am closing this case on your behalf.
    Have a nice day.
    Regards,
    Neeraj
    From:
    Sent: Tuesday, February 01, 2011 12:22 AM
    To:
    Cc:
    Subject: RE: Case 181995624; Unable to open PDF
    Any updates on this case?
    From:
    Sent: Friday, January 14, 2011 2:03 PM
    To:
    Cc:
    Subject: RE: Case 181995624; Unable to open PDF
    The EFI Fiery E-7000 Controller version is 1.2.0 and it handles the scanning and printing functionality of our Lanier LD160c copier.  I have attached two sample files.  One is a 1 page scan from our copier.  The other is a combined pdf that I just created in Acrobat 9.  The first two pages of the combined pdf consists of a webpage that I printed using Acrobat 9 and then the scan from the copier is on the 3rd page.  In Acrobat X, once you get to the 3rd page you will receive the Out of Memory error.  It will open in previous versions of Acrobat just fine though.
    From:
    Sent: Friday, January 14, 2011 11:52 AM
    To:
    Cc:
    Subject: Case 181995624; Unable to open PDF
    Hi Phil,
    Thanks for the information.
    I have the PDF file provided by you and able to reproduce the behavior. I tried to call you at 214-303-1500 but got voice mail.
    Please let me know when you will be available so that I could call you and continue further with this issue.
    Regards,
    Neeraj
    From:
    Sent: Thursday, January 13, 2011 6:57 AM
    To:
    Cc:
    Subject: Re: Case 181995624; Unable to open PDF
    It is a walk up copier and we scan to email.  The EFI Fiery controller E7000 handles pdf conversion for the copier, but yes it has the latest firmware.  The bottom line is that we have 3 or 4 years worth of pdfs created from that copier rendered useless by Acrobat X.  They open fine in previous versions of Acrobat.  Did you get the test pdf file when this case was created?
    -- Sent from my Palm Pre
    On Jan 12, 2011 6:12 PM, Acrobat Support <[email protected]> wrote:
    Hi Philip,
    Thank you for choosing Adobe Support we have got your concern, we see that you are facing an issue with opening PDF files in Acrobat X, created from Lanier (Ricoh) LD160c copier. A technical support case 181995624 has been created for your reference. In order to assist you further. We would like to have the following information.
    ·         Are you using the latest scanner driver ?
    ·         What is the exact scanning workflow ?
    Regards
    Acrobat Support

  • Out of memory error on Final Cut Express

    Hello,
    Ok so quite often we have to record into iMovie6 live (on a Macbook Pro) so that we can get all the content being recorded without gaps (tapes don't last long enough). After the project is imported (and transfered to my Powermac with FCE on it) I would rather use Final Cut Express to edit everything. So after saving the iMovie project I start a new project in FCE and import the files from iMovie. When this happens the audio always needs rendered and often when I render these files it really bogs down my PowerMac G5 and eventually gives me an out of memory error. After looking at Activity Monitor during the rendering, the System Memory just starts to become inactive and then eventually active until all the memory is used. That's usually when I get the memory error in FCE. I have 1GB of memory and I've added another Gig but the result is the same. It appears this is a problem with the app. Anyone have a clue or any ideas? I am using Final Cut Express HD 3.0.1 on my PowerMac.
    Thanks-
    Adam

    Thanks for the comments however I currently have a project that I am trying to get done and these comments don't help right now. Anyone have any advice to speed up the process?
    I just need to render the audio faster without having to reboot all the time. Any other FCE project works fine when rendering audio, it's just the import from iMovie that for some reason soaks up my memory and causes me to have to reboot to get it back.
    Thank you-
    Adam

  • Acrobat XI Pro "Out of Memory" Error.

    We just received a new Dell T7600 workstation (Win7, 64-bit, 64GB RAM, 8TB disk storage, and more processors than you can shake a stick at). We installed the Adobe CS6 Master Collection which had Acrobat Pro X. Each time we open a PDF of size greater than roughly 4MB, the program returns an "out of memory" error. After running updates, uninstalling and reinstalling (several times), I bought a copy of Acrobat XI Pro hoping this would solve the problem. Same problem still exists upon opening the larger PDFs. Our business depends on opening very large PDF files and we've paid for the Master Collection, so I'd rather not use an freeware PDF reader. Any help, thoughts, and/or suggestions are greatly appreciated.
    Regards,
    Chris

    As mentioned, the TEMP folder is typically the problem. MS limits the size of this folder and you have 2 choices: 1. empty it or 2. increase the size limit. I am not positive this is the issue, but it does crop up at times. It does not matter how big your harddrive is, it is a matter of the amount of space that MS has allocated for virtual memory. I am surprised that there is an issue with 64GB of RAM, but MS is real good at letting you know you can't have it all for use because you might want to open up something else. That is why a lot of big packages turn off some of the limits of Windows or use Linux.

  • Acrobat XI Pro "Out of Memory" error after Office 2010 install

    Good Afternoon,
    We recently pushed Office 2010 to our users and are now getting reports of previous installs of Adobe Acrobat XI Pro no longer working but throwing "Out of Memory" errors.
    We are in a Windows XP environment. All machines are HP 8440p/6930p/6910 with the same Service pack level (3) and all up to date on security patches.
    All machines are running Office 2010 SP1.
    All machines have 2GB or 4GB of RAM (Only 3.25GB recognized as we are a 32bit OS environment).
    All machines have adequate free space (ranging from 50gb to 200gb of free space).
    All machines are set to 4096mb initial page file size with 8192mb maximum page file size.
    All machines with Acrobat XI Pro *DO NOT* have Reader XI installed alongside. If Reader is installed, it is Reader 10.1 or higher.
    The following troubleshooting steps have been taken:
    Verify page file size (4096mb - 8192mb).
    Deleted local user and Windows temp files (%temp% and c:\WINDOWS\Temp both emptied).
    Repair on Adobe Acrobat XI Pro install. No change.
    Uninstall Acrobat Pro XI, reboot, re-install. No change.
    Uninstall Acrobat Pro XI Pro along with *ALL* other Adobe applications presently installed (Flash Player, Air), delete all Adobe folders and files found in a full search of the C drive, delete all orphaned Registry entries for all Adobe products, re-empty all temp folders, reboot.
    Re-install Adobe Acrobat XI Pro. No change.
    Disable enhanced security in Acrobat XI Pro. No change.
    Renamed Acrobat XI's plug_ins folder to plug_ins.old.
    You *can* get Acrobat to open once this is done but when you attempt to edit a file or enter data into a form, you get the message, "The "Updater" plug-in has been removed. Please re-install Acrobat to continue viewing the current file."
    A repair on the Office 2010 install and re-installing Office 2010 also had no effect.
    At this point, short of re-imaging the machines (which is *not* an option), we are stumped.
    We have not yet tried rolling back a user to Office 2007 as the upgrade initiative is enterprise-wide and rolling back would not be considered a solution.
    Anyone have any ideas beyond what has been tried so far?

    As mentioned, the TEMP folder is typically the problem. MS limits the size of this folder and you have 2 choices: 1. empty it or 2. increase the size limit. I am not positive this is the issue, but it does crop up at times. It does not matter how big your harddrive is, it is a matter of the amount of space that MS has allocated for virtual memory. I am surprised that there is an issue with 64GB of RAM, but MS is real good at letting you know you can't have it all for use because you might want to open up something else. That is why a lot of big packages turn off some of the limits of Windows or use Linux.

  • RoboHelp 9 gives an out of memory error and crashes when I try to import or link a Frame 10 file or

    I have Tech Suite 3. If I start a new RoboHelp project and try to import or link Frame files, RoboHelp tries for a while, then I get an Out of Memory error and the program crashes.
    I opened one of the sample projects and was able to link to one of my frame files without any problem, so it seems to be an issue with creating something new.
    Any suggestions?

    It happens when I create a new project and then try to import or link frame docs to make up the content. It starts scanning, then crashes. I did get it to the conversion setting page once, but no further.
    It does not happen if I open one of the supplied example projects and link a file. But then it doesn't let me choose, during import, any style mapping. And I can't delete the sample project fold
    Twice now it has told me when I tried to import (not link, but import) that my .fm file could not be opened, and told me to verify that Frame is installed (it is) and that the file is a valid frame file (it is).
    The docs and project are in separate folders on my C: drive.

  • Out of Memory Error While deploying as EAR file

    Hai,
    I was trying to deploy an EAR file of size 63 MB which inturn containing about 60 EJB.jars. No WARs. application.xml has all the entries for the JARs. While I am deploying it is giving Out of Memory Error. Is there any way to tweak this problem. I am using my own hand written java application which uses the SunONE deployment APIs for deployment. Can u please tell how to tackle this problem. I am running my application through a batch file which uses jdk1.4.
    Please help me regarding this issue.

    You can set the initial heap size and maximum heap size for the JVM, either in the app-server admin console, or maybe in one of your scripts. You look-up the syntax!...
    I had this error yesterday. I too had run out of memory (150Mb). You simply need to allocate more to the app-server.

Maybe you are looking for