Release 2.7.3

[nmbrthirteen]

Ships the speaker-turn work from #168 and the opener fix from #172.

What users get

Speaker detection actually runs. It was raising Could not load libtorchcodec on any machine with the ffmpeg binary but not its shared libraries, the studio looked for HF_TOKEN in the working directory instead of the podcli home, and all three entry points defaulted it off. Without speaker labels a clip cannot tell a question from an answer, and the crop cannot follow whoever is talking.

The camera follows the speaker. A face map with two clusters and no speaker mapping was read as "single speaker" and pinned the whole clip to clusters[0], first in list order. On a mixed-layout source that meant the crop sat on one person while the other talked, and landed on blank wall whenever the layout switched.

Clips ship with the captions they asked for, or say why not. An empty word list rendered a silent clip and reported success. Both empty cases now return a warning that the studio already displays per clip.

Titles are written, not copied. The JSON spec still said "title": "First strong sentence from the moment", which is how clips ended up titled "Is it having a big?".

Every clip states what the viewer gets. suggest_clips requires a payoff and a standalone check, and a clip whose setup lives outside its own range is rejected rather than waved through on a context_line that nothing renders.

Release note

Diarization is on by default now, so transcription is slower for anyone with HF_TOKEN set: roughly 100 seconds per hour of audio on Apple Silicon. Machines without torch or without a token are unaffected, they log a warning and continue.

package.json and cli/VERSION only, matching the shape of #166.

[coderabbitai]

Warning

Review limit reached

@nmbrthirteen, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 4 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: b79be143-ae43-4012-ab34-39c1679f9293

📥 Commits

Reviewing files that changed from the base of the PR and between c6e2a54 and d62d97a.

📒 Files selected for processing (2)

• cli/VERSION
• package.json

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}