A

Anonymous

Question

New in CS5, why can't I render a file larger than 2.15 GB to a network drive?

Forum|Forum|15 years ago
July 15, 2010
19 replies
43184 views

This started just as soon as I installed AE CS5. If I try to render to a shared network drive, once the file reaches 2.15 GB in size, either AE render crashes or the render completes but the file size is 2.15GB and it will not open or import back into AE. Rendering to a local drive works.

Why is this happening?

This topic has been closed for replies.

MMCT-Matt

Participant

Everyone should also be aware that since 10.6.4, into Lion and seemingly into Mountain Lion, there is an additional bug with OS X where files with long filenames (>=32 characters) saved to an NFS export will not show up for a random (but usually substantial) number of additional OS X machines mounting that same NFS export. The reason for the error is that OS X's file system manager (which is downstream of Adobe) saves the long file name with a truncation (using only 31 characters). Then, after the write is complete, it requests the filename be changed to the original. Most NFS servers comply. A check at the POSIX level (in the Terminal) will reflect the change, but at the OS X Application level (Finder, Adobe and above) many clients will still see the old file name. So, if you have automations (or other creatives) expecting a certain filename, it won't be there. For those who have access to Apple's dev site, there are two open tickets since the middle of last year on this issue.

L

Lang_Walker

Participating Frequently

Hey MMCT-Matt - that's incredibly interesting and relevant news. Is this NFS bug in Apple's Server-OS implementation of NFS, or the client OS view of the NFS file system?

We're planning to migrate away from our old AFP/SMB X-serve-mounted SAN storage to Hitachi's super-SAN setup using NFS as the core protocol (and we wanted to just leave the client connections through NFS largely because of this persistent and apparently unsolvable AFX/QT incompatibility). We mostly work in frame sequences anyway, but need to write out large quicktime files often enough to make it worth the while coming up with a permanent workaround to solve this problem that our old uncooperative overlords don't seem interested in ever actually fixing. However, if this is going to open up a large-names-freak-out-on-some-clients-and-break-scripts-nightmare then the cure is worse than the disease.

Anymore information on this NFS bug would be much appreciated (if its Apple server based only we're ok as we're abandoing that slowly sinking ship before Apple abandons us anyway).

thanks so much, Lang

D

DLpres2

Participating Frequently

I looked into enabling NFS on our systems (like theoutfitvfx), quite possible but not worth the hassle. The render-to-local-drive-and-copy workaround is fairly simple. Stupid but simple...

C

colorkite

Participating Frequently

"Stupid but simple..."

Key word being stupid.

G

Greg Leuenberger

Participating Frequently

It's pretty shocking that this is still being delt with....but I guess with FCP X working out of the local 'movies' directly they probably don't even know the problem exits.....lol..

-G

D

DLpres2

Participating Frequently

November 2011, bug still exists, nothing has changed. Of course, Snow Leopard's Quicktime has been on 7.6.6 for a while so why would there be any chance.

1. Knowing Apple, I suppose this will never be fixed for 10.6.

2. Has anyone tried force-installing QT 7.7 to see if it makes any difference? (Force since 7.7 is officially only for Leopard.)

3. Several people have mentioned NFS as a proven workaround. In this context, are there any downsides or pitfalls one should be aware of before enabling NFS?

4. I submitted this bug to Apple, for good measure:

Summary:

The 64-bit compression session API (AddMediaSample2) cannot write Quicktime files over 2.15GB (2GiB) to network volumes (AFP, SMB). Returns -1309 (fileBoundsErr).

Affects all of Adobe's Creative Suite products since CS5 as well as other products.

Steps to Reproduce:

1. Open an Adobe CS5 or CS5.5 Application on a 64bit kernel.

2. Generate / render / save a Quicktime MOV file expected to be over 2.15GB. For example 30 seconds of uncompressed 1920x1080 30p.

Expected Results:

Complete write of file.

Actual Results:

-1309 (fileBoundsErr). QT file is trimmed at 2.15GB (only frames up to a 2.15GB threshold are in the file.)

Notes:

Bug exists since April 2010.

J

JonChappell

Inspiring

There's a bug in QT 7.7 causing all sorts of issues including crashes and being unable to open movie files. These issues are also affecting people who installed the latest Snow Leopard security updates and OS X 10.7.2 so it would appear that Apple is still updating QuickTime on newer operating systems but for some reason not bumping the version number.

A

Anonymous

Aha! This happened to me on a couple overnight renders! And magically this topic appears.

Running AE CS5 10.6.8 connected via AFP to a HFS+ drive mounted on a 10.6.8 Mac. I vaguely remember this issue with Cinema 4D a couple versions back. My startup drive is an SSD, so local rendering huge Quicktimes isn't really an option. Here's hoping to CS5.5 + Lion fixes this.

L

Lang_Walker

Participating Frequently

Just a note to everyone who is being driven crazy by this bug ... it's been suggested that the best way to get Apple to pay attention to this problem is to post complaints on their discussion threads instead of just bugging Todd & the Adobe team about this. A thread has been opened here:

