Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Len property values ignored when opening a MuseScore 3.6/3.7 file in MuseScore 4 #20994

Open
scorster opened this issue Jan 13, 2024 · 3 comments
Assignees
Labels
P2 Priority: Medium playback General playback issue regression_ms3 Regression from MS3 (3.6.2)

Comments

@scorster
Copy link

scorster commented Jan 13, 2024

Issue type

Import/export issue

Bug description

On opening MS3 scores MuseScore 4 ignores the Len property duration edits made in the MS3.x Piano Roll Editor.

Related: There's no good reason for 3.6's hardcoded 2K upper value limit for the Len property (located in the upper right of the PRE panel.) This has been addressed in MuseScore 3.7 (aka MuseScore 3 Evolution) where the value limit is now 60K. The removal of the 2K limit allows the TAB Ring plugin to work in MuseScore 3.7.

Steps to reproduce

• Create a musescore 3 score
• Add four quarter notes
• With the notes selected open the Piano Roll Editor
• Decrease the Len value by 50% so the the quarters will play back sounding as eighths
NOTE: The Len property is located in the upper right corner of the Piano Roll panel
• Save the score
• Open the score in MuseScore 4
Result: You'll hear the notes playing as regular quarters, not as they did in 3.x

MuseScore Version

MuseScore 4.2

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

MacOS 13.5.2

@muse-bot muse-bot added the regression_ms3 Regression from MS3 (3.6.2) label Jan 13, 2024
@scorster scorster changed the title Len property values ignore when opening a MuseScore 3.6/3.7 file in MuseScore 4 Len property values ignored when opening a MuseScore 3.6/3.7 file in MuseScore 4 Jan 13, 2024
@XiaoMigros
Copy link
Contributor

Actually these values are not ignored when importing, as they are still present in the musescore 4 file. they simply dont affect playback.

@scorster
Copy link
Author

scorster commented Jan 13, 2024

Thanks for you reply XiaoMigros.

It's quite a relief to know that MuseScore 4 is indeed reading Len values, but it simply doesn't apply the affect during playback.

Since MS4 has no Piano Roll Editor I was unable to see if the Len values were imported and I feared that MS4 was discarding them and that any imported 3.x scores would permanently loose carefully constructed Len values.

I hope this is an easy fix.

With Len playback repaired, and the return of note velocities (Particularly Offset velocities included at import and used during playback), I would definitely take a more serious look at MuseScore 4.

@XiaoMigros
Copy link
Contributor

Offset velocities are converted to absolute velocities on import, and they do affect playback. The user/offset system has been replaced with something more uniform, but imported scores should sound the same in this regard (and the new system is just as versatile as the old).

@bkunda bkunda added the playback General playback issue label Jan 16, 2024
@bkunda bkunda added this to To do in 4.x SHORTLIST via automation Jan 16, 2024
@bkunda bkunda added the P2 Priority: Medium label Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Priority: Medium playback General playback issue regression_ms3 Regression from MS3 (3.6.2)
Projects
4.x SHORTLIST
  
To do
Development

No branches or pull requests

6 participants