QuickTime API Bug

This is a devastating, worflow destroying bug that has been driving the professional After Effects (and RedCine) communities crazy since July of 2010. The word from Adobe is that they implemented 64bit functionality in After Effects CS5 that relies on a broken quicktime API from Apple that has never been corrected. Apparently the inability to render files larger than 2.15GB to an AFP volume is still broken even with CS5.5 and OSX10.7 ... I've been complaining bitterly on Adobe's forums for months, and posted the above message on an Apple forum back in September. Adobe has at least takent he time to respond (however innefectually) to everyone's increasing frustration with this impasse, but Apple's complete lack of help or feedback is a serious indictment of the company's commitment to the professional user community.

If Apple has any intention of remaining a professional video creation platform it's incredibly important that this API bug be corrected asap. If Apple only wants to create shiny consumer devices in the future, please let us all know so we can start ramping up on our linux skills.

This is a terrible bug that causes a lot of undo file copy time and cripples our network rendering solutions when using QuickTime which serves the needs of our editorial department. I have found this bug to be prevalent with not only Adobe AfterEffects but with QuickTime Pro exports, Compressor transcoding operations and Redcine as well. It's terribly frustrating that we have an infersturutre that includes a SAN, 2 X Serves and a Prommise RAID but we can't get a file out over 2.15 that everyone can share with out first rendering to a desktop and then copying the files to our network servers. This slows down the pace of business terribly and it needs to be fixed ASAP.

Adobe has been very transparent about this issue but we have not seen any public recognition of this issue on the part of Apple. Please, repair the API and give us back our workflow!

As a footnote, the statement info that Adobe provided which suggests that SMB is a workaround to AFP is apparently false, we have not been able to get that to work applications which have the problem over AFP. Apple provided Adobe with the information that SMB was a work around.

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

It should be noted that this also affects Premiere and any other 64-bit application trying to write a QuickTime file over a network connection.

This bug has been around for years. Apple, if you are awaiting an invitation, consider yourself invited. Apple, if you don't think this is important, then Windows is looking more and more attractive to the Professional community that you are slowly but surely ignoring throughout your company and future plans.

Why is it that it seems that iCrap is getting all the resources even as the Mac business was growing?

This bug has been driving me instane for years now. In addition to affecting After Effects and Premiere it also affects all RED Camera tools (RedCine X, etc). They claim they've been trying to get a fix from Apple for a long time, but to no avail.

Apple, please, please, please fix this immediately.

Hi Apple,

Just registering my extreme frustration with this issue. Have you seen the adobe forum about this? People are furious (as are we).

Right, I'm off to make as much noise as I can about this.

I too have run into this nightmare of a problem; I even created an account just to lodge my dispare on these forums!

We have just undertaken a program of upgrading from CS4 & OSX 10.4/5 to CS5 & 10.6.7 - if we had know of such a catastophic bug, we wouldn't have bothered with either of the softwares (and most likely shifted to another platform).

We have these machines tightly integrated into our infrastructure (with LDAP authenication and autofs). Our main storage is a 92Tb store served over NFS (auto mounted with autofs), and I simply cannot believe such a fundamental bug still exists so long after these products were realeased.

Apple: whatever your issues with Adobe over recent times have been, you better start addressing this fundamental bug or you risk lossing many long time customers and your most established user base.

Seriously Apple. This problem is a nightmare. How hard could it possibly be to fix this bug. Couple lines of code and an update. Quicktime X is already a step back in workflow, at least you could make the transition less painful by fixing an obvious and blatant bug.

This is really hurting our studio as well. AFP is the best solution for our pipeline. Please fix this asap.

This needs to be fixed immediately. We are really feeling the weight on our new show as most of our REDCINE X renders go to AFP NAS through Snow Leopard Server. I will throw a couple mac pros on the job and they will all render footage that stops 2.15GB.

How will FCP X deal with this issue?

I hope all of you people are also sending reports to Apple through "feedback" channels because this area is peer-to-peer and not a "direct line" to Apple, its video programming technicians, or general service personnel.

Aside from links with in Apple Pro apps, how does one contact them through the feedback channels when the problem is with non Apple Pro app produces, in this case Adobe CS?

The best way is to file a formal bug report:

http://bugreport.apple.com

(you'll need a free developer account for this)

I found getting the developer account was easy and filed the bug report officially. I'd suggest others do the same.

I am now having my fun with this stupid bug that Apple just does not seem to have time for. Thanks Apple...for once again kicking your professional clientel to the curb (ala FCP X). I guess you want to simply sell iPads & iPhones and let everything else go to pot. Man this is so upsetting. I have been an Apple Fanboy for 15 years and this year has been the worst as far as Apple nightmares goes.

How about throwing a good ol' fanboy a bone and fixing this heinous API BUG?!?!?

PLEASE!!!!!!