Papers › FMA: A Dataset For Music Analysis

FMA: A Dataset For Music Analysis

6 Dec 2016ISMIR 2017 4arXiv:1612.01840archive 2025-07-28

Michaël Defferrard, Kirell Benzi, Pierre Vandergheynst, Xavier Bresson

We introduce the Free Music Archive (FMA), an open and easily accessible dataset suitable for evaluating several tasks in MIR, a field concerned with browsing, searching, and organizing large music collections. The community's growing interest in feature and end-to-end learning is however restrained by the limited availability of large audio datasets. The FMA aims to overcome this hurdle by providing 917 GiB and 343 days of Creative Commons-licensed audio from 106,574 tracks from 16,341 artists and 14,854 albums, arranged in a hierarchical taxonomy of 161 genres. It provides full-length and high-quality audio, pre-computed features, together with track- and user-level metadata, tags, and free-form text such as biographies. We here describe the dataset and how it was created, propose a train/validation/test split and three subsets, discuss some suitable MIR tasks, and evaluate some baselines for genre recognition. Code, data, and usage examples are available at https://github.com/mdeff/fma

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

No sample from the archive's official repository (mdeff/fma) is linked to this paper; the 14 samples below come from 2 community repositories. Syntology harvested code from mdeff/fma for another paper.

mdeff/fma: Syntology's graph links these samples to LLark: A Multimodal Instruction-Following Language Model for Music (arXiv:2310.07160; that paper's own run record: 5 ran (of which 1 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified); nothing checks that they implement this paper's method.

Syntology 14 code samples harvested from 2 repositories linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 5 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 14 samples from 2 repositories, 9 ran (9 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 6 of its repositories that Syntology harvested for other papers:

Levels written on 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

18 repositories listed; official and paper-mentioned ones first.

mdeff/fma officialmentioned in papermentioned on GitHubtfMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to LLark: A Multimodal Instruction-Following Language Model for Music (arXiv:2310.07160; that paper's own run record: 5 ran (of which 1 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified); nothing checks that they implement this paper's method. report
Golem8/Music-Genre-Classifier mentioned on GitHubSyntology: not harvested report
KrishnaManmayi/Music-Data-Visualization mentioned on GitHubSyntology: not harvested report
Manmayi/Music-Data-Visualization mentioned on GitHubSyntology: not harvested report
MorenoLaQuatra/ARCH mentioned on GitHubpytorchNOASSERTIONSyntology: not harvested report
StatisticDean/Crystal_Clear mentioned on GitHubpytorchApache-2.0Syntology: 7 samples, 5 ran (0 instrument-failed) · 2 unverified report
bhavnasud/MusicRecognition mentioned on GitHubtfMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Learning to Recognize Musical Genre from Audio (arXiv:1803.05337; that paper's own run record: 10 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 1 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified); nothing checks that they implement this paper's method. report
cocktail-fork/cocktail-fork.github.io mentioned on GitHubMITSyntology: not harvested report
crowdAI/crowdai-musical-genre-recognition-starter-kit mentioned on GitHubMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Learning to Recognize Musical Genre from Audio (arXiv:1803.05337; that paper's own run record: 10 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 1 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified); nothing checks that they implement this paper's method. report
darius522/dnr-utils mentioned on GitHubMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to The Cocktail Fork Problem: Three-Stem Audio Separation for Real-World Soundtracks (arXiv:2110.09958; that paper's own run record: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
dcase2024-task7-sound-scene-synthesis/fadtk mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Correlation of Fréchet Audio Distance With Human Perception of Environmental Audio Is... (arXiv:2403.17508; that paper's own run record: 8 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 1 violated, 4 with no contract checked; 3 where Syntology's instrument failed) · 8 unverified); nothing checks that they implement this paper's method. report
karn1986/fma_pytorch mentioned on GitHubpytorchSyntology: not harvested report
kikwon/fma_project mentioned on GitHubtfSyntology: not harvested report
markcutajar/raw-music-tagging-cnns mentioned on GitHubtfSyntology: not harvested report
mdeff/paper-fma-ismir2017 mentioned on GitHubCC-BY-4.0Syntology: not harvested report
microsoft/fadtk mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Adapting Frechet Audio Distance for Generative Music Evaluation (arXiv:2311.01616; that paper's own run record: 9 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
ucsd-dsc-arts/dsc160-midterm-group2 mentioned on GitHubSyntology: not harvested report
weepingwillowben/sound-eval mentioned on GitHubtfMITSyntology: 7 samples, 4 ran (0 instrument-failed) · 3 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

14 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 0 where Syntology's instrument failed) · 5 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

9ran
5unverified

Licence: 0 of the 14 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

StatisticDean/Crystal_Clear community (archive-listed) 7 samples, 5 ran (0 instrument-failed) · 2 unverified
make_into_3D crystal_clear/prepare.py ran Apache-2.0 (permissive) · 341a34687ad2fba2 · report fixture: signature data:ndarray/2/float · returned ndarray · level recorded 2026-09-26
make_weighted_average_on_window crystal_clear/utils.py ran Apache-2.0 (permissive) · 43f535babf9558b5 · report fixture: signature sliding:ndarray/4/float · returned ndarray · level recorded 2026-09-26
path_mp3 crystal_clear/prepare.py ran Apache-2.0 (permissive) · 735c3f6db89d9f8f · report fixture: signature track_id:int/0/int, folder:str/0/str · returned PosixPath · level recorded 2026-09-26
predict_method crystal_clear/upscale.py ran Apache-2.0 (permissive) · 9cca6de4e1c97a8d · report fixture: signature data:Tensor/2/float, model:callable/0/?, proc:SimpleProcessor/0/?, bs:int/0/int, use_gpu:bool/0/bool, show_progress:bool/0/bool · returned Tensor · level recorded 2026-09-26
wrap_for_processor crystal_clear/utils.py ran Apache-2.0 (permissive) · 4791d3c12dee84d7 · report fixture: signature f:callable/0/?, out:bool/0/bool · returned function · level recorded 2026-09-26
fourrier_from_data crystal_clear/tensor_pipeline.py unverified Apache-2.0 (permissive) · ea510ef359b43c33 · report
reconstruct in 9 papers crystal_clear/misc.py unverified Apache-2.0 (permissive) · a33053bfb337d4fd · report
weepingwillowben/sound-eval community (archive-listed) 7 samples, 4 ran (0 instrument-failed) · 3 unverified
batch_filenames spectrify_all.py ran fingerprinted MIT (permissive) · 4bb277ee9b64c89a · report fixture: signature abs_filenames:list/1/str · returned list · level recorded 2026-09-26
flatten_audios spectrogram_doc2vec.py ran MIT (permissive) · 667e6a01204b5c1e · report fixture: signature spec_list:list/1/ndarray · returned tuple · level recorded 2026-09-26
get_all_paths process_many_files.py ran MIT (permissive) · aee92765b773b981 · report fixture: signature base_folder:str/0/str, extension:str/0/str · returned list · level recorded 2026-09-26
read_file in 112 papers gather_computed.py ran MIT (permissive) · c708ef13e6436433 · report fixture: signature filename:str/0/str · returned str · level recorded 2026-09-26
get_batch_from_var spectrogram_doc2vec.py unverified MIT (permissive) · a3b1c9b3c1692bbf · report
spectrify_audios spectrify.py unverified MIT (permissive) · ea75c7dde8960478 · report
tf_spectrify spectrify.py unverified MIT (permissive) · a3ce6f94d6f60428 · report

Datasets

Introduced by this paper, per the archive.

FMA

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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