roadmaps for insights in jazz leadsheets - bob keller
DESCRIPTION
LEGO Jazz HarmonyTRANSCRIPT
Roadmaps Produced by Impro-Visor 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 Impro-‐Visor. 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 Impro-‐Visor 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. Impro-‐Visor currently produces only uniform-‐scaled 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 Impro-‐Visor, and is tracked beat by beat, so we want the spacing to correspond to a uniform meter. Another reason is that making a non-‐uniform 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 sub-‐optimal. 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 Impro-‐Visor 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 stand-‐alone 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 eight-‐measure line can end up really long if there is a lot of complexity, so occasionally four-‐measure lines are used instead. (In the future, I will probably go to a four-‐measure line as the standard, even though parallel structure is often clearer with eight-‐measure lines.)
In general, when making your own roadmaps with Impro-‐Visor, it is best to minimize unnecessary chord embellishments, as these are more likely to foil Impro-‐Visor’s brick recognition algorithm.
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146 Document Revision History Revision 1 (6 Oct. 2011):
Changed width of large maps to 10”. Revised “Old Devil Moon” (On/Off by making F7 into F7_) Revised dictionary slightly, which induced the following changes:
“Everything I Love” (Rainbow Cadence brick) “Someday My Prince Will Come” (Rainbow Cadence brick) “My Foolish Heart” (Yardbird Approach brick)