[Jeff Kay]

Are you exporting directly from AE, as in AE is doing the encoding?

If you haven’t already, try exporting raw as an intermediary and then encoding that in Media Encoder or other software that handles encoding much better.

Adobe has never had great encoding built into AE, its just not what the software does. Recently they have actually started pulling support for AE encoding because it was never intended to encode in the first place and many keep having errors when trying to encode straight from AE.

[Jeff Kay]

In the video you have “output noise only” checked.

[Jeff Kay]

Good that you have gotten it out. My typical export is video and audio mixdown of the entire sequence, exporting that as a quicktime reference, and then using a different encoder for the final, which is what I would have recommended.

When you said you tried a mixdown, was it the full sequence or was it just mixdowns to replace certain parts of the footage like you did with the HDV portions? I’ve found that even one simple edit in a mixdown sequence will make the export from MC far longer and more difficult.

[Jeff Kay]

This is more or less what I do on a semi-regular basis between my workstation and laptop. Though how well you have your media organized (both Avid Media Folder as well as AMA linked media) can make this relatively simple or a complete chore. I try to keep the subfolders of the Avid Media Folder separate for different projects, which means I only need copy that one folder. Though as of late, all of my media has been on externals and taking the external is not prohibitively difficult, so I just do that (of course everything is backed up).

Actually I’ve been archiving old seasons on external drives and I don’t need to do much more than plug in the appropriate drive and that season’s timelines are back online.

[Jeff Kay]

[Bill Davis] “I’m just saying that for the past 12 years, I’ve watched as people excoriated software for not having functions that I NEVER use”

In hindsight I might be misunderstanding this a little. If this is in reference to a new version/update to a software (which is at least where we started) missing a feature/function/compatability that was present in an old version, then I do feel that is something that shouldn’t be excused.

The primary reason from a user’s standpoint is that there is no design reason to remove functionality. There are certainly many commands/functions that one will use often and others will never touch, but having multiple ways to accomplish the same tasks is most certainly a good thing for robust software.

Though there is a much more practical reason, in virtually every case the command/functionality hasn’t actually been removed. Programmers almost without exception never delete old obsolete lines of code, so version N of a software contains all of the code of version N-1 (fairly recently Apple with FCX and Adobe with a few of their softwares have done ground up rebuilds of code, this is the exception). While I’ve had more experience with this from AutoCAD updates over the years, there have been several instances over the years where a command had officially, as according to documentation, been ‘removed’, but only the button/menu option had been removed and it could still be used via command line.

[Jeff Kay]

Yeah I meant image sequence. I just tend by default to think towards PNG and I hadn’t even thought about the differences in images types.

I only very rarely end up using image sequences to render. I’d definitely go with Walter’s experience on this.

[Jeff Kay]

I was about to say that I’m looking at one right now on my timeline and then I realized that you specified “dissolve”. (Its an AvidFX transition template I created a long while back with some animated effects, a transition that is asymmetrical depending on placement, but it is not a dissolve)

Though a dissolve template could be created where the cut is the 50% point such that a 30frame dissolve starting 10 frames from the cut goes from 0% to 50% in 10 frames and then 50% to 100% in 20 frames (which can be done with keyframing).

But we’ve all long known that starting a 30frame dissolve at 14 frames from the cut is really the same as starting the dissolve at 15 frames and then moving the cut one frame, whichever we do is dependent on the timeline in question. For instance when laying music using dissolves to bring it in or out is common, but I always place my dissolves entirely within the clip because I know that later I’m going to have to fill out a music cue sheet and doing so makes it far easier to figure out the actual length of time the music is being played.

I guess I just don’t see the point. Might as well argue that there is no such thing as video because its just a series of still images.

[Jeff Kay]

What is the final render from AE set to output as?

You should be able to render as a png sequence which will give you partial renders that should be relatively easy to combine or continue from the error. Its certainly not the most desirable option, but it should be a viable, though potentially time consuming, workaround. Then take that png sequence and encode it to whatever format you are using/delivering (its going to be pretty big, a quick estimate would put a 4min 4K video at around 240GB).

Alternatively if you can pre-render whatever pre-comps/layers/elements and then replace those elements with rendered footage, then AE will only have to deal with a video stream rather than a collection of elements that has multiple effects placed upon them.

[Jeff Kay]

I don’t know about the supermodels, but I do know for certain that 203% of Nigerian princes want to transfer millions of dollars into my bank account.

[Jeff Kay]

[Marcus Moore] “Where is this coming from again?”

From the same place as most of the comments here, such as FCX users outnumbering other NLE users.

Realtalk: Swapping NLE’s (and OS) is just not a flippant move. Archives and infrastructure play a huge role that is ignored or unaddressed. Every production house in my area that I am aware of is on the same NLE now as before FCX was released (avid, or FC7). Existing infrastructure flavors a whole lot of business decisions and it should be expected that any move away from existing infrastructure would be delayed. While there is no source, would that a source have been given this wouldn’t really a happening that should be argued against. Unless its incomprehensible that someone might not like FCX, which even a glance at how divisive FCX was/is makes that a silly sentiment.

EDIT:
[Tim Wilson] “Although I guess it depends how you’d count a “former FCPX user,” right? How long would they have had to try it before bailing in order to count?

But in general, I do think there’s a high incidence of people who saw what they needed to from the combination of 5 or 6 years without a meaningful FCLegend update, the early releases of X, and a not exciting Mac Pro. Making no value judgements myself (for once). Just an observation…

…but I do have some questions myself about the relationship between X, switching and other NLEs three years into this. The sociologist in me wishes that there had been a way to track the changes along the way….in a more substantive manner than this subject line. LOL”

Yeah, this is what I was trying to get at.