TruaceTracing the truth around AIWednesday, July 22, 2026
TRV-2026-0447Version 1 · Certified

Written 2026-07-20 10:56:32 UTC · current record

Reason for this version

Certified into the record

Canonical text (the exact bytes fingerprinted)

TRUVACE RECORD VERSION
record: TRV-2026-0447
version: 1
kind: certified
reason: Certified into the record
timestamp: 2026-07-20T10:56:32.165921Z
status: published
lens: p_space
sector: entertainment
headline: LSTM and CNN-Based Detection of AI-Generated Classical Music From MIDI Features
dek: Detecting AI-generated classical music is a growing challenge as artificial intelligence continues to improve its ability to compose pieces that closely resemble human compositions. This study explores the use of deep learning methods like LSTM and CNN to classify whether a set of classical music is generated by AI or humans. The classification is based on sequential features extracted from MIDI files using beat-based segmentation, capturing statistical data of pitch, velocity, and duration over segments. The mo…
gain_title: (none)
problem_title: AI systems can now compose classical pieces that closely resemble human compositions, making detection increasingly difficult.
trace_subject: (none)
gain_reading: (none)
gain_evidence: (none)
problem_reading: AI systems can now compose classical pieces that closely resemble human compositions, making detection increasingly difficult.
problem_evidence: Detecting AI-generated classical music is a growing challenge as artificial intelligence continues to improve its ability to compose pieces that closely resemble human compositions
quick_read: A peer-reviewed study published November 10, 2025 tested LSTM and CNN models to classify classical music as AI-generated or human-composed using statistical pitch, velocity, and duration features extracted from MIDI files via beat-based segmentation. Trained on a dataset containing both types of compositions, the models were evaluated on primary and auxiliary test sets.

High classification accuracy matters for music attribution, copyright, and platform integrity as generative models improve, but the reported results are confined to the study's MIDI datasets and feature set. Generalization to broader repertoires, live audio, or newer generative systems remains untested and would require expanded data and additional musical features.
limitation: Model robustness is limited by dataset scope and feature set, requiring broader compositions and additional musical features for wider applicability.
tag: Evidence-backed problem
key_points: Study used beat-based segmentation to extract statistical pitch, velocity, and duration features from MIDI files. | Dataset included both AI-generated and human compositions with fine-tuning for optimal performance. | LSTM outperformed CNN, achieving 99.00% on primary test set and 98.70% on auxiliary dataset versus CNN's 97.00% and 97.10%. | Evaluation included confusion matrices and classification reports showing minimal misclassification rates.
rundown: Researchers extracted sequential features from MIDI files using beat-based segmentation, capturing statistical data of pitch, velocity, and duration over segments, and trained LSTM and CNN classifiers on a mixed dataset of AI-generated and human compositions with fine-tuning.

The LSTM model achieved 99.00% accuracy on the primary test set and 98.70% on an auxiliary dataset, while the CNN achieved 97.00% and 97.10% respectively, with confusion matrices and classification reports showing minimal misclassification and indicating stronger performance for LSTM.
sources:
- peer_reviewed | Informatica | https://doi.org/10.31449/inf.v49i7.8781 | 2025-11-10
prev: 0000000000000000000000000000000000000000000000000000000000000000
sha256
c28a16bb209ce5ee731f9dea97725da2b38910071eb87df818920df3e6fc3b02
previous
0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0447 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.