Beginners Guide sound installation -- OSS and ALSA objective features

markg85 · 2009-09-01 11:40:08

Beginners Guide sound installation -- OSS and ALSA objective features needed

Hi,

In most wiki pages i just edit the things that i think need editing. Just look at the oss history
In all those cases i didn't really saw a need to ask for permission.. that would kinda destroy the wiki idea.

However i want to change the sound instructions in the beginners guide so i made a copy of the entire guide and the part that i changed there is: http://wiki.archlinux.org/index.php/Use … ling_Sound now i have a slight issue there. As you can see i'm in favor of OSS and because you can spot that it's not objective. Now i would ask 2 things.

1. Could you all post your features of OSS and ALSA
2. Once that's done can i have permission to place that section in the beginners guide? that will also include removing the sound installation from the beginners guide which i already did in my version

My personal reason to do this. i've read this and am since then pro OSS and against the ALSA/PulseAudio combo. i think that combo needs to get out of linux (most notably Fedora and Ubuntu) ASAP. and oss needs to go back into the linux kernel

Thank you for your time,
Mark

Willie Green · 2009-09-01 12:50:55

markg85 wrote:

My personal reason to do this. i've read this and am since then pro OSS and against the ALSA/PulseAudio combo. i think that combo needs to get out of linux (most notably Fedora and Ubuntu) ASAP. and oss needs to go back into the linux kernel
Thank you for your time,
Mark

First of all, I'd like to thank-you for your efforts on the OSS/ALSA issue.
As a relative newbie, I've been playing around with both, and they both work well for my modest needs. (just an average user who listens to music and watches videos on my older PC -- PIII-800 Deskpro w/ 512 Mb RAM)

Anyway, even though the tech details are greek to me, everything I've read favoring OSS seems to be written from a developers perspective... which is fine, but still leaves me scratching my head.

Could you please provide me with some simple advice from your better informed perspective?
All I really want to know is, which one is considered more "lightweight" and uses fewer resources on my older system? I can istall both and get both to work satisfactorily with no noticeable affect on performance. But needless to say, I'd like to stick with whichever one is theoretically "lighter" and more efficient.

Thanks in advance!!!

markg85 · 2009-09-01 13:54:53

Willie Green wrote:

markg85 wrote:
My personal reason to do this. i've read this and am since then pro OSS and against the ALSA/PulseAudio combo. i think that combo needs to get out of linux (most notably Fedora and Ubuntu) ASAP. and oss needs to go back into the linux kernel
Thank you for your time,
Mark
First of all, I'd like to thank-you for your efforts on the OSS/ALSA issue.
As a relative newbie, I've been playing around with both, and they both work well for my modest needs. (just an average user who listens to music and watches videos on my older PC -- PIII-800 Deskpro w/ 512 Mb RAM)
Anyway, even though the tech details are greek to me, everything I've read favoring OSS seems to be written from a developers perspective... which is fine, but still leaves me scratching my head.
Could you please provide me with some simple advice from your better informed perspective?
All I really want to know is, which one is considered more "lightweight" and uses fewer resources on my older system? I can istall both and get both to work satisfactorily with no noticeable affect on performance. But needless to say, I'd like to stick with whichever one is theoretically "lighter" and more efficient.
Thanks in advance!!!

A few things you need to get right first.
- I'm not an OSS developer (yes, as in open source software ) and haven't made a single app with OSS (yet)
- I've only used OSS for one full day now and spend one day trying to get it working.

However when reading the article about the sound state in me previous post i kinda got from no oss knowledge to liking oss. Why? well, oss has (for the avarage user like you and me) everything it needs to be perfect. It has the ability to have different volumes for different applications out of the box! if you use alsa you need pulseaudio for it.

So, only in terms of libraries OSS should be lighter since that's only one library! compared to the ALSA and PulseAudio combination
Now in terms of daemons/servers.. if you have PulseAudio running you have a service running in the background. that always sucks up cpu and mem usage and that's another thing you just don't have with OSS because it's simply not needed.

So for the memory and cpu footprint i would go for OSS. i haven't done any benchmarks but it seems logical that it's just lighter.

And in general OSS seems to be superior to the ALSA/PulseAudio combination and certainly when you are just an average user.
Last but not least installing OSS is just installing OSS and everything "should" work. (provided you start it, add yourself to the audio group and perhaps even restart your pc). There are NO files to be changes other then rc.conf.. you don't need to set up any layers like in alsa/pulseaudio where you need to change asound.conf and then just hope it works.

So, OSS is the way to go.

Now can i get an answer on my questions please

Shapeshifter · 2009-09-01 15:24:58

I'm using OSS on all of my boxes except the ones using an USB webcam, as USB sound recording, that is - from a USB microphone like the one in a USB webcam - is officially broken in OSS.
So maybe you should put that in the "why use alsa section". Not only USB sound cards themselves, but also USB microphones do not work with OSS.

Apart from that, I'm all in favour of OSS.

Btw ALSA + Pulse is still a really daft setup. Because for applications to actually make use of parallel output, they need to be compiled with pulse features or run through padsp. That means you still have to tell every app to use pulse. Yeah - OSS works perfectly out of the box. Problem is that OSS doesn't have many devs really, and little support from the kernel team.

Last edited by Shapeshifter (2009-09-01 15:35:58)

Tyriel · 2009-09-01 17:48:02

Just wanted to add that although I like OSS I would never recomend it to the average desktop user until it has matured more. Alsa will be easier and more convenient for more users imho. Bluetooth and usb work flawlessly with alsa plus pulse where as there is currently no means to do this with OSS. Despite what some people think pulse works really well when configured correctly, however this is not easy nor straight forward hence all the complaints and misconceptions. Also lets not forget how many more applications support Alsa (mixers etc). Waiting patiently for KDE 4.4 and native Kmix OSS support!

Personally I like OSS and I look forward to it being an Alsa replacement, however I do not beleive that time is now. I like how you put in the effort to improve the write up but I feel you need to be more objective and less bias. That all said keep up the good work

R00KIE · 2009-09-01 17:50:40

Some usb devices work with oss, I have a usb headset that does work although the rule seems to be as Shapeshifter says.

So far I am more pro OSS than pro ALSA, however usb support and the ability to suspend/hibernate with alsa is nice, no need to close every single app that is using audio before you suspend/hibernate as you need to do with OSS.

