CompuServe Thread

"scorestat" is used only to determine where a score is with regards to the number of times the score was set to loop with the "startscore" command. For example, if the "startscore" command was used to cause the score to play three times, you can use "scorestat" to determine which of those three times the player is currently playing. During the first time through "scorestat" will return a 3, the second time through a 2, and the last time through, a 1. This would be used perhaps to vary an animation each time through the loop, or perhaps to determine the last time through the loop where you might want to fade out or change the animation for the close, or something like that. "scorestat" will not stop the score explicitly in any way, it just reports where you are in its playback. Another way to get even more detail on the score is to use "setsigs" and "testsig" or "waitsig". You can signal on every quarter note count, or as I've found it most useful, signal on an instrument (particularly percussion or whatever instrument is pretty much always playing) then use "waitsig" and the PRINT command to print the sync event count (on the projector's window). From there I'd play the sequence, and at a point that I'm interested in, note what the value printed to the projector window was. You can then use this value as something to wait for when this particular point occurs in the score. The PRINT statements are only used to determine the values for the important events, you remove the PRINT statment and add an IF that waits for these particular values and causes some additional event (perhaps a display change or something) at these key points. You can also use such a point to begin a fadeout or something if it is near the end of the sequence, for example. Keith