A live-coding lighting controller, building on the Open Lighting Architecture with Clojure and bits of Overtone.
brunchboy on master
Turn off broken "Edit this Page… (compare)
brunchboy on master
Add antora and netlify credits … (compare)
brunchboy on master
Update other dependencies. (compare)
brunchboy on master
Update CoreMidi4J. (compare)
brunchboy on master
Update to link to netlify hoste… (compare)
brunchboy on master
Update doc readme to reflect us… (compare)
brunchboy on master
Fix typo in function name. (compare)
brunchboy on master
Remove insecure HTTP link, than… Try simplifying API doc path, u… (compare)
brunchboy on master
Working on netlify doc build. (compare)
brunchboy on master
Update Clojure version. Update Codox version. Try setting up Netlify build fo… (compare)
brunchboy on master
Update jquery.mincolors color p… Start wedding reception show. (compare)
brunchboy on master
Fix more broken images due to w… (compare)
DJMDevice.playStateMap
. (Although I know the meaning of some values that are missing in libdjm.js
: 0 means no track is loaded, 4 means a loop is playing, and 17 means the end of the track has been reached and the player has stopped.)
0x89
in the packets the CDJs send to port 50002. I call it F in the protocol analysis, and it is a bit field with interesting status values for the player, including Play, Master, Sync, and On-Air bits.
itemTypeLabel
value that you may want to add as well: 0x2e
means the message contains information about when a track was added to the collection (it seems to propagate from iTunes on my system). The last message before the menu footer in a track data response has an item type with this value, and its label 1 string contains a date in the form yyyy-mm-dd
.
0x0100
, and no arguments, and then the socket closes. Wait, I just checked, and that 0x0100
message is coming right after the 0x4402
message with the 900 bytes of waveform summary even if I don’t send any more messages. So clearly I must be doing something wrong. I guess it is time to bust out my spanned switch and do some more network captures, unless you have a better idea?
0x10
kibble which we thought contained two values with a mysterious 0x0f
in between them is probably actually two kibbles! 0x10
introduces a two-byte big-endian integer (the message type), and 0x0f
introduces a one-byte integer (the argument count).