Re: [Mscore-developer] losing tempo

Hi Nicolas, maybe I have reproduced the problem. For me this score shows a tempo of 37 but plays at something I'll guess is about 60. What does it play like for you? andante.mscx -- View this message in context: http://dev-list.mus

Re: [Mscore-developer] losing tempo

When I delete the tempo text and create it again, I get this difference in the xml file. @@ -200,12 +200,13 @@ 3 4 1 - 1 - noteQuarterUp = 37 + 0.616667 + 1 + unicodeNoteQuarterUp = 37

Re: [Mscore-developer] losing tempo

As I said before, it only follows the text in your tempo marking if the "Follow text" option is set in the Inspector, which it isn't in this case. And the text has to be followable - MsueScore won't try to guess what "Not too fast" means, etc. For tempos where following the text does not make sens

Re: [Mscore-developer] losing tempo

I think I see how to reproduce this. Open the attached andante.mscz file. Press Play and you'll see it plays at 60 bpm. How select the tempo text at the first measure by double clicking. Change the text to 37. Click outside the select region to deselect, and exit text edit mode. Now press play. Fo

Re: [Mscore-developer] programmatic access of figured bass

Jim Newton wrote > I will make some small changes in the FiguredBass related classes in order > to figure out what it is I need. > I don't need write access. Mainly I need to iterate over the annotated > figures associated with a chord/note. At each iteration I need to access > enough information

Re: [Mscore-developer] programmatic access of figured bass

Maurizio M. Gavioli wrote > [...] But the under-notated (for our 'modern' feelings) B.c. in most of > the XVIII c. music is hard to realize automatically [...] Of course, it is a typo; I was meaning the "XVII c."! Maurizio -- View this message in context: http://dev-list.musescore.org/program