Which narration languages have Cup's conversions had?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend
Research direction
Start with the operator CLI in apps/operator/src/cli.ts and find how it reads each history entry's ready outcome and accesses accounts and conversion grants. Determine whether an agent session can query production; if not, prepare exact commands for the operator to run. Report aggregate conversion counts by narration language, including entries with no language, plus generated-audio duration for languages not listed by Whisper large v3 turbo; do not include account or source details.
Written by the indexing model from the issue text.
Description
Question
Which narration languages have Cup's conversions had in production so far, and how many conversions (and how much generated audio duration) fall on languages that Whisper large v3 turbo does not list?
The 28 of Cup's 99 narration languages that neither Whisper nor Gemini 3.5 Transcribe lists matter only as much as Cup's conversions use them (Which aligner finds overlap-and-cut points reliably?). The operator CLI already prints the narration language of each history entry's ready outcome (apps/operator/src/cli.ts). Count conversions per narration language, including conversions with no narration language, over all accounts and conversion grants, and report only aggregate counts: no account, source URL or source title. If the CLI cannot reach production from an agent session, hand the operator the exact commands to run and record their aggregate output.
Part of Map: decouple speech synthesis from synchronization units.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from patricktree/cup
-
wayfinder:grilling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patricktree/cup#484 ·
-
wayfinder:grilling
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
patricktree/cup#487 ·
-
wayfinder:grilling
Difficulty 5/5 Over a week Newbie friendliness 25/100
patricktree/cup#486 ·
-
wayfinder:grilling
Difficulty 5/5 Over a week Newbie friendliness 25/100
patricktree/cup#485 ·
-
wayfinder:grilling
Difficulty 5/5 Over a week Newbie friendliness 25/100
patricktree/cup#483 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/ui#865 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
outline/outline#14638 · 1 comment ·
Maintainers usually reply within 1 day
-
bot:ai-assisted component:platform-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
midnightntwrk/platform-js#69 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day