musescore / musescore/MuseScore
Feature Request: JSON Message Support for Stream Deck Integration
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Your idea
Hi MuseScore Team,
First of all, thank you for your incredible work on developing and maintaining MuseScore — it's an essential tool for so many of us in the music community.
I would like to propose a feature request regarding Stream Deck integration. Currently, many power users and professionals rely on Elgato Stream Deck to streamline their workflows. While some basic key command triggers are possible, the level of integration is limited due to the lack of native support for JSON message communication.
Implementing JSON-based messaging or an accessible API that can send and receive structured data (such as triggering specific actions, reading score state, switching modes, etc.) would open the door for deep integration with the Stream Deck and similar tools. This would not only enhance productivity for composers, arrangers, and educators but also make MuseScore more accessible to those with specialized workflow needs.
Use case examples:
Triggering layout or engraving actions with a single button.
Real-time score navigation.
Mode switching (note input, playback, selection tools) with visual feedback.
Executing plugins or custom commands with JSON payloads.
This feature could be incredibly powerful, especially when paired with Stream Deck profiles and dynamic button states, helping MuseScore appeal even more to professional and studio users.
Is this something that could be considered for future development?
Thanks for your time and for listening to the community's ideas!
Best regards,
İlkay Bora Öder
Composer / Orchestrator / Engraver
Problem to be solved
Connection with a devide Called Streamdeck
Prior art
No response
Additional context
No response
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the existing Stream Deck or key-command integration, then define the scope of a JSON messaging or API layer, including which actions and score state it must support. Done means an agreed interface enables structured commands and responses for the described workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100