Glissando Playback
Would be possible for the developers of MuseScore to make glissando playback. E.G.: If I placed a glissando then go to the inspector, I should have three options for playback: a pitch bend option (for things like synth or violin; chromatic (for piano mimicking pitch bend), or natural notes A.K.A. white keys (for piano). I would appreciate that if it was implemented into MuseScore.
Comments
Yes, indeed. Wait a few days until MuseScore 2.0.2 is released—it's implemented. ;-)
In reply to Yes, indeed. Wait a few days by Isaac Weiss
Awesome! Only a couple of days? Wow! What day, will the Glissando have options like I said, or just something like a piano run?
In reply to Awesome! Only a couple of by David McCaulley
Guitar bends are notated with a totally marking - see the last items in the Articulations & Ornaments palette. They will play using bend as they should; glissandi will play as distinct pitches as they should.
In reply to Awesome! Only a couple of by David McCaulley
As to what day exactly, I haven't heard, but it's imminent. As to the options:
In reply to As to what day exactly, I by Isaac Weiss
An option that uses the notes with accidentals should added for instruments like harp.
In reply to An option that uses the… by ♪𝔔𝔲𝔞𝔳𝔢𝔯 ℭ𝔯𝔞𝔣𝔱𝔢𝔯♪
How is that different from chromatic?
In reply to How is that different from… by Jojo-Schmitz
Chromatic plays every note. Diatonic, as you know, plays by the key signature. Including accidentals would allow the user to make for example an F# in the key of Bb (thus making the key signature G minor) and the accidental should be honored in all octaves of the glissando. It is not uncommon for accidentals to appear in a glissando in harp music. The notes of the glissando are notated in the first octave, the glissando line is then drawn to the end note, or possibly the last 2 or 3 notes. This will not currently play back correctly.
In reply to Chromatic plays every note… by mike320
Ah, I see, thanks for explaining. So this is basically a custom gliss.
In reply to Ah, I see, thanks for… by Jojo-Schmitz
IMHO they are common enough to justify including.
The new glissando/slide sounds all wrong, at least in guitar scores. The default chromatic version just plays a chromatic scale slowly between the indicated notes: nothing like a guitar slide at all, which is faster and doesn't emphasise the intermediate notes.
For guitarists, the new slide means that they have to turn off playback in the Inspector each time it is applied. Shouldn't playback be set to "off" by default?
In reply to The new glissando/slide by geetar
I wouldn't turn it off by default. I'm sure there are a lot of coding guitarists out there but so far nobody stood up to fix the challenges we have for guitars (harmonic notehead, playback, proper slide playback, better rendering of bend and so on...). Hopefully MuseScore 2.0.2 will be good enough to attract more guitarists and let them discover itches they want to scratch :)
In reply to The new glissando/slide by geetar
You can of course turn them off all at the end at once by right clicking one, Select / All similar elements, and then going to the Inspector.
FWIW, glissando can be used for multiple purposes; guitar slides is not the only or even main one. No sense disabling playback of glissando just because it isn't ideal for *all* of the purposes it might be used for.
In reply to The new glissando/slide by geetar
The glissando playback in Chromatic mode, indeed plays a chromatic scale between the indicated notes. And in fact, it plays all the notes with equal time allocation. It would of course be possible to enhance the glissando to add a property that indicates how much time the run should take, and in that case all the remaining time would be allocated to the final note.
If someone would like this enhancement, please let me know. I'd need a better description of exactly what the user would like to specify interactively. For example, if you specify a time in seconds/miliseconds, it might not work if you change the tempo of the piece. If you specify it as a percentage, it might be more intuitive. In any case please let me know.
In reply to The glissando playback in by jim.newton.562
My general expection for glissando is that it take the final 25% or so of the first note's duration. That is, the following:
should sound more or less like this:
In reply to My general expection for by Marc Sabatella
You're absolutely right about THIS kind of "Glissando". But, there are a lot of another "glissandi", most (my opinion) should be played by MuseScore as a continous blend instead a separate group of individual notes.
BUT... It's an absolutely instrument dependent issue (not all the instruments reacts the same way). So, I think there isn't an "easy solution" to the programmers.
Whatever, I very thanks the team for all those sensational improvements!!!!!!!
Juan
In reply to You're absolutely right about by jotape1960
Yes, bends (aka portamento) are a totally separate issue, and there is playback support for them when using the guitar bend notation. There are also "slides", but no playback support for these yet. Glissandi are meant to imply playing separate notes, but for the relatively few instruments capable of playing bends, eventually it would be good to have playback support for that as well indeed.
In reply to The glissando playback in by jim.newton.562
Yes please, I'd love this addition! I agree with Marc that any adjustable delay before the gliss begins would probably be best expressed in terms of percentages.
2.0.2 is out now, available from the download page or at MuseScore 2.0.2 is released , and it is fabulous! ;-)
I'd like to second the suggested enhancement to gliss playback. The current gliss is often not fast enough for guitar slides.
In reply to I'd like to second the by geetar
Do we only need a pre-delay, or do we also need a post-sustain ? They are both the same level of difficult/ease to implement, and if we need them both we might as well add them at the same time.
In reply to Do we only need a pre-delay, by jim.newton.562
I can't imagine a use case for the post - in my experience, glissandi always reach the target note when notated; the only questions is how long you wait before starting. Doesn't hurt to add support it I guess, but it seems a bit of unnecessary clutter in the UI. Eventually, it would be good to full completely control of playabck of all of these markings via pianoroll editor or some such. Until then, I think the pre-delay is all the control one would ordinarily want.
In reply to Do we only need a pre-delay, by jim.newton.562
So for clarity's sake, has a pre-delay been implemented? And since I just discovered there's a "nightly" version (about two minutes ago), I have to ask which build this discussion is referring to.
In reply to So for clarity's sake, has a… by Bushy the Bush…
Whoever you responded to would probably not remember which nightly they were referring to since they spoke of it 3 years ago. There have been at least 2 releases and several nightlies a day built most days since then.
In reply to Whoever you responded to… by mike320
Sorry, my question was really just if it was a release or a nightly, if it was implemented at all. Thanks for the response though!
In reply to Sorry, my question was… by Bushy the Bush…
Since it is not obvious who you were talking to, what is the question you wanted answered, perhaps I or someone else can answer it for you now. BTW, sorry if I sounded rude.
In reply to Since it is not obvious who… by mike320
My question was for jim.newton.562. He said, "Do we only need a pre-delay, or do we also need a post-sustain? They are both the same level of difficult/ease to implement, and if we need them both we might as well add them at the same time," so I was under the assumption that he was working on it, or at least knew who was working on it. (He had also said to someone else, "I didn't implement a slide. All the modes I implemented were all subsets of the chromatic scale.") I figured he would know where it was implemented, if at all.
The original question I wanted answered was just if there was any version that had the pre-delay (and which one, if any).
In reply to My question was for jim… by Bushy the Bush…
Hi Bushy, I haven't looked it this is a long time. I've not even tried to compile musescore in a long time. Do you need me to look into this? I may have some time in the coming weeks.
In reply to Hi Bushy, I haven't looked… by jim.newton.562
No, it's not a necessity by any means. I just wanted to know if I would be able to find functionality for it somewhere before I spent hours looking around. It would be really nice, but you don't need to do anything just for me. I really appreciate the offer, though!
It sounds like there was a enhancement made to make Glissandos sound more like a slide than a scale climb in Musescord 2.0.2. I have Musescore 2.0.3 and I do not see a way to do this. Any help would be appreciated! I'm interested in glissando's for strings.
In reply to It sounds like there was a by LStuart
I didn't implement a slide. All the modes I implemented were all subsets of the chromatic scale.
In reply to I didn't implement a slide. by jim.newton.562
This is very much instrument-dependent, as has been already noted. I am using glissando for strings (viola and cello in my case) and this implementation is entirely unsatisfactory. A string gliss covers all the pitches between starting and ending notes. If a composer wants a fast chromatic scale run on strings, s/he will generally just write out all the notes. A glissando is a completely different effect. It would be nice if I could notate my music as I wish and have it play back as I intended.
In reply to This is very much instrument… by nleduc
There's a feature request outstanding on this, see #127341: Add Glissando playback style portamento
Edit: meanwhile implemented
Musescore should redo the trombone glissandi reflect the real sound of a trombone gliss with the smooth movement between notes.
In reply to Musescore should redo the… by oboeboiboi
Did you try the portamento option in the Inspector? Not perfect, but about as good as basic MIDI is capable of. For better results we'll probably need to move beyond that, as MuseScore 4 is looking to.