Just to follow up on this... i did figure out what my problem was. 

The AVCHD media I imported had some problems with it. 

I noticed my export would always crash around a certain point, so I checked that point out in the timeline, and at the end of a clip there was a second of black - and it said, error, disk limit or something. 

Either way, there were some bad clips in there, so all i had to do was delete that second of black error at the end of the clips that were corrupted, and it exported perfectly. 

Unlike me, first check all your media in the timeline. You might be surprised what you find in there sometimes. 

Just to follow up on this... i did figure out what my problem was. 

The AVCHD media I imported had some problems with it. 

I noticed my export would always crash around a certain point, so I checked that point out in the timeline, and at the end of a clip there was a second of black - and it said, error, disk limit or something. 

Either way, there were some bad clips in there, so all i had to do was delete that second of black error at the end of the clips that were corrupted, and it exported perfectly. 

Unlike me, first check all your media in the timeline. You might be surprised what you find in there sometimes. 

Hi all,

Greetings from the Great Land Down Under...

Now I don't know if this is going to help anyone but I had this same error today using Symphony v6.  I am exporting a 30-sec CSA as an H264 QT movie with four alternate audio mixes.  The first one is called DG1878_30_v8a.mov. the second one DG1878_30_v8b.mov etc.  Versions a, c and d experted without the error but the "b" version would not.  I ended up exporting it as just DG1878_30_v8.mov and then adding the "b" after the file had been exported.  Really, really weird I know but there it is!

Cheers,

Dave Forsyth

Software is a beautiful thing

i bump my head on this kind of stuff all day.

It is a collossal waste of time.

AVCHD is fraught with problems.

Hi all,

Greetings from the Great Land Down Under...

Just had this saome prolem myself.  I workd around it using the same method we used years ago when dealing with the old PGLUE_SAMPLE_NUM_OUT_OF_RANGE error...

1. Load the offending sequence into the timeline
2. Move in one frame from the head of the sequence and mark IN
3. Move in one frame from the tail of the sequence and mark OUT
4. Subcatalog it back to the bin 
5. Export

All is well! But here's what is really odd.  If I load this trimmed sequence into the timeline and try exporting it again, I get the same error!

Hmmm....

Dave Forsyth

I got this error today.

Running MC 8.4 with a custom-sized project (1000x1310) and source material FrameFlexed from 1920x1080 (AMA linked) files.

I had added a NewBlueFX color correction to a clip on the timeline, and got the error while trying to export as H.264 to those dimensions.

By rendering the effects, I was able to export successfully.

To be on the safe side, I rendered all the clips on the timeline first before exporting.

Always best to render up first.

If you don;t then any renders created as part of the export process are not retained so a 2nd export has to do them all again. Render first (or video mixdown even better) then export.

Hi all,

I'm bumping up this thread because there are things that just don't change...

I've had this error several times during the years but rendering and/or mixdowning always helped. Now we are on 2018.12.1 and I have this again: one (out of twelve) timeline can't be exported.

After the 56th attempt the timeline is not only rendered and mixdowned, but is a brand new timeline which only contains the mixdown (both audio and video) and the codec is the same (DNxHD185x) as the export format would be. The playback of the sequence is flawless.

Any ideas?

Luckily I've sorted this out (I exported small parts of the sequence according to the position of the progress bar indicator when the error occured). It was caused by a rendered effect (which was of course included in the mixdown), and the render itself contained something, something that didn't show up when playing the sequence, nor did it give an error during the mixdown, but it even got itself reproduced into the mixdown thus preventing the export of that too.

It would be really great if someone could explain this (and fix this bug as it'll soon grow adult and demand rights).

p.s.: I've just noticed that this is the Mac section (google brought me here). My case was on a Windows PC, but honestly it doesn't make any difference here...