Add diary audio playback - #74
Merged
Merged
Conversation
RANGROO
marked this pull request as ready for review
August 5, 2026 05:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root cause
The initial implementation passed the complete diary to the configured TTS provider in one request. The current 857-character diary exceeded Chatterbox's intended input size and produced only 20.6 seconds of garbled audio. Versioned segmented caching prevents that bad full-entry WAV from being reused.
Validation
php -l diary_audio.phpphp -l ui/diarylog.phpphp -l ui/home.phpphp tests/diary_gamets_conversion.phpDeployment
Deployed locally to
/var/www/html/StobeServer. The one current local diary was regenerated under the new segmented cache ascd58b272dd05ca71df31c59c26b794b9.wav. Local configuration, profiles, voices, and data were preserved.Compatibility
The endpoint still returns one final WAV hash, so the matching STOBE plugin requires no protocol change for segmented generation. Existing
?person=diary links continue to enter person-filter mode.Related