Roadmaps Produced by ImproVisor version 5.03 for “Insights in Jazz” Leadsheets Bob Keller 6 October 2011 Revision 1 (revision history is at the end of this document) This document contains the roadmaps for leadsheets with chord changes corresponding to John Elliott’s “Insights in Jazz” book, as analyzed by version 5.03 of ImproVisor. These were done in a single very long run, except for a few that I accidently left out in the first pass. Each roadmap was scaled manually following analysis in ImproVisor so that most features were showing, then snapped from the screen and pasted into a Microsoft Word document, which adjusted the size of each roadmap to fit the page width. ImproVisor currently produces only uniformscaled roadmaps, i.e. the width of each bar is the same, although the width of a bar can be adjusted. One reason for this is that roadmaps can be played in ImproVisor, and is tracked beat by beat, so we want the spacing to correspond to a uniform meter. Another reason is that making a nonuniform layout is a lot more difficult to program. The purpose of this is not to replace the corresponding section of John’s fine book. It is part of a research proof of concept. It is understood that some of these roadmaps are incorrect or suboptimal. We will be working toward correcting problems in future versions, which may entail modification of the leadsheet (particularly placement of section and phrase marks), the brick dictionary, and, as necessary, the ImproVisor software itself. Here are a few differences between our annotations and John Elliott’s: • We explicitly call out the inferred key (but there may be the occasional miss in this area). • Our joins appear below the first brick, rather than wedged between two bricks. • We don’t explicitly call out “Hovers” (multiple measures of the same chord). • We don’t have a notion of “abort” currently, although some equivalences may be found in our use of approaches or starts. • We don’t give nicknames to standalone chords, e.g. “Nowhere” for bVI and “Somewhere” for II7. • When two bricks have an overlapping chord, the suffix “+ . . .” appears on the first brick. (There is a current bug in that, e.g. C is recognized in overlap from a cadence, whereas “CM7” is not.) • In our case, an eightmeasure line can end up really long if there is a lot of complexity, so occasionally fourmeasure lines are used instead. (In the future, I will probably go to a fourmeasure line as the standard, even though parallel structure is often clearer with eightmeasure lines.) In general, when making your own roadmaps with ImproVisor, it is best to minimize unnecessary chord embellishments, as these are more likely to foil Impro Visor’s brick recognition algorithm.