Desktop GUI app using Qt and Azure Speech SDK.
AAS.py- main GUI applicationAAS.spec- PyInstaller build specrequirements.txt- Python dependenciesin/- input CSV filessamples/- prebuilt sample packsdocs/- docs/images
Runtime-generated folders (config/, data/, out/, build/, dist/) are created locally and ignored by git.
For FrSky users, default audio pack CSV files are available on FrSky's GitHub in the audio folder, under each language subfolder:
English example:
From repo root, run one install script for your OS:
.\install-windows.ps1Then launch:
.\.venv\Scripts\python.exe AAS.pychmod +x ./install-linux.sh
./install-linux.shThen launch:
./.venv/bin/python AAS.pychmod +x ./install-macos.sh
./install-macos.shThen launch:
./.venv/bin/python AAS.pyOn first run, enter your Azure Speech key and region when prompted. You can get them from the Azure Portal.
From repo root:
.\.venv\Scripts\Activate.ps1
pip install pyinstaller
pyinstaller AAS.specsource .venv/bin/activate
pip install pyinstaller
pyinstaller AAS.specBuild output:
dist/AdvancedAudioSuite.exe(Windows)dist/AdvancedAudioSuite(macOS/Linux)
This repo includes a GitHub Actions workflow at .github/workflows/build-cross-platform.yml.
- Run it manually from the Actions tab (
Build cross-platform binaries), or - publish a new GitHub Release to trigger it automatically.
For an existing release tag, you can also run the workflow manually and provide the required tag input (for example v1.0) to attach binaries to that release.
Each run builds on:
windows-latestubuntu-latestmacos-latest
Artifacts are uploaded per platform as:
AdvancedAudioSuite-windows.zipAdvancedAudioSuite-linux.tar.gzAdvancedAudioSuite-macos.app.zip
When triggered by publishing a GitHub Release, those same files are also attached directly under the Release Assets section.
