Page 1 of 1

Why don't OSC and keyboard support Next Column?

Posted: Wed Sep 02, 2015 12:54
by Sadler
Why the MIDI and DMX have buttons to map column advance but the keyboard and OSC don't?

Re: Why don't OSC and keyboard support Next Column?

Posted: Thu Sep 03, 2015 21:51
by Joris
I've moved your question into its own topic.

Neither Midi nor DMX have a column advance option. A Next Column button is fundamentally different from the button you are talking about. We're aware of how much you would all like such a feature and it's confirmed to come in a future version.

Midi and DMX just have the option to assign column triggers to a single DMX channel or Midi cc, where each value on that channel or cc will then trigger columns. So you can assign DMX channel 1 to this control, and then send value 1 to trigger column 1, value 2 to trigger column 2 etc. This is done so that you don't have to map 255 DMX channels to trigger clips, but rather use 1 channel to trigger all 255 of them.

OSC already can do this. Just program your sending software to send trackX/connect/, where X is the value of the column you want to trigger. A keyboard can't have this option, because it only has two states, on and off. You can't use it to trigger different columns based on a single control.

Does that explain things a bit?

Re: Why don't OSC and keyboard support Next Column?

Posted: Thu Sep 03, 2015 23:44
by Sadler
Yes it does, thanks. Always stuff to learn as ever.

Even though esoteric features like this might not be documented that still no excuse for not RTFM. The default key mappings are quite interesting - especially p & s - though p is a little sensitive it works great with a trackpad or wacom.