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

[Guest]

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?

[Todd_Kopriva]

We're still waiting for the fix from Apple.

[sweety_1136]

THANKS for the fast response!!!!

So we workaround this "..." and wait and wait and wait ..... for Apple 

[Guest]

Most of us stopped last summer.
I was at last years NAB hunting down answers and didnt get any.

Itll be render to local drive for big QT docs for now.

Most of my renders go thru MainConcepts MPEG Encoder anyway and that works over AFP network.

[Todd_Kopriva]

I've asked for an update from my coworkers who are in communication with Apple about this issue.

[Rook888]

I stopped to believe in anyone involved about this.

[Rook888]

Sure...

[JeremyNeish]

Rumor is that 10.8.2 has some network fixes and that it might solve this issue.  Sadly I can report that is not the case.  The bug still exists.  Please Apple & Adobe fix this!

[Rook888]

I am afraid that no one is listening...

[Guest]

I got responses over time. Always the same. We are working on it with

Apple. It has only been three years. Do you expect something faster from

Apple and or Adobe. I talked to some of the engineers about 2 years ago.

Very Arrogant. And did nothing but tell me how cool they were. They were

quite pleased with themselves.

[Todd_Kopriva]

We are working on it still. In fact, the issue is fixed in the recent Adobe Media Encoder and Premiere Pro CS6 (6.0.2) updates. We are still working on the After Effects piece, which has more complexity.

The speculations above about the relationship with Apple and Adobe miss the point. In fact, Apple has been cooperative in helping us to understand the issue. They tried to make a fix on their side, but it was too destabilizing in other areas. So, we needed to make some big changes on our side. We actually work rather well together.

[Guest]

thanks for clearing that up.

But what about the flash deal etc....And of cource as many folks have

stated. 3 years now???

[Guest]

Jeremy

Apple has known of this problem since 09. Mid 09.

So has Adobe. Apple even has the problem listed in the bug report

database since 09. They call the database of Bugs "It's on our Radar".

And that is where it stayed. We have made fixes around Apple many times.

Apple and Adobe seem to be having some kind of issues. Not sure why.

I have some ideas but for the most part I think with Apple it is about

I-Pods etc.. Apple left Adobe Flash out of the new I-Pad. It really

sucks. So many sites use flash.

So if you have an I-PAD and folks that have been loyal to Apple for

years have asked Apple to support Flash. But Apple did not listen.

They are now the largest company in the world thus i guess they feel

they do not have to listen to anyone. Maybe that is the deal with Apple

ignoring such a large amount of customers. Who knows. All anyone can do

is speculate. Calling Apple is a waste of time for this issue.

Now

for your problem. It has been tracked down to an issue with the

programing API Apple uses and so do developers such as HELIOS and Adobe.

So it is not exactly Adobe's fault. However I would have made a work

around long ago. We have done so in several of these Apple situations.

And there are several of them. ILM uses a very good work around. Also I

have heard that Adobe 6 no longer has the problem as they bypass the

Apple API. But I have not had confirmation on that.

I just know that we started to make a work around and discovered

there were several that are very sloppy work around such as using Dave

and there are very good work around s such as mentioned that ILM uses

one that is very good.

I would tell you but you stated to me 2.5 years ago. Apple is a company

that moves forward and does not look back.

Anyway we help out and get our customers fixed up so they do not have to

deal with the problem. We did so within Days of finding out about it. We

even suggested a way for Adobe to fix it. Not sure if they used our fix

or not but it looks as if they had a different route if it is fixed in

the latest version of Adobe.

Jim Davison

[DLpres2]

By the way, Avid Media Composer has the same problem. Wonder when they'll get around to fixing it.

[Todd_Kopriva]

This is fixed in the next version of After Effects. I listed it in the significant bug fixes here:

http://blogs.adobe.com/aftereffects/2013/04/whats-new-changed-after-effects-next.html

We're sorry that this took so long. The After Effects feature set regarding QuickTime is deeper than that for Premiere Pro and Adobe Media Encoder, so the fix that we used for those two didn't work for After Effects.

[Guest]

Hi Todd

Thanks for the message but is it not the same message from about 10

months ago???

I do not want to be rude but am I missing something here???

I never did blaime Adobe for the problem. It is clearly an Apple Problem

and SIRI is more important than the loyal customer base is what a lot of

folks are saying as they switch from Apple to Windows and quite a few to

Linux. There is some good ( Not as good as Adobe) tools for that OS that

do a good job.

Tell me what I am missing here Todd. I realy want to know and do care.

Thanks

Jim

[Todd_Kopriva]

Before, I was saying that we were working on a fix. Now, I'm telling you that the fix is in the version that we're releasing next (soon), though we still haven't announced the exact release date.

[Guest]

OK

Thank you.

Jim

[Greg Leuenberger]

THANK YOU.  Yes, it's been a long time but better late than never - this has been a huge PITA for quite some time now.  Now - if we could only get some proper multicore based rendering without having to load the same scene up 16 times to make full use of my computer's cores (I don't care if it's tile based or frame based - but every 3D app on the market is about 1000% more effficient than AfterFX on this front). : )

-Greg

[Vision3Jason]

Thank you TODD! Those of us who have been in this thread since the beginning are grateful for the work/communication you've shared the entire way. The news wasn't always good, but you shared it nonetheless. Software is always going to have bugs. But every day there are giant companies NOT giving a $@%& about it for their customers. You have proven different. So I wanted to say Thanks for that. I do have one question. You said "next version". Does this mean that it will be packaged in an update to existing CS6 or waiting until CS7?

Thanks again for everything.

-Jason

[Todd_Kopriva]

> Does this mean that it will be packaged in an update to existing CS6 or waiting until CS7?

This refers to the next version, not an update to CS6. More details on exact release dates soon. You can subscribe to our blog to be kept up to date:

http://blogs.adobe.com/aftereffects/

[Gabe Valente]

Don't mean to resurrect an old thread, but I'm working on CS6 here, and I'm still experiencing these issues...

Is there an explanation for this?

[Todd_Kopriva]

> I'm working on CS6 here, and I'm still experiencing these issues...

Is there an explanation for this?

This bug was fixed in After Effects CC (12).

See the list of bug fixes at the bottom of this page:

http://blogs.adobe.com/aftereffects/2013/04/whats-new-changed-after-effects-next.html

[Guest]

we gave up on this and focused on things that to do work.

we still upgraded to CS 5.5 knowing nothing would help.

[Guest]

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.

[DLpres2]

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.