1. Self-serve first
Start with troubleshooting docs, FAQs, and release notes so install, upgrade, and compatibility questions can often be resolved immediately.
Support
Get help with Core Musica through one clear support path.
Use docs and release notes for self-service first, open a GitHub issue for technical problems, and contact Syntax Circus for ownership, licensing, or business questions.
How to get help
Start with self-service resources, then escalate to the issue tracker or direct contact if you need more.
2. Report technical problems
Use the Core Musica GitHub issue tracker for reproducible bugs, update failures, crash reports, and product-behavior questions.
3. Contact the owner
Use Syntax Circus for ownership, licensing, legal, or business-related questions that do not belong in the public issue tracker.
Choose the right support path
Each path has a clear owner so technical issues, self-service questions, and owner-level inquiries do not get mixed together.
Docs, FAQ, and release notes
Use this path for install help, upgrade steps, known behavior, compatibility notes, and download verification.
- Read the troubleshooting guide for practical issue resolution.
- Check the FAQ for common workflow and release questions.
- Check the relevant release page before reinstalling or downgrading.
GitHub issues for technical support
Use the issue tracker for bugs, crashes, update-check failures, broken installers, and clearly reproducible product problems.
- Include your exact Core Musica version and release channel.
- State whether you are using the installer or portable build.
- Link to the matching release page if the problem started after an upgrade.
Syntax Circus for ownership questions
Reach out to Syntax Circus for licensing, brand, partnership, legal, or other questions that fall outside the public issue tracker.
- Use this path when the question is about ownership or business rather than app behavior.
- Keep technical bug reports in the GitHub tracker so issue history stays visible and actionable.
- Use the licensing page first when the question is specifically about open-source acknowledgements.
Before you open a support request
- Confirm the exact version, release channel, and install kind you are using.
- Check the latest release notes for known issues, compatibility notes, and checksum guidance.
- Capture clear reproduction steps, expected behavior, and what actually happened.
- Use the docs and FAQ links first for setup and upgrade questions that already have published guidance.
Ready to escalate a technical issue?
Use the GitHub issue workflow for product problems, or go to Syntax Circus directly for ownership and business questions.