On Jul 21 2015 23:06, Clemens Ladisch wrote:
Takashi Sakamoto wrote:
Typically, such messages should be converted to MIDI control change messages for userspace applications.
It would be possible to have ALSA mixer controls for these, but this would make sense only if these controls are suitable to be displayed in a generic mixer application. I guess this isn't the case for most of them.
Indeed. The main purpose of these physical controls is to control DAW softwares or the other devices. On the other hand, the major usage of ALSA control elements is to control the device itself.
Thus, this driver should have a converter with appropriate MIDI map. Currently I have no good idea for the map and it is not implemented yet.
I guess the Windows driver does not makes this information available in any way?
Windows driver gives GUI to select the way to parse the control information with three options. All of the options are based on MIDI messaging. Therefore, the driver perform to convert to MIDI messages, I think.
Furthermore, two of the options are somewhat compliant to Mackie something. In Open Source Software, Ardour Gtk+ can handle the Mackie something. In this reason, I think it's users' advantage to apply MIDI converter for the control messages.
If all the data is device-specific, the actual mapping chosen does not really matter, because the mixer/control application needs to have special code for parsing the data from this particular Linux driver anyway.
Exactly, with ignoring the updating interval.
Regards
Takashi Sakamoto