GS-YEM-Access: Accessibility Script for Yamaha Expansion Manager

[gabrielschuck]

Hello everyone!
I'm creating this topic because I know there are some blind users here on the forum who could benefit from my humble little contribution. If the topic is not in the right place, moderators can feel free to do so.

This is a project that will have constant development, so more experienced developers are invited to collaborate in whatever way possible to help make it even better, more functional and efficient.

Repo link on Github:
https://github.com/gabrielschuck/GS-YEM-Access

Showcase

As you all know, Yamaha Music has been developing software over the past few years to aid in the incredible functionality of their musical instruments, especially keyboards.
Unfortunately, most of these programs are not fully accessible for use by blind people.
Users with equal conditions to enjoy the same resources face difficulties, as the interface has not been adapted to work perfectly with screen readers (programs that read the displayed information aloud).
It was with this in mind that the idea of an accessibility script for Yamaha Expansion Manager was born, a free desktop application that allows the user to install and manage expansion packs, as well as transfer to compatible digital keyboards.
Although some interface elements are accessible with nvda object navigation, this ends up making them impractical to use.
For script development, macro languages (such as Autoit and Macro Recorder) were chosen so that it can work independently of the currently active screen reader.

Requirements

*Yamaha Expansion Manager version 2.8.1 or higher
*Screen resolution set to 1920 X 1080 (Full HD)

How to use?

Just run the file "gs_yem_access.au3". When the Yamaha Expansion Manager window is in focus, you will hear a sound and a welcome message from the active screen reader.
If you are not using a screen reader, the sapi voice configured by default will be used.

What can I do with this script?

*create and import packs
*edit pack, where you can export, change LSB bank, rename, change image, etc. For the next update, I plan to make available little extra hotkey driven utilities that will automatically switch from LSB to packs that require it, like those from Pro Style Music. This operation is very difficult for a blind person to do
*ADD Content: Compatible sample files. I've been using soundfonts a lot, including creating my own with the help of programs like SampleRobot which is minimally accessible. After saving and generating the CPI of the created pack, you can install it on the keyboard and improve the voice a little, with Release and Reverb parameters.
All this and much more is certainly possible in the Voice Editor. We'll still get there at some point.
*edit content: Change program change, export content as pack, etfc.
*Midi settings: For sending midi data via keyboard
*Audio settings: So you can test an unprotected pack in the software itself before sending it to the keyboard. Very useful to avoid unnecessary formatting in expansion memory.


Main shortcut keys

*f1: Opens the "add pack" menu
*f2: Opens the "edit pack" menu
*f3: Opens the "install target" menu
*f4: Opens the "add content" menu (only for packs created by you and/or unprotected)
*f5: Opens the "edit content" menu (only for packages created by you and/or unprotected)
*f6: List of imported packages. Use the up, down, left and right arrow keys to navigate the rows and columns of the table
*f7: List of contents of selected package. Use the up, down, left and right arrow keys to navigate the rows and columns of the table
*f8: Configure midi input and output
*f9: Set audio output (you need to open unprotected package content in Voice Editor first)
*f10: Generate CPI or PPI file from imported packages
*ctrl + q: Close script

Enjoy!

[Luis Carlos GM]

As I said in my topic I really congratulate your work. Hopefully there's blind people here.

[overover]

Hi Gabriel,

Thank you for this Accessibility Script for use with the Yamaha Expansion Manager (YEM) and your hard work!

Yes, we have some blind or visually impaired users here in the forum. I hope some of them will try this script in connection with their screenreader program and report it here.


Best regards,
Chris