FAQ: what are the osc messages that beatseqr uses?

[stevecooley]

roxor sends out these messages:

/beatseqr/play

/beatseqr/tempo
/beatseqr/tempoadjust

/beatseqr/swing
/beatseqr/resetMatrix

ok, so this prefix of /beatseqr is consistent for all outgoing messages. It's tedious to include that, so just know that all messages coming out of roxor are going to have /beatseqr at the start. here are the rest:

/matrix/1/0 through /matrix/1/15 (this is all of the step data. Beatseqr manages a lot of this when you change patterns, so steppa can focus on doing one pattern well)
/matrix/2/0 through /matrix/2/15
/matrix/3/0 through /matrix/3/15
/matrix/4/0 through /matrix/4/15
/matrix/5/0 through /matrix/5/15
/matrix/6/0 through /matrix/6/15
/matrix/7/0 through /matrix/7/15
/matrix/8/0 through /matrix/8/15

/velocity1 (tells steppa to change the velocity for the channel being changed on the hardware)
/velocity2
/velocity3
/velocity4
/velocity5
/velocity6
/velocity7
/velocity8

/midicc1 (tells steppa to change the midi CC values for the channel being changed on the hardware)
/midicc2
/midicc3
/midicc4
/midicc5
/midicc6
/midicc7
/midicc8

/midinotenum1 (tells steppa to change the midi note number for the channel being changed on the hardware)
/midinotenum2
/midinotenum3
/midinotenum4
/midinotenum5
/midinotenum6
/midinotenum7
/midinotenum8

roxor receives:

/currentstep (tells roxor to tell beatseqr to update the chase lights)