musescore / musescore/MuseScore

Quantization

Open
#28,402 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

MIDI
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Your idea

Please add this feature to MuseScore Studio.

Quantization is the studio-software process of transforming performed musical notes, which may have some imprecision due to expressive performance, to an underlying musical representation that eliminates the imprecision. The process results in notes being set on beats and exact fractions of beats.

It will be good if, when importing MIDI files, the user is prompted to select the quantization level.
Also, do not forget about the recognition of tuplets.
It's also nice to be able to select individual sections of the score for quantization after importing the MIDI.

Problem to be solved

If the imported MIDI file was recorded live by a human, then there will be minor inaccuracies in the correspondence of notes to rhythmic proportions.
I often have to deal with this problem when I import percussive MIDI patterns. Take a look at what I have to deal with:
Image

Because of this, multi-voices appear, and it takes a lot of time to put it all in order.

Prior art

No response

Additional context

Dorico has such a feature, including the ability to quantize individual sections of the score after importing MIDI.

There was such a feature in MuseScore 3, but now it's gone.
There is a "Shortest Note" setting in the program preferences, but I have no idea how it works, because I haven't seen anything from it alone.

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files or tests. Start by tracing MIDI import and the existing "Shortest Note" setting, then investigate how MuseScore 3 handled quantization. Done means offering a quantization level during MIDI import, recognizing tuplets, and supporting quantization of selected score sections.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.