play trills

• Mar 6, 2011 - 23:48

i think it would be really awesome if musescore could play trills instead of ignoring them


Comments

The problem is that there are many different interpretations of how trills should be played, so the software developers (thus far, and as far as I understand it) have decided to avoid the issue. Therefore MuseScore doesn't play back trills.

In reply to by Cortney M

It should just play both voices normally. Most likely, you'd want it not to play the notes that are for display only, so you could set their velocity to 0 (right click, Note Properties).

I'd agree that some sort of automatic playback for trills and other ornaments would be nice, but no automatic facility is likely to do exactly what one wants. So overall, if you really care about the results, using the type of approach I mention is usually better.

However, MuseScore could do a couple of things to make my suggestion work better. Right now, entering hidden notes for playback in another voice affects stem directions in the visible voice. I had already submitted that to the issue tracker (well, regarding hidden rests). And creating a separate staff for playback is awkward since a staff can't be completely hidden so it doesn't even take room in the layout. Plus you'd need one playback staff for each part in a score, since a staff can't change instruments mid-stream. Looks like the next major release will allow this, though - I just noticed that feature in one of the recent nightly builds!

In reply to by [DELETED] 5

Done. At least, I created the entry using the same format as the others. It looks like there in an ID tag so one can link directly to each entry, but I didn't see an actual index that contains these links.

BTW, I saw a few things in there that could use a little cleanup, so I'm going in and doing that too.

In reply to by [DELETED] 5

The velocity property of a note controls how loudly the note is played. This usage of the term comes from MIDI syntheiszers. On a keyboard instrument, it is the speed with which a key is pressed that controls its volume. The usual scale for velocity is 0 (silent) to 127 (maximum)

In reply to by Marc Sabatella

Non no no! Velocity is NOT the same as volume in MIDI!

Velocity is how hard the note is attacked - which equates to volume on a piano.

Volume is the sound level assigned to a channel.

The actual loudness of the note on instruments like strings, woodwind and brass is controlled by the Expression controller.

Unfortunately MuseScore currently does not use the Expression Controller, although it is possible to assign it in the Instruments.xml file.

In reply to by Jojo-Schmitz

What did I claim to have done? When did I claim it? Above (a long tome ago!) I said I'd add an entry for velocity, and it's there, at least for me in the English version.

Anyhow, while it is true that for *some* MIDI instruments (breath-based controllers mostly, I assume) the expression controller might be used in this way, the fact remains that for most of the history of MIDI, most instruments (eg, virtually all keyboards and drum pads) have used velocity as the one and only means of controlling volume. So MuseScore is not even slightly unusual in this respect. Maybe it *should* be otherwise, but it is what it is. So I don't see any sense in changing the glossary; it reflects the reality right now.

In reply to by Marc Sabatella

Yes it is there, but as per http://musescore.org/en/node/18570/revisions it wasn't you having added it?
Hmm, now I seem to rememberthat once we had to recover that file, I think after a bogus attempt of a translation, guess the history got lost then?
You said to have added it on March 9, 2011, looking at the history shows I created it October 19, 2012 ... so it seems I remember correctly (more than 2 years later, mind you ;-))

Anyway: it does say:
Velocity The velocity property of a note controls how loudly the note is played. This usage of the term comes from MIDI syntheiszers. On a keyboard instrument, it is the speed with which a key is pressed that controls its volume. The usual scale for velocity is 0 (silent) to 127 (maximum).

And this mention of 'volume' is what seems to need correction?

In reply to by Jojo-Schmitz

I don't remember anything about having to recover the file, but obviously the history *is* wrong - I definitely went in and did some fairly significant cleanup. I don't specifically remember adding the velocity entry, but I said I would, and it's there now, so I'm going to assume I did :-)

Anyhow, it's true that there is more to the picture than velocity = volume. But it really is that simple in MuseScore and most keyboard or drum controllers, for better or for worse. If this were a general primer on MIDI, there could definitely be more detail explaining the alternate implementation used by breath-based controllers and probably some other software as well. But I would be concerned that it would be misleading to MuseScore users until such a time as MuseScore actually implements any of this. As it is right now, velocity really does control volume; sdaying otherwise would be a lie.

In reply to by jim.newton.562

The picture above shows how you can re-display it if for some reason you had closed it; but it should come up by default, I think. It's how you do almost anything that formerly required dialog boxes - setting notes invisible or stemless, adding extra leading/trailing space, changing line properties, etc.

In reply to by rj45

Why not at least support the most common interpretations, then? Right clicking on the trill could offer an additional context menu item that would provide a customization window. There could be a check-boxes for whether or not the auxiliary should be played first and whether or not the penultimate note should be lowered a la baroque. The speed of the trill and the interval of the auxiliary and penultimate notes could be user specified, and/or determined by the current key signature. Should the user not want trills (or would rather provide a specific, uncommon implementation), there would be an option to disable effect playback.

In reply to by Brock Allen

For what it's worth, I'd like to give my opinion about how this should be implemented. A trill should have a type/play-style. There should be some default styles and the user should be able to create new ones. The style should define several play aspects of the trill.
1. which note the trill starts on. i.e., half step above, whole step above, half step below, whole step below, note above in the scale, note below in the scale, or on the note itself.
2. which note the trill ends on.
3. total trill duration. e.g., a trilled quarter note might only trill for half the duration of the quarter note or the total duration of the quarter note
4. the note value of the trill, e.g, a trilled quarter note might be played as 16th notes or 32nd notes etc.
5. which note within the trill is accented?

All of these attributes of the trill could also be entered by entering a corresponding score to play. However, for a few simple rules defining for example a baroque trill the system should be able to figure out what a baroque trill quarter note A, vs a baroque trill eighth node D#.

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