problem with note playing correctly
Not sure if this should have been noted as a bug. In the file attached, in the 3rd measure of the Acoustic Guitar, the very last note of the triplet plays as the same as the note preceding it. This should not be. Help?
Also, I've been using Musescore now for several years. Just now trying out version 4. In past versions I could bring up a Play Panel and set the speed of playback. How does one do that in the latest version?
| Attachment | Size |
|---|---|
| blueberry_hillV4.mscz | 28.7 KB |
Comments
For some involontary reason I guess, an offset was applied on the last notes of the triplet. Just reset the value with the left circular arrow, and edit for the good ones.
See the result: 1blueberry_hillV4.mscz
and https://musescore.org/en/handbook/4/playback-controls#play-position-and…
In reply to For some involontary reason… by cadiz1
I haven't a clue what you mean by "reset the value with the left circular arrow". How can the note be different from what I have input on the staff? This was a problem in Version 3 also which is why I upgraded to Version 4.
In reply to I haven't a clue what you… by joebabb
"I haven't a clue what you mean by "reset the value with the left circular arrow"
You can see this reset (left arrow, a bit hidden by the red frame) on the image above (in Properties, Appearance tab)
Have you load the "repaired" score?
"How can the note be different from what I have input on the staff? "
MuseScore don't "play" with you by inputting a wrong note by itself. I don't know how you are doing to input the notes (via the standard staff, with mouse or keyboard, or via the TAB staff?). Can you describe your work flow? But there was a mistake at a certain moment, may be also in the Properties some other reason.
"This was a problem in Version 3 also which is why I upgraded to Version 4."
Sorry, I am not aware with this "problem" in Version 3 (and yet I know this version well and enter Tablatures regularly with it)
If you can developp this point and reproduce from scratch by providing precise steps, please report it here.
In reply to I haven't a clue what you… by joebabb
It is possible to change the position of notes without changing the actual pitch. THis is what the offsets are for that cadiz shows in the picture. "reset the value with the left circular arrow" means click on the button just above the offset settings which has a circular arrow on it, to get back to the default value, which in this case most likely is zero. How this offset was modified in the first place I have no idea. But if you are the only person editing this score, it was probably you who accidentaly did something to change it.
In reply to It is possible to change the… by AndreasKågedal
Or.
I deleted and reentered the notes and the proper pitch was played. But the question remains about how this happened.
In reply to Or. I deleted and reentered… by bobjp
> I deleted and reentered the notes
Simply select the notes or measure and press Ctrl+R, that's all it takes.
> But the question remains about how this happened.
Yes, indeed. I don't know of any keyboard shortcut, with or without mouse, to create that.
Just by intentionally changing the offset in the note properties.
Edit: Oh yes, by double-clicking on the note head it can be moved anywhere in MuS 3.
In reply to > I deleted and reentered… by HildeK
Ctrl+R doesn't fix everything, I did it the way I did it. And it was just the last beat of the measure.
In reply to Ctrl+R doesn't fix… by bobjp
Yes, it doesn't fix everything, but in MuS 3 it fixes this problem.
I always try Ctrl+R first. That helps very often.
In reply to Yes, it doesn't fix… by HildeK
Fortunately my needs are simple. I can't say I've ever run into a situation in my own use of the software in which I needed to reset problems. That's why it wasn't my first choice.
In reply to It is possible to change the… by AndreasKågedal
Thanks. I am creating the thing from scratch inputting the notes by mouse. Just so we all understand, my problem was not the visual positioning of the note, but the pitch. The note played was a whole tone off and equal to the note that proceeded it. I did finally find the "left circular arrow" and indeed for that one note it was not zero. I set it to zero and then everything worked. I'm having some difficulty with the new user interface. I've only used it for a couple of hours today. I had no idea that I could set a particular note "off" pitch. So I did not do that deliberately. By the way, how is a person to know? There is nothing that clues me into selecting a note to show the "appearance" window and nothing in that window to indicate what the offset is for.
In reply to Thanks. I am creating the… by joebabb
1.To Edit a pitch, see: https://musescore.org/en/handbook/4/editing-notes-and-rests#pitch-normal
Less well known: if you make a mistake when typing with the mouse, say you're typing an E and you wanted an F, press Shift + F. This will overwrite the E (in the same voice, of course). More direct than having to use the direction or back arrows to rectify things.
For the record, about TABS: https://musescore.org/en/handbook/4/entering-and-editing-tablature-nota…
Offsets in Properties (or Inspector/V3) are not intended, and never have been, to modify notes pitch. They are intended for formatting/layout, to manually adjust certain elements: https://musescore.org/en/handbook/4/positioning-elements#manual-adjustm…
One last thing: in case of doubt (a gap between the note written and the note heard, as was the case in your score), click on the suspect note, and look in the status bar. This will give you exactly the right information. The original/heard note is indeed an E - image below.
In reply to To edit a pitch, see: https:… by cadiz1
Thank you for the added information. If offsets were not intended to change pitch, why did it work in my case? If a note is placed on the top line of a treble clef it should be an F# in this case. Why does the software think it is an E? Still a bug in my opinion.
In reply to Thank you for the added… by joebabb
"If offsets were not intended to change pitch, why did it work in my case?"
I don't follow you. It doesn't work in your case: as proof, you posted a thread complaining that the last two notes of the triplet were played like the previous two.
"Why does the software think it is an E?"
MuseScore doesn't think it's an E. It asserts that the pitch is an E as you entered it at first intention. And not an F#, which you've moved into space (vertical way) by misunderstanding the role of horizontal and vertical offsets in Properties.
Otherwise, what a mess! Offsets are for visual purposes only, and never for playback/pitch.
"Still a bug in my opinion"
Definitely not a bug. All versions of MuseScore have worked this way. It's just that you have to get used to not confusing two different functions. Take the time to read the handbook (I've provided the links) to get a feel for how to edit the pitch of a note.
In reply to If offsets were not intended… by cadiz1
Actually, they posted that the last note of the triplet played like the previous note (one). They didn't even know about offsets, so how could they have misunderstood and purposely misused the setting.
I've used MuseScore for years and never had to mess with offsets. But then my needs are simple. Someone brand new wouldn't need to know about offsets.
And you can't use the up and down arrows to get a -0.58 setting. So the question remains, how did this happen?
In reply to Actually, they posted that… by bobjp
"so how could they have misunderstood and purposely misused the setting."
Precisely by misunderstanding :)
In reply to "so how could they have… by cadiz1
But I don't think they used the setting.
In reply to But I don't think they used… by bobjp
Well, I know that with Version 3, the known cause was the editing of note pitch after an unintentional double-click. But this was fixed and no longer happens with V4. Single-click or unintentional double-click, then drag the note with the mouse: the pitch change is taken into account.
However, the OP states that he changed version to avoid a problem, this one I suppose. But since he's using V4, I don't see how he could have reproduced this behavior.
If he knows how he did it (without using Offsets), he's welcome.
See the behaviour (after double-click) V3 vs. V4:
In reply to Well, I know that with… by cadiz1
If there was no intervention in the Offsets, one possible explanation: the OP created his file in V3 (with the double-click editing error), then opened and saved it with V4, and therefore with the same saved error.
It's up to him to tell us.
In reply to If there was no intervention… by cadiz1
I think that is the source of the problem. I started the project in version 3 and then moved it to version 4. I've used musescore for many years now and never had this problem. I never knew it existed in version 3. It still a question as to why when I reset the offset to zero that corrected the problem.
In reply to I think that is the source… by joebabb
"I think that is the source of the problem. I started the project in version 3 and then moved it to version 4."
Great. Thanks for confirmation. End of story! 👍
NB: as for the reset, well, let's just say it did its job by returning the notes back in their original position.