In my case sound quality with OSS was much better than the quality with ALSA although it may have improved a little since last time I tried it.

markg85 · 2009-09-01 19:08:52

Tyriel wrote:

...
Personally I like OSS and I look forward to it being an Alsa replacement, however I do not beleive that time is now. I like how you put in the effort to improve the write up but I feel you need to be more objective and less bias. That all said keep up the good work

I know that and that's why i made a thread here. But you all seem to forget that and just say something nice about OSS (that's nice, don't get me wrong but not the question).

So again. Can everyone that reads this name his pros en cons for both alsa ans oss? for example in this format:

OSS
Pros
--
--
--
Cons
--
--
--

ALSA
Pros
--
--
--
Cons
--
--
--

That's why i started this thread ^_^ with the goal to remove out my not so objective alsa and oss opinion.

Thanx,
Mark.

t4k1t · 2009-09-01 19:29:16

On my previous Arch installs I always used alsa since it occured to me, there wasn't much to configure to make it run, but on my latest install I just wasn't able to get alsa running so I switched to oss, so here is my pro/con list:

OSS
Pro
- You install oss and it kinda just works.
- It natively supports seperate channels for seperate applications

Con
- On some soundcards(for example mine ) you have to manually mute the speakers when you plug in headphones
- The mixer-app(ossxmix) is kind of complex, the large number of bars and checkboxes is a bit irritating

ALSA
Pro
- The GUI is way simpler
- The speakers mute automaticly(at least on every soundcard I ever had)

Con
- Well I for myself can't seem to get it working again^^'

Conclusion
IMHO alsa seems to be a little bit more userfriendly, while oss is really nice if you want to control your sound exact.

P.S.
At the moment I hadn't the time to test oss with apps like ardour but at tasks like streaming music from a local-/web-server and simple playing music from my local hd it occurs to me, that the sound-quality of oss was a tick better, but that isn't really objective.
Hope that helps you a bit

benob · 2009-09-01 19:50:37

I second that. If someone makes OSS's mixer applet user friendly, and it works with intel chipsets out-of-the-box, I'll use it right away.

t4k1t wrote:

On my previous Arch installs I always used alsa since it occured to me, there wasn't much to configure to make it run, but on my latest install I just wasn't able to get alsa running so I switched to oss, so here is my pro/con list:
OSS
Pro
- You install oss and it kinda just works.
- It natively supports seperate channels for seperate applications
Con
- On some soundcards(for example mine ) you have to manually mute the speakers when you plug in headphones
- The mixer-app(ossxmix) is kind of complex, the large number of bars and checkboxes is a bit irritating
ALSA
Pro
- The GUI is way simpler
- The speakers mute automaticly(at least on every soundcard I ever had)
Con
- Well I for myself can't seem to get it working again^^'
Conclusion
IMHO alsa seems to be a little bit more userfriendly, while oss is really nice if you want to control your sound exact.
P.S.
At the moment I hadn't the time to test oss with apps like ardour but at tasks like streaming music from a local-/web-server and simple playing music from my local hd it occurs to me, that the sound-quality of oss was a tick better, but that isn't really objective.
Hope that helps you a bit

Gen2ly · 2009-09-01 20:17:44

Thanks for posting here, markg85. Always good to see people contribute to the documentation. If you don't mind bit of honest feedback (otherwise go ahead and give a st.u) .

Avoid time-sensitive material:

While the package in AUR is flagged as "out of date" i can confirm that today, '''Sept. 01. 2009''' it still works fine.

While this may be true, the author may fix this tomorrow and the next 30, 50, 100 people that read the wiki may become confused by it, ignore it, or wonder if they should fix it. Putting the comment on the AUR page itself would probably be a more appropriate location.

Avoid words like ugly, best... Wiki's are for instructional purposes. Try instead to quantify definitions and be objective.

You commented your diffs. Yeeeaahhhh! Thank you. They seem, however, to be more of a carbon-copy of your entry rather than an explanation.

As for your warning, typically we use Box Notes for such things. Take a look at http://wiki.archlinux.org/index.php/Category:Template.

There is no 'I' or 'We'. You are the drill sergeant, use 'You'.

Restored 'Installing' section. Though I see where you're getting at, this doesn't keep things simple. Muuuccchhh easier just to reboot here. As a side note, do you need libflashsupport here??? I don't have it on my system and haven't had a problem with flash, but perhaps I bjorked something up.

Some good tips here, things I didn't know about. Thanks for the contributions.

Last edited by Gen2ly (2009-09-01 20:19:44)

markg85 · 2009-09-01 20:41:18

Gen2ly wrote:

Thanks for posting here, markg85. Always good to see people contribute to the documentation. If you don't mind bit of honest feedback (otherwise go ahead and give a st.u) .
Avoid time-sensitive material:
While the package in AUR is flagged as "out of date" i can confirm that today, '''Sept. 01. 2009''' it still works fine.
While this may be true, the author may fix this tomorrow and the next 30, 50, 100 people that read the wiki may become confused by it, ignore it, or wonder if they should fix it. Putting the comment on the AUR page itself would probably be a more appropriate location.
Avoid words like ugly, best... Wiki's are for instructional purposes. Try instead to quantify definitions and be objective.
You commented your diffs. Yeeeaahhhh! Thank you. They seem, however, to be more of a carbon-copy of your entry rather than an explanation.
As for your warning, typically we use Box Notes for such things. Take a look at http://wiki.archlinux.org/index.php/Category:Template.
There is no 'I' or 'We'. You are the drill sergeant, use 'You'.
Restored 'Installing' section. Though I see where you're getting at, this doesn't keep things simple. Muuuccchhh easier just to reboot here. As a side note, do you need libflashsupport here??? I don't have it on my system and haven't had a problem with flash, but perhaps I bjorked something up.
Some good tips here, things I didn't know about. Thanks for the contributions.

Thanx a lot for your feedback. i will certainly use it when i make more edits.
As for the things you didn't know. As soon as i fully understand how i can get a microphone working in OSS i will add that to the wiki as well. Unless you already know it.. in that case, feel free to add it.

t4k1t wrote:

