-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MU4 Issue] Pedal playback not working for "pedal change" #12869
Comments
Bump - could this get prioritized? @Tantacrul - easily reproducible in any score using pedal change. |
Yeah, I've been noticing this myself too. |
FWIW, this is now the only significant issue remaining with "Reunion" - https://musescore.com/user/2975/scores/39069 |
Just had a call with Vasily an hour ago, where we placed this issue in our top 3. Won't be much longer |
I'm still having issues with pedal changes on this front, particularly when migrating from old versions of MuseScore. Notes are cut off early, general playback with MS Sounds is unreliable and unclean. Every once in a while a note goes max velocity as well. I can send example files but the songs are copyrighted so I'll have to email them or send them through other means. Just installed MuseScore 4 as of writing, using v1.0.0. |
This immediately fixes musescore#16757, which occurred when a chord right after the end of a pedal line was counted as intersecting its duration. This commit also reverts the subtraction by `Constants::DIVISION / 4` for the duration of a pedal line ending in an angled hook. This subtraction was introduced in order to fix musescore#12869, but it has caused other issues such as musescore#16757 and is probably unneeded given the fix to `isPlayable`.
This immediately fixes musescore#16757, which occurred when a chord right after the end of a pedal line was counted as intersecting its duration. This commit also reverts the subtraction by `Constants::DIVISION / 4` for the duration of a pedal line ending in an angled hook. This subtraction was introduced in order to fix musescore#12869, but it has caused other issues such as musescore#16001 and is probably unneeded given the fix to `isPlayable`.
This immediately fixes musescore#16757, which occurred when a chord right after the end of a pedal line was counted as intersecting its duration. This commit also reverts the subtraction by `Constants::DIVISION / 4` for the duration of a pedal line ending in an angled hook. This subtraction was introduced in order to fix musescore#12869, but it has caused other issues such as musescore#16001 and is probably unneeded given the fix to `isPlayable`.
This immediately fixes musescore#16757, which occurred when a chord right after the end of a pedal line was counted as intersecting its duration. This commit also reverts the subtraction by `Constants::DIVISION / 4` for the duration of a pedal line ending in an angled hook. This subtraction was introduced in order to fix musescore#12869, but it has caused other issues such as musescore#16001 and is probably unneeded given the fix to `isPlayable`.
This immediately fixes musescore#16757, which occurred when a chord right after the end of a pedal line was counted as intersecting its duration. This commit also reverts the subtraction by `Constants::DIVISION / 4` for the duration of a pedal line ending in an angled hook. This subtraction was introduced in order to fix musescore#12869, but it has caused other issues such as musescore#16001 and is probably unneeded given the fix to `isPlayable`.
Any progress with this? It seems like a pretty basic thing. And how do you include the "Ped." text symbol at the beginning of the extended line? |
The issue reported here was fixed a year ago, which is why this issue is marked “closed”. If you are having issues using a current version of MuseScore, that is probably something different. Please open a new thread and ZIP and attach the score you are having trouble with and give precise steps to reproduce the problem. To add text to a line, or change other line properties such as hooks, use the Properties panel. See the existing Ped line to see the syntax for that special symbol. If you have further questions about how to use MuseScore, please use the support forum on MuseScore.org |
Describe the bug
The standard "pedal change" marking ___/\___ does not work; it lifts the pedal off but does not return it to the on position
To Reproduce
Steps to reproduce the behavior:
Result*
Pedal lifts in bar 2 but does not re-engage
Expected behavior
Second measure should have pedal engaged just like the first
Screenshots
Platform information
Additional context
The old-style Ped___* markings work fine because they don't overlap. The issue seems to only occur on the pedal changes - the places where the end of one pedal coincides the the start of the next to create the characteristic pedal change ___/\___. If I were to guess, I'd say the pedal off and on messages are simply being sent in the wrong order.
The text was updated successfully, but these errors were encountered: