fix(realtime-transcriber-01): correct Scribe model id to scribe_v2_realtime - #83
fix(realtime-transcriber-01): correct Scribe model id to scribe_v2_realtime#83humanagent wants to merge 1 commit into
Conversation
…altime
The block passes `scribe_realtime_v2`, which the realtime API rejects. The
socket opens and is then closed by the server with 1008, so it presents as a
broken microphone rather than a bad parameter:
{"message_type":"invalid_request",
"error":"The model_id 'scribe_realtime_v2' is invalid. Supported models:
'scribe_v2_realtime', 'scribe_v2_realtime_turbo',
'scribe_v2_realtime_lite'."}
closed 1008 invalid_request
The same value is baked into public/r/realtime-transcriber-01.json, so
`shadcn add` ships it broken. speech-input.tsx already uses the correct id.
Closes elevenlabs#82
|
@humanagent is attempting to deploy a commit to the ElevenLabs Team on Vercel. A member of the Team first needs to authorize it. |
PR SummaryLow Risk Overview The same correction is applied in the published registry artifact Reviewed by Cursor Bugbot for commit 31b8ccc. Bugbot is set up for automated code reviews on this repo. Configure here. |
Fixes #82.
realtime-transcriber-01passesscribe_realtime_v2. The realtime API expectsscribe_v2_realtime.Why it is worth a look beyond the two characters
The socket opens, and is then closed by the server, so it presents as a broken microphone rather than a rejected parameter:
Nothing before that point fails, so the natural read is a permissions or device problem. I spent most of a day on the microphone before reading the close frame.
The same value is baked into
apps/www/public/r/realtime-transcriber-01.json, soshadcn add realtime-transcriber-01installs it broken.The change
Two occurrences, one of them generated:
apps/www/registry/elevenlabs-ui/blocks/realtime-transcriber-01/page.tsx:334apps/www/public/r/realtime-transcriber-01.json(edited in place to match; happy to regenerate withpnpm registry:buildinstead if you prefer the diff come from the build)registry/elevenlabs-ui/ui/speech-input.tsxalready uses the correct id in both its default and its JSDoc, so this brings the block in line with the rest of the registry. No other occurrence of the wrong id remains.Suggested follow-up, not included here
useScribetypes the parameter asmodelId?: string, which is why the transposition compiles. A string-literal union would turn this class of bug into a build error:Worth considering because the two orderings are equally plausible to read and to write — the
as conston the block suggests the author expected a union to be checking them. Left out of this PR to keep it to the fix; glad to open it separately if useful.