In the Metering tab of Preferences. There's a cluster for Peak and Clip settings.
On Sep 2, 2015, at 11:58 PM, Christopher Gilland <[email protected]> wrote: > OK. right now, my meter is set to hold infinent. Can you please refresh my > memory where in the preferences we need to go to change that over to the 3 > second hold instead? > > Chris. > >> On Sep 2, 2015, at 11:11 PM, Slau Halatyn <[email protected]> wrote: >> >> The table, in this case, is not technically a table, per se, but was >> unfortunately defined as a table. What sighted users see is a numeric >> display below the volume fader. Keep in mind that the actual fader in the >> Mix window has no number associated with it because it's just a fader, much >> like a physical fader on a console. The fact that VoiceOver users have a >> value attached to the fader is purely because that decision was made when >> the fader was made accessible. Sighted users see a number below the fader >> and that is the current position of the fader based on nominal level or 0 >> dB. Much like the same control in the Edit window's track display, this >> number can be Command-clicked and it would cycle between volume (or fader >> level), delay (meaning delay incurred from instantiated plug-ins) and peak >> (the highest level achieved in either input or playback. A sighted user can >> also click and hold on that number and a little fader pops up and the fader >> can be adjusted from that little pop-up fader. The delay value can't be >> adjusted unless a plug-in is eliminated or added. In other words, it's not >> user-definable but rather an indicator. The peak can be reset by clicking >> once on it. >> >> So, there's no difference between the two volume faders in the channel other >> than the fact that, apparently, the second volume fader, the one in the >> table, can be adjusted by a tenth of a decibel rather than a half of a >> decibel. >> >> So, forget about the delay because it really doesn't matter if you're using >> delay compensation. Further, this table has already been eliminated from the >> subsequent version of Pro Tools so things will look just a little different >> and work just like a sighted user would use it. Command-clicking on the >> second volume display will toggle between the three values. That said, the >> peak value will always be displayed on its own as a separate element and the >> delay values can be shown or hidden from the View menu. The reason for all >> these options for sighted users is because of all of the various ways that >> things can be hidden or shown so it's fairly customizable. Don't worry about >> the table too much but I'd get used to setting the level meter to display a >> three-second hold on levels. This way, you can get a sense for the dynamics >> while still having a more accurate reading on peaks. >> >> HTH, >> >> Slau >> >> On Sep 2, 2015, at 4:08 PM, Christopher-Mark Gilland <[email protected]> >> wrote: >> >>> OK, so I'm going back in more detail listenning now to Slau's recording he >>> did on the 12.2 accessibility improvements. I confess that until now, I >>> really didn't listen much to it, as I was honestly waiting for the update, >>> which I now have gotten. >>> >>> I'm sort a not getting something though. At one point in the recording, >>> Slau talks about this new table that you have within your track channel >>> strip in the mix window. In here he talks about the three aspects of this >>> table. You have apparently the peek, which makes total sense to me, but >>> I'm not quite understanding first of all, the delay. I'm not getting the >>> difference in the peek vs. the delay. >>> >>> Finally, there was the fader, which Slau demonstrates that you even can >>> move. So, what would be the reason for moving the fader inside that table >>> instead of just vo+right arrowing over to the volume up down slider which >>> by default is at 0DB unless you change it? Does one fader act differently >>> there than the other one? >>> >>> I'm sorry. I just need a little clarification, as I'm a little confused. >>> Slau, you did a great job at explaining this. Don't worry. It's not you. >>> It's probably just me having one of those logical senior moments, and >>> that's really a bad thing seeing I'm only 33. LOL! >>> >>> Chris. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Pro Tools Accessibility" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Pro Tools Accessibility" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
