Finally!! Tool section of the exact tool you want!

[Mark Norup]

Why is there no debate when some of us don't get the "bug"

[pezking]

I can't replicate what you're describing.

Maybe a video would show it to us?

[Drew Mazurek]

Originally Posted by Mark Norup

Why is there no debate when some of us don't get the "bug"

I never said bug.

But cycling through tools with the F keys, with no ability to "lock out" ones you never use, is a MAJOR workflow killer and that is what I was saying isn't debatable.

[Dizzi45Z]

Originally Posted by Mark Norup

Just tested the way you describe it.

At my system Pro Tools HD 8.0.1 it works the way you might expect it to work.. select tool - grab tool - trim tool... i've used the apple F4-3-2 shortcut
to enter the tools..

Maybe you wanna update ?

I also confirm that it works properly for me with 8.0.1 OS 10.5.8.

I do tons of audio editing for Books on CD and etc., and although I have had to cycle through the trimmer tools a few times (due to user error), I do this about once every two days or so, not 1000's of times a day.

But with that said. I think it is an excellent suggestion. It would be nice to be able to choose what tools you want available out of the trimmer tools in Preferences. Although I have used the loop tool a few times through sessions, I find it much faster and easier to use just duplicate the section.

[DigiTechSupt]

This is not a bug and the tools work as intended, however we do understand that this is a feature many people would like and we have this on our short list of features to be implemented.

[Chompers]

Once again. If this isnt a problem for you then no need to declare it.
Furthermore, it most likely will be a problem when you get faster at PT.

It is a horrible design BUG that effects EVERYONE!

Most people dont notice because they are very slow and deliberate.
Ive seen it effect users that dont even notice it.
There is no reason not to implement the idea!

PLEASE FIX IT !!

Pleae Please Please Please Please

[Chompers]

Originally Posted by DigiTechSupt

This is not a bug and the tools work as intended, however we do understand that this is a feature many people would like and we have this on our short list of features to be implemented.

Here is one from 2 years ago!!!

Originally Posted by DigiTechSupt

We hear you, loud and clear. This was one of those features that I'm pressing to get implemented because, as you said, it's a no brainer.

ANd there are more from longer ago.
Just cant seem to fix this...eh?

[DigiTechSupt]

Originally Posted by Chompers

Here is one from 2 years ago!!!






ANd there are more from longer ago.
Just cant seem to fix this...eh?

It's not a matter of 'fixing', since this IS NOT a bug. I hate to keep repeating that, but the tools function as defined. There's a big difference there in that functionality has to be redefined, written up into the engineering documents so they understand how the new functions are to be implemented, then a project has to be able to accept the engineering and testing time required to implement that functionality.

Given that most projects have a 1 year lead-time (if not more), this is something that just has not had a project with enough resources to tackle properly.

I'm not trying to downplay anything, just hoping to give some real-world, pragmatic info on why you haven't seen this change yet.

With THAT, as I've said, this is on the short-list and everything is being done to find a way to get this implemented as quickly as possible.

[Chompers]

Design flaw, not bug. I understand the difference.


It seems this would be alot easier to implement then say.. elastic audio, or any number of complex features that have been worked in to PT over the years.
Its been SO LONG!!!! Way over a year.

[DigiTechSupt]

Originally Posted by Chompers

Design flaw, not bug. I understand the difference.


It seems this would be alot easier to implement then say.. elastic audio, or any number of complex features that have been worked in to PT over the years.
Its been SO LONG!!!! Way over a year.

It's not a matter of ease of implementation. EA work was started 2 years before you saw it in Pro Tools, which is why I explaining how the process works.

Since being asked for this there just hasn't been a project that could take it in - adding it to any of them would push their release date by the amount of time it would take to implement this. Given that most of the work being done currently is for OS compatibility, timely releases are of critical importance.

Again, though, I'll stress that we're doing everything we can to implement this in the first available project that we can get it into.