[UPDATE: This has been fixed in the next version of After Effects and in Adobe Media Encoder CS6 and Premiere Pro CS6 (6.0.2/6.0.3) updates.]
We’ve been getting reports of people being unable to export QuickTime files larger than 2.15GB across a network using AFP (Apple Filing Protocol).
Here’s what’s happening:
In After Effects CS5, we moved to using the Apple API
AddMediaSample2. This API is critical for frame reordering to work and gives us access to 64-bit time samples, which means that we can export longer movies.
AddMediaSample2 has a bug that
AddMediaSample (the API that we used for After Effects CS4) doesn’t: When the file size reaches 2.15GB on an AFP volume, the function returns
fileBoundsErr), and the calling application is stuck and can’t do anything else.
This bug in this Apple API also affects Adobe Media Encoder and Adobe Premiere Pro, as well as any other program using the
AddMediaSample2 API. See this post on the Apple QuickTime API list for an example.
Adobe and Apple are working on addressing this issue.
This issue only affects individual QuickTime files larger than 2.15GB rendered and exported over an AFP network. Therefore, there are several possible workarounds:
- Use NFS instead of AFP. (Some users report success using SMB, though others report failure.)
- Render and export locally instead of across a network.
- Render and export to a format other than QuickTime.
- Render and export to image sequences and then assemble image sequences into QuickTime movies using Adobe Media Encoder or QuickTime Pro on the remote machine.
If you’d like to discuss this issue, come to this thread on the After Effects user-to-user forum, which contains some more detail and history. Do not respond in the comments on this blog post; the comment system for this blog is a greatly inferior way to have a conversation, and far fewer people read the comments here than read the forum thread.