I began with importing a mxml file from MuseScore, but I don’t think that has any bearing on the issue — In the Score edit window —Saying I have two “G’s” in a measure and I transpose the second one, either way. The first one vanishes, but it is still there in piano roll edit. Going to piano roll and transposing the note, then putting it back to “G”, makes it re- appear in Score.
Guys, the tools screens from the drop down shouldn’t auto close after edit. I finished a chart with several musical cues scattered throughout the chart. Once the chart is done, I go back and change the note heads to cues. Menu bar > Score > Note Head. Except there is no Cue size note head there (unlike MuseScore and C12) so I have to use a slash. But the problem is that the window closes after each edit. It would be great for it to stay open, instead. And really, “note head” should be under Note Functions side bar, instead of in the menu. Something I like about MuseScore is, if you right click, the note edit screen pops up that makes work go quicker..
Similar, setting number of bars per stave is a PITA, for the same reason - I can’t leave the Staves and systems window open, and make multiple edits, and, once open, I can’t make an edit… . It is way easier to read a chart if things like “B” (the bridge) begins on a new stave, not in the middle, coda sections, DC / DS, are at the beginning or end of a stave. So sometimes there has to be 5 bars per stave, then 3 on the next one, for instance. This was really easy to do in C12 - select a stave, open “Number of bars” edit, select new stave, edit, etc..
Frankly, I think your coders should start with a song like Horace Silver’s “ecaroh” which has 2 codas, shift from latin to swing, and make a chart, then transpose it to another key. I think you’ll run into a lot of the these things.
And - I can’t figure out which program, C15 or MuseScore, has this issue, but coda signs don’t always make it across correctly when using mxml. The rest of the guys in the combo use MuseScore 4.6, which has its own issues, so I prefer to work in C15, but I also have MuseScore, to make sure the import is correct in C15.
I hope to see an update to C15 score soon.