musescore / musescore/MuseScore
Tracked changes
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
When collaborating on transcriptions and compositions, it would be beneficial to have a "Track Changes" feature. This functionality would allow incremental modifications to scores to be recorded, enabling users to discuss and address changes one by one. Changes, such as added or removed bars or notes, could be highlighted in color. I envision this as an equivalent to the "Track Changes" feature in Microsoft Word, which is useful for writing collaboratively with colleagues.
Problem to be solved
The challenge of collaborating on scores is that different versions can only be compared manually. Creating a list of changes outside of MuseScore software is tedious and prone to errors.
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 score model, notation editing, and version-comparison entry points, then determine the design needed for recording and displaying additions and removals. Done would require an agreed scope and a working Track Changes workflow for collaborative scores.
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
- Needs clarification
- Newbie friendliness
- 20/100