Add Chord Symbol on a Rest Measure
Hi all - Please help with:
Add Chord Symbol on a Rest Measure
Example: Rhythm section plays but melody rests.
See attached:
BTW - Where can I help with documentation? The message I receive has grammar and punctuation errors.
Thanks,
| Attachment | Size |
|---|---|
| Screen Shot 2022-02-26 at 6.19.44 PM.png | 144.98 KB |
| Screen Shot 2022-02-26 at 6.19.53 PM.png | 406.59 KB |
Comments
Select the rest, not the measure, just as the error message tells you
Select the rest, not the measure
What grammar and punctuation errors?
Do you mean you'd want this instead?
No note nor rest selected: Please select a note or rest and retry.
In reply to Select the rest, not the… by Jojo-Schmitz
Thank you. That message would be an improvement. What I suggest is implementing the "goal before action" style of documentation.
Example:
Goal is to write a chord symbol.
Action is to select a note or a rest.
Suggested update: To enter a chord symbol, select a rest or note and type Command + K.
But not to complain about the free application - I enjoy learning MuseScore and it's better than my previous paid application, Sibelius.
In reply to Thank you. That message… by kent_donaldo
That error message is not specific to chord symbols, but to all elements requiring a note or rest to be selected.
And Command+K would be the wrong shortcut in about 80% of the cases, on Windows and Linux it is Control+K ...
In reply to Select the rest, not the… by Jojo-Schmitz
i don't think No X or Y is an error, but there should not be a colon followed by a capital letter.
In reply to i don't think No X or Y is… by underquark
Might be German "accent", in our rules a sentence after a colon starts with an uppercase letter.
Same rule BTW in American English, see https://www.grammarly.com/blog/capitalization-after-colons/
Mind though that not many of the programmers are native English speakers. Even less of those that are aware of AE and BE differences
In reply to Might be German accent, in… by Jojo-Schmitz
thank you all - it's not so much the grammar but the reason that the message is appearing. If you write messages with "goal before action" that will help the reader who might already be a little upset because it's not working correctly.
example:
to do , press .
In reply to thank you all - it's not so… by kent_donaldo
As said: that is a pretty generic error message, used in multiple places, not just for chord symbols.
And the user does know what (s)he wanted to achieve (like when having pressed Ctrk+K: adding a chord symbol) so repeating that would be pretty redundant,.
In reply to As said: that is a pretty… by Jojo-Schmitz
Sure - you can probably leave that message and it's still a good product;) - I personally got a bit frustrated that I could add chord symbols in my score by typing Command + K / Space Bar, but then suddenly when the bar has only rests, the fun comes to a halt and the message appears.
I then had to remind myself that this is a free platform and my frustration vanishes.
In reply to Sure - you can probably… by kent_donaldo
That should work though, Ctrl+K to start chord symbol entry, Space to move to next beat, note or rest, see https://musescore.org/en/handbook/3/chord-symbols#commands
In reply to Sure - you can probably… by kent_donaldo
The fun came to a halt because you selected a whole measure, if you do that to a measure full of notes you'd get the exact same error message.
In reply to Might be German accent, in… by Jojo-Schmitz
US English grammar rule:
"When a colon introduces a phrase or an incomplete sentence that is meant to add information to the sentence before it, do not capitalize the first word after the colon unless it is a proper noun".
In reply to US English grammar rule: … by underquark
And that colon is introducing a complete sentence. A capital therefore seems justified. A full stop (period in US?} at the end would be good though.
In reply to US English grammar rule: … by underquark
Thanks - I think I break the rule all the time then as I write technical docs for a living.
I understand this is off topic, but I just think the following type of language just looks better.
Example:
"Follow these steps:
1. Capitalize the first letter of a sentence.
2. Thank the people who comment on your forum.
2. Close this forum and get back to work before your boss finds out. "
In reply to Thanks - I think I break the… by kent_donaldo
I don't think the rule you quoted precludes a lower case for a complete sentence after a colon. In fact it says nothing about that case. I suggest you can rest easy that the grammar police have nothing on you. I hope the same also goes for the MuseScore team in this case.