Installing/Configuring ALSA Sound Modules In Debian 221
GonzoJohn writes "Linux Orbit explains how: "A very common question that comes up when trying Debian GNU/Linux is how the heck do you get Advanced Linux Sound Architecture (a.k.a. ALSA) sound modules set up properly? In this HOWTO we'll show you how to compile and install the ALSA kernel modules, and then setup things using the ALSA Debian script so that modules are automatically loaded and unloaded, and your mixer levels are saved and restored on boot up. Here are some things you'll need to have before you start this HOWTO""
Wow... (Score:5, Informative)
Maybe I'm missing something, but why/how is this news?
Mandrake doesn't need a guide (Score:5, Informative)
Compiling your own kernel additions is for experimental stuff, not stuff that has been working for years like ALSA
You gotta hate Linux (Score:5, Funny)
1) Why does everything have to be compiled into the kernel. What? Can the kernel not map shared objects into its memory space? And if it can't, why not?
2) Why don't they establish only standard APIs that device drivers have to implement (seperate of the kernel and not built into some stupid x-windowing system or something irrelevant to what it does example: sound drivers for KDE), i.e.:
OpenGL - graphics library [opengl.org]
OpenAL - audio library [openal.org]
insert appropriate nic standard
insert appropriate printer standard, etc. and make the stupid x-windowing system just another interface that runs on top of OpenGL, jeez.
3) The everything is a file mechanism is really getting outdated. Why are there not object oriented shells yet? Come on, just pop a javascript shell in there, make ObjectInstantiators/ObjectSerializers that detect file types and convert to the appropriate object instance, so javascript can instantiate it, use it, serialize it back to disk, and then move on.
4) Why do we still use program based architectures? Programs are way too linear. We need objects and an object handling mechanism (like javascript or something similar to it, like a Delphi UI or something) not programs. Once you make a program things get hard coded in that make it too specialized to be used in anything other than what it is designed for, if everything was just an interactive object, you could chain them together and do all sorts of neat tricks, that you could never dream of with standard file based shells/programs. And then you could serialize these object webs you create to disk for use as kind of a template(I'd say program but you could easily modify these to fit your needs). Sounds way better than standard file based scripts to me. Although javascript scripts sound nice too.
5) If we are going to be using a program/file based OS, lets make the program names intelligible. Lets see: vi, emacs, joe (joe??? what the hell man), yast, lilo, initrd, sh, etc., etc.. Come on guys name your programs something intelligible, and leave the credits in the fscking readme file. At least if dos had something it had convenient keywords (copy, rename, delete, deltree, EDIT). I realize I could make symlinks to my hearts delight, but that is only assuming you know what the program your looking for is called.
6) Why did anybody think it would be a good idea to integrate the inetd with the x-windowing system (xinetd). Yippee, all the speed of NT servers on a linux system. Of course thats assuming you use inetd to begin with.
7) This one is for the distros: quit using the damn graphical installers. Graphical installers don't make installing any faster (quite to the contrary in a lot of cases), and in installing on older hardware a lot of times it makes it nearly impossible. I'm all for straightforward installers, but you don't have to be in a graphics mode to do it (fine standard VGA modes will work)
8) Hey I got a fun idea, lets put all those binaries in one directory, with no real index as to what each of these programs with obfuscated names do, and then lets give no easy way to find out what it does short of running it. Woo! And don't say, "One word, man" or "info" those systems are pretty fucked up as it is.
9) Standardize the damn locations, follow the LSB biatches.
10) This may sound contradictory to the above, but... abolish the Unix file system layout. I can't stress enough how a simple object persistence/serialization mechanism would be way better than a file system any day. Anyways, those are just my rants/suggestions as to what needs to be changed or layered on top of the linux filesystem if they wanted it to actually be a BETTER OS than windows or MacOS.
Re:You gotta hate Linux (Score:2)
They do. ALSA is one such standard, which supercedes OSS... anyway.
If it's not in the kernel, how will it talk to the hardware directly? You would need loadable modules.
Like PostScript or PCL? Few consumer-grade printers support them directly, and I would hate to mix printer translation code into the kernel. The current system (kernel provides a character device like
Look at GLX. It's OpenGL over the X protocol; see Evas [enlightenment.org] for an impressive show. Besides which, the X primitives (lines, boxes, etc.) tend to be hardware-accelerated, depending on the drivers.
Write one, then.
OO is one of the most overrated trends in modern CS, but continue.
Such as? Look into serious shell scripting, including grep, awk, sed, and the other *nix text processing commands.
Don't like the name an author gave his program? Grep the source for occurrences, change them, and recompile. Problem solved.
Yeah, CoPy, MoVe (since moving is renaming, think about it), ReMove, ReMove -Recursively, etc. As far as edit goes, I find vi far more efficient to use than, say, nano or pico (*nix 'edit' workalikes). Let me use vi if I so choose.
xinetd doesn't use X; I run it on several systems that don't have X installed. Research before you flame.
Then use a different distro, like Gentoo, Slackware, or Debian. That's the thing: you have the choice.
How, exactly? man will tell you pretty much everything, but may refer you to info -- if not, try <program> --help.
How about FHS [pathname.com]? Gentoo already follows this, but not so pedantically so as to make things unnecessarily complicated.
Design it, submit a kernel patch, as well as patches to glibc and all the GNU tools. Wait for a few years until programs get used to it, or until people realize it has no advantages over the conventional system and abandon it.
Re:Wow... (Score:2, Funny)
Re:Wow... (Score:2, Interesting)
Hmm.
Fair call.
Why is it that Debian gets good coverage? Perhaps it's something to do with the fact that it's at the source of the revolution. Transform the way IT services are done. Create a free system. Oh! you mean I pay for support services. Uh, OK, cool.
Suddenly people with lotsa debian needing debian aware dudez. We don't need Microsoft arse-brains anymore. Closed Source is dead.
Hmm. Industry transformed. Excellent!
Re:Wow... (Score:2)
Apart from birth times, how the heck is Debian at the center of the "revolution" and Gentoo isn't, or why do you think Debian is free and Gentoo isn't?
If you are not going to give an informed answer, and will just repeat distribution zealotry, please refrain from answering.
Re:Wow... (Score:2)
but, still, what's the biggest thing, go look at www.debian.org and www.gentoo.org. gentoo.org is pushing companies actively(nvidia & ibm logos on front page, ok, news items, but still).. and has stuff like screenshots. AND 'buy mem from crucial.com blabla'
would you install gentoo on your mp3 playing machine(your old p200mmx) that you would like to keep up-to-date still but has 32mb of mem or so, and still have xfree and some bells'n'whistles? debian works great for that too.(others work well for this too)
one of my friends was just a while ago converted to debian FROM gentoo, figure it out...
these are of course just impressions and take with grain of apt-get and i personally like dselect so i guess i'm a freak. and i really don't dig that some gentoo people running around telling they're system is x percent more effective or that the windows load up faster but you can't measure it..
Re:Wow... (Score:2)
gentoo looks like it's trying to hit in to the mainstream vein, as in trying to be the desktop of choice for newbies and guru's alike.
I think you completly missed it on this one. Gentoo is not for newbies, nor do they try to sell themselves as such. To quote them directly [gentoo.org];
Gentoo Linux is a versatile and fast, completely free Linux distribution for x86, PowerPC, UltraSparc and Alpha systems that's geared towards Linux power users.
Re:Wow... (Score:2)
1) Whoever gets to the market first, and has more zealots is best (where best=more credibility, more freedom, more quality)
2) Linux should never approach companies, and capitalist markets, under the risk of losing freedom.
3) Linux distribution quality is measured largely by the ability to run in older hardware. Conversely, ability to adapt to new hardware features is irrelevant because no one measured it.
Answering point by point:
1) You should be running a *BSD. It has been around since the late 70s. Its zealots are by far the most fanatic among the OSS crowd. Security and stability are unbeatable by Linux. Its harder to run. Harder than Debian, now that I come to think of it that way.
2) Some companies are likely to see linux as a strategic advantage. In fact, IBM, the main supporter behind Gentoo, is one of them. It'd be stupid to forfeit this help. See this article [joelonsoftware.com] for some insight on IBM's (and others') motivations on OSS.
3) I totally refuse this "old hardware" vision. And it's not that you can't install older software on a Gentoo distribution. Just emerge older ebuilds. The fact that you *can* emerge recent software doesn't mean you *have to*. And to think you have to measure the gain in performance from i386 asm to P4 asm is unclassifiable.
Re:Wow... (Score:2)
*** 3) I totally refuse this "old hardware" vision. And it's not that you can't install older software on a Gentoo distribution. Just emerge older ebuilds. The fact that you *can* emerge recent software doesn't mean you *have to*. And to think you have to measure the gain in performance from i386 asm to P4 asm is unclassifiable. ***
i _want_ to have _recent_ software(xfree4.2, kde3, whatever), but i don't want to _compile_ something that will take _days_ to finish on that older hardware, the point is that gentoo isn't meant to be able to install in practical timeframe to low end pc's.
Re:Question for you about gentoo [ot] (Score:1, Informative)
It's (obviously) your call in the end as to how much it's worth to you, but Gentoo is an excellent system. It has killer package management (Portage! -- what other package manager lets you specify compile-time options?), excellent speed (GCC 3.2), and wonderful consistency and customizability.
BTW, the init scripts were crafted specifically for Gentoo; it's neither BSD nor System V.
Re:Question for you about gentoo [ot] (Score:3, Interesting)
Dunno if you've heard of it, but there is a package manager called RPM that lets you set compile time options when you are building from source packages.
Re:Thanks... (Score:2, Informative)
It's about time they wrote a HOWTO for this (Score:4, Insightful)
1) Requires recompiling the kernel and crossing your fingers.
2) Requires you to use the beasts known as ALSA and crossing your fingers.
Operating systems are no longer stale command prompts with beeps and blurps -- they are full mutlimedia systems, and having working sound support in the first install should be a priority for Linux distributions.
When Linux newbies have a lack of HOWTOs and sound support is diffuclt to implement, at best they are going to fool around with Linux for a day or two and then go back to their MP3 collection under Windows.
Re:It's about time they wrote a HOWTO for this (Score:1)
Re:It's about time they wrote a HOWTO for this (Score:1)
I don't know. Did making the origami involve a robot and/or 3D modelling software? If so, yes.
Otherwise it's just another origami boulder [origamiboulder.com]. Sorry.
Re:It's about time they wrote a HOWTO for this (Score:2)
FWIW, I have installed Woody and RH8 on a lot of systems, including my laptop, where the sound worked out of the box with no config necessary. It's alot more newbie friendly in RH8, where most of the time sound worked when I loaded up GNOME without any sound config at all.
Usually on Woody all you need is to add the user to the sound group.
Re:It's about time they wrote a HOWTO for this (Score:1)
Re:It's about time they wrote a HOWTO for this (Score:2)
SealBeater
Re:It's about time they wrote a HOWTO for this (Score:1)
Re:It's about time they wrote a HOWTO for this (Score:2, Insightful)
My laptop has one of those too. You need ALSA.
And yes, I did recompile the kernel and ALSA modules some months ago. It's not that terrible, but you do need a lot of disk (300 MB or so)... However, you do not have to compile the kernel, nor the ALSA modules, if you're using Woody and a 2.4 kernel. The package is already done, it's just that for some reason it is still in unstable. Probably some issue that hasn't been dealt with yet, I don't know. The packages work for me. Just fetch the right package for your kernel [debian.org], run dpkg -i on it, and configure for your card.
Actually, you can configure apt to do this kind of thing without having to download stuff manually, but it's probably not worth it if the only thing you want from unstable is ALSA (or see apt_preferences(5) for details, if you do want to know more).
Re:It's about time they wrote a HOWTO for this (Score:2)
Re:It's about time they wrote a HOWTO for this (Score:4, Insightful)
Re:It's about time they wrote a HOWTO for this (Score:1)
DAMN Dont Make it a headline, Slashdot! (Score:2, Funny)
(Remember the airplane joke, what the linux people did...)
Re:It's about time they wrote a HOWTO for this (Score:2)
I know this first hand. I attempted to set up debian a number of months ago, and setting up my SB AWE 64 was the biggest pain I had. I managed to get an ftp server up and running, using my linux box as a router and sharing internet access between my roommates and I, even setting up a firewall. (I've never run any kind of unix or unix-like system before). GNOME and KDE weren't much of a hassle, and I managed to even get my Voodoo 2 card working so I could run low framerate UT.
The two things I could NOT get to work (and the two things that kept me from using debian fulltime) was getting a video player to work (for all the porn on my FTP server) and my sound! (for both the porn and MP3's on my FTP server, and games)
Had I gotten those to work, I would be writing this in debian now. Sound is very important when you're trying to gib your friends in Quake3. I've heard that gentoo makes it really simple, but alas, I am now restricted to a POTS 16.9 Kbps for my internet connection (No cable/DSL where I live...) and I don't want to take the time to download the distribution again...
Re:It's about time they wrote a HOWTO for this (Score:3, Informative)
Newbies should get SuSE or Mandrake, pop in the DVD, wait for half an hour and have a full functional desktop - including office suite and loads of useful stuff preinstalled. (Try to unpack a .rar in a clean Windows install. Or try ICQ. Or IRC.)
Linux can be much easier than Windows if you choose the right distribution.
I'm so sick of FUD like this:
having working sound support in the first install should be a priority for Linux distributions
All major commercial distributions (hell, even RedHat which is by far the worst of all) had sound-support out of the box for years.
Yet the Wintrolls just don't get it.
(P.S. Yes, debian has it's uses, too. apt-get is great, the stability is excellent. Yet it's not really for users not willing to invest some time installing.)
Re:It's about time they wrote a HOWTO for this (Score:2)
Debian doesnt need mllions of users; it exists to service a small number of people who want to learn about Linux.
If they did want millions of people to use it, its developers would (for example) make superior installers, so that it can be simply used.
Each distro has its audience. Its highly unlikely that someone switching from Windows will encounter Debian as their first distro in any case.
Why is this newsworthy? (Score:4, Insightful)
Re:Why is this newsworthy? (Score:5, Insightful)
It is more of the fact that Debian can't release a new Stable version until it works on all of the supported platforms.
But you are right. There should be no reason why something like autodetection shouldn't be incorporated into the install process. That is why they are working on a new install/boot process. An active mailing list to be on, let me tell you.
Re:Why is this newsworthy? (Score:1)
I use debian fairly often but wanted to use ALSA since I found out it was able to restore sound when my laptop resumed from suspend mode. The ALSA installation just seemed to complex and I just didn't have time from my job to sit there and read the docs on the ALSA site. It's really great there are informative howtos that tell you step by step what you need and how to accomplish it. You won't believe how many howtos I've read on that old UNC site! (I think it's linuxdoc.org now?)
Re:Why is this newsworthy? (Score:2)
Shortcut around other HOWTO's (Score:1)
In other worlds, intereting read.
It does provide information about Sarge and all...
Also,*Note: Britney Spears is not part of the KDREV option, so if you do leave out KDREV it will look like...
That's interesting.
NOW they have a HOWTO.... (Score:5, Funny)
I can hear/see it now:
"Hey guys, do YOU have sound on your system? I do!", I exclaim, with beaming pride.
"Uh, yeah whatever dude," they would say. "I got sound working too. Dumbass."
I can no longer consider myself 1337. B-(
Nice Article. Audio in general (Score:5, Interesting)
I'm also evaluating getting a better audio card, but I've had trouble finding decent documentation, even on the boxes - sure, everything does eight-dimensional 12-in-1 audio output, but what's I'm more interested in is the quality of the A/D converter, so when I input sound from analog media (my old vinyl disks and analog tapes) it doesn't lose more than necessary. Are there chipsets to avoid, or to hunt around for?
Re:Nice Article. Audio in general (Score:2, Interesting)
I would recommend checking out www.pcavtech.com for actual *real* measurements -- you can see how much of the SoundBlasters are merely marketing hype, and how much is real performance.
As for ALSA support: Midiman/M-Audio's soundcards are all well-supported. I haven't any clue about the others: theoretically, if the chipset is the same or very similar, there should be no complaints, but I wouldn't count on anything...
Re:Nice Article. Audio in general (Score:2, Informative)
The Live! is very well supported in Linux as far as my experience goes, and its analog inputs are pretty good. I don't have any hard figures, but going from my old vinyl to 192kbit MP3 (through LAME) compares *very* favorably to going from CD to same quality MP3 (Perl Jam - Vitalogy on vinyl and CD)
Also, the original Live! Platinum is available for around US$50 if you shop around.
(of course, all this is useless if you're looking for archive quality recording, but moving from your 'El-Cheapo Pretends-To-Be-Soundblaster-Compatible' it'd be an order of magnitde better)
Re:Nice Article. Audio in general (Score:5, Informative)
Not that you need 24 bits to transcribe vinyl, but it does help ensure that you'll not run out of headroom. Later in the process, you can normalize the audio and truncate or dither it down to 16, while preserving every nuance of the album's pops, ticks, and surface hiss.
Plug a box like this into a sound card's SP/DIF input. The stupider, cheaper, more DSP-phobic cards will generally be more likely to do a bit-perfect job of this, such as the $12 Zoltrix Nighingale or other CMI8738-based cards. Along the same lines, do try to avoid anything branded Creative Labs, mmkay? They've got bad habits like irrevocable resampling, and are noisy throughout (even when only doing strictly "digital" things with SP/DIF IO).
That said:
I used to play engineer for a streamed talk radio show. Equipment was limited to the gear in a small project recording studio, none of which was intended for broadcast use, aside from the scrap-built Linux box running liveice and lame.
Since this box needed a sound card, I drove over to the nearest white-box OEM parts dealer and started looking. I picked a YMF744-based (XG) PCI card from AOpen, similar to this one [aopen.com], based primarily on the component count: It was the only card under $50 which was not branded Creative, and appeared to have reasonable analog filter stages and signal paths.
It turns out that this card, along with other Yamaha XG cards, has superb support under ALSA, and that the quality of the converters is not bad.
The control of the card was such that I was able to calibrate it to the output meters on the Tascam console, and monitor the program via digital loopback through its own DAC at 0 gain.
I could then push a button on the console, and switch between monitoring the signal in its original analog state, or after it'd been through a ADC->DAC stage without worrying that varying levels would skew my perception.
In the (somewhat noisy) enviroment I was in, I could hear no difference in overall quality with or without the Aopen card in-line. This cheap sound card was, in a word, transparent, at least for my purposes. Which is all I can ask of any sound card.
ALSA made this easy, but I suspect I'd have trouble doing things so precisely under other operating systems.
But I've noticed that not all XG-based cards are made the same. Hoontech sells, or at least sold a year or two ago, some expensive studio-oriented monstrosities which doubtless sound beautiful. On the other end of things, I've heard some laptops with XG chips which sounded horrible.
Lately, I've been recording my 2-year-old daughter's various noises with an SB Live 5.1. The results are OK, but nothing like what I remember hearing in the studio. I could blame the card's on-board mic preamp or the sound of my apartment, but I fear that shoddy AD plays at least as large a role in the matter.
Good luck.
So, let me get this straight. (Score:4, Insightful)
- Make sure you have a 2.5.x kernel or above.
- Select your card from a dropdown.
- Retrieve, unpack, and compile source code.
- Install resulting software with a strange command-line utility.
- Retrieve, unpack, and install even more software.
- Edit a configuration file.
- Edit another configuration file.
- Run a script.
- Start a daemon.
Wow. That's so easy! I can see why OS X is the number one selling Unix:
- Go to System Preferences.
- Select "Sound".
- Select "Output".
- Select your high-end audio card.
- Select "Input".
- Select your high-end audio card.
Let's assume that your time is worth $50/hr. After a few hours of struggling to set up sound under Linux, that extra cash for Apple hardware doesn't sound so bad...
Re:So, let me get this straight. (Score:3, Informative)
Re:So, let me get this straight. (Score:1)
How about we assume that your being paid $50/hr to setup sound for a client. I don't know about you, but after those few hours of *ahem* struggling, I just made $150 bucks.
Re:So, let me get this straight. (Score:4, Interesting)
I can't count the number of tarballs i've compiled that were designed for Linux / FreeBSD and compiled clean under OpenBSD, really there is no OS that is generally easy to use for an advanced user.
My main beefs are:
OS X: Almost nothing will compile.
OpenBSD: Everything needs to be installed from source.
Windows: Security, stability, proprietary protocols.
Linux: Unless you are using debian most things of things need to be compiled from source. If you are using debian its a nightmare to configure.
It all generally boils down to spending alot of time to get basic things working. Once you attain advanced user status its basically a matter of spending lots of time getting everything working no matter what OS you use.
Computing sucks.
Re:So, let me get this straight. (Score:1)
Re:So, let me get this straight. (Score:1)
Re:So, let me get this straight. (Score:2)
Fink.
http://fink.sf.net/
It's an OSX packaging project based on the debian packaging system but with some other goodies thrown into it. In fact, from what I read about Gentoo, it has some similarites to it. As of last count, it has over 1400 packages in the system with more being added every day. Perhaps the BEST part of this is that it makes it trivial for upstream maintainers to get their software compiling clean out of the box on OSX. Since 10.1, most common packages compile clean 'out of the box'. Others will work fine with the addition of a few command line options to turn off precompiled headers and two-level linking namespaces.
If you go to the fink project home page, look in the documentation under 'porting', it will give you a few tips. For the most part, OSX is a very 'vanilla' UNIX flavor with few surprises. Really the only thing of note is how it handles shared/dynamic libraries, and there is even a library that will 'fake' the library loading behavior of other linux platforms.
Re:So, let me get this straight. (Score:2)
tar -xjf alsa-driver-whatever.bz2
tar -xjf alsa-utils-whatever.bz2
modprobe snd-ymfpci
DONE. Everything worked magically just like it did before. Nothing locked my
Re:Of course it is a flamebait... (Score:2)
Under Linux I applied a five line .diff to an i810 sound module source, `make dep modules modules_install`, loaded the module and proceeded to listen to music. Shortly thereafter the diff was applied to the kernel and my sound was supported natively.
Every OS has its strengths and weakneses as far as hardware support is concerned - some will prevent your OS from booting, others are a mere inconvenience until support is added.
It's dead simple, though, when a vendor controls both the hardware and software on a platform. "Sound support was easy! I have Sound Card Number Three Of Five! It was SO SMART that it detected it for me, all by itself!"
We sell about 20 different sound cards alone right now, and have sold and/or serviced probably 2000 different cards. Call me when OS X supports all of them. :)
Re:So, let me get this straight. (Score:2)
As bitchy as linux is to setup, the fact that there are better games out for it (since WINE works pretty well now) means that I get to use my sound for something besides iTunes.
Re:So, let me get this straight. (Score:2)
<sarcasm>
Of course: if something doesn't work out of the box in OS X, you have nothing to do but wait for the next release (and buy it)...
</sarcasm>
And of course, everything has to work out of the box on MacOS X, since it would pretty lame for a company that gets to decide what hardware has to be put inside its machines.
And of course, everything works out of the box on a Linux distribution if you stick to the supported hardware, which is what you should do in the first place like when you bought an Apple with OS X.
The point on MacOS X is that you can't choose non-Apple-sanctioned hardware and expect the clicky-pointy things to work.
Do you remember the times of the non-Apple clones? (i.e. Umax ones). Remember how MacOS wasn't guaranteed to run very well on these?
Last I checked, ALSA was rough to install (Score:4, Insightful)
$ modprobe es1370
and away I went.
With ALSA, I could load 15 or twenty drivers, and even if I managed to pick all the right ones, the damn things were muted by default!
So.. maybe a howto is a good thing. But why is it so damn complex that it requires a howto?
Please keep this in mind.. (Score:4, Insightful)
In ALSA it sounds sort of tinny and strained, it seems like the plain-jane maestro3 as opposed to the ALSA snd-maestro3 works better at least on my laptop.
I never seem to have trouble with my sound till I start mucking with it by hand. If I accept the distro defaults I am usually better off. This is a good thing for distros by the way. However, this is the exact opposite in terms of XF86Config. It seems like I always find two or three things to tweak manually that the distro-makers miss.
Oh well...
_______________________________________________
RTFM (Score:4, Funny)
Ok, the big news was indeed: use apt-get install alsa-source and read the manual to get alsa to work on Debian
"getting sound working" is not the whole story. (Score:5, Insightful)
If you are looking to migrate away from Cakewalk, Cubase, or Logic to a Linux solution, it's still a pipe dream. Sure there are a million audio projects, but the cubase killer is just not out there, not in the pipeline, and I don't even imagine it's in the cards.
A linux version of Fruityloops would be awesome, and if it were able to host VST applications, it would be of significant value to me.
One other point; I'd like to see a howto that deals specifically with the 2.5 kernel and debian.
The article is clear and concise, and it stops short of telling you how to, say, do multitrack recording, enabling 24/96 recording and mixing, or how to enable hardware synths. It also doesn't give any card specific help (Ice1712 M-Audio cards, anyone?) This is really just a special case of "installing modules" which is documented pretty well, elsewhere.
Re:"getting sound working" is not the whole story. (Score:2, Informative)
http://ardour.sourceforge.net
VST Killer:
http://www.ladspa.org/
Asio Killer:
http://jackit.sourceforge.net/
FruityLoops Killer:
Anything
Re:"getting sound working" is not the whole story. (Score:2)
Well I don't use any of those, but what I really want is a Linux Finale-alike. (Or, even better, something like Finale which supports multiple movements.) Nobody, as far as I know, is currently working on anything even close to this.
Re:Finale, was re:"getting sound working" is not . (Score:2)
Not really, but thanks for the pointer. Generally, good sequencers don't make good music typesetters in much the same way that vim or emacs doesn't make a good LaTeX.
Re:"getting sound working" is not the whole story. (Score:2)
Ummm, yeah. So, "don't know what the hell he was talking about" and "would have to do a web search" mean different things to you? Personally I distinguish betwen internal and external memory. I don't claim to "know" anything that I don't actually have in core.
Re:"getting sound working" is not the whole story. (Score:2)
mixing, and other production tasks. The "not the whole story" I was referring to consists of everything EXCEPT the steps to "listening to MP3's"
What are the advantages of ALSA? (Score:2, Interesting)
Yeah yeah, I know... RTFM. But I'm sure others on here are wondering what ALSA brings to the fold. Easy +5 informative here guys.
Re:What are the advantages of ALSA? (Score:2)
Re:What are the advantages of ALSA? (Score:2)
full duplex support (record and play at the same time.)
multiple voices, so multiple programs can play audio at the same time.
Re:What are the advantages of ALSA? (Score:2)
Re:Why not do it incrementally? (Score:2)
"Perfect" multimedia support is all we need... (Score:3, Interesting)
Linux has become absolutely great for two of the three sets of computer users. Newbies will have no more problems installing Mandrake than when installing Windows. Redhat and Mandrake both make is simple to set up the internet, web browsing, office app, etc. Power users love the control that Linux gives them over their system. However, linux is a nightmare for the people who are right in the middle. The things (like games) are just a little too hard to set up. The things that newbies wouldn't care about are the breaking points for the intermediate people. If something isn't autodetected by the install, it's a great deal harder to set it up in Linux than Windows.
So any distro that tries to make multimedia and gaming easier and more user friendly to set up gets my vote of approval. Even if it seems redundant.
Here is a simple HOWTO (Score:2)
Re:Here is a simple HOWTO (Score:2)
Does it run on PowerPC?
Does it run on Sparc?
Does it run on Alpha?
Does it run on x86?
Is the installation/setup the same across all four hardware platforms?
Are the packages well-maintained across all four platforms, including regular security updates?
When you can answer yes to all 6 questions, I'll consider it. Until then, I have too many computers to maintain to have a software-homogenous network...
Sound from your computer? What fur? (Score:2)
"Dude, I totally got sound working on my debian box. It took like 2 days and now I can listen to my Tool cd while I am reading Slashdot.", says Linux dipshit.
"Yeah, I can listen to Tool as well.", as I place the Tool cd in my radio and push play - that was hard.
I am joking of course. Sound on Debian is a pain in the ass it's good to see they made a HOWTO. I just hope they never implement any of that auto-detection crap other distros use, then every newbie and their grandmother is going to start downloading debian and 'apt-get update' will take forever.
Peace, viva la Debian!
How many CDs do you have? (Score:2)
I work at a radio station. I love music. If I had to keep track of all my real world CDs, I wouldn't even be able to remember what was available for me to put into my stereo. Of course, I don't have a stereo, so there's that, too.
By ripping all of my CDs to (currently, because no hardware Ogg players) MP3 format, I can, if I so desire, have a randomised playlist that will last for many days. I can organise my collection in any number of ways. My roommates NFS-mount my drive, so they can listen to it all without going into my room (and I can listen to it downstairs). I can lend a CD to a friend and not really care.
I don't download MP3s from P2P networks because most of them suck and I don't have enough time to search around for the few that don't.
WTF? (Score:2, Informative)
Commercial OSS drivers (Score:2, Informative)
Why ALSA is sooo Important (Score:3, Interesting)
1. ALSA sound drivers are nearly impossible to install.
2. If you want to turn your Linux box into a PVR (Personal Video Recorder) ala TiVo, then you need the alsa drivers and the stuff from the GATOS project.
(See) http://gatos.sourceforge.net/overview.php
I am glad that someone posted the HOW-TO... Alsa has been a big thorn in my side for awhile now. Maybe now I can get the ALSA-Mixer working properly.
Good Luck, and may your all Linux boxes be PVR's!
Linux Documentation Project MIDI-HOWTO (Score:2)
I don't want to troll but the Debian community asked the Linux Documentation Project to move the HOWTO's over to the GNU Free Documentation License, ./ article [slashdot.org], yet from looking at the Linux Orbit article it appears that the MIDI-HOWTO cannot include any of it's work as there are no indications that this text is opensource.
ALSA, and Linux audio development in general, is making HUGE progress.
Yes, things are still in development, ALSA 0.9 in 2.5 kernel is not meant for wide-scale use, but there are a significant number of very happy Debian users out there and once everything goes stable Linux will be the same ass kicking platform for audio as it is for servers.
The MIDI-HOWTO covers ALSA installation and whilst earlier version were more difficult to install, support for soundcards improves every day making it easier every release.
Phil
Only works with alsa 0.9 rc 3 (Score:3, Informative)
The line
options snd snd_major=116 snd_cards_limit=4 snd_device_mode=0660 snd_device_gid=29 snd_device_uid=0
wont work with newer versions (for instance Sid has 0.9rc5, an so I guess Testing will have it soon too), because (from www.alsa-project.org)
We have changed the kernel module symbol names (module parameter names). We removed prefix 'snd_'. Please, update your
That means you need to change the previous line into something like:
options snd major=116 cards_limit=4 device_mode=0660 device_gid=29 device_uid=0
Hope this helps
There is another good howto for the same thing (Score:2)
Kalin
Re:what's wrong? (Score:2)
SealBeater
Re:what's wrong? (Score:2)
Re:what's wrong? (Score:2, Informative)
Re:what's wrong? (Score:1, Flamebait)
Re:RTFM.... (Score:5, Informative)
Re:RTFM.... that's the WinME manual, right ... (Score:2)
A direction I sincerly hope linux doesn't go.
SealBeater
Re:RTFM.... that's the WinME manual, right ... (Score:4, Insightful)
You don't learn anything. Learning new things is important to me, if not to anyone else.
Automagically detecting hardware is not an exact science. If all you use is a tool to do something, then you can't fix it if said tool breaks.
Lots of time to read is relative. In the time it takes to read the HOWTO, you could have read the documentation that comes with ALSA and walked away with far more knowledge. You have to learn how to do anything, that's just a fact.
SealBeater
Re:RTFM.... that's the WinME manual, right ... (Score:1, Insightful)
I don't know. You could use this time to learn something that is actually useful. Like an interesting programming language, or some theory, or something not related to computers at all. I don't like the face the software FORCES me to use my time to learn its configuration, as opposed to saving me time I could use on what I want. Unless you're a mindless drone who, if not given a configuration problem, just reads Slashdot and chats on ICQ...
Last time I checked, you could override drivers on Windows.
Re:RTFM.... that's the WinME manual, right ... (Score:1)
Re:RTFM.... that's the WinME manual, right ... (Score:2)
That's fine. Enjoy Windows. Let me know what your mp3s sound like when DRM takes away your ability to play them. Maybe then you'll read some documentation.
SealBeater
Re:RTFM.... that's the WinME manual, right ... (Score:1)
Re:RTFM.... that's the WinME manual, right ... (Score:2)
By the way, I am not a "everyone should do it the hard way" but I am cognizant of the benefits reaped from actually reading documentation and being able to learn. Just to add, the HOWTO has nothing that isn't in the ALSA docs. I am not against HOWTOs, I am against HOWTOs that are distro specific and contain no new or helpful information.
SealBeater
Re:RTFM.... that's the WinME manual, right ... (Score:1)
i think i understand your viewpoint; it would certainly be difficult to wade through the list of HOWTOs if there were many superfluous ones. but just because there is little unique information does not mean they are useless. a good HOWTO is likely to be better organized and a gentler and quicker introduction than the full documentation.
i agree that it's better not to have distro-specific documentation, but i'd rather that mean authors try writing documentation that is helpful for all distros, rather than simply not writing about something because it's distro-specific. there are many people using each distro, and there should be useful documentation for them, whether it's helpful to the entire community or just part of it.
Re:RTFM.... that's the WinME manual, right ... (Score:2)
Re:RTFM.... that's the WinME manual, right ... (Score:1)
Re:RTFM.... that's the WinME manual, right ... (Score:1)
Reading documentation? I work with computers all day long, the last thign I want to waste my time with is reading a howto to find where to add the extra line to a config file to make a sound card work. That shit is tolerable when it comes to configuring a server, but a sound is not critical to a server. It is critical to a multimedia home computer and most IT professionals do not want to have to fiddle with their hoem computer just to make it work. It is a total waste of time.
Re:RTFM.... that's the WinME manual, right ... (Score:1)
i've installed linux many times on a lot of different machines (generally for friends and friends of friends ever since high school), and have very rarely needed to do any major tweaking just to get things to work. perhaps with obscure hardware sound would be difficult, but at this point major distros seem to get it right. i dont think anyone using those really is forced to read and configure if they dont want to.
when i first put linux on my laptop (back in 1999), i had to read and tweak for an hour or two to get sound to work on the stupid neomagic sound/video card, but once it worked it actually sounded better than it had on win98 (which came with the machine), mostly because the driver for windows had some serious problems. that's when i started to appreciate linux, because with windows there was nothing i could do to fix sound, and after that the amount of work to configure linux seemed trivial.
before claiming that linux isnt ready for the desktop, maybe you should look into it more so you can at least base your decision on personal experience and not on your impression of some
Re:I know why this ended up on the main page (Score:2)
Hemos is the one that posted it to slashdot
Re:I know why this ended up on the main page (Score:1)
Re:And people wonder why Lunix isn't 'mainstream' (Score:2, Insightful)
Linux isn't mainstream because people like you assume that "it ISN'T INTENDED, and NEVER WAS INTENDED, to run on the desktop." How very short-sighted of you to assume something so silly. The sad thing is that in a few years when Linux has made major inroads toward that goal, we'll still have your claim in the Slashdot archives to look back on and laugh.
BTW: You should probably have a look at the HOWTO for IIS (running on that vastly superior OS where no HOWTOs are needed?). You've got a bit of a problem at http://beaner.dyndns.org.
* Error Type:
Microsoft JET Database Engine (0x80040E09)
Cannot update. Database or object is read-only.
Stick that in your pipe and smoke it.
Re:And people wonder why Lunix isn't 'mainstream' (Score:2)
I myself am devoid of Microsoft zealotry. It's simply a platform that I and all of my high-paying clients use. I don't have any high-paying clients who use Lunix, except as a cheap web server. Please reflect on your Lunix zealotry, and decide whether it is the best use of your time.
Re:And people wonder why Lunix isn't 'mainstream' (Score:2)
Re:And people wonder why Lunix isn't 'mainstream' (Score:2)
Fine, this ALSA thing is Debian centric, but it's just endemic of a greater problem with linux: ease of hardware configuration. Or even simpler, ease of configuration period.
How much of your hardware is supported? Fully supported? Working?
Is all your software configured properly? Do you even know where to configure the software?
I've been running linux since 94 and I've never once had my system work exactly right. Take for instance my zip drive.
I have to run devfs if I want to use USB, fine. If I use ide-floppy, the zip drive only gets created if there's a disk in it at boot. If I use scsi-ide on my zip drive, then
This is moronic. Say what you will about windows, but at least my hardware works right the first time, and more importantly I don't have to fuck 3 hours with it.
Linux isn't mainstream because people like you assume that "it ISN'T INTENDED, and NEVER WAS INTENDED, to run on the desktop."
*bzzz* Sorry. You're wrong. Thanks for playing. Here's your year supply of Rice-a-Roni "The San Fransico Treat".
Linux isn't a mainstream desktop because quite frankly it sucks. Hardware doesn't always work without major work. (Yes, compiling is major work. Hell looking up that my card uses the 3c905 chipset rather than, it's a "3com Whatever" is a pain in the ass.) The desktop environments are annoying at best. (Nautilus only has "clean up by name option"...)
And then of course you have The Community(tm). Post a bug, and if you're not completely ignored, you get a "Damn you you insolent cur! Fix the thing yourself! If you use it your a developer! I do this for free damn it! Show some resepect!"
First off, I'm a user not a developer. I do not have any intention to learn the inner workings of vector based text rendering to learn why the ghostscript drivers you provided don't work.
Secondly, when you release stuff, expect bug reports. Expect that most people don't really give a damn about how your pet project works, they just want it to work. How arrogant are you that you to think that I'm going to drop everything I'm doing to spend a week to help you. It's your piece of software, maintain the damn thing. Is there a known solution? You could have documented it in the time it took you send the 20 "Fuck you" emails you just sent.
The sad thing is that in a few years when Linux has made major inroads toward that goal, we'll still have your claim in the Slashdot archives to look back on and laugh.
You mean like this article [slashdot.org]? Or this this comment [slashdot.org]?
BTW: You should probably have a look at the HOWTO for IIS (running on that vastly superior OS where no HOWTOs are needed?). You've got a bit of a problem at http://beaner.dyndns.org.
* Error Type:
Microsoft JET Database Engine (0x80040E09)
Cannot update. Database or object is read-only.
Stick that in your pipe and smoke it.
You mean like this error I just got on
Re:Alsa (Score:2, Informative)
ALSA does not cause "random crashes of the
machine if you have an onboard sound card."
There have been some buggy chipsets that
can lead to lockups without some driver
workarounds. I have one in my laptop - a NeoMagic 256 A/V (ugh). Takashi Iwai of the ALSA project
invested a great deal of time in responding to
my problem reports and fixed the problems I was
having with that chip.
If you're having problems with ALSA and lockups, it's specific to your soundcard. Try a more recent version of ALSA, and if it's still broken,contact the developers. They want to fix it, but they don't have access to every piece of hardware under the sun.
--PW
Re:installing alsa? (Score:2, Informative)
I don't completely agree with you here. I do agrre in that Debian's efforts to ease the road for the newbies are pretty lackluster, to say the least. However, maybe I'm just insensitive, but I can't say I care too much about that. For power users, there isn't anything close to Debian --anything that I've tried, anyway. That includes several other Linux flavors, Windows, Solaris and MacOS pre-X (I'm really interested to try FreeBSD, Gentoo and MacOS X, but alas, no time).
But that's a feature, not a bug! That's precisely what allows me to build full-featured Debian routers out of old 486 boxes with 240 MB hard disks (no kidding).
You just have to read a little. By now I'm sure you found out that in Debian you don't edit modules.conf directly, but put files in /etc/modutils, which update-modules assemble into a modules.conf file. It's cleaner, easier to maintain, it avoids one package from clobbering other package's modules. If only you manage to get used to it, you'll probably find that there's usually a very good reason behind most of Debian's oddities.
Debian will seldom touch your hand-edited files, if you know where and how to write them. I know, that can annoy a great deal out of an old timer used to edit conf files freely --but then again, Debian's scheme of things allows you to install and deinstall things, and even to upgrade from slink to potato to woody, without worrying about breaking anything. I think that's a good reason to deviate from traditional setups.
Yeah, that is a problem. Again, I don't care much: I use FVWM, and the few GTK/Gnome apps that I need (Mozilla, Evolution, XChat, the Gimp) I installed from Woody and work flawlessly. But I do see someone getting frustrated from the lack of Gnome2 and/or KDE3. I hope someone that actually gets bothered enough by this will go help the guys packaging that stuff --they've been doing it for a long time, and a little bit of help probably won't hurt.