U-he plugins accessible for a blind users

[Alex_Longard]

Hello Urs and all U-he team.
Do you can add some parameters to the list of host automation params?
For example: modulation destinations and some others params, that show in plugin UI and there is no host automation.
You are in a certain topic already said that it is unnecessary to anyone, only this one convenient option for blind users for use your plugins, since we can not use the mouse to turn the handle on the plug-in screen or open the desired menu.

Or can forget all about the use of your plug-ins?

[Urs]

I'm afraid it's very difficult to add certain parameters to host automation. Modulation destinations for instance are based on internal parameter IDs, of which there are hundreds, if not thousands. These IDs may vary from build to build. So if someone actually automates those in a host software, every update of the plug-in would randomly change the sound. We have no clever solution for this at this point of time.

I guess some of our plug-ins are better suited for blind people than others.

We however see several paths to improve things for blind and visually impaired people. Some concepts auch as full keyboard control are not viable for plug-ins due to random conflicts with host software. The most promising solutions appear to be in conjunction with standalone software. We have worked on standalone software on and off, and some day we hope to be able to offer it. In that context it might be possible to offer broader means of accessibility than in plug-in version.

[Alex_Longard]

Hello Urs,
in your plugins have many params and menus are now available for screenreaders.
In Hive i see 332 parameters for automation, some this params shows as menus.
For example: menu in host automation list
parameter: MM1: Source (224)
this param have values:
None (1)
ModWhl (2)
PitchW (3)
etc...

Do you can write the same parameters for host automation as I wrote above?

See please my C-code where i show as plugin shows params in host, your plugins convey parameters about the same.

Code: Select all

delete

At this time instead of the normal management of some parameters have to use scripting to AutoHotKey,
there my code:

Code: Select all

delete

I do not have the possibility to ask for sighted people to help me find the coordinates of all the necessary controls, so I can write them in my script and share with other blind who want to use your plugins.
I really like how the structure devised to save presets, skins, but I still can not understand where the values ​​in the parameters of skin show actual coordinates of the element.

Very big thanks for your answer!