Issue/annoyance
Linux applmage on chrome MS5.3.2....
Sorry, doing two here! Have not decided if might be a mouse problem? In clicking a note, many times get a second note a 2nd above, could be mouse, yet it has also added note 5th above and that was not me or the mouse. Sometimes program refuses to exit notation mode by just pushing n
key, pointer has to be moved up to menu N
above. Are these problems or just annoyances?
Comments
And still there is no MuseScore 5.3.2...
If one mouse-click adds 2 notes, the mouse is likely broken
In reply to And still there is no… by Jojo-Schmitz
Jojo I am going to respond to all your thoughts at once since you are the only one who has responded. I am sorry for transposing two numbers in my memory. I am certainly sure that no one else has ever misspelled a word or transposed anything on the forum before. I am also sorry if this is going to sound pissy, but that's exactly what I feel I got! I tend to respond in kind. It is why I really hate to bring anything to this forum, but I thought someone might be interested.
I went back in to try things and check things again. Font size is what is used in the program, but since I could not get to that pop-up window , I had forgotten. When you change font sizes many call that changing pixel pitch. The window does not show up as I said when you click text edit! Go to the program and enter a note! Push up/down arrow and get a natural sign. If you can not, even though you say you can... that is where clicking the pallet sign does NOT work, unless notation mode is turned off! When you enter a note you can push up/down arrows to get an accidental, you do NOT have to re-highlight that note!! Now reread my post and maybe you will begin to understand! The mouse is brand new working fine except for one thing....but I guess that makes it defective, because it certainly could not be anything else, especially since it only happens sometimes...it`s probably only occasionally broken.
Since I doubt I will hear anything else useful, thanks for responding.
In reply to Jojo I am going to respond… by R. L. F.
Sorry, I've never heard the teerm "pixel pitch" before.
Font size of any text item can get changed in the Inspector. Or in the text tool (at the bottom of the screen, when the text is in Edit mode). Not in the right-click context menu, not since MuseScore 3 at least
In reply to Sorry, I've never heard the… by Jojo-Schmitz
Sorry for using a confusing term. Since I was unable to get to the menu item I was expecting this was the only thing I could think of to call it. I have only used inspector for making things invisible/visible so I did not think of going there. Now, my question is why is text edit still in right click menu if that`s not where the service is to be found and why does text edit bring up window for midi tempo. Not where I would be looking for that. Thanks again, hope my other post to you explains my confusions!
In reply to Sorry for using a confusing… by R. L. F.
It's also important to keep in mind that while this is the English-speaking forum, not everyone who volunteers their time to assist here is a native English speaker. FWIW, I am, but to me, "pixel pitch" suggests distance between things, so I was guessing you might have meant the distance between two liens of text. MuseScore has never provided that before, but in our constant effort to improve the program and add more and more flexibility, version 3.6 will now provide this ability.
The Inspector in previous versions was very limited, now it is far more powerful and flexible, able to do things that previously could only be done more clumsily via right-click menu and separate modal dialogs that prevented you from working with the score while the dialog was open.
As for "Text Edit", there is no such entry in the right-click menu. Maybe you mean "Edit Element"? This hasn't changed, it does what it always has - it puts the element in edit mode. For text, that means giving you a cursor so you can literally edit the text - type new letter, delete old ones, etc. It has nothing to do with any properties of the text like visibility or size. Basically, "Edit Element" is just the same as double-click. Again in the interest of flexibility, we provide both ways of accessing edit mode.
I have no idea, though, what you mean by "window for midi tempo". There is no such window I am aware of.
In reply to It's also important to keep… by Marc Sabatella
"Window for MIDI tempo" -> Play Pannel? That's at least the place for tempo-rary overrides ;-)
In reply to It's also important to keep… by Marc Sabatella
Marc thanks for your comments.helpful as always! I know now I should have said I was just moving from 2.3. This might have helped understand my confusion. As for inspector, I only used it for visible/invisible, so I was not looking for font size there. I went back to 2.3 and in the right click menu it is text style or text properties. I would use text style for font size and the window does say
text edit
something. This is what I remembered, so confusion on not finding what I was looking for in right click where I had been used to it. Change does mean relearning. I am sure that I do not know/use even 40% of what the program is able to do. So any change is disconcerting! I think it`s actually midi change and 2nd window is swing tempo, naturally I combined both.(I believe jojo has a levity comment in his second post, though I do not think I follow it?!In reply to Marc thanks for your… by R. L. F.
Such a description might correspond with the properties window of a staff text, which you can indeed reach via right click on a staff text.
In reply to Such a description might… by jeetee
Jeetee You are no doubt right. As I commented to Marc, coming from 2.3 right click on text through text style choice brought me to window for font size. The window said text edit at top and I am sure that`s what I remembered. Sorry for my confusion when I could not locate what I had always found. Thanks!
In reply to Marc thanks for your… by R. L. F.
Glad it's starting to become more clear:
In both 2.3 and 3.5.2, there is a dialog called "Staff Text Properties" that has some MIDI options, swing options, and more. You get there by right-clicking a staff text and choose "Staff Text Properties". None of this has changed at all, and at no time does the word "Edit" appear in conjunction with this, and none of this is at all relevant for setting fonts in either version.
To set fonts, 2.3 made you open and close a separate dialog called "Text Properties" (as opposed to "Staff Text Properties"). In this dialog, you could change fonts for the select text, but only that text, and your score didn't update in real time, and you couldn't keep working with your score while that dialog was open.
This is vastly improved in MuseScore 3, where you can set fonts directly in the Inspecotr which you can leave open at all times - thus saving the trouble of separate steps to open and then close it. Also, while it is open (normally always), you can continue to work with your score normally. plus your score updates in real time as you make changes. Plus you can apply changes to as many similar elements as you want.
In reply to Glad it's starting to become… by Marc Sabatella
Marc
I would also add in 2.3 right click text styles also allowed font changes in a text edit styles window. Both system or staff, as I am sure you remember. I would hit one or the other props or styles, make my change and click back out. Everything updated and I continued working on the score. Since I was just making one change quickly, it was not worth leaving any window open. With inspector, I would just make whatever invisible/visible close out and move on with any other additions. No need to have inspector open. The same is true for 3.5.2. For ME, I just do not see a reason for leaving a window or pallet open to make
one
quick change. Now that I have found where everything has changed to, I can continue to work. I am glad if these things have made the program more flexible for others, but as I hope you see they just made me do things differently. No better, but not too worse. As with others I still like MS. My only continuing confusion is the many double notes showing up, but I guess I live with it for now! Thanks again Marc for your thoughts... I hope you also see what I was thinking!In reply to Jojo I am going to respond… by R. L. F.
When you get to the point where things don't work normal, look in the bottom right corner of the MuseScore window. When you are in note entry mode, it will tell you which note entry mode you are in. If you have a defective mouse, you may be sending a double click to the program and it is putting you into edit mode. The bottom right of the MuseScore window will tell you this. If you are in edit mode, all of the things you describe will happen. N won't turn off the current mode and clicking the toolbar won't add an accidental. What is more likely is that the note will move when you press arrows, though pressing an arrow with no other key in edit mode will likely appear to do nothing but it's actually changing the y offset a very small amount for each arrow pressed.
It sounds like you mouse is sending a double click and sometimes the program is interpreting the double click as a double click cause edit mode to activate and sometimes as two quick distinct clicks and you get chords entered.
Jojo can be a bit over-legalistic in his responses at times (like "there is no 5.3.2") but I would seriously consider any advice he gave me concerning the program. He is among the most knowledgeable contributors to these forums. I often defer to him in issues that elude me and even ask for his advice directly in these forums at times. No one is perfect and the best we can do is give possibilities since we have no ability to touch your computer.
In reply to When you get to the point… by mike320
Thanks again for your comments. Afraid this time you are losing me with details. I click n key and enter notes, click n key again and if I see something I highlight it and make whatever correction might be necessary. I do believe I remember seeing something at the bottom, I will look more closely now! I think it is best to say a new mouse is not defective, but
very
sensitive. This I buy into. I do not click in chords, so I am not sure what happens. Are you only talking about entering part of a chord? Because from your thought that would have been the result I got. I will continue to watch further.In reply to Thanks again for your… by R. L. F.
What is supposed to happen when you move your mouse over an existing note/chord you get the preview note (mine is blue but I don't remember if I customized it) showing where the note will be entered. If you have a note there already it should add a note to the chord. Sensitivity is a consideration. If you don't have a steady hand it's possible to move the mouse to the left a little and accidentally add a note to the previous chord rather than where you want it.
As for accidentals, what someone previously tried to explain (and might have been able to do it better) is that since about version 3.3 you have needed to click the accidental button on the toolbar before you add a note. Prior to that, you added a note then clicked the toolbar to add the accidental. This change was not clearly explained so it is possible you didn't know about it. So you know, a lot of people complained because when they wanted a G# they had to enter a G hear that note then click the accidental and hear that note. The request was very reasonable and the change is actually more logical. It totally messed up my workflow though, so I'm glad you can now define shortcuts that will apply accidentals after note entry if you prefer.
Remember, I don't know what you know about the program and music in general, so if I tell you something you know take it as too much information on my part. When you enter a note without an accidental it will always follow the key signature if it's the first occurrence of the note on that staff or it will be assume the same accidental of the note of the same pitch previously entered. This means that if you have an F# (and no E#) in the key signature, the first time you enter an F in a measure you get an F#. The status bar at the bottom left of the MuseScore window will confirm this. If you want an F natural you can either apply an accidental or press the down arrow to change the pitch. If you do this, the next F you enter in that measure will be an F natural by default with no accidental necessary and pressing arrows will change it to either an F# (with an accidental) if you press up or an E if you press down. It is possible that this is what you are having a problem with in regards to the naturals. I originally assumed you knew this and the problem was likely with your mouse. Since it's so new, it's not likely (but not impossible) to be the mouse so there must be something you are not understanding about how the program works.
In reply to What is supposed to happen… by mike320
Thanks again for the thoughts mike320. You are correct I did not know of the change. I have been working in 2.3! Yeah, it is making me change, though another comment has suggested the accidental toolbar on the left allows adding after the note is entered. I will check that soon, hope so! You are correct in your explaination of accidentals...only problem is I do not work with key signatures! Therefore I am always adding accidentals and then negating them with a natural sign for the benefit of the performer, when necessary. If the last note of a measure of 16th
s is e flat and one of the first three notes of next measure of running 16th
s is a e natural for the performers benefit I add a natural signed. They would pencil in the sign for ease of playing, anyway. I do not think the change is a benefit, I like hearing the change sound so I know it happened. Alas, I do not have perfect pitch to know the correct (my choice) pitch was notated by the program. If I can I will continue working as I have. Because I do not often use traditional chords I am not following your thoughts. I do now think something was toooo sensitive. Which, I do not know. I will be working awhile with my old mouse, so will see what happens. Thanks again!In reply to Thanks again for the… by R. L. F.
As I said, the change messed up my workflow and I don't mind hearing the wrong note followed by the correct note or the same note twice in the case of a courtesy accidental (the natural you spoke of that's not needed musically but tells the performer the editor did not make a mistake). You said that you don't like to keep palettes open so a possible alternative when version 3.6 is released probably on Wednesday is to define a shortcut for accidentals added after the notes. The shortcuts you will want to define are the ones that do not say "Non toggle". It seems you like to use the mouse so using a keyboard shortcut will be a bit of a change in workflow but it is another alternative. One thing I like about MuseScore is that there are often several ways to accomplish most tasks. Unfortunately you can't change the effect of clicking on the toolbar.
In reply to As I said, the change messed… by mike320
Mike 320 I probably will not be bothered by a one key shortcut for adding naturals, but as we spoke before I prefer to know I did it and not the program on its own! But I am keeping it in mind. DanielR gave a good alt and I am liking it so far, keeps my same work flow. I fear I will only change if I have to!!! Thanks
In reply to What is supposed to happen… by mike320
Mike320
I hope you find this much later post. I have continued to have double note problems! I went back to my old mouse. In 2.3 I
never
had double notes. But, even with the old mouse and pad they continue to show up. You imply that a click on the button is not necessary. Is this what you mean? Because I would say that is what is happening, as no extra clicks are made. Yet another note is suddenly there. Any way to change this? Any thoughts...and sorry I have not tried 150% yet. It`s a little large for me. Does say 120% work as well? If you see this any thoughts will be grateful!In reply to Thanks again for your… by R. L. F.
R.L.F. I've had the occasional problem with using the mouse alone when entering notes. But I suspect it had mostly to do with the level of magnification in MuseScore and/or the sensitivity of my mouse. I found I got much better (i.e. accurate with what I wanted to do) note entry by increasing the view size to e.g. 150% via 'View - Zoom In' or entry of '150' into the page size text box at the top of the screen. It's not necessarily a fix for your issue, but if you have no success with the other tips, you may want to try this technique.
In reply to R.L.F. I've had the… by Lofo
Lofo Thanks for responding. I have in the past used 150%, so I might try again. My only problem is some of the additions seemed to show up when I was not touching the mouse. Will be using my old mouse and see if things happen again.
Consider my confusion lessened...thanks for all the help!!