Same file opened on different PCs have different chord symbol locations
PC1 has the corrected version of locations for the chord symbols saved to a shared drive.
PC2 opened the same file and has the chord symbols in the original uncorrected locations.
See red circles in the attached files and the placement location info in the inspector window.
| Attachment | Size |
|---|---|
| Capture PC1.pdf | 127.14 KB |
| Capture PC2.pdf | 130.06 KB |
Comments
When I open the files directly from file explorer instead of from musescore they look the same.
In order to investigate, we would need you to attach the actual score, not just pictures. Best guess is that you are using some font not present on both systems.
In reply to In order to investigate, we… by Marc Sabatella
On further investigation, the problem seems to be a set of chord symbols entered as text and not the two PCs reading the same file differently. The problem seems to be that changes to certain chord positions are not saved.
See score example attached. In mm4 and other similar places, the position of the chord symbol E7superscript-9 can be changed to the right position by clicking the y offset and then the revert 'x' symbol. However, this change is not saved and upon reopening the file, the chord symbol position remains unchanged.
In reply to On further investigation,… by patspector
The E7-9 in measure 4 has automatic placement turned off, so do the other true chord symbols. For me, though, nothing happens if I hit the reset button on the E7-9 offset. So I'm still not sure how to reproduce the problem you refer to.
However, there are a few things going on here that are causing problems. I guess this score was probably imported from 2.3.2? It probably had some things that were manually moved from above to below the staff and/or vice versa, and this is what resulted in some issues on the import as we tried our best to represent this in the new way layout works. In particular, that staff text is set to "below" the staff so the offset is backwards. Better to change it to above and then use a normal offset - or, just change it to a true chord symbol.
In reply to The E7-9 in measure 4 has… by Marc Sabatella
Just changing those positions to above fixed the problem and it saves correctly. Thanks, it was an import from 2.3.2.
In reply to Just changing those… by patspector
True chord symbols do not permit superscript and subscript which is why I used text with the chord superscript symbols. Anyway of implementing super and sub scripts to true chord symbols?
In reply to True chord symbols do not… by patspector
True chord symbols already superscript and subscript automatically as appropriate for the selected style (Standard vs Jazz). I order for the automatic formatting to work correctly, we can't also allow user overrides.
If you have your own special chord symbol style you want to enforce that does formatting different than either the Standard or Jazz style, you have the option of defining a Custom style. If you search around these forums, you will find some information on this, but it's definitely an advanced technique that requires some investment of effort.
Anyhow, if these are true chord symbols, you definitely do not want to resort to plain text. In addition to the inconsistency in formatting compared to true chord symbols, they won't transpose, they won't work with capo, they won't export to MusicXML properly, etc.
In reply to True chord symbols already… by Marc Sabatella
Is there anyway of changing the font in Jazz style?
In reply to Is there anyway of changing… by patspector
No, some of the formatting is built in to the font itself (eg, it provides pre-superscripted versions of relevant glyphs).