musescore / musescore/MuseScore
"Regroup rhythms" causes AccessibilityController "Inconsistent state for item" errors
Open
@Eism is already working on this.
Since Aug 7, 2026.
cli
P1
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Other type of issue
Description with steps to reproduce
- Run MuseScore from the command line
- Open any score (even a brand new score with one instrument)
- Use "Regroup rhythms"
The console gives an error message for (I think) every single chord/rest in the whole piece. For a big piece it's thousands of lines of errors.
22:06:28.499 | INFO | main_thread | ActionsDispatcher::doDispatch | try call action: reset-groupings
22:06:28.500 | ERROR | main_thread | AccessibilityController::stateChanged | Inconsistent state for item: "Rest Bar, Bar 1 Beat 1"
22:06:28.501 | ERROR | main_thread | AccessibilityController::stateChanged | Inconsistent state for item: "Rest Bar, Bar 2 Beat 1"
22:06:28.501 | ERROR | main_thread | AccessibilityController::stateChanged | Inconsistent state for item: "Rest Bar, Bar 3 Beat 1"
...
Repeating the action causes the same output again.
The same happens when calling cmd("reset-groupings") directly from within a plugin.
Supporting files, videos and screenshots
In which versions of MuseScore Studio is this issue present?
OS: macOS Sequoia (15.7.7), Arch.: arm64, MuseScore Studio version (64-bit): 4.7.4-260706075, revision: github-musescore-musescore-7688c00
Regression
I was unable to check
Operating system
macOS
Additional context
No response
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
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.
Assessment
This issue has not been assessed yet.