Regarding Github development triage (Len property, Piano Roll Editor Velocity)

• May 11, 2024 - 00:14

Because playback is import to me I can't imagine doing any serious work in MuseScore Studio until it supports
LEN and note Velocity properties as well as MuseScore 3 does. That is:

• Velocities working with MuseSounds and other VSTs
• and LEN properties function with MSBasic, MuseSounds and other VSTs

So I'm quite curious. What does it mean when a regression is added to the 4.x SHORTLIST?

The LEN property issue is tagged Priority 2 in the SHORTLIST... but it's not currently part of the 4.4 Project.

I'm wondering if the SHORTLIST is lower priority than the 4.4 Project. Anyone know?

scorster

  
UPDATE 2024-06-11 = = = = = = = = = = = = = = = =

The LEN property issue is now in Github's MuseScore Studio Backlog

I'm interested to know if that means it's been promoted or demoted in priority.

scorster

Comments

• Oct 10, 2024 - 07:09

Here's another example of guitar realism that demonstrates why the LEN property, the Piano Roll Editor, and Velocity are essential to my workflow ... which is why I can't create or advance my work in MS4.0 thru MSS4.4.2:

     https://audio.com/audius/audio/spike-driver-blues

I initiated my solo finger-picking arrangement of Spike Driver Blues in MuseScore 3.6 and 3.7, where I processed play durations with the TAB Ring plugin. Unfortunately—because MS3.7 and earlier releases don't support VST sound libraries—I had to export to MIDI for mastering in Logic Pro. (The guitar used is Picked Nylon by Native Instruments.)

Note that the LEN properties imparted via TAB Ring are the ingredients that make projects like this sound so realistic. And TAB Ring yields durations far superior and far more manageable than can be accomplished with Let Ring / Laissez Vibrer.

Ideally I'd have been able to master the sound file in MS 4.4.2—afterall it supports Picked Nylon via Kontak.

That would be possible if not for the limitations listed above:

     • In MS 4.4.4 LEN properties are ignored
     • LEN is not exposed to plugins
     • the Piano Roll Editor is still MIA out-of-commission, which may cause the prior point.
     • velocities entered in 3.7 or earlier are trashed.

With regard to playback fidelity and finesse these limitations have been a longstanding and serious step backwards. Every notation app I've used distinguishes between the duration expressed by a note's face value, and a "play duration" which can be significantly longer or shorter than the face value, in exactly the ways that a guitarist might interpret guitar notation.

It was a proud day when MuseScore wisely appealed to a large guitarist market with MuseScore 4.2 which included some significant improvements for guitar. I hope soon we see a similar follow up that addresses the issues mentioned here.

scorster

Reply

• Dec 17, 2024 - 20:29

Today I noticed that development moved the restoration of Let Ring was into the MuseScore Studio 4.5 project:

    https://github.com/musescore/MuseScore/issues/20993#issuecomment-254824…

... and within the same day it passed checks and was approved:

    https://github.com/musescore/MuseScore/pull/25864

This is a well needed functionality, revived after a painful regression that occurred two years ago on the release of MuseScore 4.

However, while Let Ring suffices on pieces that are largely pure arpeggios, Let Ring tends to add too much sustain on more sophisticated counterpoint compositions, resulting in dissonant 2nds, 4ths and 7ths.

In contrast, the Let Ring Plugin (for v3.7 and 3.6) wisely works its way around those issues, and allows you into the "play duration" decision making process.

Viva Lassiez Vibrer! But PLEASE:

     • expedite the recognition of the LEN in MuseScore Studio
     • restore the Piano Roll Editor

Reply

Do you still have an unanswered question? Please log in first to post your question.