Commit

4e99434

Happy to. Need two things: the exact dated model id (repo only uses dated snapshots, e.g. qwen3.5-omni-flash-realtime-2026-03-15), and a DASHSCOPE_API_KEY, none here. Then I add it to vxasr builtin and run the vxasr CLI on testdata. @dtinth
Created .env in ~/ghq/github.com/dtinth/vxbeamer/.claude/worktrees/pairing-auth/ (gitignored) with DASHSCOPE_API_KEY placeholder. Docs say 3.8 needs a workspace endpoint, so also DASHSCOPE_WORKSPACE_ID. @dtinth fill both and tell me.
You are right, sorry. Left the worktree, main is fast-forwarded to the merged PR. The .env placeholder (API key, workspace id) now lives in ~/ghq/github.com/dtinth/vxbeamer/.env. Fill it and I wire up qwen3.8. Delete my 3 old worktrees? @dtinth
Old worktrees deleted. Qwen3.8 works: draft PR 125. On the 9.2s clip, 3 runs: same transcript and tokens as 3.5-flash in 2 of 3 (1 rendered deploy in Thai), ~10s, coarser partials (9-11 vs 31). Handshake unchanged, needs workspace endpoint.
Caveats: no dated model id exists yet (I exempted it by name from the pinned-ids test), and price is a placeholder copied from 3.5-flash, docs give none. Want more recordings tried, or the real price from your console? @dtinth
Side finding: our 3.5 price table charges $17.70 for text output, but the page lists $3.30 for text and $17.70 for audio. 3.5 costs may be 5x overstated on output. Left alone, want it fixed? @dtinth
On it: fixing the 3.5 text-output rates, then a timeline of when partials arrive vs the audio, then the two Qwen-Audio-3.1 models. Will report back.
Please add. BTW, can you show me the exact text that came out from the four models? We don't care about the partials. It is there to, you know, uh, help the user feel assured that they are being listened to.
@dtinth Added qwen-audio provider (both models), pushed to #125, 170 tests pass. Correction: message is not stable. 5 of 6 runs gave the good text; 1 wrote Thai phonetics for every English word. Streaming: no word spaces, MongoDB garbled every run. Prices still unverified, please…
@dtinth Yes: all 3 new models accept audio faster than real time (9.2s clip in 0.8-2.6s, 3 runs each), same text and token counts as paced. Starting the adversarial review now, then I will mark #125 ready.

commit 4e99434