Default horizontal alignment of 2nds in a linked tablature staff
In the attached score Measure 1 shows tablature after the addition of a linked tablature staff. The notes of the harmonic major 2nd are appropriately spaced in the treble clef, but the tablature needlessly follows this alignment—but the correct tablature alignment would have no horizontal offset. And to my surprise Control/Command r doesn't fix it.
I've pasted Measure 1 into Measure 2 and that cures the tablature misalignment, so there is a workaround. Note that it doesn't matter whether I copy/paste the treble clef or tablature.
Horizontal placement of 2nds in Tablature.mscz
MacOS
Scorster
Comments
Are you saying that the 0 and 7 are vertically misaligned in the first measure?
![same_align.png]( "same_align.png")
Here's what I see:
The TAB looks okay to me.
In reply to Are you saying that the 0… by Jm6stringer
The alignment in the image you posted does look okay. And when I reopen my score the notes are aligned as you show. So it appears that reopening the score is workaround No. 2.
This is what I saw:
Also I see that my original hypothesis was incorrect. I proposed that MuseScore misaligned the 2nds on adding a linked staff. To test that notion I entered a 2nd in a guitar staff and added a linked tablature staff. But everything was fine. Nevertheless I see the reported alignment problem a few times a week. So I'll see if I can identify steps to replicate. In pursuit of that I traced through my steps.
The score Provenance was MusicXML exported from an old Encore file.
I reopened it (• set the staff instrument to Guitar • then add linked Tab) and surprisingly the reported measure is fine, but there is an instance of the misplacement on a 2nd:
... and a few instances of the misplacement on 3rds!
Here's the musicXML. (When viewing the score it's probably helpful to clean it up by removing all staff text objects and running Reset Beams.)
Corelli Op5. #8 GTb Fpk.xml
Scorster
In reply to That does look okay. And… by scorster
After a musicXML import I reported tablature misalignments in prior posts in this thread.
Then I closed and reopened the score ... and all the misalignments are now corrected. That's why nobody saw the issue when opening the submitted MuseScore file.
Does anyone else see the misalignments on opening the attached MusicXML?
Corelli Op5. #8 GTb Fpk.xml
If so, is there a remedy besides a) closing and reopening the score b) copy/paste? Note, you'll also need to:
• set the staff instrument to Guitar
• then add linked Tab
Scorster
In reply to After musicXML import… by scorster
That's a clarinet score, so how would a tablature go along with it?
In reply to That's a clarinet score, so… by Jojo-Schmitz
Sorry, I forgot the mention:
• set the staff instrument to Guitar
• then add linked Tab
I've updated the posts so others won't be confused by the clarinet score.
Scorster
I don't see any issue either.
I also tried it not changing the instrument. Same result.
I also opened the mxl in Sibelius. Same procedures and same result. No offset. Although the opened mxl looked much different between the two programs.
Which reminds me that different programs will deal with mxl files differently. You seem to view having to close and reopen a score as a work around. It seems to me that the first thing I might want to do with an mxl is save it as the native format of the program I'm using. Then open it and work on it.
Even if there were some offset problems, there are many other things more important that need correcting.
In reply to I opened your mxl in… by bobjp
You wrote:
2. Changed the instrument to guitar, and added a tab staff.
3. C+P the guitar part int the tab.
Those are unlinked staves, The problem occurs with linked staves (no C+P involved).
In reply to I opened your mxl in… by bobjp
@bobjp
Your Step 3 could be the reason you don't see the issue. As mentioned, copy-paste cures the misalignment.
Maybe try again, but for step 3:
• press i
• then add a linked tablature staff
bobjp wrote >> You seem to view having to close and reopen a score as a work around.
Yes, I do.
bobjp wrote >> It seems to me that the first thing I might want to do with an mxl is save it as the native format of the program I'm using. Then open it and work on it.
If the developers agree with you on that point (after MusicXML import, always save, close and reopen) then that should happen automatically, or somewhere in the import process MuseScore should post that advice.
Scorster
scorster wrote:
Does anyone else see the misalignments on opening the attached MusicXML?
I do - I'm on Windows 10 - when I change the instrument to guitar and add a linked TAB staff.
![screen.png]( "screen.png")
Here's your first picture (upper) compared to what I saw (lower):
I do see the misalignment, but I also get beaming which differs from your picture. Also, your picture shows the first C and B notes played on the 3rd string instead of on the 2nd string (what my TAB shows). Did you make changes?
In reply to scorster wrote: Does anyone… by Jm6stringer
@Jm6stringer Thanks for testing and confirming the issue!
BTW, MacOS here.
Mainly for others following along ...
The misalignment occurs on the Major 2nd between A and B notes, but only in newly added linked tablature.
In our example imagess the difference in fret numbers is inconsequential (including the C and B that Jm6stringer asked about) and merely shows:
a) that I altered some of the string assignments from their default positions
b) that doing so does not correct the misalignment
c) the string assignments in Jm6stringer's example are simply the default locations
As mentioned, I ran Reset Beams to eliminate the flags. I also swapped Voice 1 and Voice 2. And in looking for a cure I pressed Control/Command r but didn't see any affect.
Presently the only cures seem to be:
Close and open the score
Copy/paste the notation ... even into the same measure.
jm, Can you check if those fix the alignment?
In reply to @Jm6stringer Thanks for… by scorster
@scorster...
You wrote:
Can you check if those fix the alignment?
I can confirm that both work to fix the misalignment.
In reply to @scorster... You wrote: Can… by Jm6stringer
#333035: Fret number misalignments on opening a MusicXML file and then adding a linked tablature staff
In reply to scorster wrote: Does anyone… by Jm6stringer
Correct. I did not add a linked tab staff on purpose. Does my way take longer? Maybe. All anyone seems to care about around here is how fast something can be done. Linked staff=errors that have to be corrected with a close and reopen. Non linked staff=no errors, but must use C+P. Could be a toss-up depending on the situation.
In reply to Correct. I did not add a… by bobjp
bobjp wrote >> All anyone seems to care about around here is how fast something can be done.
I don't think anyone here said that his/her only care is purely speed of accomplishment.
We're merely reporting bugs and identifying/confirming steps to replicate:
• Copy/paste is not a step that replicates
• Adding a linked tablature staff does replicate (which jm6stringer confirmed.)
That's all we're saying.
Scorster
In reply to bobjp wrote >> All anyone… by scorster
One observation I made is that changing the instrument from clarinet directly to a Guitar Tablature instrument (without creating a treble clef staff at all) also shows misalignments.
This might be considered "speed of accomplishment". :-)
In reply to bobjp wrote >> All anyone… by scorster
I fully understand which method causes what. All I'm saying is if there is a procedure that produces a result you don't like, why continue it? This is a possible non-issue because the next time you open the file, it is fixed.
In reply to I fully understand which… by bobjp
As a further experiment, I went through the procedure to add a linked staff and, of course, got the miss-alignment. Then I saved the file as an mscz. Reopened that and the problem was still there. Closed and reopened that and the problem was gone.
BTW, you can't just hit the save button while in an mxl file. It tries to save it but even though it is in the list of recent files to open, it can't find it. This is because no extension was added.
So there are a few problems here. Though some people might not see them as such.