From: Paul Davis <pbd@op.net>
To: Abramo Bagnara <abramo@alsa-project.org>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@suse.cz>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: how to define a 2-index control element?
Date: Tue, 07 May 2002 20:00:41 -0400 [thread overview]
Message-ID: <200205080000.CAA29681@alsa.alsa-project.org> (raw)
In-Reply-To: Your message of "Wed, 08 May 2002 00:06:20 +0200." <3CD84FDC.1056ACA1@alsa-project.org>
>We have well designed control keys (id) and I don't see any reason to
>change something that's perfectly suitable (without any compromise) for
>the job.
the implementation is not well designed for cases of 1500
controls. perhaps, as jaroslav says, this could be improved. but even
if that is done, the API forces the user application to do some
special encoding to generate the index that cannot be inferred from
the description provided by the API. an application that wants to
modify the gain for source S to destination D will have to know how to
encode S and D into the index - it cannot discover this from the API.
thats a lot worse than just a compromise if you ask me.
>We have the sane association one control / one value and just because
>this card has many controls, you seems to wish to go toward a different
>(IMO insane and confusing) solution.
IMHO, the 1:1 association is sane only when there are relatively small
numbers of controls. It doesn't make any sense to me to
>Consider that independently from how you represent the data this card
>will ever have many controls (i.e. many values to show/change).
this isn't true. if we had a MATRIX element type, applications could
easily say
"i don't display matrix elements"
"i don't display matrix elements of dimensionality > 2"
"i don't display matrix elements when the matrix is larger than N"
and so forth. the problem with the current system is that if anyone
makes the mistake of firing up a generic control API program, they
will see all 1500 controls. i'd like to see you explain that as "sane"
to the user.
>I definitely don't see your point, sorry.
are you claiming that you really designed the control API as it exists
now to handle situations with this many controls?
--p
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
next prev parent reply other threads:[~2002-05-08 0:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 12:45 how to define a 2-index control element? Paul Davis
2002-05-04 13:18 ` Abramo Bagnara
2002-05-05 13:48 ` Paul Davis
2002-05-05 15:50 ` Jaroslav Kysela
2002-05-06 1:32 ` Paul Davis
2002-05-06 6:46 ` Jaroslav Kysela
2002-05-06 11:22 ` Paul Davis
2002-05-06 11:44 ` Jaroslav Kysela
2002-05-06 12:03 ` Takashi Iwai
2002-05-06 12:19 ` Abramo Bagnara
2002-05-06 12:53 ` Takashi Iwai
2002-05-06 19:11 ` Abramo Bagnara
2002-05-07 9:29 ` Takashi Iwai
2002-05-07 9:55 ` Jaroslav Kysela
2002-05-07 10:34 ` Takashi Iwai
2002-05-07 17:17 ` Paul Davis
2002-05-07 22:06 ` Abramo Bagnara
2002-05-08 0:00 ` Paul Davis [this message]
[not found] <20020508000005.EB5AC59D35D@kerberos.suse.cz>
2002-05-08 7:52 ` Jaroslav Kysela
2002-05-08 9:52 ` 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=200205080000.CAA29681@alsa.alsa-project.org \
--to=pbd@op.net \
--cc=abramo@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=perex@suse.cz \
--cc=tiwai@suse.de \
/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.