https://discussions.apple.com/thread/3042027

If everyone could please take a few minutes to register their frustration with this flawed Quicktime API with Apple, maybe we all stand a better chance of eventually seeing this fixed.

thanks,

Lang

Brandon Kraemer

Known Participant

We were discussing this ongoing and painfull issue again today at work and wondering if Lion offered up any solutions to this issue. Can Adobe or anyone comment with tested knowledge about this?

Also, I formally submitted a bug report via the Apple developers site and got confirmation that this was a known bug and that Apple was working on it. They also confirmed that the bug exists with SMB and AFP, neither protocol works with files of 2.15 GB.

I can only speculate that the 'fix' involves Adobe moving to AV Foundation and away from QT API. Can we get an update from Adobe about the status of the progress on this bug and if Apple and Adobe are still jointly pursuing the issue?

Thanks in advance,

bk

Todd_Kopriva

Inspiring

I know that Apple was investigating a fix in Lion, but I don't think that the fix got into the current version of Lion. I've asked one of our quality engineers to verify that, though.

T

theoutfitvfx

Participating Frequently

Hi Todd,

Your post says that SMB works. Can you confirm this? I have found that both SMB and AFP Experience this issue. Only NFS works for me

Todd_Kopriva

Inspiring

> Your post says that SMB works. Can you confirm this? I have found that both SMB and AFP Experience this issue.

According to the engineering manager, SMB is the workaround that Apple recommended. But, if it's not working for you, we need to know that. Can you try again and confirm?

I'll get someone to look at this post and confirm from our side that SMB works.

T

theoutfitvfx

Participating Frequently

I have done a whole lot of testing on this issue. I have this problem

across both Shake and Nuke in our facility. Both AFP and SMB have

this problem. Did you test SMB and confirm that it works? The only

protocol that works for me is NFS. I have tried this both on our

XServe Server and Isilon Cluster. Mounting either Server over SMB I

can not render a quicktime over the 2.15GB Limit with either After

Effects CS5, Shake, or Nuke.

Andrew Yoole

Inspiring

I've created a new discussion in Apple's Support Forums about this issue. Any existing discussions I found were archived, hence the new one.

I strongly suggest you post your own thoughts to the thread if you wish to get Apple to address the issue.

https://discussions.apple.com/thread/3042027

L

Lang_Walker

Participating Frequently

Wow ... double fail. Unbelievable.

Thanks PK for notifying us of those results. We weren't planning on stampeding to the 5.5 upgrade anyway (imho, having to pay for a dot upgrade is a bit of a kick in the teeth when the initial offering is still so buggy) ... but I was really hoping OSX10.7 + CS5.5 would have solved this. Maybe final release of 10.7 will be different? One can only hope the feuding giants eventually get over their civil war and back to their job of making our lives easier ...

Todd_Kopriva

Inspiring

> One can only hope the feuding giants eventually get over their civil war and back to their job of making our lives easier ...

We're not feuding. We're working together on this. I can't share the details of our communication, but the communication is there, and it's not a feud.

Regarding this being supposedly easy to fix becuase it worked before:

After Effects CS4 used an old QuickTime API. After Effects CS5 can't use the old API because it doesn't work with 64-bit values and doesn't provide some crucial features. Apple told us to use a new API, so we did. It has a bug. Apple has acknowledged that bug. They are working on a fix. We hope that it comes soon. If you do, too, then ask Apple to hurry. We certainly are.

A

Anonymous

Not to start anything but I was at NAB and had a few goals in mind.
One was to talk to someone from Adobe about this.
Well after a few demo jockeys (actually not even just the ones working on the perimieter), none of them have heard of this problem.

Funny there must have been an invsible force-field of something cause all surrounding vendors around the Adobe booth seems to know about the ugly thruth.

I for one am skipping our enterprise upgrade to 5.5.

T

theoutfitvfx

Participating Frequently

If you have the ability to connect to a network Server over NFS you will not have this issue. I have had this problem for a long time with both Shake and Nuke. Not sure what is different about NFS but there is no limitation on file size. I just tested CS 5 and Nuke and both fail when connecting to our server over SMB, but when connecting over NFS everything works fine.

Shame on Apple and Quicktime. Quicktime is my worst nightmare in our environment and trying to manage all of it's flaws in a professional environment is such a waste of time

M

Majestic_Skyline01AC

Participating Frequently

theoutfitvfx,

Thanks for the NFS workaround!!!

I can confirm this works.

J

JeremyNeish

Participating Frequently

Did this get fixed in 5.5? Please say yes! This is driving me crazy.

And yes, Adobe isn't alone in this, I've been complaining about this buggy QuickTime API from Apple over a year now. REDCine-X has the same limitation/bug for the same reason:

http://reduser.net/forum/archive/index.php/t-48966.html

L

Lang_Walker

Participating Frequently

Hi Todd:

Are we just going to have to wait until OSX 10.7 comes out in July/August sometime for this to be fixed?

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded