Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Avid Media Composer Avid Errcode -2034

  • Avid Errcode -2034

    Posted by Jen Milano on August 18, 2009 at 5:44 pm

    I am having an issue with the Avid where it will not export same as source Quicktimes. I receive this error message when I attempt to do so.

    Exception: Movie Export from Procedures FAILED! errcode -2034

    Does anyone have any idea what this means and how this can be remedied?

    Thanks~

    Jen

    Darby Macinnis replied 13 years, 10 months ago 6 Members · 12 Replies
  • 12 Replies
  • Jon Zanone

    August 19, 2009 at 5:32 pm

    Can you play the Quicktime? I seem to rmember that as a corrupt media file. Are you working on a Meridian system, by chance?

    Jon

    “Jamming our heads full of figures and angles
    And telling us stuff that we already know”

    Willie The Wandering Gypsy & Me
    Billy Joe Shaver

  • Jen Milano

    August 19, 2009 at 6:17 pm

    Hi there – There is no Quicktime which results – the export goes for a few seconds and then comes up with the error. My hunch is that it is corrupt media somewhere, but I wanted to see if anyone had experienced this before?

    I am running Media Composer Adrenaline 2.1.8

    Thanks~

  • Jon Zanone

    August 20, 2009 at 12:40 am

    How much space do you have the on hard drive you are trying to export to?

    Jon

    “Jamming our heads full of figures and angles
    And telling us stuff that we already know”

    Willie The Wandering Gypsy & Me
    Billy Joe Shaver

  • Kris Anderson

    August 20, 2009 at 9:47 am

    Check your version of Quicktime.

    I got caught out once and had the same problem when itunes self updated and messed up my quicktime.

  • Jen Milano

    August 20, 2009 at 2:42 pm

    10GB – and trying to create a 10mb file

  • Jen Milano

    August 20, 2009 at 2:43 pm

    we don’t actually have iTunes on the systems – we are running QT 7..

  • Michael Hancock

    August 20, 2009 at 3:06 pm

    [Jen Milano] “we are running QT 7..”

    You should be on Quicktime 6.5.2 if you’re running Media Composer 2.1.8. Check the version matrix here:

    https://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=267087

    That may be part of the problem. Also, have you tried selecting just a short portion of your sequence and exporting that? Set your export options to Use Marks and Use Selected Tracks. If you can export just a small portion then it’s likely corrupt media in your timeline like was suggested. If that’s the case you need to find it and replace it (recapture/rerender/reimport).

    I’d start by rolling back Quicktime to the right version and trying the export again.

    Michael

    ——————————-
    I’ll be working late.

  • Kris Anderson

    August 21, 2009 at 4:10 am

    Are you running on PC or Mac?

    If you’re PC and you’re trying to export 10gb to a FAT32 drive it will stop due to the file size restrictions of FAT32. In order to isolate the problem, can you export in another codec with any success, say Animation for arguments sake? If so, it’s not the drive format but most likely the QT version you’re running.

  • Jen Milano

    August 21, 2009 at 1:18 pm

    I am on a PC – and actually only trying to export a 10mb file – I can do this successfully for other projects – this particular one has been a stickler.

  • Michael Hancock

    August 21, 2009 at 1:32 pm

    I think it’s time to divide and conquer. Mark and In and Out on just the first half of your sequence and try to export. If that works, try it with the second half. If you get the error there’s corrupt media or another problem there. Divide that half in half and export. If that works then you have corrupt media in the other half. Divide that in half, export. Etc…until you find out what where the corrupt media is.

    Also, are you giving these files a new name every time you try to export? I know on the old Meridien systems I had an issue where I’d get an error on export, do something to fix it, and if I exported with the same name I’d continue to get the error. If I changed the name on export it would go through. So maybe try that too.

    Michael.

    ——————————-
    I’ll be working late.

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy