On Thu, 19 Dec 2024 00:24:11 +0100, Correo Alternativo wrote: > > Hi, I'm trying out MIDI 2.0 and found a problem, when using > snd_seq_set_client_midi_version > > With SND_SEQ_CLIENT_LEGACY_MIDI I get the following sequence of events > when connecting a midi device (using the method snd_seq_event_input or > snd_seq_ump_event_input) (timidity command:timidity --interface=A > --buffer-fragments=2,8 --output-mode=s1l --sampling-freq=44100): > > SND_SEQ_EVENT_CLIENT_START > SND_SEQ_EVENT_PORT_START > SND_SEQ_EVENT_PORT_START > SND_SEQ_EVENT_PORT_START > SND_SEQ_EVENT_PORT_START > > But with SND_SEQ_CLIENT_UMP_MIDI_1_0 and SND_SEQ_CLIENT_UMP_MIDI_2_0 I > don't get the SND_SEQ_EVENT_PORT_START events, I only get the > following: > > SND_SEQ_EVENT_CLIENT_START > SND_SEQ_EVENT_SYSTEM > SND_SEQ_EVENT_SYSTEM > SND_SEQ_EVENT_SYSTEM > > I don't know if I'm asking this in the right place, what mistake am I > making? Just by modifying that it stops working. Hmm, there should be no difference in this regard between the legacy and UMP clients. Do you mean that the destination client (i.e. timidity) doesn't receive *_PORT_START events when you send from a UMP client? Or how is the actual setup and the connection? thanks, Takashi
