Sure, this is what I do at the moment because it works across DAWs. Takes double the amount of time though for each pass, so thought it was worth asking.
Scott On 3/24/15, Chris Smart <[email protected]> wrote: > oh cool. I had no idea! Thanks for that. > > Of course, you can always find the loudest section of the song, loop > part of it, and read the track or bus meter peaks with compression > engaged then bypassed. > > At 11:26 AM 3/24/2015, you wrote: >>Yes, in the sonnets compressor, if you pressed f2, it would read you >>the input, output, and gain reduction meters. >>Brian >> > On Mar 24, 2015, at 10:46 AM, Chris Smart <[email protected]> wrote: >> > >> > really? I've never noticed that. Can you remember what keystroke you >> > used? >> > I'm asuming you're talking about the Sonitus compressor. >> > >> > >> > At 08:18 AM 3/24/2015, you wrote: >> >> Hi Scott, >> >> I used to use the Cakewalk Sonar package from Dancing dots with >> the CakeTalking scripts for Jaws. You could read the gain >> reduction meters in that compressor that came with Sonar. Thanks, >> >> Brian >> >> > On Mar 23, 2015, at 2:39 PM, Scott Chesworth >> <[email protected]> wrote: >> >> > >> >> > Hi Brian, >> >> > >> >> > I see your question has already been answered, but it raises another >> >> > one. The way its phrased suggests that you can read gain reduction >> >> > with your current setup. I'm curious about what you're using, just >> >> > because in both of my regular DAWs it isn't doable. Feel free to >> >> > drop >> >> > me a line off list so we don't stray off topic. >> >> > >> >> > Cheers >> >> > >> >> > Scott >> >> > >> >> > On 3/23/15, Brian Howerton <[email protected]> wrote: >> >> >> How agre folks getting around not being able to read gain >> reduction meters >> >> >> in pt? >> >> >> >> >> >> Sent from my iPhone >> >> >> >> >> >>> On Mar 23, 2015, at 8:50 AM, David Eagle >> >> >>> <[email protected]> >> >> >>> wrote: >> >> >>> >> >> >>> Yes, being able to adjust slider values in larger increments would >> >> >>> be >> >> >>> massively helpful. And gain reduction feedback in >> compressors too. I'm a >> >> >>> bit unsure what happens when you increase the volume on a >> track. If you >> >> >>> have a compressor insert on that track, does the volume >> adjustment affect >> >> >>> the level before or after the compressor? In sonar there was >> a trim and a >> >> >>> volume option. >> >> >>> Thanks aplenty Slau. >> >> >>> >> >> >>> Sent from my iPhone >> >> >>> >> >> >>>> On 23 Mar 2015, at 12:18, studiojay >> >> >>>> <[email protected]> >> >> >>>> wrote: >> >> >>>> >> >> >>>> Hi Slau, Thanks again for every thing you are doing. My >> input. I agree >> >> >>>> with Gord, it would be cool to change plugin values in >> larger increments. >> >> >>>> Also, it would be nice to be able to read gain reduction meters >> >> >>>> in >> >> >>>> compressor plugins both stock and 3rd party. Also, there are 2 >> >> >>>> popup >> >> >>>> menus in the select-split notes dialog that do not work >> with voiceover. >> >> >>>> This dialog is accessed with option y. Regards, Jason >> >> >>>> >> >> >>>>> On Monday, March 23, 2015 at 1:53:01 AM UTC-4, Gord wrote: >> >> >>>>> Is there any hope for >> structure? That is an >> >> >>>>> >> >> >>>>> Avid virtual instrument, isn't it? Also, it would be nice >> to be able to >> >> >>>>> >> >> >>>>> adjust some parameter sliders in larger increments, or to >> type in values >> >> >>>>> >> >> >>>>> directly. >> >> >>>>> Keep up the good work Slau! >> >> >>>>> Gord >> >> >>>>> >> >> >>>>> -----Original Message----- >> >> >>>>> From: Slau Halatyn >> >> >>>>> Sent: Sunday, March 22, 2015 6:58 PM >> >> >>>>> To: [email protected] >> >> >>>>> Subject: Re: feedback needed for Pro Tools 12 >> >> >>>>> >> >> >>>>> Hi John, >> >> >>>>> >> >> >>>>> Yep, you might have missed the previous reply. Click is >> definitely an >> >> >>>>> issue >> >> >>>>> that needs to be resolved. For now, all of the parameters >> are accessible >> >> >>>>> via >> >> >>>>> a control surface. For those who don't have a surface, >> I'll see if I can >> >> >>>>> >> >> >>>>> come up with a number of presets to help in the mean time. >> I'm leaving >> >> >>>>> town >> >> >>>>> this week and will be gone for 2 weeks so it'll be a while. >> >> >>>>> >> >> >>>>> The status of the Input monitor button is identified by its >> >> >>>>> name. >> >> >>>>> VoiceOver >> >> >>>>> indicates when it's engaged but not when it's not engaged. In >> >> >>>>> other >> >> >>>>> words, >> >> >>>>> much like a mute button that is off, you'll only hear the >> name of the >> >> >>>>> button >> >> >>>>> as opposed to hearing that it's in its "on" state. >> >> >>>>> >> >> >>>>> Hope that helps. >> >> >>>>> >> >> >>>>> best, >> >> >>>>> >> >> >>>>> Slau >> >> >>>>> >> >> >>>>> On Mar 22, 2015, at 5:17 PM, John Gunn <[email protected]> wrote: >> >> >>>>> >> >> >>>>>> Hello Slau, >> >> >>>>>> >> >> >>>>>> Great you are meeting with a programmer and here are a couple >> >> >>>>>> of >> >> >>>>>> things I >> >> >>>>>> have. >> >> >>>>>> >> >> >>>>>> First when selecting a click sound other then the default >> click, I am >> >> >>>>>> >> >> >>>>>> unable to choose for example cowbell, stick ETC. This of course >> >> >>>>>> is >> >> >>>>>> setting up a click track. >> >> >>>>>> >> >> >>>>>> Secondly and this might be user error on my part but is there a >> >> >>>>>> way >> >> >>>>>> finding the status of a track if it is set to input >> monitor? Tryied >> >> >>>>>> to >> >> >>>>>> bounce a session last week and message unable to bounce because >> >> >>>>>> of >> >> >>>>>> input >> >> >>>>>> monitor. >> >> >>>>>> >> >> >>>>>> Feel free to let me know if I am way off base on any of >> my feedback. >> >> >>>>>> >> >> >>>>>> John >> >> >>>>>> >> >> >>>>>> >> >> >>>>>>> On Mar 16, 2015, at 9:41 AM, Slau Halatyn >> <[email protected]> wrote: >> >> >>>>>>> >> >> >>>>>>> >> >> >>>>>>> In a couple of weeks, I'm going to have a unique >> opportunity to sit >> >> >>>>>>> down >> >> >>>>>>> with a programmer to work on some accessibility issues >> in Pro Tools. >> >> >>>>>>> >> >> >>>>>>> Under the circumstances of my trip, Avid has allowed for >> this meeting >> >> >>>>>>> to >> >> >>>>>>> be scheduled barring any last minute crisis with the >> release of Pro >> >> >>>>>>> Tools >> >> >>>>>>> 12. This will be largely driven by bug submissions >> already within the >> >> >>>>>>> >> >> >>>>>>> beta system but I wanted to get a sense of what the user base >> >> >>>>>>> is >> >> >>>>>>> focused >> >> >>>>>>> on day to day. My goal is to address quality-of-life issues >> >> >>>>>>> that >> >> >>>>>>> affect >> >> >>>>>>> the use of Pro Tools with VoiceOver. For example, the >> way the inserts >> >> >>>>>>> >> >> >>>>>>> and, in particular, sends are displayed is simply awful. >> This needs >> >> >>>>>>> to be >> >> >>>>>>> overhauled. There are a number of such issues that can >> hopefully be >> >> >>>>>>> taken >> >> >>>>>>> care of in one marathon session of tweaks. >> >> >>>>>>> >> >> >>>>>>> I have a clear idea of what I personally think should be >> >> >>>>>>> addressed >> >> >>>>>>> but I >> >> >>>>>>> thought I'd take the temperature of the community. What >> I'm asking of >> >> >>>>>>> the >> >> >>>>>>> list is for people to enumerate 3 to 5 things that most >> affect their >> >> >>>>>>> >> >> >>>>>>> productivity and would like to see improved. Now, I don't mean >> >> >>>>>>> for >> >> >>>>>>> people >> >> >>>>>>> to suggest a different method for importing files to an >> >> >>>>>>> existing >> >> >>>>>>> track. >> >> >>>>>>> That's a bigger fish to fry and the subject of a longer term >> >> >>>>>>> solution. >> >> >>>>>>> These are, as I said, quality-of-life issues that can be >> >> >>>>>>> addressed >> >> >>>>>>> quickly. Also, don't bring up issues in version 10. We're >> >> >>>>>>> talking >> >> >>>>>>> existing issues in version 11. Give me your top 3 or top >> 5 items and >> >> >>>>>>> >> >> >>>>>>> we'll see which seem to reveal themselves as the biggest >> >> >>>>>>> concerns. >> >> >>>>>>> The >> >> >>>>>>> sooner you get those to me, the sooner I can prepare. >> >> >>>>>>> >> >> >>>>>>> Thanks, >> >> >>>>>>> >> >> >>>>>>> Slau >> >> >>>>>>> >> >> >>>>>>> -- >> >> >>>>>>> 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. >> >> >> >> -- >> >> 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.
