Update documentation to reflect new color ID from #13

Also flesh out color table documentation.

Author: brunchboy

doc/modules/ROOT/pages/anlz.adoc

@@ -291,7 +291,8 @@ include::example$tag_shared.edn[]
 (draw-box (text "unknown" :math [:sub 1]) {:span 3})
 (draw-box (text "time" :math) {:span 4})
 (draw-box (text "loop_time" :math) {:span 4})
-(draw-related-boxes (repeat 12 nil))
+(draw-box (text "c" :math [:sub "id"]))
+(draw-related-boxes (repeat 11 nil))
 
 (draw-box (text "len_comment" :math) {:span 4})
 (draw-gap "comment" {:min-label-columns 4})
@@ -330,9 +331,16 @@ _type_ is 2, meaning that this cue stores a loop, then __loop_time__
 at bytes{nbsp}``18``-`1b` stores the track time in milliseconds at
 which the player should loop back to _time_.
 
-The next twelve bytes have an unknown purpose, but seem to have the
-value `00`, except for the second byte which seems to have the value
-`10`. They are followed by __len_comment__, which contains the length,
+Immediately after the loop time, at byte{nbsp}``1c`` is the single
+byte value __color_id__ (labeled _c~id~_). This holds the color,
+if any, assigned to memory points and loops. If it is not zero,
+it is the ID of a row in the <<exports.adoc#color-rows,color table>>.
+Hot cues do not use this value, and have their own color information
+later in the entry.
+
+The next eleven bytes have an unknown purpose, but seem to have the
+value `00`, except for the first byte which seems to have the value
+`01`. They are followed by __len_comment__, which contains the length,
 in bytes, of the _comment_ field which immediately follows it. If
 __len_comment__ has a non-zero value, _comment_ will hold the text of
 the comment, encoded as a UTF-16 Big Endian string with a trailing
@@ -342,25 +350,25 @@ trailing `NUL`).
 
 WARNING: Some extended cue entries are incomplete, and their
 __len_entry__ indicates they end before the comment, or include the
-comment but end before the color information. Code that processes them
-needs to be prepared to handle this, and treat such partial cues as
-having no comment and/or color.
+comment but end before the hot cue color information.
+Code that processes them needs to be prepared to handle this,
+and treat such partial cues as having no comment and/or hot cue color.
 
 Immediately after _comment_ (in other words, starting __len_comment__
 + `1c` past the start of the entry) there are four one-byte values
-containing color information. __color_code__ (labeled _c_ in the
-diagram) appears to be a code identifying the color with which
-rekordbox displays the cue, by looking it up in a table. There have
-been sixteen codes identified, and their corresponding RGB colors can
-be found by looking at the
+containing hot cue color information. __color_code__
+(labeled _c_ in the diagram) appears to be a code identifying the color
+in which rekordbox displays the cue, by looking it up in a table.
+There have been sixteen codes identified, and their corresponding RGB
+colors can be found by looking at the
 https://github.com/Deep-Symmetry/beat-link/blob/v0.6.1/src/main/java/org/deepsymmetry/beatlink/data/CueList.java#L457-L509[`findRecordboxColor`
 static method] in the Beat Link library’s `CueList` class. The next
 three bytes, __color_red__ (labeled _r_), __color_green__ (labeled
 _g_), and __color_blue__ (labeled _b_), make up an RGB color
 specification which is similar, but not identical, to the color that
 rekordbox displays. We believe these are the values used to illuminate
 the RGB LEDs in a player that has loaded the cue. When no color is
-associated with the cue, all four of these bytes have the value `00`.
+associated with the hot cue, all four of these bytes have the value `00`.
 
 We do not know what, if anything, is stored in the remaining bytes of
 the tag.

doc/modules/ROOT/pages/exports.adoc

@@ -457,6 +457,26 @@ to have any meaning.
 (draw-bottom)
 ----
 
+Regardless of the names assigned to the colors by the user, the
+row _id_ values map to the following colors in the user interface
+of rekordbox and on CDJs:
+
+.Colors displayed.
+[cols=">1m,<8"]
+|===
+|ID |Meaning
+
+|0 |No color
+|1 |Pink
+|2 |Red
+|3 |Orange
+|4 |Yellow
+|5 |Green
+|6 |Aqua
+|7 |Blue
+|8 |Purple
+|===
+
 [[genre-rows]]
 === Genre Rows
 

src/main/kaitai/rekordbox_anlz.ksy

@@ -247,8 +247,8 @@ types:
       - id: color_id
         type: u1
         doc: |
-          References a row in the colors table if the memory cue or loop
-          has been assigned a color
+          References a row in the colors table if this is a memory cue or loop
+          and has been assigned a color.
       - size: 11  # Loops seem to have some non-zero values in the last four bytes of this.
       - id: len_comment
         type: u4
@@ -263,22 +263,22 @@ types:
       - id: color_code
         type: u1
         doc: |
-          A lookup value for a color table? We use this to index to the colors shown in rekordbox.
+          A lookup value for a color table? We use this to index to the hot cue colors shown in rekordbox.
         if: (len_entry - len_comment) > 44
       - id: color_red
         type: u1
         doc: |
-          The red component of the color to be displayed.
+          The red component of the hot cue color to be displayed.
         if: (len_entry - len_comment) > 45
       - id: color_green
         type: u1
         doc: |
-          The green component of the color to be displayed.
+          The green component of the hot cue color to be displayed.
         if: (len_entry - len_comment) > 46
       - id: color_blue
         type: u1
         doc: |
-          The blue component of the color to be displayed.
+          The blue component of the hot cue color to be displayed.
         if: (len_entry - len_comment) > 47
       - size: len_entry - 48 - len_comment  # The remainder after the color
         if: (len_entry - len_comment) > 48