From: "S. Christian Collins" <s.chriscollins@gmail.com>
To: Mark Hills <mark@xwax.org>, Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: "alsactl store" fails to save Echo Gina3G mixer
Date: Wed, 30 Aug 2017 09:17:49 -0500 [thread overview]
Message-ID: <13fd0b91-d0ed-3b8e-4042-1ad996135661@gmail.com> (raw)
In-Reply-To: <1708292129400.21841@stax.localdomain>
On 08/29/2017 03:36 PM, Mark Hills wrote:
> I think you're suffering the same problem I am with my Echo Layla 3G. Does
> 'echomixer' work?
Yes, 'echomixer' works fine for me. I have to launch it on occasion to
properly set my audio output level (just launching it restores the
correct level). I didn't have to do this in the past, so I'm guessing
it's probably related to the problem with 'alsactl store' not working
anymore for the card.
> I have been intending to make a 'proper' report to the list, or even
> investigate more myself. But priorities did not permit that yet. I also
> wasn't able to find information on what these fields actually mean. As far
> as I could tell, some of these attributes are unique to the echo3g and
> echomixer.
Yeah, I've never seen a mixer quite like this one. Using 'alsamixer' to
adjust my Echo3G is almost pointless, since it is impossible to tell
what is what.
-~Chris
prev parent reply other threads:[~2017-08-30 14:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 15:34 "alsactl store" fails to save Echo Gina3G mixer S. Christian Collins
2017-08-29 3:33 ` Takashi Sakamoto
2017-08-29 3:46 ` S. Christian Collins
2017-08-31 3:50 ` Takashi Sakamoto
2017-08-31 20:25 ` S. Christian Collins
2017-09-04 20:23 ` Mark Hills
2017-09-14 13:40 ` S. Christian Collins
2017-09-15 5:21 ` Takashi Sakamoto
2017-10-03 1:53 ` Takashi Sakamoto
2017-10-03 18:05 ` S. Christian Collins
2017-08-29 20:36 ` Mark Hills
2017-08-30 14:17 ` S. Christian Collins [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=13fd0b91-d0ed-3b8e-4042-1ad996135661@gmail.com \
--to=s.chriscollins@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=mark@xwax.org \
--cc=o-takashi@sakamocchi.jp \
/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.