Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FR: make parameter names and values accessible to screen reader software for the visually impaired #18

Closed
IsaakCode opened this issue Nov 26, 2021 · 3 comments

Comments

@IsaakCode
Copy link

A user with visual impairment, who also happens to develop sample libraries, inquired about sampling engines that are accessible from screen reading (text-to-speech) software. Logic and EXS are compatible with Mac OS built in screen reader, but most other sampling engines / plugins don't reveal their parameters and values.

Would it be possible to make the parameter names and the values in Sfizz accessible to these text-to-speech applications for visually impaired users? This would make Sfizz the only sampling engine with that feature outside of the Logic environment afaik.

Here is the original thread discussing the underlying issue in more detail:
https://www.pianobook.co.uk/forums/topic/blindness-and-the-challenges-of-samples/

@paulfd
Copy link
Member

paulfd commented Nov 26, 2021

Heh... JUCE actually has something for this nowadays, but I guess VSTGUI doesn't out of the box. It's a worthy goal, but it's not an easy one so I can't promise to have this ready before the next release ! However I'll definitely keep it in mind.

@IsaakCode
Copy link
Author

Appreciate it!

@paulfd
Copy link
Member

paulfd commented Dec 30, 2021

Just a side note: this should rather happen after we switch to the next VSTGUI point release (and solves its problems) -> #21

@redtide redtide transferred this issue from sfztools/sfizz May 8, 2023
@sfztools sfztools locked and limited conversation to collaborators Nov 2, 2023
@redtide redtide converted this issue into discussion #117 Nov 2, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants