/dev/null
Sign in

Commit

0913af2

dtinth’s bot@dtinth-bot
Here! Fresh orphan branch v2 is checked out and empty. Where do you want to start: the transcription model, the audio capture side, or the viewer?
dtinth’s bot@dtinth-bot
Sure. I read the 2024 README: sender, server, fast partial ASR + Gemini batch refine, viewer. First question: keep that two-pass idea, or aim for one realtime model good enough on its own?
Thai Pangsakulyanont@dtinth
Basically, I aim for a single real-time model, but the transcript can be later post-processed with LLM if needed. re. model, see: - https://help.aliyun.com/en/model-studio/real-time-speech-recognition-user-guide?spm=a2c4g.11186623.help-menu-2400256.d_1_2_2_0_1.362dc690INtcxw -…
help.aliyun.comReal-time speech recognition - QwenLearn about real-time speech recognition capabilities, streaming audio calls, and ways to improve recognition results.
dtinth’s bot@dtinth-bot
mattpocock-skills is already installed as a plugin here. For the per-repo setup, my defaults: 1. Issues: GitHub Issues on dtinth/live-speech 2. Triage labels: the default five 3. Docs: single GLOSSARY.md + docs/adr/ 4. Agent file: AGENTS.md (with CLAUDE.md pointing to it) OK, or…
Thai Pangsakulyanont@dtinth
All agree. More re.directions: - Have a simple web interface. Admin can create room. To create room requires a master password from env file. - Then a room has its own password which can be copied out and sent to teammates e.g. to the audio crew for streaming.
dtinth’s bot@dtinth-bot
Noted: admin creates rooms with a master password from env; each room gets its own shareable password. Writing setup files now. I need GitHub access for labels/issues: please approve claw grant code 3BR664 (expires in 15 min).
dtinth’s bot@dtinth-bot
Setup is committed locally on v2 (AGENTS.md, CLAUDE.md, docs/agents/). The claw grant request 3BR664 lapsed before approval, so labels aren't created yet. Want me to request a new code?