Note offset
I know that Inspector of Musescore 3 is in Properties of Musescore 4 now. Do I have to set the offset for the note and for the stem separately? Can I do that altogether for the entire accord? [It would be sad if no, Musescore 3 did allow that].
The attached image has the dotted notes in the 1st voice. I want to offset them -3.85 cm for them to merge with the first notes in the triplets in the second voice.
| Attachment | Size |
|---|---|
| Capture.PNG | 17.14 KB |
Comments
When I set the offset separately for each note (E and G# above) and for the stem, the horizontal bar still stays where it is. How to force it to extend? I didn't see anything like that in Musescore 3
In reply to When I set the offset… by blvsntl
Make head of the shorter duration note invisible and the longer duration note will move to share its visible notehead.
In reply to Make head of the shorter… by SteveBlower
Did it. The notes became closer, but still not there:
![Capture1.PNG]( "Capture1.PNG")
![Capture2.PNG]( "Capture2.PNG")
The expected result from Musescore 3:
In reply to Did it. The notes became… by blvsntl
It should work in MU4. Do you still have the offset applied? If so, reset it to zero.
I will try to replicate tomorrow. Time for bed here now.
In reply to It should work in MU4. Do… by SteveBlower
Thank you for readiness to help. I checked, The offset is 0, but the issue is still there. Here is the test file for your convenience.
In reply to Thank you for readiness to… by blvsntl
This is what I see in the properties panel when I select that first sixteenth note, the E in voice 2.
Note the horizontal offset = -2.5 and visibility is checked.
If I reset the offset to zero and uncheck the visibility the noteheads become merged (or at least look as if they are merged). Like this:
In reply to This is what I see in the… by SteveBlower
Thank you for your effort. Apparently, the problem is deeper. When I open that file, this is what I see.
![Capture4.PNG]( "Capture4.PNG")
![Capture5.PNG]( "Capture5.PNG")
![Capture6.PNG]( "Capture6.PNG")
When that note is visible:
When that note is invisible:
(See, they are closer, but still not there)
For both cases, the offset has the value 0:
I am surprised that we don't see the same thing. I did reinstall Musescore 4, reboot the computer and seemingly did everything what should be done. Any ideas what's going wrong.
I also noted that your palette tab is cleaner, but I don't think that is the issue. I have just installed Musescore 4 and didn't adjust it foк myself yet (you apparently did).
In reply to This is what I see in the… by SteveBlower
And this is what I see when I give the offset the value 2.5 for the note and the stem separately:
![Capture7.PNG]( "Capture7.PNG")
And there is no option to move the beam horizontally. Musescore 4 allowes the vertical shift only (using the standard handles)
In reply to And this is what I see when… by blvsntl
There is no need to move anything. Indeed, having an offset prevents the noteheads merging. If there is no offset and the shorter notehead is invisible, the stem and beams move automatically to line up with the longer note giving the impression of overlapping noteheads. At least, that is what should happen.
Are you perhaps selecting more than just the notehead. That would also cause the different appearance of the properties panel. To clarify, here is the process broken down into small steps.
Or, perhaps you are using a different version. I am using version 4.2.0 on Windows 10.
Another thing to try is a factory reset. Help>Revert to Factory Settings. Of course, that is a bit drastic as it will remove any customisations you have made, but perhaps it is just those customisations that are causing the problem.
In reply to There is no need to move… by SteveBlower
Thank you for the detailed answer. Unfortunately, nothing helped (factory reset included, the Musescore version is the same as yours etc.). I believe that it is what we have when we switch to the newer version of the software. I tried to retype that bar anew and everything worked like a charm:
![Capture.PNG]( "Capture.PNG")
So thank you for your involvement. I am going to retype those bars...
In reply to Thank you for the detailed… by blvsntl
It is very odd as I was using the file that you attached to your post and everything worked as it should for me.
Ah well, time to shrug one's shoulders and move on.