From: Adrian Knoth <adi@drcomp.erfurt.thur.de>
To: alsa-devel@alsa-project.org
Subject: Re: hdspmixer broken for 96khz
Date: Sun, 3 Apr 2011 12:25:16 +0200 [thread overview]
Message-ID: <20110403102516.GJ28811@ltw.loris.tv> (raw)
In-Reply-To: <201104031139.41395.tim@klingt.org>
On Sun, Apr 03, 2011 at 11:39:41AM +0200, Tim Blechmann wrote:
> > > the updated hdspmixer doesn't work for 96khz any more. the 44.1/48 khz
> > > versions are drawn correctly, the 88.2/96 khz version hides all
> > > controls, so just the menu is visible.
> >
> > I've seen "both", a *working* hdspmixer at 96k and all hidden controls.
> > The latter could be caused by wrongly initialized or restored presets.
> >
> > Can you try to activate the controls in the View menu again? Maybe even
> > the shortcuts work: I for Input section, P for Playback and O for
>
> ok, after removing my old hdspmixer configuration file, it seems to
> work. would be good to have a more robust behavior, since the current
> behavior is quite confusing and people may have rather complex mixer
> setups, which they would need to regenerate.
I thought I have paid attention to migrate the settings from the old
file format to the new one:
http://git.alsa-project.org/?p=alsa-tools.git;a=commit;h=287bc091e9dba539399ba4540c60623dee1a3bc3
I wonder what went wrong. If you like, feel free to further dig into
this.
However, the current on-disk format is utterly stupid, it has no
meta-information at all, it will break if the order of cards change.
The whole hdspmixer is a dead-end, even supporting more than one card in
a single app complicates things like hell (I have an upcoming patch
series. Took me 6hrs or so just to get switching back/forth between two
cards right).
So the next thing I'd like to implement is to limit hdspmixer to a
single card and then run a new instance on the second, third, 4th a.s.o.
card. Like alsamixer -c 1: hdspmixer -c 1, maybe -c reflecting the ALSA
card number as found in /proc/asound/cards.
Anyway, the whole codebase is subtle broken, and the best approach would
be a rewrite from scratch. Maybe it makes sense to merge hdsp and hdspm,
first. Comments welcome. ;)
Cheers
--
mail: adi@thur.de http://adi.thur.de PGP/GPG: key via keyserver
next prev parent reply other threads:[~2011-04-03 10:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 12:28 hdspmixer broken for 96khz Tim Blechmann
2011-04-03 8:16 ` Adrian Knoth
2011-04-03 9:39 ` Tim Blechmann
2011-04-03 10:25 ` Adrian Knoth [this message]
2011-04-04 7:21 ` Tim Blechmann
2011-04-04 7:58 ` Takashi Iwai
2011-04-04 8:05 ` Tim Blechmann
2011-04-04 10:01 ` Adrian Knoth
2011-04-05 10:29 ` Tim Blechmann
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=20110403102516.GJ28811@ltw.loris.tv \
--to=adi@drcomp.erfurt.thur.de \
--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.