Skip navigation
Currently Being Moderated

Export Error. Error compiling movie. Disk Full.

May 13, 2012 7:20 AM

I have the following error since CS6 when exporting some videos: Export Error. Error compiling movie. Disk Full.

 

All my drives have plenty of space, NTFS 7200rpm, everything was fine with CS5.5. Same problem with Encoder or Premiere Pro.

 

Much of the stuff I export is going fine but I have this error with some sequences and formats.

 

It always crash to this error when exporting sequences with "Match Sequence Settings".

 

For one of my projects, when exporting to wmv, out of 6 sequences one always crash to Export Error. Error compiling movie. Disk Full.

 

If I encode those sequences to mpeg2, everything is fine.

 

I installed the new update this morning but it doesn't help.

 
Replies
  • Currently Being Moderated
    May 13, 2012 3:10 PM   in reply to Proj.L

    You  mentioned MPEG2 does not have this issue and WMV does have this issue. What other export formats have you tried that have or not have this problem.  Just for sake of narrowing down this issue, would you remove all effects you have applied to projects/sequences and try to export that project and see it the problem goes away?  Another test for WMV is to select a different Bitrate setting in Export Settings [Video tab]. Default is VBR, try selecting CBR and see if that solves the issue. 

     
    |
    Mark as:
  • Currently Being Moderated
    May 14, 2012 11:06 AM   in reply to Proj.L

    The part about AME incorrectly reporting that the disk was full sounds similar to a bug that we found late in the cycle and thought that we had fixed.

    Are you encoding multiple outputs in parallel? If so, please try with the Enable Parallel Encoding option disabled in the Preferences dialog.

    Is AME crashing or hanging, or is encoding failing but the app continues running and remains responsive?

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 18, 2012 11:22 AM   in reply to Proj.L

    I have the same error popping up. My hard drives are formatted NTFS and have plenty of space. I'm working on APE 4.0. I tried encoding into an internal and external hard drive.

     

    I'm trying to encode a 4:00 Film into .mpeg format. But the error 'Error compiling movie. Disk Full.' keeps popping up. If I encode into AVI it goes through.

     

    I don't get this error... I want to encode into mpeg.

     

    I sympathize with my friend and I would really like to resolve this issue. Thank you!

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 28, 2012 8:19 AM   in reply to BennyDj5

    I too am having the same issue when I try and match sequence settings.  It runs for a few seconds then I hear that dreaded goat sound and it fails because the "disk is full" but I have about 80 gig left on the drive.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 7, 2012 11:54 AM   in reply to Proj.L

    I have this problem all the time. Its something Adobe needs to fix but there are two ways to get around it.

     

    1.Delete all your render files in the project and try again.

    2.Turn off the mecury playback engine use software only.

     

    I have found the mecury playback engine to be unreliable and I am dissapointed with its use in a real production enviornment. It's just a cool toy Adobe uses to sell there product. 

     

    Also your effects will change when switching to software render so retweeking the whole project will be nessecery.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 9, 2012 8:02 AM   in reply to Mark Mapes

    Sorry to come late to this party but i am experiencing a very similar issue, well at least i think i am.

    I am using CS6 (creative cloud) on a mac and when using AME, I am getting constant disk full messages. this does not happen when exporting direct from prem pro (even when exporting to higher bit rate formats).

    My media cache settings are correctly set to my scratch disk and not my system drive and so i just can't see what might might be causing this problem.

     

    Any help would be gratefully received.

     

    Cheers

     

    Ben

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 9, 2012 8:10 AM   in reply to bensandstrom

    Quick question for everyone. Are these project that have been created in earlier versions of Premiere and opened in CS6?

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 9, 2012 8:15 AM   in reply to TYLERART

    I was going to say no but i've just realised that i was passed the dailies with a synced project file from CS5.5.

    So i've been using a converted version of that......

    Would explain why i haven't seen that issue before hand.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 9, 2012 8:44 AM   in reply to bensandstrom

    Most of my problems come from importing old projects. They are very strange and random and if I try and duplicate them I can't. Turn off the mercury playback engine (If your system is using it) use software only see if that helps.

     

    Project / project settings / Render: mercury playback engine software only

    I find this causes %90 of the stability issues in premiere.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 9, 2012 8:50 AM   in reply to TYLERART

    Check out this strange bug. This was an imported CS5.5 project the bug only happens when using secondary color correction with a blurred mask and pop in a non real-time effect. And only while using the mercury playback engine GPU acceleration. But if you clear the effects and recreate them the bug is gone. ( Strange right?)

    Screen1.jpg

    Screen2.jpg

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 9, 2012 8:57 AM   in reply to TYLERART

    yeah that is strange. i am using the mecury playback engine and the video i have been struggling to output had a magic bullet looks effect on it. (and like i say was imported from 5.5).

    My system disk is an SSD which is quite small so i thought that might be the issue but i definitely haven't had this problem before and as I said in my first post, i can output a higher quality file from prem pro with no problem at all.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 9, 2012 10:10 AM   in reply to bensandstrom

    Ok everyone I have been on the phone with Adobe about similar issues. They have rewritten the timeline code in CS6 and admit there are bugs when importing from older versions of premiere. I suggest you continue using the older versions of premiere with projects not created in CS6. They are working to fix the problems. But please call adobe and report the problems to their technical support team. If the problems are not reported they can’t fix them. 

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 9, 2012 10:27 AM   in reply to TYLERART

    Tyler,

     

    Please give me the case number for your interaction with Adobe Technical Support. I fear that you have may been given some bad information, and I need to check into it.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 9, 2012 10:59 AM   in reply to Todd_Kopriva

    0183516445

    I don’t feel it was bad just helpful I have had several problems when importing from older versions with effects being buggy mainly when using the GPU acceleration. I think his exact words were “we can’t deny your problem we will look into it"

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 14, 2012 1:00 PM   in reply to TYLERART

    I am having a similar problem.  Whenever I try to "match sequence" I am told that my disk is full, even though it certainly is not.  Very frustrating.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 15, 2012 2:59 AM   in reply to Todd_Kopriva

    I'm also having a similar problem. I have a 2 hour 20 minute XDCAM EX project, orignated in CS6, which I'm trying to export as MXF. I've tried deleting the render files and rendering without the GPU acceleration and AME still fails a few moments into the encode, with an 'unknown error' file. I've also tried splitting the project and exporting in two halves - still no luck. All of my work is XDCAM and I nearly always want to export my projects as MXF. So how am I supposed to complete anything when I can't export it? Please tell me that Adobe is going to sort this out very soon, as at the moment Premiere Pro is seeming like a waste of money.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 15, 2012 10:03 AM   in reply to eajg

    eajg: I recommend that you start a new thread about the issue you're encountering, and include as much of the info requested here as possible. Also, please file a bug report and attach your project to it--without any content at least to start with. You'll find that AME is not listed among the products, so set it against Premiere Pro.

    You're on the right track in troubleshooting this by breaking the sequence down. In addition to cutting it in two by duration, I'd suggest simplifying both in terms of layers and effects, too. 

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 18, 2012 6:14 AM   in reply to Mark Mapes

    I think the problem was caused by CD audio tracks which I had copied over from my Mac laptop and dropped them into the sequence (on a Z600) as AIFF files. Does that sound like that would be a likely cause to you?

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 23, 2012 12:47 PM   in reply to Proj.L

    I have exactly the same problem.  The project was not created using an earlier version, I have deleted all the render files and am using the MPE software only.  No joy.

     

    When trying to export using "match sequence settings" I get the disk full error.  My disk is not full.

     

    I have never enabled parallel encoding and don't know where to find it in preferences.  Using any other encoding options it works fine.

     

    Now, I have both Premiere Pro CS6 and CS5 installed on my computer.  I created the project in CS6 (and this is where I get the error).  However, if I open the same project in CS5, (after the dialogue to convert the CS6 project to CS5), I can export it using "match sequence settings" in CS5 fine, no problem.  No change, exactly the same souce, sequence and action, just a different result.  In CS5 it works, in CS6 it gives this weird error.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 11, 2012 12:48 AM   in reply to bwrlane

    Hi, since my last post there has been no activity on this thread, so...

     

    Has anyone found a workaround?  I find it incredibly inconvenient and unforgivable that I get this error when trying to export a movie in PPCS6 using "Match Sequence Settings".  Some facts:

     

    1. I always get this error when trying to export from PPCS6 using match sequence settings.  It happens with all movies.  Starting a new sequence doesn't change it

     

    2. I never get this error if I use another encoding option

     

    3. My disk is not full

     

    4. It happens whether I use software engine or GPU acceleration (and also if I delete the previews)

     

    5. It happens on both the PC and MAC versions of PPCS6.  With sequences created natively on each machine and imported one to the other.

     

    6. If I import the sequence into CS5, then hey presto, it works without error.  At the moment that is my workaround, but it is not at all acceptable that I have to do this.

     

    7. The sequences were all created in CS6.  None of them were imported from another version

     

    8. My source video is 1080p AVCHD footage

     

    Any further thoughts on how to deal with this really frustrating and crippling new bug in CS6 would be incredibly welcome.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 20, 2012 3:51 PM   in reply to Todd_Kopriva

    When is this fixed, I just bought creative cloud today, and I am to experiencing the disk full issue, when I went to export, I just selected same as project, and it selected mpeg as the codec, which is fine.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2013 3:51 PM   in reply to CharlieMuk

    I just encountered same error when trying to export a shakey clip for offline processing in Mercalli SAL (Warp Stablizer does not work when No Motion is selected). AVCHD 1080p 60fps. 23 second clip. Error exporting clip. Disk full. Bogus msg; plenty of room on the disk. New install of CS6 Creative Cloud. No coming up from prior versions. And for all the talk about Direct Export as an option, I don't see it in the Export menu. Only choice is to go thru the AME.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 9, 2013 5:29 AM   in reply to thetasound

    I have just started getting this problem too!

    It is strange because it has just begun after my latest patch upgrade.

    Whenever   trying to export from PPCS6 using match sequence settings it always says disc full even though there is 700GB available!

    The encoder works with mp4, wmv etc ok, but as soon as I choose   'match sequence settings' it says disc full.

     

    A few weeks ago all was fine, but now it fails all the time ... It is very infuriating as I use this setting OFTEN (well, that is until recently!)

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 9, 2013 10:56 AM   in reply to thetasound

    Only choice is to go thru the AME.

     

    Direct export first showed up in CS5.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 22, 2013 4:32 AM   in reply to Proj.L

    same error just coverting mxf to proreshq but if I change to save on desktop it is ok but not same directory as source!

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 27, 2013 12:49 PM   in reply to Proj.L

    I consistently got this error when trying to export AVCHD 1080p60 footage. For lower frame rates, simply checking the "Match Sequence Settings" option worked well. Not so for the 59.975 frame rate.

     

    After fidddling with it for a while, I finally got it to export by unchecking the "Match Sequence Settings" option and manually selecting H.264 Level 5.1.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (1)

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