Skip to content

[Feature Request] Support for Numbered Musical Notation (Jianpu) rendering/export #34541

Description

@FreeCodeCampXYG

Your idea

Title: [Feature Request] Support for Numbered Musical Notation (Jianpu) rendering/export

Description

I would like to propose adding support for Numbered Musical Notation (also known as Jianpu in Chinese or Cipher Notation) as an alternative rendering/export format.

Why is this useful?

While staff notation is the global standard, numbered notation has unique advantages that complement MuseScore's mission of making music accessible:

  1. Lower Barrier to Entry: In many East Asian and Southeast Asian regions, numbered notation is the primary method for community music education, choral singing, and folk music. It allows non-professional musicians to read music intuitively without learning staff notation first.
  2. Movable-Do System Alignment: Numbered notation is inherently a movable-do system, which aligns perfectly with relative pitch training and transposition workflows. The numbers represent scale degrees directly, making key changes visually trivial.
  3. Compact Layout: For monophonic melodies and vocal scores, numbered notation is significantly more space-efficient than staff notation, reducing page count and printing costs for community ensembles.
  4. Existing User Base Demand: There is a large, active community of MuseScore users in China, Japan, Korea, and Vietnam who currently rely on separate, often outdated software for this workflow. Native support would consolidate their workflow into MuseScore.

Proposed Scope

I understand that implementing a full WYSIWYG numbered notation editor is a massive undertaking. A more feasible initial step could be:

  • A rendering layer that displays existing staff notation as numbered notation
  • An export option (PDF/PNG) in numbered notation format
  • This approach leverages MuseScore's existing internal data model without requiring a parallel editing engine.

Problem to be solved

在 MuseScore 中支持简谱,本质上是为了解决**“五线谱单一记谱体系无法覆盖所有用户场景”**这一核心痛点。具体来说,它解决了以下四个层面的功能缺失:

1. 解决“读谱门槛过高”的普及性问题

  • 现状: MuseScore 目前只有五线谱视图。对于大量通过社区、老年大学、合唱团学习音乐的业余爱好者(尤其在东亚地区),五线谱的学习曲线过于陡峭。
  • 解决后: 简谱以数字对应唱名(1=Do, 2=Re),符合直觉。用户无需重新学习音高位置,即可直接使用 MuseScore 进行打谱、播放和分享,将潜在用户群从“专业/半专业人士”扩展到“全民音乐爱好者”

2. 解决“移调与首调思维不匹配”的认知问题

  • 现状: 五线谱是固定调记谱。当乐曲移调时,音符在五线谱上的位置会完全改变,用户需要重新识谱。
  • 解决后: 简谱天然是首调唱名法。无论什么调,主音永远是“1”。移调只需更改调号标记,旋律数字完全不变。这完美契合了声乐排练、即兴伴奏等频繁移调的场景,解决了五线谱在移调时“视觉与听觉脱节”的问题。

3. 解决“单声部/声乐谱面效率低下”的排版问题

  • 现状: 对于纯旋律线或合唱谱,五线谱占用大量垂直空间(五条线+加线),导致每页能容纳的小节数少,打印成本高,翻页频繁。
  • 解决后: 简谱是紧凑型文本式记谱,垂直高度仅为五线谱的 1/3 到 1/2。同样的乐谱内容,页数可减少一半以上,极大提升了阅读连续性和打印经济性。

4. 解决“跨软件工作流断裂”的生态问题

  • 现状: 想用 MuseScore 的强大回放和管理功能,又必须用简谱的用户,被迫使用两套软件(如 MuseScore + EOP/JP-Word),中间需要通过 MIDI 转换,丢失大量表情、歌词、排版信息。
  • 解决后: 实现 “一份数据,两种视图”。用户在 MuseScore 内完成编辑、回放、管理,按需切换或导出简谱视图。消除了格式转换带来的信息损耗和重复劳动,让 MuseScore 成为真正的“一站式”解决方案。

📌 一句话总结

简谱功能不是要替代五线谱,而是为 MuseScore 补上一块 “面向非专业用户、首调思维、高密度排版” 的拼图,使其从一个“专业制谱工具”进化为一个“全民音乐创作平台”。

Prior art

其他应用是增加一个轨道,或者是借助五线谱自动转换下,目前是AI时代,可以考虑AI加上。

Additional context

暂无

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions