Fix typo in install command for macOS

[fernando-alves]

Summary by CodeRabbit

• Documentation
  • Updated Conda installation instructions for Nvidia GPU (CUDA) and Google Colab (CPU) scenarios: corrected the package specification and clarified channel configuration to improve reliability of environment setup. The CPU no-hardware-acceleration guidance remains unchanged.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Updated a Conda installation command in README.md: replaced a shortened package spec with the full package name and moved to explicit channel ordering (-c pytorch -c conda-forge). No other functional or error-handling changes.

Changes

Cohort / File(s)	Summary
Documentation README.md	Updated Conda install command: replaced audio-separator-c pytorch -c conda-forge with audio-separator -c pytorch -c conda-forge (full package name and explicit channels)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A conda command was quite confused,
With channels mixed and poorly used,
But now the flags shine clean and bright,
audio-separator set just right! ✨
The docs now guide with crystal clarity!

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title claims to fix a typo for macOS, but the actual change updates a Conda installation command by correcting the package name from 'audio-separator-c' to 'audio-separator' and adjusting channels—not a macOS-specific issue.	Revise the title to accurately reflect the change, such as 'Fix Conda installation command package name' or 'Correct audio-separator package specification in Conda install command'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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.}

---

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 98d0a6d and 19cb3e5.

📒 Files selected for processing (1)

• README.md

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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]

Actionable comments posted: 1

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 69cb8f9 and 98d0a6d.

📒 Files selected for processing (1)

• README.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (12)

• GitHub Check: test-windows (3.12)
• GitHub Check: test-ubuntu (3.12)
• GitHub Check: test-windows (3.11)
• GitHub Check: test-windows (3.13)
• GitHub Check: test-macos (3.12)
• GitHub Check: test-macos (3.10)
• GitHub Check: test-windows (3.10)
• GitHub Check: test-ubuntu (3.13)
• GitHub Check: test-macos (3.13)
• GitHub Check: test-ubuntu (3.11)
• GitHub Check: test-ubuntu (3.10)
• GitHub Check: integration-test