Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: usage of snd_rawmidi_status_get_avail()
Date: Thu, 20 Feb 2020 03:18:45 +0100 (CET)	[thread overview]
Message-ID: <20200220021845.B9BD7F80278@alsa1.perex.cz> (raw)
In-Reply-To: <1582165123128607035-webhooks-bot@alsa-project.org>

alsa-project/alsa-lib issue #26 was edited from MusicMaker:

In non blocked raw MIDI, is snd_rawmidi_status_get_avail supposed to return the number of available bytes than can read via snd_rawmidi_read. (port is opened for read only)  It seems get_avail always returns 0 even there is MIDI data when using a read.  Else is there a(nother) way to find the number of unread received bytes in the buffer?
snd_rawmidi_status_alloca (&status);  	
snd_rawmidi_status(client, status); 
snd_rawmidi_status_get_avail(status);

Issue URL     : https://github.com/alsa-project/alsa-lib/issues/26
Repository URL: https://github.com/alsa-project/alsa-lib

       reply	other threads:[~2020-02-20  2:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1582165123128607035-webhooks-bot@alsa-project.org>
2020-02-20  2:18 ` GitHub issues - edited [this message]
     [not found] <1582165218427489996-webhooks-bot@alsa-project.org>
2020-02-20  2:20 ` usage of snd_rawmidi_status_get_avail() GitHub issues - edited
     [not found] <1582165206036581993-webhooks-bot@alsa-project.org>
2020-02-20  2:20 ` GitHub issues - edited
     [not found] <1582165190266139030-webhooks-bot@alsa-project.org>
2020-02-20  2:19 ` GitHub issues - edited
     [not found] <1582165079840311050-webhooks-bot@alsa-project.org>
2020-02-20  2:18 ` GitHub issues - edited
     [not found] <1582164934834173918-webhooks-bot@alsa-project.org>
2020-02-20  2:15 ` GitHub issues - opened

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=20200220021845.B9BD7F80278@alsa1.perex.cz \
    --to=github@alsa-project.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox