Hello everyone,
I am experimenting with the VirtualDJ Accessibility Extension in a somewhat different way than its original purpose, and I hope someone from the accessibility or scripting community can help me understand the correct syntax and workflow.
I am visually impaired, but not fully blind.
I use VirtualDJ with:
Most important browser information such as BPM, track titles and some larger UI elements are still visible enough for me. However, during live performances I currently spend too much time looking at the screen instead of reading the crowd and focusing on the mix itself.
My goal is therefore not a full accessibility workflow, but rather a lightweight “audio assist layer”:
Examples:
I would like to work with a dedicated custom PAD page where I can manually request the information I need during mixing.
At the moment I am also struggling to fully disable some of the default accessibility speech output and announcements. Is there a quick/easy way to disable most automatic announcements while keeping the speech engine active for custom scripts?
I have been trying to figure this out myself together with ChatGPT and some “vibe coding”, but I have not yet managed to get the custom speech output working to my liking.
My intention is to build VDJ scripts and map these to pad page and some buttons that i rarely use on my controller.
Is there anyone who could help me better understand how to approach this?
Any guidance would be greatly appreciated.
--
www.virtualdjaccessibility.com
---
You received this message because you are subscribed to the Google Groups "AccessibleDJSoftware" group.
To unsubscribe from this group and stop receiving emails from it, send an email to accessibledjsoft...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/accessibledjsoftware/c5b44147-dfe1-4f74-9036-bfe787dc0a67n%40googlegroups.com.