The Score Editor is quite different from other editors in that it does not aim at 100 % exact visual representation of stored MIDI data. A direct translation of recorded MIDI notes into score graphics in most cases would (and in the case of some cheap sequencers actually does) result in a score that is so compley, that it is practically unreadable. The Space Toad for the most cases produces sufficiently readable scores, since it never directly displays its material, but rather creates a simplified interpretation of it. However, this interpretation is often a bit off the track. This because score notation is a medium for intelligent human beings, while computers are terrible stupid - especially when programmed by people as stupid as the Space Toad developer! So you will often like to make the program to interpret its data different. You can do so by adding hints to individual MIDI notes that will override the programs decision on how to interpret the data. So it should be possible to arrive at an accurate score for even complex cases as long as the following restrictions are observed (many of these may become removed in future versions):
A complex issue is how time positions will be interpreted in case of a real-time recording. Human players (even when following a metronome) never play notes on mathematically "exact" positons, but stretch and compress time according to the musical context. The Space Toad lets you decide, if you want to view a piece rather from the mathematical side or the musical side by setting up the so-called Rubato Tolerance.
When Rubato Tolerance is low, time divisions are likely to be presented "as is", even when the presence of an internal rubato requires the use of a complex rhythmic division. A "shuffle beat" e.g. (a rhythm oscillating between a 1+1 duplet and 2+1 triplet division) may have the following display when Rubato Tolerance is low (example is Jelly Roll Morton's "Frog-I-More Rag" sequenced by W. S. Trachtman):
The 3+2 quintuplet is chosen because it lies directly between there aforementioned divisions and is therefore the most accurate representation of a "shuffle beat" from a mathematical standpoint. But when Rubato Tolerance is raised, the picture becomes different. The program now starts to avoid the unusual quintuplets and replaces them by ordinary duplets and triplets according to what is nearest in the actual phrase:
Rubato Tolerance can also be completely turned off, but that is only to be recommended when dealing with MIDI scores written by hand that don't have any rubato.
These are the actions you can perform with this editor:
Use Select / Shift as Mouse Mode and click on note heads to toggle their selection status. As with other editors clicking somewhere into the void deselects all currently selected notes. Clicking into empty space and dragging the mouse opens up a selection frame.
Use Delete as Mouse Mode and click on the note heads.
Right-click on a bar line to open the corresponding dialog.
Right-click on a note head to open the respective dialog. In this special dialog you may also attach the interpretation hints mentioned above. Remember that these "hints" are really hints to the program. Sometimes it is already sufficient only to "hint" the first note of a line with debatable interpretation to correct the following notes en suite:
Move note permanently to one of the two staves. These hints can also be attached to all selected notes at once by using the functions To Upper Staff & To Lower Staff that are accessible through the context menu (right-click into an empty region to open it).
Causes notes to always have that accidental. Note that the "sharp" and "flat" hints also have the meaning of "never make this flat" and "never make this sharp". So there is a purpose to attach them even to white keys. An F that has a "flat" hint e.g. would never be taken as an E sharp, even with a C sharp major key.
A beat within which a note with such a hint is found will always be divided as given by the hint. Don't use this feature to correct the interpretation of a real-time recording played with so much rubato that it will not display correctly even with a very high Rubato Tolerance. A much better way is to adapt the bars and beats to the rubato time by using the Time Stretching function as described under the topic "Recording Techniques".