- About This Site (Start here!)
- About the book Fundamentals of Music Processing
- About the CCRMA Workshop on Music Information Retrieval
- What is MIR?
- Python Basics and Dependencies
- Jupyter Basics
- Jupyter Audio Basics
- SoX and ffmpeg
- NumPy and SciPy Basics
- Sheet Music Representations
- Symbolic Representations
- Audio Representation
- Tuning Systems
- MIDI Note to Frequency Conversion Table
- Understanding Audio Features through Sonification
- Basic Feature Extraction
- Segmentation
- Energy and RMSE
- Zero Crossing Rate
- Fourier Transform
- Short-time Fourier Transform and Spectrogram
- Constant-Q Transform and Chroma
- Video: Chroma Features
- Magnitude Scaling
- Spectral Features
- Autocorrelation
- Pitch Transcription Exercise
- Novelty Functions
- Peak Picking
- Onset Detection
- Onset-based Segmentation with Backtracking
- Tempo Estimation
- Beat Tracking
- Video: Tempo and Beat Tracking
- Drum Transcription using ADTLib
- K-Means Clustering
- Exercise: Unsupervised Instrument Classification using K-Means
- Neural Networks
- Genre Recognition
- Exercise: Genre Recognition
- Principal Component Analysis
- Nonnegative Matrix Factorization
- NMF Audio Mosaicing
- Harmonic-Percussive Source Separation
This repository contains instructional Colab notebooks related to music information retrieval (MIR). Inside these notebooks are Python code snippets that illustrate basic MIR systems. You can actually execute the code from inside the notebook.
2023 October 09: Hello everyone! I'm Iran R. Roman and I'm honored to be the new administrator of musicinformationretrieval.com. Feel free to reach out and say hi. I would love to hear from you. iran <at> ccrma <dot> stanford <dot> edu
2022 April 22: It's 2022, and Colab seems to be much more popular and usable than it was a few years ago. You can help me migrate musicinformationretrieval.com to Colab. Edit a Colab notebook, and submit a pull request. Ping iran <at> ccrma <dot> stanford <dot> edu to let me know.
Your contributions are welcome! You can contribute in two ways:
-
Submit an issue. Click on "Issues" in the right navigation bar, then "New Issue". Issues can include Python bugs, spelling mistakes, broken links, requests for new content, and more.
-
Submit changes to source code or documentation. Fork this repo, make edits to your fork, then submit a pull request.
gh-pages
is the default branch for this repo. Try to follow the style conventions in the existing notebooks. Ping iran <at> ccrma <dot> stanford <dot> edu to let me know you submitted a pull request.