I'm scared. Someone hold me.

I have to update adobe (and other) software constantly as part of my QA work on Pr and really never have problems where a new version just won't work once it's publicly released. But our users have reported such occurrences here, so it's a legitimate fear. The difference is probably because I keep most of my testing environments clean of as much other clutter as a I can and restore back to 'clean' images regularly, especially before major updates. That's probably not realistic for most users though, and I agree with the more conventional wisdom that says never update in the middle of an important project or when you otherwise can't afford to troubleshoot some things, even if it's just feature design changes or other things that aren't necessarily bugs.

jstrawn wrote:

 

really never have problems where a new version just won't work once it's publicly released. But our users have reported such occurrences here, so it's a legitimate fear. The difference is probably because I keep most of my testing environments clean of as much other clutter as a I can...

Hah. I'm with Derjis on this one (though I do appreciate the even-handed tone). And it's not just plug-in incompatibilities etc. from a dirty system. Updating is a constant nailbiter for us, never knowing which bugs (yes, true bugs) are going to pop up and wreak havoc with our workflows. Like that time Premiere introduced random audio noise into crossfades on export. Or like how Speedgrade 2014 didn't launch on Retina MacBook Pros.

Derjis - I'm curious, have you made the jump? We're finally ready to expand our pilot station's 2014 version throughout the studio, but would love to know if you've encountered any issues. We're primarily Canon MXF too.

Thanks Derjis, sounds good.

I'm going to do it! Right now. Hmm. Or maybe on three. One, two... ok just a sec. Deep breath.....

@dergis

I think it is /was a good idea to do them one by one.

From anecdotal evidence...I would expect you will run into an issue on one or the other but hopefully not.

Let us all know how you get on. It will be helpful ( anecdotally) for other Mac usres.

Hi Derjis,

I'm not seeing many problems. Which forum are you speaking of? This one?

Thanks,

Kevin

Hi Derjis,

Thanks for the links. Looks like we have all those posts covered, so we don't know if these are actually issues affecting everyone yet. The last post has been solved already.

So far, most issues can be solved by updating video drivers and/or trashing preferences.

Thanks for your concern,

Kevin

Sounds good, Derjis. Though I encourage everyone to update, I fully understand if you don't want to jump in the pool at the first opportunity.

Thanks,
Kevin

1. Solved by updating graphics driver
2. Waiting to see if it's also a driver issue. Given that the user is on 10.8.5, which is a year old, I like the odds that a fresh driver will resolve the issue.
3. In the most recent post (Oct 6, 2014 11:59 AM), the user reports that he's not certain which version he's on.
4. Resolved by renaming folder. And this is not new to 2014.1

Having serious trouble with fresh created project and .mp4 files coming in with no audio. Renaming to .mov is a workaround but no solution.

H.264 Audio

No bashing i love the software and flexibility but i can understand people beeing scared about version 0.0 updates. I never would update with unfinished projects.

Hi K Mueller,

What happens if you change the name of the folder the media is in?

Thanks,

Kevin

Derjis wrote:

I've said it before, and I'll probably say it again, but Adobe seriously needs to have some sort of compensation system in place for customers to recoup money for lost/wasted time spent troubleshooting buggy releases. With a subscription model, we're all paying Adobe to provide us with a service (i.e. working software). If Adobe can't supply that service for a given period of time, our contracts should be extended --- if our boxes are down for a half-day while we try to figure out why AVCHD files don't work all of a sudden, then it's only fair that our contract be extended by a half-day.

That sounds like a reasonable request to me. I would say it seems fair to get a free month point product deduction if you have to waste half a day, but please don't quote me on that. It's mostly users and point product people in here with no way to design and enact such a policy. Have you tried sending the idea in to some official avenue of customer support, for example: Contact Customer Care

I can't think of any better places to send it, but if anyone can, please do tell. (CEO's personal # ? --- kidding, I don't have that, sad to say.) If I can find the proper channel internally, I'll submit the request for you myself.

As a start, is there some sort of public-facing bug tracker or continuously updated list of known issues? Something easier than poring over forum posts?