Add Glissando playback style portamento
Priority
P2 - Medium
Type
Functional
Frequency
Many
Severity
S5 - Suggestion
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
Some instruments (such as vocals) are able to perform a glissando as if it were a long pitchbend/slide between two notes.
Current workaround for playback purposes (using a hidden bend) only works for intervals of up to 3 tones and doesn't play well with tied notes ending with a glissando.
Fix version
3.6.0
Comments
referring to the current Bend implementation: https://github.com/musescore/MuseScore/blob/2.0.3/libmscore/rendermidi…
came up again: https://musescore.org/en/node/152496
Requested again at https://musescore.org/en/node/183576 (and I'm pretty sure several more times since the link in comment #2 above).
See this: #13811: Select playback method of Grace Notes, Arpeggio & Glissando and Articulations & Ornaments
And maybe call it "Continuous"
(Came up again in https://musescore.org/en/node/197321)
and again in https://musescore.org/en/node/197446
other possible names: 'slide' / 'smooth'
...and here:
https://musescore.org/en/node/202861
Came up again in https://musescore.org/en/node/238836
Came up again in https://musescore.org/en/node/260981
In reply to Came up again in https:/… by Jojo-Schmitz
One more: https://musescore.org/fr/node/267684
I support this entirely. Trying to get a trombone playback is a nightmare in this condition.
Came up again in https://musescore.org/en/node/270909
I was just about to suggest this exact feature again; I'm glad I came across this thread first. I like Jojo's idea of calling it "continuous" or Jeetee's "smooth," and I definitely can't wait for when (if) this gets implemented. The closest I've been able to get to a continuous glissando over a large range with multiple instruments (even trombones) is having them all leap by different intervals, forcing them to change notes at different times, creating a "mush" of changing notes. It sounds more or less continuous, but it also sounds like a mess.
not just trombones, but clarinet glissandi too.
Came up again https://musescore.org/en/node/274596
I'd like to add my support for this feature - as a fretless bass player this would be useful for making transcriptions sound more faithful.
I support this
In reply to I support this by iGotTwixNCaps
Came up again https://musescore.org/en/node/276693
In reply to Came up again https:/… by mike320
Came up again https://musescore.org/en/node/277149
came up again in https://musescore.org/en/node/281064
Related to #286108: [EPIC] Bends issues.
In progress but i won't open a PR until I get it working with midi export and along with bends so you can bend and gliss at the same time which would accommodate this: https://musescore.org/en/node/286107
Or #286107: Bends: change implemention of bend steps to "note-to-note" (not sp.)
See https://github.com/musescore/MuseScore/pull/4824
Shall we use the official Italian musical term?
The PR calls it "Continuous" though.
In reply to The PR calls it "Continuous"… by Jojo-Schmitz
Continuous is a mathematical term.
In reply to Continuous is a mathematical… by ♪𝔔𝔲𝔞𝔳𝔢𝔯 ℭ𝔯𝔞𝔣𝔱𝔢𝔯♪
or a laymans term.
But yes, I agree, portamento is the "correct" term and we should use it.
It needs to match the other options though. Which are "Chromatic", "White Keys", "Black Keys" and "Diatonic". So indeed maybe "Portamento" is a better fit than "Continuous", but maybe it needs a tooltp? (Internally the PR calls it portameto in many but not all places)
See further up, Continuous, smooth, slide were the terms discussed for this earlier.
Please! Please! I play trombone and am trying to arrange/compose pieces on Musescore for barbershop quartet as well. Portamenti are essential for both!
Came up on the Facebook usergroup as well https://www.facebook.com/groups/musescore/permalink/3605265529499739/
Came up again #117746: Continuous glissando (for any version)
I have seen people requesting the three usual types of glissando: pitch bend, chromatic, natural notes (or white keys)
Can I request for another type of glissando here? I feel that there should be an option for key-awared glissando.
For example: on a A major piece, you can play a F# to A downward glissando like this: F#, E, D, C#, B, A. They are basically the notes of the key.
Some wind musicians do that a lot, and I surprised that I don't see people mentioning about that.
I believe diatonic glissando is available already
This issue here though is about portamento or continuous glissando
Came up again in https://musescore.org/en/node/296078
Came up again in https://musescore.org/en/node/299066
and again in https://musescore.org/en/node/299447
Please add this.
Yes, I agree, would like to see this too. But the PR needs to get rebased first
Now (also?) https://github.com/musescore/MuseScore/pull/5853 (rebased version of @Michael Froelich's one)
There's an issue with the implementation: using an upwards portamento, if the highest pitch of such a portamento doesn't have a sound in the soundfont anymore (like C#7 or higher for Voice, Choir Aahs Expr.), the entire portamento doesn't sound. An 'normal' glissando though work in that case up to the highest available pitch (of course it drops those that are higher).
Not an issue for the same portamento downwards though, so it is just an issue with upwards and it's highest note
Test versions available, Linux (AppImage), macOS, Windows
In reply to Test versions available,… by Jojo-Schmitz
First test: test.mscz
Why with the portamento effect I don't hear First, the G, to arrive to the B (instead to hear: attack on a A, more or less, then portamento, and B) ?
To sum up: the effect must at least make hear the starting note clearly
In reply to Test versions available,… by Jojo-Schmitz
Mac link gives me 404.
Works for me, try again
In reply to Works for me, try again by Jojo-Schmitz
Still 404 for me
try https://github.com/musescore/MuseScore/pull/5853/checks?check_run_id=52… and then to the click on Artifacts and there on the dmg
See also #302937: Glissando portamento playback on 3.5-dev issues
So if this is where i can find out how to add a portamento style glissando, Can someone explain what i must do?
Edit: Nevermind, i found out it doesn’t yet
There could be the option to choose the portamento interpolation curve, as for SND. I.e.: linear, ease-in, ease-out, exponential, logarithmic.
According to James Thistlewood, there are built-in functions in
ChangeMap
that could be used.In reply to What you means by … by cadiz1
@cadiz1 Yes, that could be fixed if we have an option to choose the interpolation curve. "Ease-in, ease-out" or "ease-in" or also "exponential" would mostly produce better results than "linear", the only option available currently.
In reply to try https://github.com… by Jojo-Schmitz
Tried clicking CI_artifacts, saw the two files, but i couldn't seem to do anything with them.
One is a dmg for macOS, the other an AppImage for Linux. For Windows you'd need the 7z file from https://ci.appveyor.com/project/MuseScore/musescore/builds/31619603/art…
In reply to One is a dmg for macOS, the… by Jojo-Schmitz
No, I meant I couldn't download the files at all, i tried clicking, double-clicking, and my cursor didn't even change.
Which of them, Linux (AppImage), macOS, Windows ? All work for me
In reply to Which of Test versions… by Jojo-Schmitz
Mac and Linux both give 404s. Win tries but fails to download. The artifacts on the github page just sit there and do nothing no matter how many times I click them.
In reply to Mac and Linux both give 404s… by rohanarr
Those links do work for me. But I do have an account on github, maybe that is needed? Not on AppVeyor though, so the Windows build should download
> if the highest pitch of such a portamento doesn't have a sound in the soundfont anymore (like C#7 or higher for Voice, Choir Aahs Expr.), the entire portamento doesn't sound.
This has to do with how the portamento is calculated, I found it easier to use the second note and modify its pitch rather than using the first note. If there is no second note then I guess there's nothing to modify!
can anything be integrated soon? i need this
EDIT: i didnt mean that the workaround doesn't work just that i don't use forked builds; can anyone rewind this?
See https://github.com/musescore/MuseScore/pull/4824#issuecomment-613501871 for the issues that need to get fixed before we can integrate this
In reply to (No subject) by Jojo-Schmitz
What workaround? There is no workaround on this.
In reply to What workaround? There is no… by Ludwig van Benteuer
For small ranges 'up to 3.5 tones) there is a workaround; use a hidden bend.
FOR small ranges, only, for upwards bends, only. It has to be for the general case, though. No way this can be called a workaround in this scope. If I could even compile MS, I could try solving the issues with the current implementation of portamento.
In reply to There could be the option to… by Ludwig van Benteuer
Please, this is a must, it's been 3 years since the request.
In reply to Great idea by FranLegon
Didn't you see the pull report? It's in the beta from what i understand.
No, the PR has not been mergeed into any branch yet
Portamento would indeed be a lovely and useful feature. I appreciate the work being done on its behalf.
In reply to There could be the option to… by Ludwig van Benteuer
Rather that implementing multiple mathematical functions for interpolation, I'd rather go with a Bezier curve arranged as an ease-in, ease-out curve that can be parameterized to emulate any practical function.
Examples of such parameterized Bezier transfer functions as here:
Related to #311174: [EPIC] UI/UX issues and suggestions
In term of UI/UX. I thought of something like the following:
The ease-in and ease-out should be applicable whatever actual underlying glissando or portamento. The example shows a portamento on a fretted instrument where each fret holds the pitch for a very short while.
I wanted to mention that I would like to implement this parameterable ease-in, ease-out Bezier-based function once Michael Froelich PR is merged.
In reply to In term of UI/UX. I thought… by ypoissant2
I look forward to the implementation of the proposed function!
In reply to One is a dmg for macOS, the… by Jojo-Schmitz
The artifacts have expired on Appveyor. Would you mind re-uploading them?
Please don't change the title to something entirely meaningless and unrelated to the issue at hand.
Then see the updated artifacts at https://github.com/musescore/MuseScore/actions/runs/80675831 and https://ci.appveyor.com/project/MuseScore/musescore/builds/32248924/art… (those will expire in 3 days)
Edit: new ones are being built as we speak...
Edit 2: Windows, Mac, Linux
Fixed in branch 3.x, commit cf03d9a4ee
fix #127341: implements portamento for fluid
Fixed in branch master, commit f3fcf67510
fix #127341: implements portamento for fluid
Any updates on this? I was just thinking this would be useful for the trumpet, which has a half-valve technique.
It will be in 3.6 once that gets released, and is in the development builds already
Automatically closed -- issue fixed for 2 weeks with no activity.