QuickTime API Bug
Users of Adobe After Effects CS5 and CS5.5 are hamstringed by an ongoing fault with a Quicktime API. Rendering a QT file of over 2GB to a network drive fails, which can be disastrous to many collaborative workflow environments, where rendering to local drives is not possible or logical.
This problem occurred following the transition of Adobe After Effects to 64 bit. The old QT 32bit (working) API was replaced by Apple with a new one. Trouble is, the new one has a bug. That bug has now existed for over a year. The bug has prompted an ongoing, year-long discussion at the Adobe After Effects User To User Forums.
Apple, this is a MAJOR issue for your professional customers. This issue strangles the workflow of THOUSANDS of users every day. Surely you aren't just sitting on your hands until the release of OS 10.7? Please, help us by addressing this serious flaw urgently.
This topic was raised last year by another poster:
I've been flaming the Adobe engineers pretty heavily on the Adobe forums about a nasty bug in After Effects CS5 that prevents the program from writing quicktime files >2GB to a network drive (AFP).
Apparently the bug isn't actually in the AFX code, but in the "new QuickTime Compression Session API that Apple asked [Adobe] to use" ... specifically "AddMediaSample2 has a bug that AddMediaSample1 doesn't. That is when you hit 2.15 gigs on an AFP volume, the function returns -1309 (fileBoundsErr) and we are stuck and can't do anything else."
Do you think you guys could spare an engineer or two from your new consumer products empire to support some of the pro stuff you used to care about in the good old days?
Many, Mac OS X (10.5.4)
