Sysex data versus midi controller data

[richford]

I notice that all the Kronos controls send sysex messages.

Is there a way to map midi CC numbers to these so that I can for example edit the automation of the filter cutoff?

[ed_f]

I notice that all the Kronos controls send sysex messages.

Is there a way to map midi CC numbers to these so that I can for example edit the automation of the filter cutoff?

Check the parameter guide midi implementation to see what is controlling any options. If it is sysex only - there isn't a way to map directly for example CC101 to some sysex. You can do it if you are going out to a computer though, that works really well.

[StephenKay]

I notice that all the Kronos controls send sysex messages.

Is there a way to map midi CC numbers to these so that I can for example edit the automation of the filter cutoff?

Just about every operation on the Kronos sends SysEx messages. However, many things already have CC's assigned to them.

For example, Filter Cutoff is CC#74.

Check the manual for details on what CC's are available, before you attempt to play with SysEx.

And no, there is nothing you can do on the Kronos to assign a CC to something that sends SysEx, that does not already have a CC specified for it. You can do that in a computer with various programs, as ed_f said.

[SoundQuest]

As I believe Ed_f is suggesting, the Kronos editor is capable of linking any control in the editor interface to a CC value. Once this is done, for any received CC, the comparable SysEx data is output to the Kronos. This allows you to effectively control any Kronos parameter with CC values even if the instrument doesn't specifically support it. Of course, you do need to be connected to the computer to do this.