Hi Fiore,
One other thing: I just checked out the link to the "how it works" page and
noticed a few instances of "continuous" being misspelled and I believe there
was also a typo on "highly." I didn't check carefully but those did stick
out—just an FYI.
Best,
Slau
On Dec 10, 2015, at 1:59
Hi Fiore,
I've had a chance to take a look at the plug-in and I think it's a useful tool,
to be sure. I personally don't find the continuous "sonification" (as you put
it) mode to be particularly handy but it's nice to have an option. Speaking of
the mode, I found a peculiar aspect to the
You are right indeed !
It must be a typo my hand does automatically cause it occurs three times.
Thanks for flagging that! I'll fix it tomorrow.
F.
On Thursday, December 10, 2015 at 7:09:27 PM UTC, Slau Halatyn wrote:
>
> Hi Fiore,
>
> One other thing: I just checked out the link to the
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, depic.resea...@gmail.com wrote:
>
> Hi,
>
> thank you Slau for
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
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
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,
Hi, I just checked this out and it does exhibit the same behavior. But
thank you for pointing this out, it makes PT much more responsive in elcap.
However, it still slows way down during playback. Have you figired out any
reason for this? What made you think of the LED thing? I also saved this
Hi Fiore,
Having spent a little more time with the meter plug-in, one thing now stands
out to me as something that I feel is incorrect about the threshold parameter.
Given that we're dealing primarily with full scale metering, most of us think
of the meters as being 0 dB FS, thus, with the
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 wrote:
>
> While the "how it works" info on the page that Fiore linked to provides an
> explanation,
Hi Fiore,
Having spent a little more time with the meter plug-in, one thing now stands
out to me as something that I feel is incorrect about the threshold parameter.
Given that we're dealing primarily with full scale metering, most of us think
of the meters as being 0 dB FS, thus, with the
Replying to a few people's points all in one message:
Slau: aside from the extra levels of patronage (which I've seen over
complicate some projects if not thoroughly thought through), crowd
funding is the neatest way I know of getting paid a base rate that you
can live with before pumping time
http://www.soundtoys.com/moas/?utm_source=Master+List_campaign=ac8c414240-Give_a_Little_Launch_12_9_2015_medium=email_term=0_bbd3e23605-ac8c414240-82133213
--
You received this message because you are subscribed to the Google Groups "Pro
Tools Accessibility" group.
To unsubscribe from this
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
Wew. Something shifted just then. Maybe everything is going to be ok after all.
Just chiming in late as someone who has burned a ton of time and
effort on remapping for DAW use on both platforms since Apple did away
with embedded numpads. The conclusion I've come to is that it wasn't
entirely
I'd be very surprised if the setup utility for this was accessible,
but hey, some surprises are good. Could be a neat way into control
surfaces for someone with limited budget or space if there's some sort
of sharing mechanism for individual apps couldn't it.
On 12/9/15, Ramy Moustafa
Dear Pro Tools Accessibility group,
I am a member of a research group called Design Patterns for Inclusive
Collaboration at Queen Mary University of London
Part of our research has involved accessibility of Digital Audio
Workstations.
More on our research can be found here:
Wow, thank you for sharing this with the list.
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of
depic.resea...@gmail.com
Sent: Thursday, December 10, 2015 7:51 AM
To: Pro Tools Accessibility
Subject: Accessible Peak Meter AAX plugin released
Dear Pro
No problem. Slap, if you don’t mind and have some time, could you do a demo of
how this thing works? I don’t even know if I am putting the plugin in the
right place LOL. Obviously not because it’s not showing up in my plugins.
> On Dec 10, 2015, at 12:50 PM, Slau Halatyn
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 wrote:
> Hello folks,
>
NO worries, I'll have words with Tim Cook instead. ;)
On 12/11/15, TheOreoMonster wrote:
> I blame auto correct here. It usually got my back, but this time it stabbed
> me in the back instead lol. Apologies man.
>
>> On Dec 10, 2015, at 7:09 PM, Scott Chesworth
I blame auto correct here. It usually got my back, but this time it stabbed me
in the back instead lol. Apologies man.
> On Dec 10, 2015, at 7:09 PM, Scott Chesworth wrote:
>
> Replying to a few people's points all in one message:
>
> Slau: aside from the extra
Oo, you've piqued my interest ;) Thanks for the info and I'm sure folks will
give it a spin.
Cheers,
Slau
On Dec 10, 2015, at 11:50 AM, depic.resea...@gmail.com wrote:
>
> Dear Pro Tools Accessibility group,
>
> I am a member of a research group called Design Patterns for Inclusive
>
The problem is exactly what Gordon mentioned: it's virtually impossible to
navigate to a specific parameter to be able to click on it to be able to
utilize the knob. For thos those who might b unaware, when VoiceOver "sees" a
parameter, that parameter's "location," per se, has absolutely
I think navigating to a particular element
would be very difficult. Without knowing what item the mouse cursor is
over, we wouldn't be able to drag the fader or knob we want. The fact that
it uses eye tracking technology certainly doesn't bode well for our
I just wanted to reply a bit here as there have been several responses. At the
outset, let me say that a few people have mentioned Groove 3 as a model. Let me
point out that a model such as groove 3 requires an infrastructure that I
simply don't have and will never aspire to so that's just
26 matches
Mail list logo