Arpeggio playback speed

• Jul 1, 2015 - 22:20

Hi!!!

I wonder why not to add an specific control to the playback speed of the arpeggios.

As an arpeggio is the fact to play a chord (more than one note) with a time shift from note to note, to control the arpeggio speed is to control how much time shifting should be between the notes.

It is absolutely independent from the rhythmic figure we are using to that chord.

With a guitar, for example, we can use a whole note chord (C - E - G - C, for example) but we can play the arpeggio effect with a long time (too slow) cadence or with, the opposite, a very short time (too fast) rift.

So, Why not to add this Arpeggio Playback Speed Control, please? ???

BTW: There are specific marks to the guitar chords I can't find into MuseScore. I'm talking about the mute stop (to stop the sound with the hand opened) and others like: hand down, hand up, etc. Where are those signs? ???

Greetings!!!

Juan


Comments

In reply to by Xianyue賢越

As a guitarist, I too am interested in the playback speed of arpeggios - especially to make them sound as a strum.

Perhaps you know of a workaround like this:

In your Humoresque example, for the purpose of playback, you can add another treble clef - with 'faster sounding' arpeggios - and make that staff invisible. Then, via the inspector, simply make the 'slower sounding' arpeggios silent.

Play back the attachment, and open menu item: Edit -> Instruments to toggle the invisible staff.

Regards.

Attachment Size
3-04 Humoresque - Copy2.mscz 11.55 KB

In reply to by Jm6stringer

As a violinist, I use musescore a lot to make piano ACC, thanks to Musescore team, it's a wonderful software.

Just opened the one you edited, thumbs up! it sounds much better, now the full score is just finished. it's going to take a long to do these short 1/32's ......

Thanks! it solves the need now, hope to see musecore 3.0 let us set its speed.

Attachment Size
3-04 Humoresque.mscz 43.58 KB

In reply to by Xianyue賢越

Nice job!

I see you have written for two pianos - the 'real' one, and a 'fake' one; and then muted the 'real' one in the Mixer.

Here's a suggestion...
To save work, enter only the part you need for correct arpeggio playback. Since it is in the treble clef, only one extra staff is needed for the 'fake' piano - and only where necessary.
So...
Enter notes only where you want the 'fake' piano to play. Then
select those measures - treble clef only - with the bad (slow) arpeggios (i.e. the real piano) and; in the Inspector, click the Notes tab at the bottom, then untick the Play button for those measures. No need to mute anything in the mixer, and no need to copy the entire score onto two 'fake' piano staves.
Then in menu item: Style / General / Score, you can hide the empty measures for the 'fake' piano.

Additionally, you can make the entire 'fake' piano staff invisible using menu item: Edit / Instruments - e.g. for printing the score.

See attachment.

Regards.

Attachment Size
3-04 Humoresque - Copy3a.mscz 43.87 KB

In reply to by Xianyue賢越

You wrote... it’s very time consuming...

Actually, in your Humoresque score, there is basically a three measure phrase (of which two measures, the 1st and 3rd, are identical). As you know, the notation has to be tweaked for satisfactory playback - and then placed in a 'fake piano' treble staff. Once that phrase is created, a mere copy/paste can be used wherever the phrase repeats. That's one reason why I replied to your post... it is simple enough.

However...
I do realize that the piano staccato/arpeggio effect is absolutely necessary here for the feel and spirit of the playback.
Also, a different score might not be so repetitively simple, so I do indeed support arpeggio speed control.
Until then, we will have to be content with 'workarounds' to achieve our playback goals. (Insert MuseSore mantra here - i.e. MuseScore is primarily a notation...)

But...
The good news is that arpeggio playback made it to the issue tracker:
https://musescore.org/en/node/113051
so we wait...

BTW:
Indeed, the 'hide and seek' part of MuseScore is the very reason score attachments are often required to aid users here. The many settings (which are hidden in a 'picture' of the score) are only accessible in the actual .mscz file. In your particular Humoresque example, especially for printing, the 'fake' piano would be made invisible via Edit / Instruments.

Regards.

Don't forget about the offset editing in the pianoroll editor available upon right-clicking a measure.

At any rate, it might be nice to have the execution timing of arpeggiated chords be accessible via the inspector as an evenly divided percentage of the chord's note-duration, or something similar, rather than resorting to manipulating the P.R. Editor's OnTime values. . .

Two years now, yes indeed, but not bad for two years.

So, what's it all about... playback... or bug fixes?

MuseScore 2.0.2 was released July 16, 2015. The release notes show approximately 100 bug fixes, along with miscellaneous items like new templates - in addition to palette and UI improvements.
Playback improvements included tremolo rendering, realization of trills (and other ornaments) and FluidR3 soundfont improvements.
See:
https://musescore.org/en/developers-handbook/release-notes/release-note…

MuseScore 2.0.3 was released April 6, 2016. Release notes show approximately 140 bug fixes, 15 UI improvements, 22 MusicXML import/export fixes, 9 Tablature fixes, among other tweaks.
Playback tweaks show 8 bug fixes and 5 assorted improvements.
See:
https://musescore.org/en/developers-handbook/release-notes/release-note…

MuseScore 2.1 was released May 2, 2017.
Top new features included the new note input modes, improved Zerberus support, clipboard "Swap" command, plus more than 20 others.
The release notes also show more than 130 user interface, score layout, and bug fixes.
Playback improvements list 15 fixes (in addition to the Zerberus support).
See:
https://musescore.org/en/developers-handbook/release-notes/release-note…

So...
The mantra, it seems, still holds: MuseScore is primarily a notation software (i.e. to produce musical scores readable by human musicians) and that playback, while implemented, is a secondary priority.
That is not to say the devs have abandoned this particular issue. It's in the tracker:
https://musescore.org/en/node/113051

I, personally, thought TABs, fretboard diagrams, (even the improved chord symbol parser) was icing on the cake. (Apparently the sweet tooth is not fully satisfied.)
Given the workaround discussed here (and the piano roll editor mentioned as alternative), I can wait.

Carry on, MuseScore devs!

Regards.

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