Skip to content
TimeCues Studio

Contact

TimeCues Studio is built and maintained by Sapir Caduri.

All contact happens on GitHub — issues for trackable items, discussions for thoughts, research, and collaboration. Public, threadable, and easier to find again later than email.

Bugs and feature requests

🐛 Open an issue on the TimeCues repo.

Or use the Send feedback page for pre-filled templates.

Useful to include in a bug report:

  • What you were doing (which page, which annotation layer, what file).
  • What you expected vs. what you saw.
  • Your browser + OS — TimeCues is tested on recent Chrome / Firefox / Safari; Brave or Arc-specific issues need explicit reports.
  • If reproducible: a short clip / screenshot, or the song slug if you’re using a public dataset.

Research collaboration, general questions, longer threads

💬 Start a discussion on the TimeCues repo.

Good fits for Discussions: music structure analysis collaboration, MIR evaluation methodology, inter-annotator agreement experiments, proposals to contribute a custom detector, or asking whether a use case fits the tool before opening an issue. Include a sentence about what you’re working on for context.

🔗 github.com/sapirca/timecues-studio — the repo.

🎛 Live demo — sign in with Google, get your own annotator namespace.