All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Knoth <adi@drcomp.erfurt.thur.de>
To: alsa-devel@alsa-project.org
Subject: Re: alsa-tools HDSP mixer broken
Date: Mon, 4 Apr 2011 13:58:51 +0200	[thread overview]
Message-ID: <20110404115851.GS28811@ltw.loris.tv> (raw)
In-Reply-To: <BANLkTim9G+a=7Qqd+4n-5AWWT0J4=v1eYA@mail.gmail.com>

On Mon, Apr 04, 2011 at 08:16:21AM +0200, Klaus Schulz wrote:

Hi!

> The official version of alsa-tools 1.0.24.1 seems to be broken.
> HDSP mixer won't run.
> 
> I made it work though  with the git version.
> 
> Would be nice if you could release a tools 1.0.24.2 soon. I consider this a
> critical bug.


Please don't release hdspmixer without having the preset load/restore
issue sorted out.

The ondisk structure contained no meta information, so it's already hard
enough to tell which version of hdspmixer created a given preset file.

Having more officially released versions available complicates things.
I've recently introduced a magic header for the new ondisk structure,
but it isn't stable, yet.

While I think it's perfectly acceptable to have unstable ondisk
structures during development, I would like to have a stable format
when releasing.

Current plan:

  - no magic: old (pre v1.0.24 format or broken v1.0.24.(.1))
  - v1 style: fixed format, maybe will become v1.0.24.2
  - v2 style: only single card instead of three cards in one preset file


Just my €0.02

-- 
mail: adi@thur.de  	http://adi.thur.de	PGP/GPG: key via keyserver
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2011-04-04 11:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  6:16 alsa-tools HDSP mixer broken Klaus Schulz
2011-04-04 11:58 ` Adrian Knoth [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=20110404115851.GS28811@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.