opie177:

I really dont WANT to... but I feel I may have to until a solution is offered! Just to keep my sanity.

Take a deep breath and relax.  Give it a try before you "have" to go back to v4.  Many of the bugs have been fixed.  Now it's about workflow preferences that have been changed.

this escalated rather quickly

I still think that as a clean install of MC 5 results in most of the "new" stuff being ON by default the readme SHOULD have a PROMINENT section for existing users on how to turn off as much of the "new UI features" as is posible before they start using MC5.

A great deal of the UI can NOW be made to work as an existing MC user would expect but each person has to first have a bad experiences and then discover for themselves how to get productive again.

AndrewAction:

I still think that as a clean install of MC 5 results in most of the "new" stuff being ON by default the readme SHOULD have a PROMINENT section for existing users on how to turn off as much of the "new UI features" as is posible before they start using MC5.

A great deal of the UI can NOW be made to work as an existing MC user would expect but each person has to first have a bad experiences and then discover for themselves how to get productive again.

That's a great idea!

AndrewAction:

{snip}

A great deal of the UI can NOW be made to work as an existing MC user would expect but each person has to first have a bad experiences and then discover for themselves how to get productive again.

When you say now... do you mean since the MC5.0.3 version?  Or, was this ability always there since 5.0... what is strange is that... I can't think of one AVID rep that has mention this option (or anyone for that matter).

Joe:

For example, the theory is that in MC5 if you enable the settings option "clicking TC ruler disables Smart Tool", and if you map the segment yellow and red edit modes and the audio keyframer to buttons or the keyboard, the timeline behaves exactly as it did in MC 4 and earlier. And that is indeed true, because that's what I have done. The fly in the ointment is the fact that the smart tool randomly re-enables itself, forcing you to consciously and continuously keep an eye on it, which is distracting to the creative process. That's the main reason we are asking for an "on/off" switch.

Joe M:

I can't think of one AVID rep that has mention this option

Yes, and these are the same re-sellers that touted AMA as "just plug a drive in and edit" without explaining all the variances that each codec, machine, etc could have on AMA performance...

OK... then perhaps Andrew may have overstated the idea of disabling portions of the UI... or, I read it wrong.

Joe M:

overstated the idea of disabling portions of the UI.

IMO this info is currently scattered all over the place and easy to miss. Again IMO it should all be in one easily accesible place. The readme seems the most obvious choice but a KB item would also work.

Admittedly this may reak of being a "hindsight is 20 20" but it comes from reverse engineering my opinion that if something, destructive to existing users workflows like the Smart Tool, was introduced in the future, Avid would have all of this new "Xxxxx Tools" settings defaulted to OFF. Then document how to turn it on and what turning it on achieves.

AndrewAction:

Admittedly this may reak of being a "hindsight is 20 20" but it comes from reverse engineering my opinion that if something, destructive to existing users workflows like the Smart Tool, was introduced in the future, Avid would have all of this new "Xxxxx Tools" settings defaulted to OFF. Then document how to turn it on and what turning it on achieves.

They won't do this because they don't think the new "features" are "destructive to existing users workflows," or else why would they have introduced them?  Playing devil's advocate for a sec, if they were to do this it would be an admission that the new "features" have failed.  You don't have to turn on any other features to get them to work (i.e. AMA, ScriptSync, Mix & Match, etc).  

ciao,
Carl 

camoscato:

You don't have to turn on any other features to get them to work (i.e. AMA, ScriptSync, Mix & Match, etc).  

True, but in the case of AMA, we do have a master enable/disable switch.

Larry Rubin:

Joe:

For example, the theory is that in MC5 if you enable the settings option "clicking TC ruler disables Smart Tool", and if you map the segment yellow and red edit modes and the audio keyframer to buttons or the keyboard, the timeline behaves exactly as it did in MC 4 and earlier. And that is indeed true, because that's what I have done. The fly in the ointment is the fact that the smart tool randomly re-enables itself, forcing you to consciously and continuously keep an eye on it, which is distracting to the creative process. That's the main reason we are asking for an "on/off" switch.

As a convert to MC5 from Liquid, I am probably one of the type of editor that the smart tool is aimed at, and I like the way it works.

Of course I understand that other may not, but given that it didn't randomly turn itself back on, I'd have thought those that don't like it could turn it off.  Therefore I think that the engineers need to comoplete the task of making the Smart Tools work correctly as designed.

Then that issue would be closed?

camoscato:

AndrewAction:

Admittedly this may reak of being a "hindsight is 20 20" but it comes from reverse engineering my opinion that if something, destructive to existing users workflows like the Smart Tool, was introduced in the future, Avid would have all of this new "Xxxxx Tools" settings defaulted to OFF. Then document how to turn it on and what turning it on achieves.

They won't do this because they don't think the new "features" are "destructive to existing users workflows," or else why would they have introduced them?  Playing devil's advocate for a sec, if they were to do this it would be an admission that the new "features" have failed.

This is one of the main points here, Avid not admitting the mistake(s) with MC 5, here is a quote from the second post in this discussion

Larry Rubin:

Instead of taking our feedback on the interface settings to heart, they are stubbornly digging in their defensive heels, trying to justify the unjustifiable.

SussexJohn:

I think that the engineers need to comoplete the task of making the Smart Tools work correctly as designed.

Then that issue would be closed?

John, the thread is humonguos, but to summarize, we not only complain about the not-so-smart tool, but because of the CTRL key behaviour changes, the restrictions on the GUI customizability and other amenities, so just fixing the the not-so-smart tool won't be enough to close the issue.

luca.mg:

SussexJohn:

I think that the engineers need to comoplete the task of making the Smart Tools work correctly as designed.

Then that issue would be closed?

John, the thread is humonguos, but to summarize, we not only complain about the not-so-smart tool, but because of the CTRL key behaviour changes, the restrictions on the GUI customizability and other amenities, so just fixing the the not-so-smart tool won't be enough to close the issue.

I was refering only to the ST issue being closed