output-formats: note that pcm_16000 is version-gated - #11
Merged
Merged
Conversation
Every output-formats recipe offers pcm_16000 as the telephony choice with no qualification, in the README and again in a comment beside the format list. The knowledge engine cites these recipes when asked which output_format to use for 16 kHz Twilio audio, and answers pcm_16000 flat. On a workspace pinned before API version 2026-09-30 the Simba 3 models answer pcm_16000 with 24 kHz samples labelled rate=16000, so a 16 kHz pipeline plays them 1.5x slow and pitched down. Nothing errors; the audio is just wrong. A workspace created on or after 2026-09-30 is already correct, and an older pin keeps the bytes it has always received on purpose. Each README gains the caveat and the two ways out, and each format list gains a one-line comment beside pcm_16000 so somebody copying the array sees it without reading the prose. Five recipes, bash, python and typescript, native and SDK. Grounded in apps/server/swagger.yaml and the 2026-09-30 TTS changelog; the docs page is SpeechifyInc/speechify-api#4015.
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
1 participant
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.
Every
output-formatsrecipe offerspcm_16000as the telephony choice with no qualification — in the README, and again in a comment beside the format list. The knowledge engine cites these recipes when asked whichoutput_formatto use for 16 kHz Twilio audio, and answerspcm_16000flat.On a workspace pinned before API version
2026-09-30, the Simba 3 models answerpcm_16000with 24 kHz samples labelledrate=16000— a 16 kHz pipeline plays them 1.5× slow and pitched down. Nothing errors; the audio is just wrong. A workspace created on or after2026-09-30is already correct, and an older pin keeps the bytes it has always received on purpose.Ten files across five recipes (bash, python, typescript × native, SDK):
pcm_16000, so somebody copying the array sees it without reading the prosePython and bash syntax-checked; the TypeScript edits are comments only.
Grounded in
apps/server/swagger.yamland the2026-09-30TTS changelog. Docs page: SpeechifyInc/speechify-api#4015 (merged). Skill: Speechify-AI/skills#2.The docs page alone did not change the engine's answer — with it live and the cache flushed, retrieval still reached for the skill and these recipes first. These are the sources that actually move it.