From: Torben Schulz <public@letorbi.de>
To: Alsa-Devel <alsa-devel@alsa-project.org>
Cc: Takashi Iwai <tiwai@suse.de>
Subject: [PATCH 0/1] Improved MacBook 3,1 support
Date: Mon, 18 May 2009 12:51:49 +0200 [thread overview]
Message-ID: <4A113DC5.5040300@letorbi.de> (raw)
Hi guys,
this patch improves the support for the MacBook 3,1, which had been handled by the "mbp3" model before. The "mbp3" model is quite inappropriate for the sound-chip of the MacBook 3,1 (RealTek ALC889A). Especially the lack of subwoofer support is one of the biggest disadvantages of this model (See bug 0004086).
In contrast to the other models this model is part of the ALC883 configuration, which reflects the ALC889A sound-chip far better than the ALC882 configuration, which all other Apple models are part of.
I myself own only a MacBook 3,1, but as far as I know it should also work for the MacBook 4,1 - perhaps even for other models. It would be good if someone could check this out...
The new MacBook 3,1 model is called "mb31" and has the following features:
- sound from the third speaker (aka "subwoofer")
- 5.1 surround sound
- speakers and subwoofer are muted when headphones are plugged in.
- 4 channel modes
- 2ch: speakers:front, subwoofer:CLFE, headphones:front, line:input
- 4ch: speakers:front, subwoofer:CLFE, headphones:front, line:CLFE
- 5ch: speakers:front, subwoofer:CLFE, headphones:rear, line:input
- 6ch: speakers:front, subwoofer:off, headphones:rear, line:CLFE
However, there are also two "issues":
Speaker will be unmuted, when channel-mode is changed while headphones are plugged in. But this can easily be solved, by plugging the headphones out and in again or using the speaker switches in the mixer.
I haven't managed to get "real" surround sound. It seems that the front channel is mapped to all other channels before they get to the mixers (front-left=front-left, front-right=front-right, rear-left=front-left, rear-right=front-right, LFE=front-right, center=front-right). The volume of each channel can be set individually through the mixer. However, this could also be an high configuration issue on my side (please tell me ^^)...
Bai
Torben
reply other threads:[~2009-05-18 10:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A113DC5.5040300@letorbi.de \
--to=public@letorbi.de \
--cc=alsa-devel@alsa-project.org \
--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.