[Rwp] My! Lord! am I impressed!

Alex H. linuxx64.bashsh at gmail.com
Wed Apr 8 15:43:25 EDT 2015


This is more of an OSX/VoiceOver limitation in how it caches objects I
think. This isn't the only example where VO lags heavily. Large
preference panes in the OS itself do this. Not really a good and easy
fix to this one I'm afraid, until Apple can speed up the loading of
tons and tons of items. Not intending to starting a wrestling match
over it; it's what I've experienced.

Most times the plugin's UI (not the generic UI) is useless to a VO user.

As a possible way to make things a bit friendlier, have you tried the
item chooser menu? You can arrow down through the list and wack enter
on what sounds interesting, and only have to wait once rather than
every time you VO+Left/Right through the UI

HTH,
Alex

Alex

On 4/8/15, Nadine Jahns via RWP <rwp at bluegrasspals.com> wrote:
> hi!
>
> Exactly this window i mean. Usually, you maybe won't notice itfor many
> plugins, because it really seems to depend on how many parameters the plugin
> has and i think, Vo just has problems showing such a big window and says
> busy all the time.
>
> A good way to reproduce this, is to take a softsynth with very many
> parameters. What first comes to my mind, is maybe the demo of predator,
> because here it happens for sure:
> http://www.robpapen.com/predator-demo.html
> <http://www.robpapen.com/predator-demo.html>
>
> Greetings
>
> Nadine
>
>
>> Am 08.04.2015 um 01:48 schrieb James Teh via RWP <rwp at bluegrasspals.com>:
>>
>> On 8/04/2015 9:34 AM, Scott Chesworth via RWP wrote:
>>> Interesting, so the generic Reaper UI for plugs is accessible on Mac
>>> then?
>> That'd make sense. It's technically accessible on Windows too to the
>> extent that REAPER's buggy accessibility code allows... which isn't
>> enough.
>>
>>> Have you ever had the opportunity to get some eyes on the case
>>> to find out whether the generic UI falls flat for sighted users too in
>>> those instances when no controls are shown?
>> The generic UI can only show automatable parameters, just like
>> ReaAccess/OSARA's FX parameters dialogs. If an effect doesn't expose a
>> parameter for automation, the generic UI won't show it.
>>
>> Jamie
>>
>> --
>> James Teh
>> Email/MSN Messenger/Jabber: jamie at jantrid.net
>> Web site: http://www.jantrid.net/
>> Twitter: jcsteh
>>
>> _______________________________________________
>> RWP mailing list
>> RWP at bluegrasspals.com
>> http://bluegrasspals.com/mailman/listinfo/rwp
>
>


More information about the RWP mailing list