Ricard Wanderlof wrote:
On Sun, 10 Apr 2016, Clemens Ladisch wrote:
By default, amidi ignores Active Sensing messages because they are sent by many devices in the background and would only interfere with the actual messages that amidi is supposed to capture. However, there are also devices that send Clock messages with the same problem, so it is a better idea to filter out all System Real-Time messages.
I would argue that it would be better to have both options, somehow. I.e. active sensing is mostly a nuisance, but I can imagine occasions (analyzing the output from a sequencer perhaps) where one would want to keep the rest of the real time messages.
I can imagine this too, and even more complex filters.
But the amidi tool is designed to be simple, and works on the lowest level, with raw MIDI bytes. This makes it appropriate to handle SysEx stuff and to debug low-level hardware problems, but when you care about the semantics of the messages, you should use a higher-level tool, such as aseqdump.
Filtering out clock messages serves an actual need. But I am not willing to add complexity for a problem that is, at the moment, nothing but a figment of our imaginations.
Regards, Clemens