ExactImage wrote:
Thanks to Greg and Kevin for this info, but honestly this is a little scary because it definately sounds like some people (internally) are arguing for it to "not" be in CS6, but to require users to pay for an upgrade to get this fix. This is totally unacceptable. Please let them know that this would be an almost certain nail in the coffin for my future plans with Adobe.
ExactImage,
The product team definitely knows about this. Please understand that it has nothing to do with holding back a fix to sell you on the next version of Premiere Pro. It's all about a major architectural change that was necessary to fix the issue.
ExactImage wrote:
I know I'm not alone in this.... so future business from me and a few others at least rests upon Adobe doing the right thing for CS6 users.
Thanks very much for letting us know how important solving this issue is to you.