The dataset viewer is not available for this subset.
Exception: SplitsNotFoundError
Message: The split names could not be parsed from the dataset config.
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 286, in get_dataset_config_info
for split_generator in builder._split_generators(
~~~~~~~~~~~~~~~~~~~~~~~~~^
StreamingDownloadManager(base_path=builder.base_path, download_config=download_config)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/webdataset/webdataset.py", line 81, in _split_generators
first_examples = list(islice(pipeline, self.NUM_EXAMPLES_FOR_FEATURES_INFERENCE))
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/webdataset/webdataset.py", line 32, in _get_pipeline_from_tar
fs: fsspec.AbstractFileSystem = fsspec.filesystem("memory")
~~~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/fsspec/registry.py", line 302, in filesystem
cls = get_filesystem_class(protocol)
File "/usr/local/lib/python3.14/site-packages/fsspec/registry.py", line 239, in get_filesystem_class
raise ValueError(f"Protocol not known: {protocol}")
ValueError: Protocol not known: memory
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/split_names.py", line 71, in compute_split_names_from_streaming_response
for split in get_dataset_split_names(
~~~~~~~~~~~~~~~~~~~~~~~^
path=dataset,
^^^^^^^^^^^^^
config_name=config,
^^^^^^^^^^^^^^^^^^^
token=hf_token,
^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 340, in get_dataset_split_names
info = get_dataset_config_info(
path,
...<6 lines>...
**config_kwargs,
)
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 291, in get_dataset_config_info
raise SplitsNotFoundError("The split names could not be parsed from the dataset config.") from err
datasets.inspect.SplitsNotFoundError: The split names could not be parsed from the dataset config.Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
BEAT ICML 2026 Piano Dataset
This repository hosts the piano-score dataset release for BEAT: Tokenizing and Generating Symbolic Music by Uniform Temporal Steps (ICML 2026).
Released archive
BEAT-ICML2026-piano-v3-dedup-musicxml.tar.gz contains 169,283
deduplicated piano scores in score-partwise MusicXML format. This is the v3
deduplicated release of the MuseScore-derived XML portion of the BEAT piano
corpus. The paper reports a broader piano training collection of approximately
208K pieces: about 193K MuseScore pieces before release filtering/deduplication,
plus about 15K piano pieces from the Lakh MIDI Dataset. The archive here does
not include that separate Lakh MIDI subset.
- Files: 169,283
.musicxml - Archive size: 1,645,907,562 bytes
- SHA-256:
b39d2bb79fae10f96e60e782170b7af783215d8b942089b2eccbef354d650781
Privacy cleanup
The released copy removes document-level MusicXML identity and provenance fields, including work/movement titles, creators, rights, source and encoding information, uploader/miscellaneous fields, page credits, comments, and processing instructions. Notes, score structure, part and instrument names, lyrics, directions, harmony, tempo, and dynamics are preserved. The original source files and metadata cache are not included.
Using the data with BEAT
Clone BEAT-code, extract the archive
into data/piano_xml/, and run:
python -m data_prep.xml2pianonpz --workers 32
accelerate launch --multi_gpu --num_processes 4 -m scripts.train_piano
The v3 preprocessor expands repeat bars and voltas by default, creates the NPZ representation, and writes stable 80/10/10 train/eval/test manifests. See the BEAT repository README for the full data layout and options.
Rights notice
Removing embedded document metadata does not alter any rights that may apply to the underlying musical works or source scores. Users are responsible for ensuring that their access and use comply with applicable terms and law.
Citation
@article{qian2026beat,
title = {BEAT: Tokenizing and Generating Symbolic Music by Uniform Temporal Steps},
author = {Qian, Lekai and Gu, Haoyu and Zhao, Jingwei and Wang, Ziyu},
journal = {arXiv preprint arXiv:2604.19532},
year = {2026}
}
- Downloads last month
- 37