Todd, can you have the engineers define local disk? Will we have issues with SAN disks under XSAN, MetaSAN or SANmp or is this limited to just afp or all network protocols?

Hi Todd:

I can understand that's it's difficult to work with Apple if they're giving you bad information, but didn't you guys bother to test this software across a network at all? It's not like generating quicktime movies > 2.15 GB on a network drive is an obscure workflow. And suggesting we submit a "feature request" to restore a major feature lost in this "upgrade" is a bit cheeky.

Sorry to whinge, but seriously - shifting everything to image sequences is a major workflow nightmare, and rendering locally in a collaborative environment is a version-control nightmare. Please sort something out with Apple to get AFX CS5 working properly with Quicktime asap. Until then it's really just a beta release.

I sure wouldn't have suggested purchasing it if I'd known about this first. And I definitely won't suggest anyone else gets it until this is fixed.

Thanks for clarifying that bug reports and feature requests are available on the same link.  "Blaming" was a poor choice of words on my part... but it's not like most of us know what "QuickTime Compression Session API" is... we just know our workflow is broken, hopefully temporarily.  That is the end user perspective I guess.  Glad to know the engineers are aware of this.  I did follow up and submit a bug report on this issue.

thanks

Some of the video files I work with are for large res video walls and  thereby terabytes in size. We always work uncompressed until we have to compress. We do have a RAID setup on the main machine,  however, I'm not sure THAT'S enough room for some of these files "Locally".(Not to mention the time it takes to copy them back over to the network afterwards so they can be backed up.)

I hope this  doesn't spin off into another wrestling match between Apple and Adobe.  The two (QT and AE) have worked hand in hand for most of us for so long.

Consider this not a complaint, but a plea... please remedy this ASAP. I've got another HUGE project coming LOL. I'm sure that would make us all very happy people.

Todd,

Thanks for the quick follow-up. That's going to the plan for now. Image Sequence –>.mov–>Network.

Thanks again for working on it.

-J

Another caveat to image sequences is they don't always play so well in a SAN environment.  Bring on the QT fix, the sooner the better.

Thank you very much for your effort and keeping us informed.

In the meantime here is another funny one:

Due to this situation we decided to render out in a Tiff sequence -and then to convert this back to a animation quicktime.

We encountered a problem with a certain tiff-seqence where we are unable to create a animation quicktime from it.

We can make uncompressed quicktime or compressed formats from it,-but nothing

with animation codec.

we would like to give you a link to this special file.

Thank you very much,

Why isnt this fixed yet?

This is a serious setback in installing CS5 in my production facility.

I also teach at local college and have expressed that its not worth upgrading to CS5 until this is resolved.

We use AFP off a XServe Leopard system.

The resources and AE docs reside on the network.

Even if you render to local, this doesnt work.

Ive tested everything under the sun.

We even installed MainConcept MPEG Encoder and used that as the codec.

It just crashes trying that route.

Were still forced to use CS4.

Having a hard time explaining this to my company after spending 12k on upgrades.

Hi Todd,

Thanks for all your help in explaining the problem publically. I just have a couple of quick questions if you don't mind.

1) If this bug truly lies with Apple (and I most certainly believe it does at its core), why doesn't Adobe reimplement their old way of doing things from CS3 (don't have CS4 in house, so I don't know if it works in that version) in the meantime to solve this particular problem? Seems like a waste to wait on Apple when Adobe already has in-house code that doesn't have this problem.

2) From the reports you've been getting (and this is open for anyone else to chime in on), is this issue only limited to Snow Leopard, or does it occur with Leopard 10.5 installations as well? My studio is finally all upgraded to 10.6 SL, and I don't have the time or energy to roll back a production machine to 10.5 just to see if the bug still occurs there.

Again, I appreciate the time you've taken to describe the problem, but it seems pretty disingenuous to lay the blame at Apple and wait for them to fix it rather than actively seek to find an appropriate solution within AE (not that I'm saying you guys are ignoring it completely). Every single motion graphics facility I've worked with in the Hollywood-based film/TV industry uses this workflow to render out product, and to continually recommend using workarounds doesn't seem like the best "solution" to the problem.

Jason

Todd,

Thank you so much for your lightning fast response! As a former QA tester at Apple, I understand the process and lead times that go into such fixes. I absolutely appreciate all the hard work you guys are doing, and other than that AE CS5 is still a great product. If there's anything I can ever to to assist in testing, it would be my pleasure to do so. Thanks again, and happy new year to you and the entire CS5 dev crew!

Jason

Todd,

Todd,

Thanks for the quick response.

quick comment:

Our  company also upgraded to CS5 and found we could not render quicktimes  from our local computers to our network drive. (Bossman was  pretty excited about that after almost a  10grand upgrade). However, we have three render boxes that are running  the CS5 render engine (also working over the same network) and those  little guys have no problem slapping  down quicktime files on the network drive (average file size abour 6 gigs)