NR23Derek wrote:
Kevin thanks for the information. The problem is this issue has caused probably quite a lot of us a lot of problems and expense, there will no doubt be a lot of people out there even now struggling to make it work who are unaware of this issue Adobe really should go public and admit there is a problem and explain the transcoding work-around. Not only that, but when it is solved it needs to be treated as a bug fix, not a program upgrade as far as existing customers are concerned.
As I said, it was a major architectural change that needed to be made to find a fix in the upcoming version. Yes, it is a problem for Premiere Pro CS6 users, and we have indicated it is a known issue. We are trying now to see if a fix is possible for Premiere Pro CS6, so stay tuned.
I suggested a feature request, because as Greg said, it is faster to getting the word to the right people. If you want to call it a bug fix, that is fine too.
NR23Derek wrote:
If that amounts to a free upgrade to 6.5 or whatever the next version is, then so be it. We have suffered and we expect nothing less than a free fix and for Adobe to take this on on the chin.
I'm not sure what the team will do yet, or what the result will be, but thanks very much for your feedback. As I said, we know how important it is to users like yourself.