docs: clarify Cartesia role in README (Fixes #268)

[aniruddhaadak80]

Closes #268

Corrected the description for Cartesia in the examples table to accurately reflect that Cartesia handles the emotional TTS alongside a vision model.

cc: @aliev @Nash0x7E2 @d3xvn

Summary by CodeRabbit

• Documentation
  • Updated Cartesia demo description to clarify how Sonic 3 model works alongside a vision model for storytelling capabilities.

[coderabbitai]

📝 Walkthrough

Walkthrough

The README.md Cartesia demo description was updated to clarify that visual understanding capability depends on both Cartesia's Sonic 3 model and a separate vision model working together, rather than implying Cartesia alone provides visual frame analysis.

Changes

Cohort / File(s)	Summary
Documentation Update README.md	Revised Cartesia example description to accurately reflect that visual frame analysis requires both Cartesia's Sonic 3 TTS/STT model and a separate vision model, correcting the previous implication that Cartesia alone provided visual understanding.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A single line recants the lie,
Where vision bloomed from Cartesia's breath—
Now truth admits the dual eye,
Twin models weave what one cannot wreath,
In clarity, the error dies.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: clarifying Cartesia's role in the README documentation by correcting its inaccurate description.
Linked Issues check	✅ Passed	The PR addresses issue #268's requirement to correct the README's Cartesia description from implying visual frame-by-frame analysis to accurately describing it as emotional TTS alongside a vision model.
Out of Scope Changes check	✅ Passed	The change is limited to updating the Cartesia demo description in the README, which directly addresses the linked issue with no extraneous modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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 and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

README.md (1)

196-196: Fix is accurate — bullet points could be slightly more precise (optional nit).

The corrected prose ("alongside a vision model") resolves the core ambiguity from issue #268 and aligns with the Integrations table description of Cartesia as a TTS-only plugin (line 145). The sonic-3 model reference remains valid.

One optional polish point: the bullets Real-time visual understanding and Frame-by-frame analysis still lack attribution to the vision model rather than Cartesia. A reader skimming only the bullets could still infer these as Cartesia capabilities. Consider tightening:

✏️ Optional bullet clarification

- • Real-time visual understanding
  • Emotional storytelling
- • Frame-by-frame analysis
+ • Real-time visual understanding (via vision model)
  • Emotional storytelling
+ • Frame-by-frame analysis (via vision model)

Based on learnings, Cartesia's sonic-3 is a valid TTS model_id, so retaining that reference in the description is correct.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 196, The README entry for Cartesia currently implies
visual capabilities belong to Cartesia; update the description line that
contains "<h3>Cartesia</h3>Using Cartesia's Sonic 3 model alongside a vision
model..." and change the bullets "Real-time visual understanding" and
"Frame-by-frame analysis" to explicitly attribute those features to the
accompanying vision model (e.g., "Real-time visual understanding (via vision
model)" and "Frame-by-frame analysis from the vision model"), while keeping the
"sonic-3" model_id reference and the rest of the prose intact.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@README.md`:
- Line 196: The README entry for Cartesia currently implies visual capabilities
belong to Cartesia; update the description line that contains
"<h3>Cartesia</h3>Using Cartesia's Sonic 3 model alongside a vision model..."
and change the bullets "Real-time visual understanding" and "Frame-by-frame
analysis" to explicitly attribute those features to the accompanying vision
model (e.g., "Real-time visual understanding (via vision model)" and
"Frame-by-frame analysis from the vision model"), while keeping the "sonic-3"
model_id reference and the rest of the prose intact.