changing a tempo marking with NVDA
I don't really know where to put this, I'm quite new to muse score. I'm working on an arrangement that I've had in my head for 20 odd years. I was able to get off the ground thanks to some wonderful documentation and external links. I find I had to redo some of the notes I accidently tied, but that's ok. I want to change my tempo marking in the beginning of the piece. I set it at 70 but it still way way way too fast. I tried going into edit mode with alt shift e, but could not see a way to edit the tempo marking. Is this not yet accessible with nvda, or am I missing a step. So far I'm quite impressed at how far I've gotten in the hour or 2 I've been playing with it. Already this arrangement is starting to come together.
I use nvda 2021.x and Windows 10 21H1 (x64) build 19043.1237 and musescore 3.
Thanks so much.
Comments
Can you attach the score?
Which version of MuseScore eactly?
In reply to Can you attach the score?… by Jojo-Schmitz
I can attach the score. I'm not proud of it as it's not done lol! See m my prior reply for version.
Hello! Which version of MsueScore 3 specifically? The current is 3.6.2. For me, editing the tempo works fine - I hear the tempo marking being read a character at a time as I move the cursor. But I know there are some situations where for whatever reason, text isn't always read while editing. Instead, you can just trust that hitting the End key will move the cursor to the end of the text, then backspace twice to remove the "70", then type whatever you want instead, then hit Esc to leave edit mode. Then have NVDA re-read to the tempo if it doesn't do so already, to see if you got it right.
Good luck, and feel free to ask here if you have further questions!
In reply to Hello! Which version of… by Marc Sabatella
Hello. I'm using muse score Version: 3.6.2.548021803 OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.6.2.548021803, revision: 3224f34
sorry about that long revision number. woops?
I made a video, sorry about the "welcome to twitch trhere shown, my fault, I didn't realize that was there. As you can see and hear the tempo is not bein changed nor is I think focus getting to the marking. Also I don't recall having 2 tempo markings there.
https://www.dropbox.com/s/trlw9rovbaqz0ma/muse%20score%20and%20tempo%20…
I'm also having trouble with my OBS right now, so we'll see if I can also fix that.
In reply to Hello. I'm using muse score … by marrie1
I forgot to say as well, I'm using nvda 2021.2. I have no clue if this will help anybody troubleshoot what's going on as far as what the screen reader is trying to do, however it never hurts to include that.
Thanks all.
In reply to Hello. I'm using muse score … by marrie1
From what I can tell in your video (MuseScore itself is not visible, btw, just a terminal window), it seems you may indeed have two separate tempo markings. Also. you probably accidentally entered the E's into your tempo marking when you meant to enter them as notes. If you attach your score, I can probably tell better what is going on.
But I think the main problem here is that you are probably not on the tempo marking itself when you try to edit - I think you're on the note or rest to which the tempo is attached. MuseScore reads all markings attached to notes or rests when you navigate to them, but then you still need to navigate to the individual markings directly, via Alt+Left/Right. It's a little hard for me to tell what is actually going on because I don't know exactly what you're pressing. You're hearing NVDA read to you what you expect based on what you press when navigating, but I don't know which navigation commands you are actually doing, so it's harder for me to keep track, plus I'm not as used to navigating by audible feedback only. But When you say you're entering edit mode, I hear NVDA read "edit mode" rather than "text edit mode", which is the feedback I need to tell me you aren't actually on the tempo marking.
In reply to From what I can tell in your… by Marc Sabatella
Ah I see. Hmm odd. I wonder why a terminal window is being shown when I can navigate fine. I attached a more complete, well up to the end of first verse sans lyrics, that I will do very very last. Sorry about the horrible video. I'm not a videographer. lol! My talent is not that.
If you have NVDA on your computer which you can get from http://nvda-project.org you can navigate with audible feedback to see what we are seeing etc.
Thanks so much. Bjtw I don't care if this thing takes me months to get done, I'm not in any rush. I'm just excited to finally get what I've had in my head for almost 12 years finally written down, and for me to make this much progress in under 3 hours edited time is amazing.
In reply to Ah I see. Hmm odd. I wonder… by marrie1
To be clear: I do have NVDA installed, also JAWS, also Orca on my Linux machine, and I test with all of these regularly. So I do know how they work in principle; I'm just not good at debugging problems by lsitening to the audio output only! I can do it better on my own system because I know what keys I'm pressing.
Anyhow, did my suggestion work? I'm 90% certain that was the problem - you weren't on the tempo marking when you press Alt+Shfit+E, you were on a rest. That also explains why you were thinking there were two tempo markings. There aren't, as I can now tell - there is just the one. You heard NVDA read it once when you were on the rest, and then you heard it read again when you were actually on the tempo marking. So be sure you're on the tempo marking and not the rest when you give the edit command and all should be well.
BTW, that aside, great start on your arrangement - it's so wonderful you've come so far so quickly!
One little glitch I noticed - bar 11, piano part, top staff, last beat (the sixteenths) - the first sixteenth actually has three E's - two E5's and an E6. You can safely delete one of the two E5's.
In reply to To be clear: I do have NVDA… by Marc Sabatella
Yep I already nixed the extra e, dunno how that got there lol! Maybe my fingers got tongue tied? Yep I modified the tempo. Thanks for that. I do have other questions but I'll voice them in other threads while I explore and poke around the manuals. Hopefully I can actually one day hear this thing sung, and hopefully it works.
Thanks so much you guys.