On my previous Arch installs I always used alsa since it occured to me, there wasn't much to configure to make it run, but on my latest install I just wasn't able to get alsa running so I switched to oss, so here is my pro/con list:
OSS
Pro
- You install oss and it kinda just works.
- It natively supports seperate channels for seperate applications
Con
- On some soundcards(for example mine ) you have to manually mute the speakers when you plug in headphones
- The mixer-app(ossxmix) is kind of complex, the large number of bars and checkboxes is a bit irritating
ALSA
Pro
- The GUI is way simpler
- The speakers mute automaticly(at least on every soundcard I ever had)
Con
- Well I for myself can't seem to get it working again^^'
Conclusion
IMHO alsa seems to be a little bit more userfriendly, while oss is really nice if you want to control your sound exact.
P.S.
At the moment I hadn't the time to test oss with apps like ardour but at tasks like streaming music from a local-/web-server and simple playing music from my local hd it occurs to me, that the sound-quality of oss was a tick better, but that isn't really objective.
Hope that helps you a bit

Alsa 2nd pro, is that a pro or a con? I see that as a con actually because i expect alsa to just remember my last used sound level and use it next time.
About the conclusion. depends on how you look at it.. if you look at just alsa (no pulseaudio at all) and then just look at the user interfaces then i agree. in any other case OSS wins for me.

As for the pro/con list, thanx a lot for that. it's just a bit to few right now to be really helpful but once a few more (2?) people send in a list like that as well then there will be enough pro/con for alsa and oss to be useful on the beginners guide. or that's how i think about.

t4k1t · 2009-09-01 21:18:20

Sorry about the short list, but as I wrote above I just hadn't enough time to really test it out.
The second Pro means that the speakers mute when I plug in headphones so it's really a Pro. But this brings me to another Con of ALSA which is that you have to manually create a file to make it save the levels from the last time(at least as far as I recall).

markg85 · 2009-09-01 22:37:21

t4k1t wrote:

Sorry about the short list, but as I wrote above I just hadn't enough time to really test it out.
The second Pro means that the speakers mute when I plug in headphones so it's really a Pro. But this brings me to another Con of ALSA which is that you have to manually create a file to make it save the levels from the last time(at least as far as I recall).

Oke then it's a pro indeed but not one that an average user will see much. The con is a little different. it doesn't require you to save a file but it does require you to run a command (alsactl store?) to save it.

ngoonee · 2009-09-01 22:52:43

I'm an alsa/pulse user, so I'll give a bit of the 'other side'.

Alsa/pulse
Pros:-
network sound
advanced connection of sink/source (including merging sinks)
bluetooth support!
highly supported by existing apps, either through directly supporting Pulse or through its alsa plugin (you should not need to recompile properly-written apps which do not assume they should write audio data directly to hardware, I think I only needed to recompile mpd on my system)

Cons:-
Setup isn't the easiest. Can't comment vs OSS4 because I haven't tried it

OSS4
Pros:-
Everyone seems to say sound quality is better. I guess that's because they're comparing it with dmix alsa. Use pulse with alsa and you should not notice any difference in sound quality though.
Cons:-
Most apps nowadays default output to alsa. Meaning OSS plays them using an alsa plugin.
USB support is admittedly skimpy.

EDIT: Having read the sound article you referred to, my only comment is that the writer really has it in for Pulse... 3 seconds latency, where'd he get that from? I use pulse for audio recording (when I'm lazy to fire up JACK) and while there IS latency, its definitely in the ms range.

Last edited by ngoonee (2009-09-01 22:58:42)

Gen2ly · 2009-09-01 23:10:21

Gen2ly wrote:

...As a side note, do you need libflashsupport here???...

markg85, libflashsupport isn't needed. [1]

pacman -Ql oss | grep flash

If you don't know, please don't put in wiki, this could cause unnecessary problems. As for the mms section:

If your stream sounds ugly in totem like it did with me then you could try to play it with another codec like ffmpeg (mplayer). That "fixed" the issue for me. This will not fix the issue that somehow pops up in gstreamer when playing MMS streams but it will give you the option to play it with good sound quality. Playing it in mplayer is simple:
# mplayer mmsh://yourstreamurl

Could you fix this? ffmpeg is not a codec . Also define ugly, and what is somehow?

markg85 wrote:

Thanx a lot for your feedback. i will certainly use it when i make more edits.
As for the things you didn't know. As soon as i fully understand how i can get a microphone working in OSS i will add that to the wiki as well. Unless you already know it.. in that case, feel free to add it.

For the mic, I did get mine going. Can't remember just how I did mine (sorry, think I had to disable one of the inputs), but do remember to prevent it from passing through the speakers had to disable "Misc Microphone".

