Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
wiki:alsa_part2 [2012/10/13 19:52] – [Surround sound] mention mics aus9 | wiki:alsa_part2 [2018/10/04 20:22] (current) – [Other web resources and credits] aus9 | ||
---|---|---|---|
Line 38: | Line 38: | ||
add line to / | add line to / | ||
^opt/ | ^opt/ | ||
- | or | ||
- | < | ||
- | sudo echo -e ' | ||
- | </ | ||
**Note** we drop the first / for each file in filetool.lst. | **Note** we drop the first / for each file in filetool.lst. | ||
Line 51: | Line 47: | ||
Add extra line to filetool.lst | Add extra line to filetool.lst | ||
^usr/ | ^usr/ | ||
- | or | + | |
- | < | + | Next add the following line to bootlocal.sh |
- | sudo echo -e '\nusr/local/etc/asound.state' | + | ^/usr/local/sbin/alsactl |
- | </ | + | |
- | The alsasound script will restore | + | |
**alsaconf users**\\ | **alsaconf users**\\ | ||
Add extra line | Add extra line | ||
^etc/ | ^etc/ | ||
- | or | ||
- | < | ||
- | sudo echo -e ' | ||
- | </ | ||
**sound device model changed to fix up controls or options**\\ | **sound device model changed to fix up controls or options**\\ | ||
Line 74: | Line 64: | ||
First use root powers to edit / | First use root powers to edit / | ||
< | < | ||
- | echo -e ' | + | sudo echo -e ' |
</ | </ | ||
There is no need to add the home file mysound.state to filetool.lst as it goes into mydata.tgz on shutdown or reboot. | There is no need to add the home file mysound.state to filetool.lst as it goes into mydata.tgz on shutdown or reboot. | ||
Line 84: | Line 74: | ||
Need to know what their bootloader is, and use root powers to edit that config file.\\ | Need to know what their bootloader is, and use root powers to edit that config file.\\ | ||
Typically, the file is likely to be under /boot folder and /boot is outside the rootfs (the unpacked core.gz). boot folder is often at same partition as the tce folder but its not necessary that it is. | Typically, the file is likely to be under /boot folder and /boot is outside the rootfs (the unpacked core.gz). boot folder is often at same partition as the tce folder but its not necessary that it is. | ||
+ | |||
+ | **/ | ||
+ | This file is backed up to mydata.tgz so no further action need for it. Be aware that you may have changed mixer levels. | ||
=====Persistence - LIVE TEST and CHECKLIST===== | =====Persistence - LIVE TEST and CHECKLIST===== | ||
Some users may like to test that their saved mixer level files are good before reboot? Try | Some users may like to test that their saved mixer level files are good before reboot? Try | ||
Line 142: | Line 135: | ||
The above help is not helpful for microphone or capture devices, these input devices need the SPACE BAR to activate or de-active. The default seems to be de-active. | The above help is not helpful for microphone or capture devices, these input devices need the SPACE BAR to activate or de-active. The default seems to be de-active. | ||
- | So I have made up a new image that might help newbies? | ||
- | |||
- | {{http:// | ||
I have hidden the mic sections below as most users tend not to use mics. | I have hidden the mic sections below as most users tend not to use mics. | ||
Line 193: | Line 183: | ||
**Part 2 - CREATE NEW BOOTLOADER ENTRIES**\\ | **Part 2 - CREATE NEW BOOTLOADER ENTRIES**\\ | ||
- | Ok you may need to revisit blacklist section link 66666666 | ||
- | |||
We blacklist all sound modules. While editting, we create 2 entries one for each sound device. So your bootloader config editted with root powers becomes\\ | We blacklist all sound modules. While editting, we create 2 entries one for each sound device. So your bootloader config editted with root powers becomes\\ | ||
Line 264: | Line 252: | ||
=====Normal microphones===== | =====Normal microphones===== | ||
+ | |||
+ | Check how many inputs you have, in case you did not know, or suspect broken hardware wtih | ||
+ | < | ||
+ | arecord -l | ||
+ | |||
+ | (my example) I have front and rear mics in a tower | ||
+ | **** List of CAPTURE Hardware Devices **** | ||
+ | card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] | ||
+ | Subdevices: 2/2 | ||
+ | Subdevice #0: subdevice #0 | ||
+ | Subdevice #1: subdevice #1 | ||
+ | </ | ||
+ | |||
+ | If you want to use command mode those are renamed as hw:0,0,0 and hw:0,1,1 | ||
+ | |||
+ | Now lets explain that.\\ | ||
+ | first number is the card index number\\ | ||
+ | second number is subdevice\\ | ||
+ | third is sub-component | ||
If you have normal 3.55 mm orange colour connector microphone, you may still need to do some tweaking.\\ | If you have normal 3.55 mm orange colour connector microphone, you may still need to do some tweaking.\\ | ||
Line 273: | Line 280: | ||
and I have 2 sliders and 2 settings in my alsamixer. | and I have 2 sliders and 2 settings in my alsamixer. | ||
- | {{http:// | + | image to be updated later |
In above image, I have paired slider 1 with setting one and slider 2 with setting 2 so it reads\\ | In above image, I have paired slider 1 with setting one and slider 2 with setting 2 so it reads\\ | ||
Line 279: | Line 286: | ||
...the second capture device is zeroed for back mic with dmux set to zero. | ...the second capture device is zeroed for back mic with dmux set to zero. | ||
- | **How to activate your mic**\\ | + | =====How to activate your mic===== |
- | If your alsamixer mic control does not dispaly the word CAPTURE above the bottom capture control, then press the **SPACE BAR** in alsamixer to unmute or activate the mic. Next, use the page up or down or arrow up or down to set the volume levels. So if active, you must see 2 " | + | If your alsamixer mic control does not dispaly the word CAPTURE above the bottom capture control, then press the **SPACE BAR** in alsamixer to unmute or activate the mic. Next, use the page up or down or arrow up or down to set the volume levels. |
TIP, distortion is more likely at max volume try somewhere between 80-90% and consider doing record and playbacks to confirm. | TIP, distortion is more likely at max volume try somewhere between 80-90% and consider doing record and playbacks to confirm. | ||
- | {{http:// | + | {{wiki:mic.jpg}} |
+ | |||
+ | The mux setting is like a kind of mic amplifier and I suggest you do not use it unless with volumes maxed etc, you can not hear sufficient volume. Note when raised mux is more likely to lead to distortion. | ||
+ | |||
+ | If your alsamixer image has a slider and one named digital then you have an advantage over most sliders. The non-digital slider can be volume zero but kept active, and your mic volume is controlled by the digital slider. | ||
- | The mux setting is like a kind of mic amplifier | + | TIP |
- | hear sufficient | + | If you have a headset |
- | Note when raised .....mux....can lead to distortion. | + | =====Volume guidelines===== |
+ | As a general rule, never set volume | ||
===== How to change setting for mic ===== | ===== How to change setting for mic ===== | ||
Line 327: | Line 339: | ||
Depending on whether you are using skype or video recording, you may need to save a backup of your mixer levels for that webcam. For problems with microphones see Forums, e.g. http:// | Depending on whether you are using skype or video recording, you may need to save a backup of your mixer levels for that webcam. For problems with microphones see Forums, e.g. http:// | ||
+ | =====Modems===== | ||
+ | If you happen to have a modem supported by alsa, then you may find some settings for it in alsamixer, showing as a distinct sound device, e.g. Off-hook and Caller ID. | ||
=====Other web resources and credits===== | =====Other web resources and credits===== | ||
TC maintainers for OSS and Alsa | TC maintainers for OSS and Alsa | ||
- | * -Jason W, Juanito, Curaga | + | * Jason W, Juanito, Curaga |
+ | * Moderator Rich for setup guide | ||