Chord symbols no longer play when adding or changing them (after updating to MuseScore 4.4.0)
I just updated to 4.4.0, and lost this feature. Before, when I was adding or modifying a chord symbol, they would be played immediately after the action is completed. That is sadly no longer the case. It worked just fine 10 minutes ago in the previous release before the update came.
I checked the settings, "Play chord when editing" and "Play chord symbol when editing" options are checked. I tried to uncheck and check them again along with restarting MuseScore. Unfortunately, none of that helped.
I wonder if anyone is aware of some workaround how to bring this feature back, and if MuseScore development team is aware of the issue and if it's going to be fixed soon?
OS: macOS 14.5, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.0-242390800, revision: 0fcd11b
Comments
Works for me, Windows 11
In reply to Works for me, Windows 11 by Jojo-Schmitz
Well, it doesn't work for me on MacOS 14.5. :)
I can confirm that it's some kind of a bug in 4.4.
I installed 4.3 again, and it still works perfectly fine there – after you enter a chord symbol, it's played automatically right after that.
Then, after installing 4.4, the feature is broken – the chord is not played after it's entered or modified.
I am attaching the videos that demonstrate the issue.
In reply to I can confirm that it's some… by csbubbles
Report it on GitHub then
In reply to Report it on GitHub then by Jojo-Schmitz
Sorry, I am not involved in the development, and not part of GitHub. Isn't this forum for reporting bugs?
In reply to Report it on GitHub then by Jojo-Schmitz
Anyway, I figured it out – https://github.com/musescore/MuseScore/issues/24485.
PS I guess next time I will just go ahead and create a bug there from the very beginning, and not be reporting it here, and it seems to be just duplicate work (which also delayed actual bug reporting by a week)...
In reply to Anyway, I figured it out –… by csbubbles
No, it's very useful to report here first to try to get confirmation it's not just a misunderstanding, or something off in your system configuration somehow. So far no one else is able to reproduce this, but I haven't seen anything one way or another from anyone on macOS, so it would be good if someone else who uses that OS could try this out.
In reply to No, it's very useful to… by Marc Sabatella
Confirmed here on Mac OS 13.5.2 in MS 4.4.0 (But it's fixed in 4.4.1)
In MS 4.4.0 there's no playback/feedback when entering chord symbols. This occurs even when Preferences>Note Input>Play chord when editing" and "Play chord symbol when editing" options are checked.
This is fixed in 4.4.1. The currently entered chord symbol sounds on commit ... and when advancing to the next position.
In reply to Confirmed here on Mac OS 13… by scorster
Which 4.4.1 do you have installed? Mine is 64-bit, 4.4.1-242490810, revision: 0b3dd00, the issue is reproducible there.
In reply to I have MuseScore Studio… by csbubbles
I'm also using:
OS: macOS 13.5, Arch.: arm64, MuseScore Studio version (64-bit): 4.4.1-242490810, revision: 0b3dd00
In chord input I'm advancing via pressing the space bar—doing so sounds the just-entered chord and moves the insert point forward one beat in 4/4.
Pressing Tab does not advance, and hence no sound. Rather the Tab key now functions for accessibility and begins cycling through various UI elements, starting with Palettes. Same in 4.4.0.
In 3.6.2 and 3.7, while in chord symbol input mode, the Tab key advances input the start of the next measure. And that's a behavior users are quite accustomed to.
I'm all for accessibility, but would love to turn it off in MuseScore on my computer so I can have my old shortcuts back.
In reply to I'm also using: OS: macOS 13… by scorster
> I'm advancing with the space bar
I typically press Esc after entering/editing a chord, not Space (as in most cases I prefer advancing to the next chord position using a trackpad/mouse). I bet if you try the same, there will be no sound.
In reply to > I'm advancing with the… by csbubbles
@csbubbles wrote
I prefer advancing to the next chord position using a trackpad/mouse). I bet if you try the same, there will be no sound.
Correct.
In reply to I'm also using: OS: macOS 13… by scorster
It's true that existing users are used to the very non-standard shortcut Tab in this particular scenario, but given that they are also quite accustomed to using Ctrl+Right to advance to the next measure in all other modes, they should be able to adapt easily. It's objectively simpler for both users of older version and for new users to remember one "advance to next measure" shortcut than to use one shortcut in one mode and a different shortcut in a different mode.
Which isn't to say it wouldn't be possible for some programmer in the open source community to implement a way to disable the usual function of Tab that is required by all accessibility standards as well as all major OS UI design guidelines, as long as they do so in a way that doesn't in any way break the standard behavior for others.
In reply to Confirmed here on Mac OS 13… by scorster
What I have realized is that normal chord input where you press Space or any of the other shortcuts (Ctrl+Right, etc) to complete entry of one chord and move on to the next does work in all versions. But the very last chord you enter in the sequence may not play if you terminate input with Esc or by clicking outside the edit area. That particular bug affects both 4.4.0 and 4.4.1
In reply to What I have realized is that… by Marc Sabatella
FYI, my workflow is a bit different from what you call "normal". :) I usually select a specific note in a measure (typically the one of the downbeat), press Cmd-K, type a chord, press Esc, then select another note (most of the time in a different measure) using a mouse/trackpad, and keep doing the same. So, my "sequence" doesn't have Space in it. Effectively I never hear how the chord sounds after I enter one now.
I don't use Space except for the cases when I need to enter another chord symbol in the same measure. It might be a matter of your personal preferences, but I personally don't find using Space convenient in other cases.
The same is when I need to correct a chord – I don't need to navigate to another beat, I just need to edit a chord to fix it, and then press Esc or click outside to exit the chord edit mode.
In reply to FYI, my workflow is a bit… by csbubbles
To advance to the next measure, simply press Ctrl+Right. No reason to resort to constantly leave and re-enter chord symbol edit mode.
But anyhow, the bug is logged now, and confirmed, so hopefully a fix will be forthcoming.