summaryrefslogtreecommitdiff
path: root/src/tangara/tts/provider.cpp
AgeCommit message (Collapse)Author
2025-02-18Gate playback on the existence of /.tangara-tts/.Tursiae
Also, clang-format previous changes in provider.hpp.
2025-02-11TTS: Implement and wire up a TTS toggle in Display Settings (#251)Tursiae
This change introduces the ability to enable or disable the spoken interface/TTS from the on-device settings, either via the UI or the Lua console. This closes out the implementation of issue #245. The TTS setting is only visible in Display settings if voice samples are present in `/.tangara-tts/` on the SD card. Playback of new TTS voice samples is inhibited when TTS is disabled. By default, the setting is enabled, as the device will only play back TTS voices if samples are present on disk. If you need samples to test TTS on your device, feel free to grab the voice samples I have at https://codeberg.org/tursiae/tangara-tts-samples. There's about 80-85% coverage of the UI, with the remainder to be added soonish. Reviewed-on: https://codeberg.org/cool-tech-zone/tangara-fw/pulls/251 Co-authored-by: Tursiae <git@tursiae.org> Co-committed-by: Tursiae <git@tursiae.org>
2025-02-06Make the TTS playback work by assuming the file is a .wav.Tursiae
The extension is needed to trigger format detection in the tag reader.
2024-09-12Clean up some tts logging and descriptionsjacqueline
2024-09-11Play TTS files in response to TTS prompts, but it's legible nowjacqueline
- input files are upsamples and padded to stereo before playback - any in-progress playback is cancelled before playing a new file
2024-09-09Play basic wav files in response to tts promptsjacqueline
It's currently quite limited (no stereo or sample rate conversion, multiple messages clobber each other, only plays if music is playing), but we're getting there!
2024-07-19WIP initial tts player wiringjacqueline
2024-05-29Start on TTS support by logging the data that will become TTS linesjacqueline
Includes some misc cleanup of haptic double-triggering (or non-triggering), since those cases all end up being TTS event double-reporting, which to me crosses the threshold from "annoying" to "usability issue"