Datasets › Slakh2100

Slakh2100 (Synthesized Lakh Dataset)

Introduced by Ethan Manilow et al. in Cutting Music Source Separation Some Slakh: A Dataset to Study the Impact of Training Data Quality and Quantity1 Jan 2019 archive 2025-07-28

The Synthesized Lakh (Slakh) Dataset is a dataset for audio source separation that is synthesized from the Lakh MIDI Dataset v0.1 using professional-grade sample-based virtual instruments. This first release of Slakh, called Slakh2100, contains 2100 automatically mixed tracks and accompanying MIDI files synthesized using a professional-grade sampling engine. The tracks in Slakh2100 are split into training (1500 tracks), validation (375 tracks), and test (225 tracks) subsets, totaling 145 hours of mixtures.

Source: http://www.slakh.com/ Image Source: http://www.slakh.com/ Audio Source: http://www.slakh.com/

Benchmarks archive 2025-07-28

All 3 leaderboards whose dataset resolves to this page shown (sort by any header). "First row" is the archive's own first row at snapshot, in the archive's row order; nothing here re-ranks and metric direction is not asserted.

First row (archive order)PaperCode
Music Transcription Slakh2100 YourMT3+ (YPTF.MoE+M) note-level F-measure-no-offset (Fno) 0.8456 YourMT3+: Multi-instrument Music Transcription with... mimbres/yourmt3 6 Compare
Multi-instrument Music Transcription Slakh2100 YourMT3+ (YPTF.MoE+M) Multi F1 74.84 YourMT3+: Multi-instrument Music Transcription with... mimbres/yourmt3 5 Compare
Music Source Separation Slakh2100 LQ-VAE + Scalable Transformer SDR (bass) 7.42 Unsupervised Source Separation via Bayesian Inference in... michelemancusi/LQVAE-separation 2 Compare

Papers archive 2025-07-28

papers with a benchmark row: 6 · with a code link: 5 · where Syntology ran a sample: 2 (2 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology

Show: all papers with a benchmark rowonly where code ran (2 of 6 with a benchmark row: 2 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)

Page 1 of 1: papers 1 to 6 of 6 with a leaderboard row on this dataset's benchmarks, newest first by the archive's date (ties by slug; undated papers last).

The archive's own "papers using this dataset" list was never published, so this is the benchmark-backed subset, not that list; the archive's count for this dataset is 38. The Syntology column is from Syntology's graph, stated per sample; it is not part of any archive number. A line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified” (C is a part of N, never taken away from it); the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced. When the archive marks a repository official for the paper, the cell starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record.

Dataset loaders archive 2025-07-28

No loader listed in the archive.

Tasks archive 2025-07-28

License archive 2025-07-28

No licence recorded in the archive. Absence here is not a statement about the dataset's terms.

Modalities archive 2025-07-28

Languages archive 2025-07-28

No language tagged.

Variants archive 2025-07-28

  • Slakh2100

1 variant name, as the archive lists them.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections