Re: Reading input/output levels in a plug-in
Sure, every bit helps :) > On Apr 6, 2017, at 5:01 PM, John André Lium-Netland > wrote: > > Hi Slau, I see your point. However, if AVID was able to do this for their > stock plugins, at least for EQ3 and compressor, it would help a lot. ;) > > > Best, > John André > > -- > 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 ptaccess+unsubscr...@googlegroups.com. > 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Reading input/output levels in a plug-in
Hi Slau, I see your point. However, if AVID was able to do this for their stock plugins, at least for EQ3 and compressor, it would help a lot. ;) Best, John André -- 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Reading input/output levels in a plug-in
The idea of a new interface for plug-ins was brought up in the past and it would put even more responsibility on plug-in developers to jump through an extra hoop which, sounds reasonable to us but has proven to be a challenge at best. That doesn't mean it couldn't happen but one has to consider the plug-in eco system and where it might be headed in 5 years rather than a year. The issue has to be addressed from a broader perspective which takes longer and involves higher level strategy, etc. Beyond that, the issue of plug-in level meters is just one of many fish to fry, some of which are arguably more critical and have more of an impact on users. Naturally, we want it all and we won't get it all but we've gotten a lot and we'll continue to get more over time. It'll get better :) Slau > On Apr 6, 2017, at 10:08 AM, John Covici wrote: > > Maybe you should bring up a case with Avid, if several people do this, > maybe they can fix -- just an idea. > > On Thu, 06 Apr 2017 09:55:07 -0400, > Slau Halatyn wrote: >> >> Hi John Andre, >> Unfortunately, individual level meters are not readable in any plug-in >> windows. As it's not an automation parameter, the standard method of >> accessing information doesn't apply. It's the kind of thing where each >> input, output, gain reduction meter, etc. would have to be made accessible >> for each plug-in—not likely to happen any time soon but anything can happen >> eventually :) >> Best, >> Slau >> >>> On Apr 5, 2017, at 10:17 PM, John André Lium-Netland >>> wrote: >>> >>> Hi, >>> >>> When working with stock plugins like EQ3 or a Compressor, is there an >>> accessible way to read the input and output meter level in the plugin, to >>> make sure they are the same? Of course, I would like the ability to have >>> the output level automatically set to the same as the input signal, but >>> such a feature is unfortunately not found in these plugins. So if >>> VoiceOver could read out the values, it would help… Yes, I know I can A/B >>> test the audio with the bypass button, but I would like an alternative way >>> to do this… ;) >>> >>> Also, I would like to be able to read gain reduction values for a specific >>> compressor plugin, since I assume this is also shown visually in the plugin >>> window. Is this possible? Yes, I can trust the values shown for the track >>> gain reduction, but this will only work if you only have one compressor or >>> limiter on the track. >>> >>> Best, >>> John André >>> >>> -- >>> 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 ptaccess+unsubscr...@googlegroups.com. >>> 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 ptaccess+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici > cov...@ccs.covici.com > > -- > 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 ptaccess+unsubscr...@googlegroups.com. > 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Reading input/output levels in a plug-in
Maybe you should bring up a case with Avid, if several people do this, maybe they can fix -- just an idea. On Thu, 06 Apr 2017 09:55:07 -0400, Slau Halatyn wrote: > > Hi John Andre, > Unfortunately, individual level meters are not readable in any plug-in > windows. As it's not an automation parameter, the standard method of > accessing information doesn't apply. It's the kind of thing where each input, > output, gain reduction meter, etc. would have to be made accessible for each > plug-in—not likely to happen any time soon but anything can happen eventually > :) > Best, > Slau > > > On Apr 5, 2017, at 10:17 PM, John André Lium-Netland > > wrote: > > > > Hi, > > > > When working with stock plugins like EQ3 or a Compressor, is there an > > accessible way to read the input and output meter level in the plugin, to > > make sure they are the same? Of course, I would like the ability to have > > the output level automatically set to the same as the input signal, but > > such a feature is unfortunately not found in these plugins. So if > > VoiceOver could read out the values, it would help… Yes, I know I can A/B > > test the audio with the bypass button, but I would like an alternative way > > to do this… ;) > > > > Also, I would like to be able to read gain reduction values for a specific > > compressor plugin, since I assume this is also shown visually in the plugin > > window. Is this possible? Yes, I can trust the values shown for the track > > gain reduction, but this will only work if you only have one compressor or > > limiter on the track. > > > > Best, > > John André > > > > -- > > 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 ptaccess+unsubscr...@googlegroups.com. > > 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 ptaccess+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com -- 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Reading input/output levels in a plug-in
Hi John Andre, Unfortunately, individual level meters are not readable in any plug-in windows. As it's not an automation parameter, the standard method of accessing information doesn't apply. It's the kind of thing where each input, output, gain reduction meter, etc. would have to be made accessible for each plug-in—not likely to happen any time soon but anything can happen eventually :) Best, Slau > On Apr 5, 2017, at 10:17 PM, John André Lium-Netland > wrote: > > Hi, > > When working with stock plugins like EQ3 or a Compressor, is there an > accessible way to read the input and output meter level in the plugin, to > make sure they are the same? Of course, I would like the ability to have the > output level automatically set to the same as the input signal, but such a > feature is unfortunately not found in these plugins. So if VoiceOver could > read out the values, it would help… Yes, I know I can A/B test the audio with > the bypass button, but I would like an alternative way to do this… ;) > > Also, I would like to be able to read gain reduction values for a specific > compressor plugin, since I assume this is also shown visually in the plugin > window. Is this possible? Yes, I can trust the values shown for the track > gain reduction, but this will only work if you only have one compressor or > limiter on the track. > > Best, > John André > > -- > 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 ptaccess+unsubscr...@googlegroups.com. > 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: Flo tools has changed certain behaviours since upgrading to latest PT and OS version
Hi Chuck! I had it under El and Yose... Don't know why. Maybe a German OS thing. But it's gone. :-) Best! / Martin > -Original Message- > From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] > On Behalf Of CHUCK REICHEL > Sent: Thursday, April 6, 2017 2:02 PM > To: ptaccess@googlegroups.com > Subject: Re: Flo tools has changed certain behaviours since upgrading to > latest PT and OS version > > Hi Martin, > Never had that issue in El Capitan! > Use that command every session! > Strange. :) > Talk soon > Chuck > > On Apr 6, 2017, at 6:45 AM, Martin (Punky) Sopart wrote: > > > Hi! > > > > The best on Sierra regarding Pro Tools is that you finally are abel to go > > to a > tables top or end by VO+Home / VO+End. > > In older versions of OS X VoiceOver very often froze when e.g. trying to go > to the top in the MIDI event list or track list. > > > > Best! / Martin > >> -Original Message- > >> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] > >> On Behalf Of Steve Sparrow > >> Sent: Thursday, April 6, 2017 12:50 AM > >> To: 'Joy Bausch' via Pro Tools Accessibility > >> Subject: Re: Flo tools has changed certain behaviours since upgrading to > >> latest PT and OS version > >> > >> if i could also ask a question here. I have not yet upgraded to sierra as > >> yet, > >> still running yousemeties. it seems fine. are there any benefits to > upgrading > >> to sierra when running protools or am i better to stay with yousemeties. I > >> know we have serie on sierra but i wouldn’t think i’d need that in the > studio. > >> does anything run more efficiently with sierra. > >> Steve > >>> On 6 Apr 2017, at 12:55 am, Brian@Wavefield Recordings > >> wrote: > >>> > >>> Ah crap sorry Slau, I had a fear that some of this was already out > >>> there, I must get a better system for searching/archiving list posts > >>> going. > >>> > >>> Thanks as usual and apologies for going over old ground, > >>> > >>> Preparing to learn to live in acceptance of the bugs, > >>> Brian. > >>> > >>> On 4/5/17, Slau Halatyn wrote: > Hi Brian, > This is the issue with VoiceOver and sierra that was discussed last year. > Apple is aware of the issue and there are other focus issues with > >> VoiceOver > in Sierra. Yes, it is annoying that focus has sort of a "ghost > remembrance" > of what was previously in focus. There's no specific work-around > except > that, if you use the Inspector to bring up, say, the plug-in window > rather > than interacting, focus goes back to the track you were on before > opening > the plug-in window. > > As far as hot spots go, you need to make sure that the hot spot is set to > the table itself rather than a focused track, of course. Also, you might > have to reset a hot spot since the OS update. I'm not sure if voiceOver > focus in general has changed somewhat in Sierra but it might be worth > resetting the hotspot. Incidentally, you can simply press > Control+Option+j > to jump to the track list table and you should automatically be placed > on > the first selected track. > > HTH, > Slau > > > On Apr 5, 2017, at 10:33 AM, Brian@Wavefield Recordings > > wrote: > > > > Hi all, > > > > So as the subject explains I updated my second machine to test out > how > > things would work with the latest OS and latest PT version. > > > > I've been mixing on the go this week and am a bit frustrated to find > > that the following things have changed which greatly slow down my > > workflow, so far I think these may be the only issues to pop up. > > > > Firstly, when using the command option W key stroke to close plugin > > windows, Voice Over jumps focus back to the top of the mix window > i.e. > > the left as you arrow with voice over, where as before closing the > > window would land me back on the name of the track I was working > on, > > which I believe is the proper behaviour. > > > > Further more when I arrow back over from the top of the mix window > to > > get back to the track I was working on it will sometimes randomly > > arrive into the insert section of the track I was working on as I pass > > by, as though it kind of half remembers I had been working on that > > track or something. A bit strange and laborious. > > > > Secondly, a small detail but a little annoying, I always set hot spot > > 5 to the trackless table for speed of track selection and such, but it > > used to automatically interact with he trackless table, now I have to > > manually interact with the track list table after I jump to the hot > > spots, not a major deal but its an extra key stroke in my work flow > > that used to be unnecessary. > > > > I haven't really tried solving these issues beyond running the > > installer for flo tools again and have not yet had ti
Re: Flo tools has changed certain behaviours since upgrading to latest PT and OS version
Hi Martin, Never had that issue in El Capitan! Use that command every session! Strange. :) Talk soon Chuck On Apr 6, 2017, at 6:45 AM, Martin (Punky) Sopart wrote: > Hi! > > The best on Sierra regarding Pro Tools is that you finally are abel to go to > a tables top or end by VO+Home / VO+End. > In older versions of OS X VoiceOver very often froze when e.g. trying to go > to the top in the MIDI event list or track list. > > Best! / Martin >> -Original Message- >> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] >> On Behalf Of Steve Sparrow >> Sent: Thursday, April 6, 2017 12:50 AM >> To: 'Joy Bausch' via Pro Tools Accessibility >> Subject: Re: Flo tools has changed certain behaviours since upgrading to >> latest PT and OS version >> >> if i could also ask a question here. I have not yet upgraded to sierra as >> yet, >> still running yousemeties. it seems fine. are there any benefits to upgrading >> to sierra when running protools or am i better to stay with yousemeties. I >> know we have serie on sierra but i wouldn’t think i’d need that in the >> studio. >> does anything run more efficiently with sierra. >> Steve >>> On 6 Apr 2017, at 12:55 am, Brian@Wavefield Recordings >> wrote: >>> >>> Ah crap sorry Slau, I had a fear that some of this was already out >>> there, I must get a better system for searching/archiving list posts >>> going. >>> >>> Thanks as usual and apologies for going over old ground, >>> >>> Preparing to learn to live in acceptance of the bugs, >>> Brian. >>> >>> On 4/5/17, Slau Halatyn wrote: Hi Brian, This is the issue with VoiceOver and sierra that was discussed last year. Apple is aware of the issue and there are other focus issues with >> VoiceOver in Sierra. Yes, it is annoying that focus has sort of a "ghost remembrance" of what was previously in focus. There's no specific work-around except that, if you use the Inspector to bring up, say, the plug-in window rather than interacting, focus goes back to the track you were on before opening the plug-in window. As far as hot spots go, you need to make sure that the hot spot is set to the table itself rather than a focused track, of course. Also, you might have to reset a hot spot since the OS update. I'm not sure if voiceOver focus in general has changed somewhat in Sierra but it might be worth resetting the hotspot. Incidentally, you can simply press Control+Option+j to jump to the track list table and you should automatically be placed on the first selected track. HTH, Slau > On Apr 5, 2017, at 10:33 AM, Brian@Wavefield Recordings > wrote: > > Hi all, > > So as the subject explains I updated my second machine to test out how > things would work with the latest OS and latest PT version. > > I've been mixing on the go this week and am a bit frustrated to find > that the following things have changed which greatly slow down my > workflow, so far I think these may be the only issues to pop up. > > Firstly, when using the command option W key stroke to close plugin > windows, Voice Over jumps focus back to the top of the mix window i.e. > the left as you arrow with voice over, where as before closing the > window would land me back on the name of the track I was working on, > which I believe is the proper behaviour. > > Further more when I arrow back over from the top of the mix window to > get back to the track I was working on it will sometimes randomly > arrive into the insert section of the track I was working on as I pass > by, as though it kind of half remembers I had been working on that > track or something. A bit strange and laborious. > > Secondly, a small detail but a little annoying, I always set hot spot > 5 to the trackless table for speed of track selection and such, but it > used to automatically interact with he trackless table, now I have to > manually interact with the track list table after I jump to the hot > spots, not a major deal but its an extra key stroke in my work flow > that used to be unnecessary. > > I haven't really tried solving these issues beyond running the > installer for flo tools again and have not yet had time to start from > a clean PT session to see if the problems still occur. > > My main studio machine is still on Yosemite and as some of you may > recall, I couldn't check the box to let voice over be controlled by > apple script, so there fore couldn't install flo tools, so given the > change in behaviour of flo tools after upgrading my second machine, > I'm a little hesitant to do the same to my main machine just to get > flo tools up and running in case anything else goes wrong. > > Any ideas would be greatly appreciated as always and hopefully I > managed to get th
RE: Flo tools has changed certain behaviours since upgrading to latest PT and OS version
Hi! The best on Sierra regarding Pro Tools is that you finally are abel to go to a tables top or end by VO+Home / VO+End. In older versions of OS X VoiceOver very often froze when e.g. trying to go to the top in the MIDI event list or track list. Best! / Martin > -Original Message- > From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] > On Behalf Of Steve Sparrow > Sent: Thursday, April 6, 2017 12:50 AM > To: 'Joy Bausch' via Pro Tools Accessibility > Subject: Re: Flo tools has changed certain behaviours since upgrading to > latest PT and OS version > > if i could also ask a question here. I have not yet upgraded to sierra as > yet, > still running yousemeties. it seems fine. are there any benefits to upgrading > to sierra when running protools or am i better to stay with yousemeties. I > know we have serie on sierra but i wouldn’t think i’d need that in the > studio. > does anything run more efficiently with sierra. > Steve > > On 6 Apr 2017, at 12:55 am, Brian@Wavefield Recordings > wrote: > > > > Ah crap sorry Slau, I had a fear that some of this was already out > > there, I must get a better system for searching/archiving list posts > > going. > > > > Thanks as usual and apologies for going over old ground, > > > > Preparing to learn to live in acceptance of the bugs, > > Brian. > > > > On 4/5/17, Slau Halatyn wrote: > >> Hi Brian, > >> This is the issue with VoiceOver and sierra that was discussed last year. > >> Apple is aware of the issue and there are other focus issues with > VoiceOver > >> in Sierra. Yes, it is annoying that focus has sort of a "ghost remembrance" > >> of what was previously in focus. There's no specific work-around except > >> that, if you use the Inspector to bring up, say, the plug-in window rather > >> than interacting, focus goes back to the track you were on before opening > >> the plug-in window. > >> > >> As far as hot spots go, you need to make sure that the hot spot is set to > >> the table itself rather than a focused track, of course. Also, you might > >> have to reset a hot spot since the OS update. I'm not sure if voiceOver > >> focus in general has changed somewhat in Sierra but it might be worth > >> resetting the hotspot. Incidentally, you can simply press Control+Option+j > >> to jump to the track list table and you should automatically be placed on > >> the first selected track. > >> > >> HTH, > >> Slau > >> > >>> On Apr 5, 2017, at 10:33 AM, Brian@Wavefield Recordings > >>> wrote: > >>> > >>> Hi all, > >>> > >>> So as the subject explains I updated my second machine to test out how > >>> things would work with the latest OS and latest PT version. > >>> > >>> I've been mixing on the go this week and am a bit frustrated to find > >>> that the following things have changed which greatly slow down my > >>> workflow, so far I think these may be the only issues to pop up. > >>> > >>> Firstly, when using the command option W key stroke to close plugin > >>> windows, Voice Over jumps focus back to the top of the mix window i.e. > >>> the left as you arrow with voice over, where as before closing the > >>> window would land me back on the name of the track I was working on, > >>> which I believe is the proper behaviour. > >>> > >>> Further more when I arrow back over from the top of the mix window to > >>> get back to the track I was working on it will sometimes randomly > >>> arrive into the insert section of the track I was working on as I pass > >>> by, as though it kind of half remembers I had been working on that > >>> track or something. A bit strange and laborious. > >>> > >>> Secondly, a small detail but a little annoying, I always set hot spot > >>> 5 to the trackless table for speed of track selection and such, but it > >>> used to automatically interact with he trackless table, now I have to > >>> manually interact with the track list table after I jump to the hot > >>> spots, not a major deal but its an extra key stroke in my work flow > >>> that used to be unnecessary. > >>> > >>> I haven't really tried solving these issues beyond running the > >>> installer for flo tools again and have not yet had time to start from > >>> a clean PT session to see if the problems still occur. > >>> > >>> My main studio machine is still on Yosemite and as some of you may > >>> recall, I couldn't check the box to let voice over be controlled by > >>> apple script, so there fore couldn't install flo tools, so given the > >>> change in behaviour of flo tools after upgrading my second machine, > >>> I'm a little hesitant to do the same to my main machine just to get > >>> flo tools up and running in case anything else goes wrong. > >>> > >>> Any ideas would be greatly appreciated as always and hopefully I > >>> managed to get the message across relatively concisely, > >>> > >>> > >>> Brian. > >>> > >>> -- > >>> You received this message because you are subscribed to the Google > Groups > >>> "Pro Tools Accessibility" group. > >>> To unsubsc
