musescore / musescore/MuseScore

[musicxml] problem importing rests in multiple voices from Finale

Open
#24,971 5 comments 0 reactions 1 assignee View on GitHub

@miiizen is already working on this.

Since Oct 1, 2024.

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

Description

Issue type

Import/export issue

Description with steps to reproduce
  1. Import the attached test-mvrest.musicxml file into a new MuseScore document
  2. See that the rests do not appear on the specified staff lines in the xml file.
Supporting files, videos and screenshots

Here is a screen shot of the original Finale file:

Screen Shot 2024-09-29 at 8 50 37 PM

These are floating rests in their default position.

Here is a screen shot of the xml file imported into MuseScore:
Screen Shot 2024-09-29 at 8 52 11 PM

The xml file specifies F5 for the V1 rests and E4 for the V2 rests. Ideally these would also be the default position in MuseScore, but I can't figure out how to import an xml with the rest style default set to 2 space offsets. (Please let me know if there is a way.)

[EDIT: I figured out how to import with 2 space offsets: set the default style in MuseScore Preferences.]

If I select all the rests and restore them to their default positions along with changing the rest style to 2-space offsets, then they look like the original. My goal is not to have to do that manually everywhere the situation arises.

The xml file (zipped).

test-mvrest.musicxml.zip

What is the latest version of MuseScore Studio where this issue is present?

MuseScore 4.4.2

Regression

I was unable to check

Operating system

macOS 12.7.6

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

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.