Hi Brian, Well, that depends on how you'd use the plug-in. For example, If you're checking out a master fader and want to be aware of approaching a certain threshold, you can take the dry (or input) signal down and pay more attention to the wet (or meter tone) sound. I'm not sure that the meter would be particularly useful during tracking, given that it produces a series of musical tones that may or may not be sonorous with the source material. As I've mentioned before, recording that close to 0 dB full scale is a novice mistake. Anyway, there's no right or wrong with the use of the meter although, if you do turn down the dry signal, you'll be turning down the output so that's something to consider. Slau
On Dec 10, 2015, at 3:30 PM, Brian Howerton <[email protected]> wrote: > Slap, > Thanks for the clarification. For that first dry parameter, would you > recommend keeping this all the way at 0? > Brian >> On Dec 10, 2015, at 3:14 PM, Slau Halatyn <[email protected]> wrote: >> >> While the "how it works" info on the page that Fiore linked to provides an >> explanation, I'll try to elaborate. Also, I will suggest a few things that >> Fiore might consider as tweaks to the nomenclature. >> >> Parameters: >> Master Bypass >> This is obvious and, if anyone needs further clarification… I'll refrain >> from commenting,lest I offend them. >> >> Dry >> this parameter is the level of the audio being input into the plug-in. If >> you keep this all the way at 0, the audio is passing through at the same >> level with no attenuation to the incoming signal. I believe this parameter >> should be renamed to something like Source Monitor Level. >> >> Dry >> This is the level of the meter's tone level. If you want just a tiny bit of >> feedback, keep this level low. If you want a louder signal just to warn you >> if you're coming close to your threshold, set it higher. I think this >> parameter would be better named something like Meter Monitor Level. >> >> Threshold >> this is the threshold for the meter's detection. It's more apparent how it >> works when you're in the Clipping mode. Threshold is straight-forward enough >> as a parameter name but perhaps "Meter Threshold" might help stress the fact >> that this is a threshold for the meter's behavior rather than any sort of >> threshold having to do with the audio itself. Users are conditioned to think >> of a threshold as being an active item that affects the incoming audio. In >> this case, the threshold does nothing to the incoming audio but rather sets >> the level that the meter is referencing for its behavior. >> >> Sonification Type >> Well, right at the outset, I'll say that "sonification" is a clumsy word. >> Essentially, the function of the plug-in is to notify or indicate the >> current level in relation to the incoming signal against the threshold >> setting. To me, it would be clearer to call this Indicator Type, either >> continuous or clipping. This control obviously simply switches between the >> two modes. >> >> Decay >> This is the decay of the meter's tone generator. I think it would be a >> little clearer to call it Meter Decay" or "Tone Decay" or something like >> that. >> >> Hope that helps, >> >> Slau >> >> >> On Dec 10, 2015, at 2:30 PM, Brian Howerton <[email protected]> wrote: >> >>> Thanks for explaining this. What are the other parameters in the plugin? I >>> believe they had something to do with the wet and dry mix? Not sure though >>> as I only had a quick look. Thanks, >>> Brian >>>> On Dec 10, 2015, at 1:59 PM, [email protected] wrote: >>>> >>>> Hi, >>>> >>>> thank you Slau for making it clear where to drop the plug-in >>>> I'll adjust the README with your instructions that seem to be more screen >>>> reader friendly >>>> >>>> As for how it works: >>>> >>>> You have to modes: clipping and continuous >>>> >>>> clipping mode : you set the threshold parameter and each time the audio >>>> signal goes past the threshold you'll hear a short beep. By default the >>>> threshold is set >>>> to 0db so you won't hear anything unless your audio is distorting. But if >>>> you're mixing and you want to keep, say, 6dB of headroom then just set it >>>> to -6dB and keep, >>>> >>>> The continuous mode just plays a continuous sine wave which is mapped to >>>> the audio level in dB. A possible usage of this mode is to understand if >>>> the >>>> dynamic range is high or low by listening to the sine wave. High dynamic >>>> range would result in a relevant change of the pitch of the sine wave, >>>> whereas a sine wave more or less stable around the same pitch would reveal >>>> a highly compressed sound. >>>> >>>> the modes can be switched with the Sonification Type parameter >>>> >>>> a more detailed description of the plug-in can be found at: >>>> http://depic.eecs.qmul.ac.uk/apm/howitworks.html >>>> >>>> >>>> >>>> On Thursday, December 10, 2015 at 6:06:20 PM UTC, Brian Howerton wrote: >>>> Ah, thanks for that Slau. That worked. The read me file was a little >>>> confusing maybe how voiceover was reading it even after interacting with >>>> the text to take a closer look at the file and folder path name. Anyway, >>>> got it, now just don’t understand how it works, definitely understand the >>>> concept but looking forward to seeing how it works with voiceover. Did >>>> find a little bug with it at least on my system and setup though. When >>>> interacting with the parameters, you can change them with voiceover, but >>>> if you want to change it back, you can’t just interact and VO up and down >>>> arrow to change it back to the previous setting. However, pressing VO >>>> space will reset it and change it back. Maybe it’s not a bug, but maybe >>>> that’s how you do it, but anyway that’s what I have noticed after having a >>>> quick look at it. >>>> Brian >>>> > On Dec 10, 2015, at 12:52 PM, Slau Halatyn <[email protected]> wrote: >>>> > >>>> > Hi Brian, >>>> > Open your boot up drive. Go to Library. Open the Application Support >>>> > folder. Go to Avid. Go to Audio then to plug-ins and paste it in there. >>>> > reboot Pro Tools and you should see it. >>>> > HTH, >>>> > Slau >>>> > >>>> > On Dec 10, 2015, at 12:47 PM, Brian Howerton <[email protected]> wrote: >>>> > >>>> >> Hello folks, >>>> >> I downloaded the accessible peak meter plugin for pro tools which was >>>> >> released today, and I have read the read me for the plugin, and I >>>> >> thought I put it in the right location, but it is not showing up in my >>>> >> plugins. Where exactly do we put it. I am running pro tools 12.3. >>>> >> Also, would really love to hear someone do an audio demo of this. I >>>> >> watched the youtube video, but there are a couple of things I don’t >>>> >> understand. They really did not show this in action so would love to >>>> >> hear how this thing works. Thanks, >>>> >> Brian >>>> >> >>>> >> -- >>>> >> 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. >> >> >> -- >> 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.
