This was posted by LightORamaJohn.
The CCB controller has one unit ID and 320 channels. Channels 1-160 are bulb string one. 1-150 = RGB, 151-157 = res/macro/color-effect, 158-160 = reserved. Channels 161-320 are bulb string two. 161-310 = RGB, 311-317 = res/macro/color-effect, 318-320 = reserved. In legacy unit ID mode it can take up to 20 unit IDs.
A bulb string is programmed like a CCR. Same RGB, res/macro/color-effects. This was done for sequence compatibility. The only difference is that the res channel can be used to 'flip' a bulb string. Adding 50 to the resolution intensity channel flips the pixels on that bulb string. I. e. a resolution of 100 means a resolution of 50 but the pixels on the string are addressed opposite the configured orientation -- which is normally pixel one closest to the controller. This is an easy way to mirror any effect programmed, either RGB or macro without changing the sequence.
This is a total rewrite of the CCR firmware into a higher performance language and will be moved to the CCR once it is proven. The rewrite was required to handle the worst case of almost 70,000 adjustments per second required in the CCB controller. Right now a 100-bulb CCB consumes an entire DMX universe. On a LOR network, you can drive, at the pixel level, about three CCB controllers each with two 50-bulb strings. We are hoping the new firmware will allow us to run at twice the current fastest network speed so that twelve 50-bulbs strings can run on one LOR network -- we'll see. This doubling would also apply to CCRs.
The Sequence Editor will be enhanced to make insertion of a double string CCB easier.