Josh, I have sent you a PM

drbgaijin:

Hopefully your MC 4s can do the job required until we all see a more stable product to move on to, whether it be an upgrade of 5 or indeed a completely new version.
Time will tell.

The thing is that if "we" keep using MC4 then Avid will not generate enough income as we do not buy upgrades.

What is missing is adequate communication to ensure users the problems will be solved. Without putting the blame on him personally the communication of Frank Capria is not convincing me at this moment that we can see a turnaround in this patch process anytime soon.

I hope we can hear some good news soon from him.

My worst fear is that the change/loss in functionality of Option+C was intentional as it is not a standard OS type of command for copying to the clipboard.  All of the v5 changes we've seen to Control and Option combos were driven by adapting them to standard OS behavior.  

If Option+C no longer copies a section and places it in the Source monitor and the change was intentional, then what key combo will?  

I'm not particularly interested in talking about the next major version of MC when it seems as though Avid never did deliver a fully working MC 5. Some of you have mentioned the next version of MC as (possibly) the version that will fix all the failings of MC 5 - I've played this game of tag with other software products and I can tell you that it is most unsatisfying.

My confidence in Avid has absolutely been shaken by MC 5. Every indication points to a less than optimal development / test cycle. I have no reason to believe that this will change with the next major version release. I wonder how Avid will build confidence back into its install base.

Thank you all for your input, the problem has been identified and is in the process of being fixed.

 

To all the users expecting for a next to come after NAB bugfree release: why should I pay for bug fixes? With MC 5 I've already been charged for the CTRL key "improvements", the unfriendly so-called-smart-tools, and a plethora of minor bugs, which could be major bugs if they happen to interfere with Your workflow, I'd rather having what I already payed for in a fully working state instead of forgetting MC 5 and shopping for MC 6.

Thanks for letting us know, Josh.  :)

Carl

josh calvi:

Thank you all for your input, the problem has been identified and is in the process of being fixed.

 

Does this mean that we have to wait another month to get a fix and deal with the bug like we've had to with all of the other problems? Or is this a fix that is coming soon?

ramz434:

Does this mean that we have to wait another month to get a fix

 

Even if I knew I'm not sure I'd be at liberty to discuss such things.  Sorry, I understand your frustration but I don't make these decisions.

 

 

 

"Even if I knew I'm not sure I'd be at liberty to discuss such things"

That's strange... I can understand not discussing new release dates for major product upgrades... but, a patch? 

Can you imagine if other businesses ran their communication and flow of information this way to their customers...

I can see it now...

Mechanic fixing your car:  "I'd like to tell when the repairs on your new car will be done, but I am not a liberty to discuss such things..." {scratching head} 

That being said... it is good to see a response... and, that there is an acknowledgment.  Anything added beyond that would be nice...a godsend... or... freak of nature (take your pick).

 

Let's don't all start shooting the messenger.  I've sent Marianna an email to see if she can provide more info about this.

ciao,
Carl 

josh calvi:

ramz434:

Does this mean that we have to wait another month to get a fix

 

Even if I knew I'm not sure I'd be at liberty to discuss such things.  Sorry, I understand your frustration but I don't make these decisions.

 

Josh,

In light of the on going frustration experienced and expressed here (for awhile now) I really think you should pass along to the higher-ups that, in this case, an announced ETA for a new patch that is as close to immediate as possible would be a very good idea.

Avid has had a campaign going on where it promised to be more open and communicative and better test its products. Avid releasing this recent patch and not giving an ETA on a fix goes against just about everything we were told to put our faith in.

I understand that problems happen and that the patch did fix quite a bit. But Avid not willing to give an ETA on fixing a core feature that it just broke is very hard for me to get my head around.

I hope the decision makers reconsider their stance of non-communication.

 

P.S. I hope you don't read the above as being critical of you. And it's very much appreciated that you did post here.

I'm not sure this analogy works in this case since a mechanic's job is to restore the car to its original factory condition, or to how it was originally supposed to have worked. Avid is constantly evolving as a product; constantly being reinvented. It's harder to predict the time frame of reconception than of repair.

BobbyMurcerFan:

 

Josh,

In light of the on going frustration experienced and expressed here (for awhile now) I really think you should pass along to the higher-ups that, in this case, an announced ETA for a new patch that is as close to immediate as possible would be a very good idea.

 

 

I'll pass it along.  FWIW this issue landed in my inbox via the "higher-ups".

Allow me to clarify; I'm not the person who decides when things ship.  Therefore it is not appropriate for me to make such comments.  If I get any information that I can pass along, I will do so.

Thank you very much. It really is much appreciated.