From: Clemens Ladisch <clemens@ladisch.de>
To: Josh Lehan <alsa@krellan.com>
Cc: Sergey <sergemp@mail.ru>, alsa-devel@alsa-project.org
Subject: Re: [PATCH - alsa-utils 5/5] The amidicat program itself, better late than never
Date: Thu, 10 Jul 2014 08:53:26 +0200 [thread overview]
Message-ID: <53BE3866.1030806@ladisch.de> (raw)
In-Reply-To: <53BDD1F4.5030003@krellan.com>
Josh Lehan wrote:
> On 07/09/2014 12:54 AM, Clemens Ladisch wrote:
>>> (unlike aplaymidi, amidicat does no filtering, it shows you
>>> everything, even including itself in the list).
>>
>> It should list only those ports it can use, i.e., connect from/to.
>
> It already does, in a way. Anything that has read/write permission,
> direct and/or subscription, is usable. I like showing everything, it's
> useful for diagnostics/troubleshooting.
Showing unusable ports _will_ introduce user errors.
If you are doing troubleshooting for something that does not involve
amidicat, the complete port list is already available in
/proc/asound/seq/clients.
Regards,
Clemens
prev parent reply other threads:[~2014-07-10 6:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 8:54 [PATCH - alsa-utils 0/5] The amidicat program as a patch Josh Lehan
2014-06-30 8:54 ` [PATCH - alsa-utils 1/5] Adding amidicat subdirectory to SUBDIRS Josh Lehan
2014-06-30 11:32 ` Clemens Ladisch
2014-07-01 7:30 ` Josh Lehan
2014-06-30 8:55 ` [PATCH - alsa-utils 2/5] Add amidicat Makefile to AC_OUTPUT list Josh Lehan
2014-06-30 8:55 ` [PATCH - alsa-utils 3/5] Makefile for amidicat, includes manual page Josh Lehan
2014-06-30 8:55 ` [PATCH - alsa-utils 4/5] Documentation manual page for amidicat Josh Lehan
2014-06-30 11:32 ` Clemens Ladisch
2014-07-01 7:34 ` Josh Lehan
2014-06-30 8:55 ` [PATCH - alsa-utils 5/5] The amidicat program itself, better late than never Josh Lehan
2014-06-30 11:33 ` Clemens Ladisch
2014-07-01 8:10 ` Josh Lehan
2014-07-08 23:55 ` Sergey
2014-07-09 5:26 ` Josh Lehan
2014-07-09 7:54 ` Clemens Ladisch
2014-07-09 23:36 ` Josh Lehan
2014-07-10 6:53 ` Clemens Ladisch [this message]
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=53BE3866.1030806@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=alsa@krellan.com \
--cc=sergemp@mail.ru \
/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.