# ossmix
Selected mixer 0/High Definition Audio ALC888
Known controls are:
jack.green.mode <front|rear|center/LFE|side|pcm4|input> (currently front)
jack.green [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.green.mute ON|OFF (currently OFF)
jack.black.mode <front|rear|center/LFE|side|pcm4|input> (currently center/LFE)
jack.black [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.black.mute ON|OFF (currently OFF)
jack.orange.mode <front|rear|center/LFE|side|pcm4|input> (currently rear)
jack.orange [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.orange.mute ON|OFF (currently OFF)
jack.gray.mode <front|rear|center/LFE|side|pcm4|input> (currently pcm4)
jack.gray [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.gray.mute ON|OFF (currently OFF)
jack.pink.mode <front|rear|center/LFE|side|pcm4|input> (currently input)
jack.pink [<leftvol>:<rightvol>] (currently 19.9:19.9 dB)
jack.pink.mute ON|OFF (currently OFF)
jack.fp-pink.mode <front|rear|center/LFE|side|pcm4|input> (currently front)
jack.fp-pink [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.fp-pink.mute ON|OFF (currently OFF)
jack.blue.mode <front|rear|center/LFE|side|pcm4|input> (currently input)
jack.blue [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.blue.mute ON|OFF (currently OFF)
jack.fp-green.mode <front|rear|center/LFE|side|pcm4|input> (currently front)
jack.fp-green [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.fp-green.mute ON|OFF (currently OFF)
record.mix.mute.mic1 ON|OFF (currently OFF)
record.mix.mute.fp-mic1 ON|OFF (currently OFF)
record.mix.mute.linein1 ON|OFF (currently OFF)
record.mix.mute.fp-headphone1 ON|OFF (currently OFF)
record.mix.mute.green1 ON|OFF (currently OFF)
record.mix.mute.black1 ON|OFF (currently OFF)
record.mix.mute.orange1 ON|OFF (currently OFF)
record.mix.mute.gray1 ON|OFF (currently OFF)
record.mix.mute.input-mix1 ON|OFF (currently OFF)
record.mix1 [<leftvol>:<rightvol>] (currently 38.9:38.9 dB)
record.mix.mute.mic2 ON|OFF (currently OFF)
record.mix.mute.fp-mic2 ON|OFF (currently OFF)
record.mix.mute.linein2 ON|OFF (currently OFF)
record.mix.mute.fp-headphone2 ON|OFF (currently OFF)
record.mix.mute.green2 ON|OFF (currently OFF)
record.mix.mute.black2 ON|OFF (currently OFF)
record.mix.mute.orange2 ON|OFF (currently OFF)
record.mix.mute.gray2 ON|OFF (currently OFF)
record.mix.mute.input-mix2 ON|OFF (currently OFF)
record.mix2 [<leftvol>:<rightvol>] (currently 4.4:2.9 dB)
misc.mic [<leftvol>:<rightvol>] (currently 0.0:0.0 dB)
misc.fp-mic [<leftvol>:<rightvol>] (currently 46.4:37.4 dB)
misc.linein [<leftvol>:<rightvol>] (currently 38.9:38.9 dB)
misc.fp-headphone [<leftvol>:<rightvol>] (currently 34.4:34.4 dB)
misc.green [<leftvol>:<rightvol>] (currently 34.4:38.9 dB)
misc.black [<leftvol>:<rightvol>] (currently 38.9:38.9 dB)
misc.orange [<leftvol>:<rightvol>] (currently 38.9:38.9 dB)
misc.gray [<leftvol>:<rightvol>] (currently 40.4:41.9 dB)
misc.input-mix <mic|fp-mic|linein> (currently mic)
misc.front-mute ON|OFF (currently OFF)
misc.input-mix-mute1 ON|OFF (currently OFF)
misc.front1 [<leftvol>:<rightvol>] (currently 43.4:43.4 dB)
misc.front2 <front|input-mix> (currently front)
misc.rear-mute ON|OFF (currently OFF)
misc.input-mix-mute2 ON|OFF (currently OFF)
misc.rear1 [<leftvol>:<rightvol>] (currently 4.4:4.4 dB)
misc.rear2 <rear|input-mix> (currently rear)
misc.center/lfe-mute ON|OFF (currently OFF)
misc.input-mix-mute3 ON|OFF (currently OFF)
misc.center/lfe1 [<leftvol>:<rightvol>] (currently 41.9:41.9 dB)
misc.center/lfe2 <center/LFE|input-mix> (currently center/LFE)
misc.side-mute ON|OFF (currently OFF)
misc.input-mix-mute4 ON|OFF (currently OFF)
misc.side1 [<leftvol>:<rightvol>] (currently 35.9:35.9 dB)
misc.side2 <side|input-mix> (currently side)
misc.pcm4-mute ON|OFF (currently OFF)
misc.input-mix-mute5 ON|OFF (currently OFF)
misc.pcm41 [<leftvol>:<rightvol>] (currently 25.4:25.4 dB)
misc.pcm42 <pcm4|input-mix> (currently pcm4)
vmix0-enable ON|OFF (currently ON)
vmix0-rate <decimal value> (currently 48000) (Read-only)
vmix0-channels <Stereo|Multich> (currently Stereo)
vmix0-src <Fast|Low|Medium|High|High+|Production|OFF> (currently Medium)
vmix0-outvol <monovol> (currently 25.0 dB)
vmix0-invol <monovol> (currently 25.0 dB)
vmix0.pcm8 [<leftvol>:<rightvol>] (currently 19.9:19.9 dB) ("knotify4")
vmix0.pcm9 [<leftvol>:<rightvol>] (currently 25.0:25.0 dB)
vmix0.pcm10 [<leftvol>:<rightvol>] (currently 25.0:25.0 dB)
vmix0.pcm11 [<leftvol>:<rightvol>] (currently 25.0:25.0 dB)

markg85 · 2009-09-02 14:45:05

ngoonee wrote:

I'm an alsa/pulse user, so I'll give a bit of the 'other side'.
Alsa/pulse
Pros:-
network sound
advanced connection of sink/source (including merging sinks)
bluetooth support!
highly supported by existing apps, either through directly supporting Pulse or through its alsa plugin (you should not need to recompile properly-written apps which do not assume they should write audio data directly to hardware, I think I only needed to recompile mpd on my system)
Cons:-
Setup isn't the easiest. Can't comment vs OSS4 because I haven't tried it
OSS4
Pros:-
Everyone seems to say sound quality is better. I guess that's because they're comparing it with dmix alsa. Use pulse with alsa and you should not notice any difference in sound quality though.
Cons:-
Most apps nowadays default output to alsa. Meaning OSS plays them using an alsa plugin.
USB support is admittedly skimpy.
EDIT: Having read the sound article you referred to, my only comment is that the writer really has it in for Pulse... 3 seconds latency, where'd he get that from? I use pulse for audio recording (when I'm lazy to fire up JACK) and while there IS latency, its definitely in the ms range.

Thanx for the input

Gen2ly wrote:

...As a side note, do you need libflashsupport here???...

markg85, libflashsupport isn't needed. [1]

pacman -Ql oss | grep flash

If you don't know, please don't put in wiki, this could cause unnecessary problems. As for the mms section:

If your stream sounds ugly in totem like it did with me then you could try to play it with another codec like ffmpeg (mplayer). That "fixed" the issue for me. This will not fix the issue that somehow pops up in gstreamer when playing MMS streams but it will give you the option to play it with good sound quality. Playing it in mplayer is simple:
# mplayer mmsh://yourstreamurl

Could you fix this? ffmpeg is not a codec . Also define ugly, and what is somehow?

markg85 wrote:

Thanx a lot for your feedback. i will certainly use it when i make more edits.
As for the things you didn't know. As soon as i fully understand how i can get a microphone working in OSS i will add that to the wiki as well. Unless you already know it.. in that case, feel free to add it.

For the mic, I did get mine going. Can't remember just how I did mine (sorry, think I had to disable one of the inputs), but do remember to prevent it from passing through the speakers had to disable "Misc Microphone".

# ossmix
Selected mixer 0/High Definition Audio ALC888
Known controls are:
jack.green.mode <front|rear|center/LFE|side|pcm4|input> (currently front)
jack.green [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.green.mute ON|OFF (currently OFF)
jack.black.mode <front|rear|center/LFE|side|pcm4|input> (currently center/LFE)
jack.black [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.black.mute ON|OFF (currently OFF)
jack.orange.mode <front|rear|center/LFE|side|pcm4|input> (currently rear)
jack.orange [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.orange.mute ON|OFF (currently OFF)
jack.gray.mode <front|rear|center/LFE|side|pcm4|input> (currently pcm4)
jack.gray [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.gray.mute ON|OFF (currently OFF)
jack.pink.mode <front|rear|center/LFE|side|pcm4|input> (currently input)
jack.pink [<leftvol>:<rightvol>] (currently 19.9:19.9 dB)
jack.pink.mute ON|OFF (currently OFF)
jack.fp-pink.mode <front|rear|center/LFE|side|pcm4|input> (currently front)
jack.fp-pink [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.fp-pink.mute ON|OFF (currently OFF)
jack.blue.mode <front|rear|center/LFE|side|pcm4|input> (currently input)
jack.blue [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.blue.mute ON|OFF (currently OFF)
jack.fp-green.mode <front|rear|center/LFE|side|pcm4|input> (currently front)
jack.fp-green [<leftvol>:<rightvol>] (currently 29.9:29.9 dB)
jack.fp-green.mute ON|OFF (currently OFF)
record.mix.mute.mic1 ON|OFF (currently OFF)
record.mix.mute.fp-mic1 ON|OFF (currently OFF)
record.mix.mute.linein1 ON|OFF (currently OFF)
record.mix.mute.fp-headphone1 ON|OFF (currently OFF)
record.mix.mute.green1 ON|OFF (currently OFF)
record.mix.mute.black1 ON|OFF (currently OFF)
record.mix.mute.orange1 ON|OFF (currently OFF)
record.mix.mute.gray1 ON|OFF (currently OFF)
record.mix.mute.input-mix1 ON|OFF (currently OFF)
record.mix1 [<leftvol>:<rightvol>] (currently 38.9:38.9 dB)
record.mix.mute.mic2 ON|OFF (currently OFF)
record.mix.mute.fp-mic2 ON|OFF (currently OFF)
record.mix.mute.linein2 ON|OFF (currently OFF)
record.mix.mute.fp-headphone2 ON|OFF (currently OFF)
record.mix.mute.green2 ON|OFF (currently OFF)
record.mix.mute.black2 ON|OFF (currently OFF)
record.mix.mute.orange2 ON|OFF (currently OFF)
record.mix.mute.gray2 ON|OFF (currently OFF)
record.mix.mute.input-mix2 ON|OFF (currently OFF)
record.mix2 [<leftvol>:<rightvol>] (currently 4.4:2.9 dB)
misc.mic [<leftvol>:<rightvol>] (currently 0.0:0.0 dB)
misc.fp-mic [<leftvol>:<rightvol>] (currently 46.4:37.4 dB)
misc.linein [<leftvol>:<rightvol>] (currently 38.9:38.9 dB)
misc.fp-headphone [<leftvol>:<rightvol>] (currently 34.4:34.4 dB)
misc.green [<leftvol>:<rightvol>] (currently 34.4:38.9 dB)
misc.black [<leftvol>:<rightvol>] (currently 38.9:38.9 dB)
misc.orange [<leftvol>:<rightvol>] (currently 38.9:38.9 dB)
misc.gray [<leftvol>:<rightvol>] (currently 40.4:41.9 dB)
misc.input-mix <mic|fp-mic|linein> (currently mic)
misc.front-mute ON|OFF (currently OFF)
misc.input-mix-mute1 ON|OFF (currently OFF)
misc.front1 [<leftvol>:<rightvol>] (currently 43.4:43.4 dB)
misc.front2 <front|input-mix> (currently front)
misc.rear-mute ON|OFF (currently OFF)
misc.input-mix-mute2 ON|OFF (currently OFF)
misc.rear1 [<leftvol>:<rightvol>] (currently 4.4:4.4 dB)
misc.rear2 <rear|input-mix> (currently rear)
misc.center/lfe-mute ON|OFF (currently OFF)
misc.input-mix-mute3 ON|OFF (currently OFF)
misc.center/lfe1 [<leftvol>:<rightvol>] (currently 41.9:41.9 dB)
misc.center/lfe2 <center/LFE|input-mix> (currently center/LFE)
misc.side-mute ON|OFF (currently OFF)
misc.input-mix-mute4 ON|OFF (currently OFF)
misc.side1 [<leftvol>:<rightvol>] (currently 35.9:35.9 dB)
misc.side2 <side|input-mix> (currently side)
misc.pcm4-mute ON|OFF (currently OFF)
misc.input-mix-mute5 ON|OFF (currently OFF)
misc.pcm41 [<leftvol>:<rightvol>] (currently 25.4:25.4 dB)
misc.pcm42 <pcm4|input-mix> (currently pcm4)
vmix0-enable ON|OFF (currently ON)
vmix0-rate <decimal value> (currently 48000) (Read-only)
vmix0-channels <Stereo|Multich> (currently Stereo)
vmix0-src <Fast|Low|Medium|High|High+|Production|OFF> (currently Medium)
vmix0-outvol <monovol> (currently 25.0 dB)
vmix0-invol <monovol> (currently 25.0 dB)
vmix0.pcm8 [<leftvol>:<rightvol>] (currently 19.9:19.9 dB) ("knotify4")
vmix0.pcm9 [<leftvol>:<rightvol>] (currently 25.0:25.0 dB)
vmix0.pcm10 [<leftvol>:<rightvol>] (currently 25.0:25.0 dB)
vmix0.pcm11 [<leftvol>:<rightvol>] (currently 25.0:25.0 dB)

For libflashsupport on the same page you linked it clearly states:

# Flash V9 and V10 require libflashsupport to output sound via OSS. Typically a 32-bit version of the library is required.
# Flash V10 has a 64-bit version which requires a 64 bit libflashsupport.

Also i tested it with and without libflashsupport. On archlinux (x64 running here) there most certainly is a need for libflashsupport when you want to have sound in your flash. And yes i tested the archlinux OSS version and the mercurial version (running now) bith need it installed manually! On my pc sound in flash didn't work without it but did with it. So, no not removing from the wiki as it's needed. But i see you removed it for me! please do NOT do that if you didn't even verified it. I use flash 10 x64 and i need it!

As for the ffmpeg "codec" changed it to backend.

And i did get the microphone working near perfect: http://www.4front-tech.com/forum/viewtopic.php?p=13192

Now for some news you all might like.
On my school i need to do an investigation to whatever i want and i'm heavily thinking about investigating the pros/cons of alsa compared to oss (or oss compared to alsa). That investigation will take from monday next week till next mondey till friday 23 of oktober. In that investigation i'm going to do some in depth look of alsa and oss and that will include the usability as well.

Following up on that investigation i will spend another 8 weeks on my school making a volume control application that can be used with alsa and oss and easily expandable with other sound systems. The goal of this is to make one sound application that can manage (in the first place) alsa and oss. oss is going to be implemented and alsa is probably going to be dummy implemented because it's likely way to much for me to implement both.

Before you get to exited, both projects (investigating and making the application) are just made up today and i just don't know if both will get accepted by my school. I asked one teacher and he liked the idea a lot and could potentially have a value for the sound management under linux. Once i do get this started i will involve the community (YOU!) with this since this project can't be done without the community specially the investigation.

And once i start and have something to tell/ask i will blog about it on http://blog.mageprojects.com

edit::
And this idea already got dumped. read more a few posts down or click: http://bbs.archlinux.org/viewtopic.php? … 34#p612634

Last edited by markg85 (2009-09-03 17:51:45)

ngoonee · 2009-09-02 15:02:40

markg85 wrote:

Also i tested it with and without libflashsupport. On archlinux (x64 running here) there most certainly is a need for libflashsupport when you want to have sound in your flash. And yes i tested the archlinux OSS version and the mercurial version (running now) bith need it installed manually! On my pc sound in flash didn't work without it but did with it. So, no not removing from the wiki as it's needed. But i see you removed it for me! please do NOT do that if you didn't even verified it. I use flash 10 x64 and i need it!

Uh.... It's a wiki. It's not 'your' article per se. I'm not saying he should not have discussed the change with you as the initial author, but the whole point of a wiki is that you can make changes to it as and when you see fit. Not when the original author sees fit.

markg85 · 2009-09-02 15:07:48

ngoonee wrote:

markg85 wrote:
Also i tested it with and without libflashsupport. On archlinux (x64 running here) there most certainly is a need for libflashsupport when you want to have sound in your flash. And yes i tested the archlinux OSS version and the mercurial version (running now) bith need it installed manually! On my pc sound in flash didn't work without it but did with it. So, no not removing from the wiki as it's needed. But i see you removed it for me! please do NOT do that if you didn't even verified it. I use flash 10 x64 and i need it!
Uh.... It's a wiki. It's not 'your' article per se. I'm not saying he should not have discussed the change with you as the initial author, but the whole point of a wiki is that you can make changes to it as and when you see fit. Not when the original author sees fit.

Done undo works well ^_^

jacko · 2009-09-02 17:35:48

OSS pro

On old hardware the AC97 codec was used on a majority of mother boards. There still is a AC97 bug in alsa that sets the gain on this codec incorrectly. Therefor at higher volumes huge amounts of noise are injected into the audio output stream.

Hannu might be an ass, but at least he understands audio technology and has more then the ability to make the best sound drivers for linux. I for one am hoping that hannu pulls through with his OSSv5 project and gets OSS back into the kernel where it belongs.
http://4front-tech.com/hannublog/?p=36

uastasi · 2009-09-02 19:46:41

I switched to OSS on my previous laptop and it worked like a charm; actually I own a dell studio xps 13 with a nVidia MCP79 HDA and with OSS I noticed a really crappy sound output. I've switched to the mercurial one and this issue seems solved.
Next step would be set up muting headphones/speaker automatically without using ossxmix.
Here is my list, according to my experience with two laptops:

OSS
Pro
- Best audio quality
- A channel for each audio application
- No software mixing

Con
- ossxmix is not so usable as it should be. Too many checkboxes and sliders, and it's not fitted to the screen.
- It's not so easy to set up each channel in the right way. I've tried many combinations to mute the speakers when plugging in headphones without success.
- Why should I kill applications using OSS before hibernating? This makes hibernation useless.

ALSA
Pro
- Hibernation working flawlessly
- No need to mute speakers/headphones manually.
- Gnome-applet and hotkeys works out of the box

Con
- Worse audio quality

smartboyathome · 2009-09-02 22:27:59

Tyriel wrote:

Just wanted to add that although I like OSS I would never recomend it to the average desktop user until it has matured more. Alsa will be easier and more convenient for more users imho. Bluetooth and usb work flawlessly with alsa plus pulse where as there is currently no means to do this with OSS. Despite what some people think pulse works really well when configured correctly, however this is not easy nor straight forward hence all the complaints and misconceptions. Also lets not forget how many more applications support Alsa (mixers etc). Waiting patiently for KDE 4.4 and native Kmix OSS support!
Personally I like OSS and I look forward to it being an Alsa replacement, however I do not beleive that time is now. I like how you put in the effort to improve the write up but I feel you need to be more objective and less bias. That all said keep up the good work

Well, I use OSS because it was easier to configure for my soundcard. For some reason, Alsa refused to work completely, Pulseaudio refused to work with more than 1 app. OSS worked perfectly with many apps accessing the soundcard OOTB. The only problem I have is that timidity is alsa-only and fluidsynth doesn't want to work for me, so I have no midi playback.

Gen2ly · 2009-09-02 22:55:50

markg85 wrote:

Gen2ly wrote:
markg85, libflashsupport isn't needed. [1]
pacman -Ql oss | grep flash
...
For libflashsupport on the same page you linked it clearly states:
# Flash V9 and V10 require libflashsupport to output sound via OSS. Typically a 32-bit version of the library is required.
# Flash V10 has a 64-bit version which requires a 64 bit libflashsupport.
Also i tested it with and without libflashsupport. On archlinux (x64 running here) there most certainly is a need for libflashsupport when you want to have sound in your flash. And yes i tested the archlinux OSS version and the mercurial version (running now) bith need it installed manually! On my pc sound in flash didn't work without it but did with it. So, no not removing from the wiki as it's needed. But i see you removed it for me! please do NOT do that if you didn't even verified it. I use flash 10 x64 and i need it!

Did you try the above command?? Possibly it's different for you (shouldn't be!) but clearly shows to me that the oss package DOES install 'libflashsupport'. The only thing I can think of is that if this command doesn't show:

oss /usr/lib/libflashsupport.so

then that removing the package 'libflashsupport' removed it???? Not sure just how pacman works in this respect (whether it detects conflicts...).

markg85 wrote:

As for the ffmpeg "codec" changed it to backend.

Great. Thank you. Please though, could you define ugly. That description doesn't really provide any usefull feedback. Perhaps, 'crackling' or 'distorted'... would do better?

markg85 wrote:

And i did get the microphone working near perfect: http://www.4front-tech.com/forum/viewtopic.php?p=13192

Hey thanks, should've thought to look there .

markg85 wrote:

Now for some news you all might like.
On my school i need to do an investigation to whatever i want and i'm heavily thinking about investigating the pros/cons of alsa compared to oss (or oss compared to alsa). That investigation will take from monday next week till next mondey till friday 23 of oktober. In that investigation i'm going to do some in depth look of alsa and oss and that will include the usability as well...

Huh, sounds interesting. Looking forward to it when it goes up.

markg85 · 2009-09-03 17:50:46

Gen2ly wrote:

markg85 wrote:
Gen2ly wrote:
markg85, libflashsupport isn't needed. [1]
pacman -Ql oss | grep flash
...
For libflashsupport on the same page you linked it clearly states:
# Flash V9 and V10 require libflashsupport to output sound via OSS. Typically a 32-bit version of the library is required.
# Flash V10 has a 64-bit version which requires a 64 bit libflashsupport.
Also i tested it with and without libflashsupport. On archlinux (x64 running here) there most certainly is a need for libflashsupport when you want to have sound in your flash. And yes i tested the archlinux OSS version and the mercurial version (running now) bith need it installed manually! On my pc sound in flash didn't work without it but did with it. So, no not removing from the wiki as it's needed. But i see you removed it for me! please do NOT do that if you didn't even verified it. I use flash 10 x64 and i need it!
Did you try the above command?? Possibly it's different for you (shouldn't be!) but clearly shows to me that the oss package DOES install 'libflashsupport'. The only thing I can think of is that if this command doesn't show:
oss /usr/lib/libflashsupport.so
then that removing the package 'libflashsupport' removed it???? Not sure just how pacman works in this respect (whether it detects conflicts...).
markg85 wrote:
As for the ffmpeg "codec" changed it to backend.
Great. Thank you. Please though, could you define ugly. That description doesn't really provide any usefull feedback. Perhaps, 'crackling' or 'distorted'... would do better?
markg85 wrote:
And i did get the microphone working near perfect: http://www.4front-tech.com/forum/viewtopic.php?p=13192
Hey thanks, should've thought to look there .
markg85 wrote:
Now for some news you all might like.
On my school i need to do an investigation to whatever i want and i'm heavily thinking about investigating the pros/cons of alsa compared to oss (or oss compared to alsa). That investigation will take from monday next week till next mondey till friday 23 of oktober. In that investigation i'm going to do some in depth look of alsa and oss and that will include the usability as well...
Huh, sounds interesting. Looking forward to it when it goes up.

pacman -Ql oss | grep flash

is not outputting flash here (oss-mercurial in my case but the same results)

for defining ugly, changed to this:

== MMS sound cracking in totem ==
If your stream sounds with cracks or strange noise in totem like it did with me then you could try to play it with another backend like ffmpeg (mplayer). That "fixed" the issue for me. This will not fix the issue that somehow pops up in gstreamer when playing MMS streams but it will give you the option to play it with good sound quality. Playing it in mplayer is simple:
# mplayer mmsh://yourstreamurl

And for the "news" i had in my last message.. Already dropped that because it exists!
Currently the gnome-volume-control application is doing exactly what i want (including the volume applet) thus there is no point for me to investigate if it's possible and make it because that's already been done.

So for ossxmix that is way to complex for the average user; use gnome-volume-control. I will also add this information in the OSS wiki page.

edit:

Just replaced the mixer section of OSS with this:

= Volume control =
== Gnome Volume Control ==
If you want to have clear to the point sound mixing you can simply use the gnome-volume-control application. That application can manage both ALSA and OSS in a clear sane way. If you open the Gnome Volume Control application you might need to click the device dropdown and select the option that has something with "OSS" (without the quotes) in it.
Another advantage is that the volume applet of gnome is also managing OSS just fine so you can keep using that with OSS.
More advanced volume control settings can be done in ossxmix.
== OSSXMIX ==
The command line mixer is called <tt>ossmix</tt>. It's very like the BSD audio mixer (<tt>mixerctl</tt>).
A more friendly, graphical mixer, is available too. It's called <tt>ossxmix</tt>. It needs the optional depend <tt>gtk2</tt> to work.
The <tt>ossxmix</tt> controls are explained in the following example:
______________________________
/ High Definition Audio ALC262 \ ----------------------------------> One tab for each sound card
/________________________________\_______________________________
|
| [x] vmix0-enable [vmix0-rate: 48.000kHz] vmix0-channels \ The vmix (virtual mixer) special configurations
| [ Stereo [v] ] |--> appear at the top. These include sampling rate
| / and mixer priority. They are provided by OSS.
| __codec1______________________________________________________
| | _jack_______________________________________________________ \
| | | _int-speaker____________________ __green_________________ |
| | | | | | | These are your sound card configurations.
| | | | _mode______ | | | | _mode______ | | | Every mixer control that is shown here is
| | | | [ mix [v] ] o o [x] [ ]mute | | [ mix [v] ] o o [x] |--> provided by your sound card. Every sound card
| | | | | | | | | | | specific control is shown here.
| | | |________________________________| |_______________________ |
| | |____________________________________________________________ |
| |______________________________________________________________ /
|
| ___vmix0_______________________________________________________ \
| | __mocp___ O O _firefox_ O O __pcm7___ O O | Here are the vmix mixer controls. These are
| | | | O O | | x x | | O O | virtual mixer controls provided by OSS. Each
| | | | | | x O | | | | x x | | | | O O | slider is the volume control of a different
| | | o o [x] | x x | o o [x] | x x | o o [x] | O O |--> application. When one application uses the
| | | | | | x x | | | | x x | | | | O O | sound card, its name is shown in the place of
| | |_________| x x |_________| x x |_________| O O | the 'pcm#' labels. There are also sound level
| |______________________________________________________________ | meter levels for each application.
|________________________________________________________________ /
=== Saving and restoring mixer settings ===
If you wish to save your mixer settings manually, run {{Codeline|savemixer}}. As regular user you will need permissions to use {{Codeline|/usr/sbin/savemixer}} in the sudoers file or you can modify write permissions to {{Filename|/usr/lib/oss/etc/mixer.save}}. Alternately, the <tt>-f</tt> switch can be used to save the mixer to a file and {{Codeline|savemixer -L}} to restore it.
Please note that the init scripts run these commands before shutdown/after starting to keep mixer settings across boot, so most users don't need to worry about it.

Still includes ossxmix (not edited) but renamed the section to volume control and added Gnome Volume Control with a little information.

Last edited by markg85 (2009-09-03 18:04:02)

Gen2ly · 2009-09-04 00:39:10

markg85 wrote:

Gen2ly wrote:
pacman -Ql oss | grep flash
is not outputting flash here (oss-mercurial in my case but the same results)

Well since this looks to be a case with oss-mercurial wouldn't it be best to put libflashsupport there?

markg85 wrote:

for defining ugly, changed to this:
== MMS sound cracking in totem ==
If your stream sounds with cracks or strange noise in totem like it did with me then you could try to play it with another backend like ffmpeg (mplayer). That "fixed" the issue for me. This will not fix the issue that somehow pops up in gstreamer when playing MMS streams but it will give you the option to play it with good sound quality. Playing it in mplayer is simple:
# mplayer mmsh://yourstreamurl

Ah, much better though still a few personal/case-sensitive references.

markg85 wrote:

= Volume control =
== Gnome Volume Control ==
If you want to have clear to the point sound mixing you can simply use the gnome-volume-control application. That application can manage both ALSA and OSS in a clear sane way. If you open the Gnome Volume Control application you might need to click the device dropdown and select the option that has something with "OSS" (without the quotes) in it.
Another advantage is that the volume applet of gnome is also managing OSS just fine so you can keep using that with OSS.
More advanced volume control settings can be done in ossxmix.

Remember from my previous post:

Gen2ly wrote:

Avoid words like ugly, best...

You may have seen my comment on the OSS wiki page edit comment:

When you catch an adjective kill it.

This is a quote that Mark Twain applied to Journalism, but has the same effect here: "clear to the point", "clear sane". The point being that we want readers to be able to make up their own mind what is best for them. Also, these definitions: ("might need to", "something with") leave the reader uncertain. You're the drill sergeant. It either is, or it isn't. An even bigger problem here though is that the edit is assumptive. Consider you target audience. This addition assumes that users use/prefer the Gnome Desktop Environment. Not everyone uses Gnome or wants to install Gnome. I'd even venture that most Arch users don't even use Gnome (ok, don't shoot me [I may have unintentially stirred the pot here] ) What works good for you may not be what other users want. Ossxmix, works on all desktop environments without having to configure too many dependencies. Personally, I think that adding a section on sound volume managers that have support for OSS would be a good way to go.

Edit

Ok, just put it in: OSS:Other Mixers

R00KIE · 2009-09-04 09:12:54

I have noticed something that doesn't seem to apply to OSS exactly as stated.

In "Changing the Sample Rate", "By default the sample rate is 48000hz. There are several conditions in which you may want to change this. This all depends on your usage patterns. You want the sample rate you are using to match the media you use the most. If your computer has to change the sampling rate of the media to suit the hardware it is likely, though not guaranteed that you will have a loss in audio quality. This is most noticable in downsampling (ie. 96000hz → 48000hz). There is an article about this issue in "Stereophile" which was discussed on Apple's "CoreAudio API" mailing list if you wish to learn more about this issue."

The article you link is about OSX but the description sounds much like the crappy job dmix did or still does (the resampler alsa uses/used) or if the vmix quality is set to fast. The resampler in OSS is much better, I don't have any native 96KHz material to test with but I can be playing 48KHz and 44.1KHz material at the same time with no strange artifacts introduced by the resampling (vmix set at 48KHz), just change the vmix quality to production (the increase in cpu usage will not be obscene), and start the playback again. This is something most if not all OSS users can agree on, just search in the forums and see for yourself.

Also changing the sample rate to 96KHz will cause a slightly higher cpu usage because most material will need to be resampled and again I doubt most users will ever notice any improvement in sound quality. If anything the change should be done to the rate the user most uses to avoid the cost of resampling, of course this might be vary from user to user.

Arch Linux

#1 2009-09-01 11:40:08

Beginners Guide sound installation -- OSS and ALSA objective features

#2 2009-09-01 12:50:55

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#3 2009-09-01 13:54:53

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#4 2009-09-01 15:24:58

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#5 2009-09-01 17:48:02

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#6 2009-09-01 17:50:40

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#7 2009-09-01 19:08:52

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#8 2009-09-01 19:29:16

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#9 2009-09-01 19:50:37

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#10 2009-09-01 20:17:44

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#11 2009-09-01 20:41:18

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#12 2009-09-01 21:18:20

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#13 2009-09-01 22:37:21

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#14 2009-09-01 22:52:43

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#15 2009-09-01 23:10:21

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#16 2009-09-02 14:45:05

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#17 2009-09-02 15:02:40

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#18 2009-09-02 15:07:48

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#19 2009-09-02 17:35:48

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#20 2009-09-02 19:46:41

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#21 2009-09-02 22:27:59

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#22 2009-09-02 22:55:50

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#23 2009-09-03 17:50:46

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#24 2009-09-04 00:39:10

Re: Beginners Guide sound installation -- OSS and ALSA objective features

#25 2009-09-04 09:12:54

Re: Beginners Guide sound installation -- OSS and ALSA objective features

Board footer