All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos <correocebe@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Possible bug with snd_seq_event_input_pending
Date: Sat, 1 Feb 2025 20:11:51 -0300	[thread overview]
Message-ID: <b77a2cd6-7b59-4eb0-a8db-22d507d3af5f@gmail.com> (raw)
In-Reply-To: <cb5ca1c7-64a3-43df-b506-db07a2b5f790@gmail.com>

Hi, I don't know if this is a bug or not, but I'll report it in case it is.

If I configure my client as follows:

snd_seq_set_client_midi_version(seq, SND_SEQ_CLIENT_LEGACY_MIDI);

snd_seq_set_client_ump_conversion(seq, 0);//I disable ump conversion

And then I send a midi event from a MIDI 2.0 device, the 
snd_seq_event_input_pending(seq, 1) function will not respond until it 
receives any other legacy event.

Now I know that with SND_SEQ_CLIENT_LEGACY_MIDI I shouldn't disable ump 
conversion, but I expected it to return 0.

Thank you

  parent reply	other threads:[~2025-02-17 10:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-18 23:24 Ask snd_seq_set_client_midi_version Correo Alternativo
2024-12-30 11:34 ` Takashi Iwai
2025-02-01 23:11 ` Carlos [this message]
2025-02-17 11:04   ` Possible bug with snd_seq_event_input_pending Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b77a2cd6-7b59-4eb0-a8db-22d507d3af5f@gmail.com \
    --to=correocebe@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.