Skip navigation
Currently Being Moderated

Flash CS6, QuickTime: The export operation failed because it ran out of memory.

Jun 1, 2012 5:48 PM

Exporting a QuickTime movie file seems to be an old issue with previous versions too. In CS6 I always get the error message: "The export operation failed because it ran out of memory." I've got tons of memory and have allocated increasing amounts to the cache with no success.

 

My small and fairly simple file was created with Flash CS5 which seemed to work fine at the time of creation. I've tried everything recommended online but with no luck so far. BTW, I reinstalled CS5 and tried that too but it just hangs now, and there's no error message.

 

Does anyone have a solution?

 

(OS X 10.7.4)

 
Replies 1 2 Previous Next
  • Currently Being Moderated
    Jun 4, 2012 11:31 PM   in reply to 231212

    Export the same movie as MPEG , then import in flash and export to quicktime.  Check whether this will works for you.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 5, 2012 9:16 PM   in reply to 231212

    Please use AME (Adobe media encoder). You can launch AME from import video wizard

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 6, 2012 9:22 PM   in reply to 231212

    Export the video in any vimeo presets matching in your video dimension and import video again export as quick time.

    Please let me know if its works for you.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 7, 2012 10:19 AM   in reply to 231212

    Hi! Your animation is a simple swf  (you see in the preview exactly what you want)? If so you could import the swf inside AfterEffects and it gonna be treated as a video. I don´t remember but i think that Quicktime also could open it.

     

    hope this could be useful to you.

     

    cheers, martín

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 30, 2012 3:38 PM   in reply to 231212

    Under "QuickTime Export Settings" there is a radio button selection for "Store temp data:". Change it from "In memory (recommended for higher frame rates)" to "On disk (recommended for longer movies). Try that.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 17, 2012 9:07 AM   in reply to 231212

    Hi all

     

    I was having the same issues. I've got a simple animation and started getting the Out of Memory error during the "Recording Flash Content" part of the export to Quicktime in CS6.

     

    After trying a few things, it seems that what was causing the problem for me was a Bad Action script at the end of the timeline.  (ie. there was a  "goto next scene" and there was not another scene). I deleted that action and the export seems to work fine. I even added in a "stop movie" action at the end just to see if it was ALL actions that caused this and it also worked fine.

     

    I called Adobe as well and they said this is a known issue and are working on it. So, Its seems that if you have strange actions, they cause errors.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 17, 2012 10:38 AM   in reply to 231212

    This is a long shot, but what is the frame rate of your flash document? I find that using the QE is much more successful when the frame rate is set to 29.97. Quicktime likes that.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 17, 2012 10:40 AM   in reply to 231212

    "I'm glad Adobe is working on it though none too soon. The only action I have is a stop action at the end. But it still doesn't work (in CS6; CS5 is still okay)."

     

    – That's so weird. Mine seems to work with the stop at the end.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 17, 2012 10:43 AM   in reply to chris georgenes

    I've been useing a few frame rates. One is 30 and the other is 18 or 12. I end up dumping this all into Final Cut anyway which complies them all together nicely. I find that even then, when I've got synched dialogue with my characters, Flash seems to drop some frames and i need to re-slide the audio into position in Final Cut.

     

    My next "work around" is to import the SWF file into After Effects. I read that this is what the pro animators to.   

     

    We'll see.   I just hope Adobe fixes all this crap.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 17, 2012 11:26 AM   in reply to Marcus Kihn

    It should work fine with a stop(); action.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 17, 2012 11:29 AM   in reply to Marcus Kihn

    In my experience using the QE, if my Flash doc frame rate is anything other than 29.97fps, I will always experience dropped frames and/or some frames where the content is visually affected (noticeable slicing and general destruction and interference of the image). If I change to a 29.97 frame rate and export again, the MOV is frame accurate and all images in all frames look perfect. But this may be getting off topic from the original issue.

     

    I would also try copying all frames and actionscript to a new CS6 document and try exporting again.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 18, 2012 5:58 PM   in reply to millerstudio1

    Under "QuickTime Export Settings" there is a radio button selection for "Store temp data:". Change it from "In memory (recommended for higher frame rates)" to "On disk (recommended for longer movies). Try that.

    This solved it for me, thanks. It's not so fast, especially the final, compressing part, and takes about two or three times the real time of the video, I estimate, but it's a 1280x720 so I quess that weighs in too. I even used a some actionscript, like a counter, works fine so far.

     

    BTW, 231212, do you hear your hard disk crunching away / can you see activity spikes on this in the OS X Activity Monitor when you have this option on, or is it doing nothing?

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 19, 2012 12:30 PM   in reply to 231212

    You're not the only one with a Mac Pro, hot shot      I am under the impression that the hard disks in the large, metal case can be heard better then the HD in most iMac models.

     

    On topic: If you think it might be something with your particular installation, I can take give it a try over here if you like.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 19, 2012 9:51 PM   in reply to chris georgenes

    Could you please share the files used for export,  You can share file using web site like  4share.com

    And also provide the details of

     

    Machine

    quick time version

    Anyother video editing application installed in your system.

    If graphic card,  Please mention the graphic card name.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 3, 2012 6:19 AM   in reply to 231212

    hi we also have trouble exporting Qt from Flash CS6 Mac. Always runs out of memory. We're exporting 1 min to 2 min animatics for an animation. The only work around is exporting swf & then bringing into CS3 to export a QT. We have animators working in CS5 who can export fine - just not CS6.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 3, 2012 6:27 AM   in reply to stickystu

    Stickystu, I never use Premiere Pro but it (CS6 suite) was on the machine I was working on. I found out it renders .swf's without running out of memory.

     

    (ActionScripts still don't work though and not all kinds of 'sub' animations in movieClips work either, but animations on the main timeline do.)

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 3, 2012 6:31 AM   in reply to laptopleon

    Hey laptopleon thanks yeah AFX can render the swfs to QT too. we just don't get why CS6 Flash mac can't do it when cs3-5 were fine. It's not just the export function either all our artists are finding CS6 flash (mac) difficult, encountering the spinnng wheel a lot - so back to CS5 we go. cheers.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 11, 2012 6:13 AM   in reply to 231212

    I'm having the same problem in CS5.5.

     

    I have an animation with no actionscript, a computer with plenty of free memory. I restarted Flash to clear any performance memory.

     

    I don't have Adobe Premier so I can't use a different program, and Quicktime won't allow me to open a SWF file.

     

    It's 30seconds long and I just want to export a .mov file!

     

    I have tried changing all the settings.. I just don't understand why this function isn't working!

     

    Did anyone find any other solutions to this?

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 11, 2012 6:35 AM   in reply to lauracostelloe

    Like I said.. open the .swf with Premiere Pro and it will render it, no matter how big it is.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 5, 2012 7:01 AM   in reply to 231212

    I did a very deep test about this issue (out of memory while exporting to mov) and partially understood its behaviour:

     

    In all this tests I've always used the "After time elapsed:" option.

     

    - issue is not happening in CS5, both "in memory" and "on disk" setting works.

     

    - issue is happening in CS6 if original fla document size is HD (1920x1080): even creating an empty movie of that size, and then trying to export the mov causes the issue!

    if I reduce the size to 1280x720, for example, the export works and the mov is created correctly. In every case I had to set the "on disk" option.

    The "on memory" does not work.

     

    OSX 10.6.8

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 5, 2012 7:23 AM   in reply to Riccardo Sallusti

    @Riccardo I only tried this in CS6. Others have claimed it works fine in CS5. That's interesting to know, but hardly a solution IMHO.

     

    I don't think it's just the resolution, because very short HD animations did export fine here, if I recall correctly. If a certain amount of memory is exeeded, it runs out of memory. Even if you have much more hardwired memory available.

     

    What seems to happen is this: Flash renders the movie frame by frame and just puts every pixel in the RAM memory. Because it doesn't compress anything at this level, the amount of raw pixel-data is huge. It doesn't matter what the size of a frame is, but of course with frames of 1920x1080, you will hit the problematic limit much sooner than with 1280x820. Then it's the x limit and stops the operation.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 5, 2012 7:42 AM   in reply to laptopleon

    I totally agree with you: the problem is related to bad memory usage/management.

     

    But I've tried again one minute ago to export to mov an empty movie of 60 empty frames sized 1920x1080 and it throwed that error again...

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 6, 2012 10:36 AM   in reply to Riccardo Sallusti

    If I may join this discussion...  I loaded up CS6 two days ago and have just completed my first 60 second animation using it.  Like everybody else here, it all went fine until I tried to export it to QuickTime – something that has never been problematic before. 

     

    I ended up exporting it as a swf and opening that in CS4.  Then I could export it, but the resulting QuickTime movie was over 500 MB in size!  Okay, so then I opened it in QuickTime Pro and exported it from there.  This brought the file size down to a far more reasonable 35 MB, but now the soundtrack has gone!  So now I am having to replace the sound in Final Cut Pro. 

     

    This is a real palaver – and not conducive to heaping praise on CS6 when questioned.  I note that there is talk of Adobe rectifying this "bug", but it would be really good to hear from somebody at Adobe with:

     

    a) An apology

     

    b) An estimated time of delivery

     

    c) A best practice work round

     

    But I'm guessing that anybody that works at Adobe will be the last person to read this...

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 17, 2012 9:49 AM   in reply to 231212

    I can't find a solution for this. Having the same problem, tried everything in this thread.

     
    |
    Mark as:
  • lingoes
    11 posts
    Oct 18, 2012
    Currently Being Moderated
    Oct 18, 2012 1:46 AM   in reply to SteveMerrittGrp

    Out of memory is the old issue, I just add my MBP

    Virtual memory and the notice reduce

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 18, 2012 1:50 AM   in reply to lingoes

    Hi Lingoes

    Please can you expand upon this answer.  MBP = ?   And do you mean that the notice disappears, or just reduces? 

    Thanks for your help.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 18, 2012 6:41 AM   in reply to kalaharibob

    I re-installed Flash CS5.5 and was able to export to an .mov fine. No idea why it works in one and not the other. (I wasn't using any actionscript either)

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 18, 2012 1:10 PM   in reply to SteveMerrittGrp

    I had the same issue with CS6, and still months away Adobe hasn't fixed this ?? What the F***? what the heck are those folks doing at Adobe ?

    I need this fixed IMMEDIATELY, no more time to waste, when will this be fixed ADOBE ?????????????

     
    |
    Mark as:
1 2 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points