musescore / musescore/MuseScore

Dialogue for Export MIDI: Please explain 'RPN'

Open
#17,399 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

Problem:
In order to understand the 'RPN' option in the MIDI dialogue, I had to search around quite a bit on the web to find an explanation of this term, and even then (see below) I am not much the wiser.

There is scope for the dialogue to be more helpful here, as I suspect many other people won't know either.

The text should read something like
"[] Include the RPNs (Registered Parameter Numbers). For advanced users of MIDI."

The reason it would be 'advanced' is clear if we look at the parameters currently registered with the IMA (whatever that is 😆):
0x0000 – Pitch bend range
0x0001 – Fine tuning
0x0002 – Coarse tuning
0x0003 – Tuning program change
0x0004 – Tuning bank select
0x0005 – Modulation depth range

Whew!

Ref:
https://www.recordingblogs.com/wiki/midi-registered-parameter-number-rpn

Proposal.
The text should read something like
"[] Include the RPNs (Registered Parameter Numbers). For advanced users of MIDI."

Problem to be solved

The user will not be left unsure whether or not they should have ticked this box.

Prior art

No response

Additional context

A related post is:
Additional text for MU4 User Manual: File export / File formats / MIDI format #17400

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

Start by locating the Export MIDI dialogue and its RPN option. Update the option text to explain “RPN” as “Registered Parameter Numbers” and identify it as intended for advanced MIDI users, then verify that the dialogue makes the checkbox choice clear.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.