TimeCues Studio: A Workspace for Music Annotation and Algorithm Prototyping

Sapir Caduri, Yoav Goldberg
9/9/2026
cs.SDcs.HCcs.LG

No confident code implementation found for this paper.

Abstract

Multimedia applications require precise music annotation-labeled positions, segments, or loops-placed by hand or algorithmically. Machine-learning algorithms are scalable and effective but need annotated training data, scarce for many tasks. TimeCues Studio is an open-source workspace where algorithm-development teams annotate a music corpus, compare detection algorithms against those annotations, and prototype new ones. Unlike existing tools built for a single track at a time, TimeCues targets teams annotating whole collections, tightly integrated with algorithm development. Annotators place several marker types-each supporting ambiguity-aware labeling-on a grid-locked timeline that visualizes many music features, including separated audio stems. The same timeline drives an algorithm-comparison engine with bundled baselines, a Python sandbox for prototyping new models, and an ambiguity-aware evaluator that honors the structured fields. The same visualization suits solo annotators on music-sync projects. TimeCues is MIT-licensed and deploys via one Docker Compose command.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{caduri2026timecues,
  title  = {TimeCues Studio: A Workspace for Music Annotation and Algorithm Prototyping},
  author = {Sapir Caduri and Yoav Goldberg},
  year   = {2026},
  eprint = {2609.10338},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2609.10338v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2609.10338.svg)](https://codeofpaper.com/paper/2609.10338)

Discussion