Hi Atkinsgj,
Atkinsgj wrote:
"I would begin to look for workarounds or a change in workflow so you can avoid this particular bug. Transcoding footage is one way you can do that. Is that possible for the near term? At least you could continue working after doing so."
It's possible, but it'll cost us a lot of time. It's easier just to revert to an older version of the software, recreate our projects, and pray that the other previous bugs don't surface.
That sounds like a good plan of action.
Atkinsgj wrote:
I can't spend any more time on this thread, I'm sorry.
Thanks for your feedback. I'll continue to advocate for a fix.
Atkinsgj wrote:
This release is a write-off. I'm telling the shop to keep the car, it's too broken and too expensive to keep tinkering with.
It works fine for most people, but some customers might be having trouble with 8.1. Especially affected are those updating complex project files and using Canon .mxf footage. I'm sorry this happened to you.
Atkinsgj wrote:
Please don't mistake criticism of your employer for criticism of you - I'm happy with your support, but not the policies that prevent you from giving us info we need to better understand what the road ahead looks like. You can communicate to the engineering team, but perhaps they can communicate back when the next planned bug-fix is, or what the cycle for that kind of stuff is.
Thank you. Unfortunately, there are rules against disclosing precise information regarding our releases that extend beyond company policy and into the legal realm. Sorry. I might eventually be able to provide the info that a bug will be fixed in an upcoming version, but that's about it.
Atkinsgj wrote:
Let's not pretend that your software updates haven't been in a predictable cycle, what I want to know is will we be waiting another half-year, or will an intermediary come out if they can in fact recreate the issue? You're not withholding information, rather the information we need isn't available to you. That's the disconnect.
See my previous comment.
Atkinsgj wrote:
Best of luck...I've sent you video evidence of the issue, a lot of people have described it here...if your engineering team wants the files they can make us an offer in the form of reduced licensing fees because we paid for something that should work out of the box (err, cloud). I know that sounds petty but I can't spend any more time without some sort of guaranteed return.
Sorry, all I can offer is my word that I will continue to advocate for this issue. If you do not want to contribute by filing a bug report or providing us sample files, that's fine. I hope other people reading this thread will do so, though. Here is the link once more: http://adobe.ly/ReportBug
Atkinsgj wrote:
Thanks for dedicating extra resources to this thread, please do not take my frustration personally, you're a real asset to the company and clearly you've been given a hand-grenade of a release to work with, and all of the angry customers that come with it. Sorry for any misplaced angst, but please understand that this is our livelihood.
Thank you. As an editor with over 25 years of experience, I have been in your situation before and I do apologize for what you've been going through. It's not fun. I'll do my best to get this issue fixed ASAP.
Regards,
Kevin
