From alsa-user-owner@alsa.jcu.cz  Sun Jan 10 14:29:56 1999
Received: from pluto.andeby (IDENT:ahermans@t2o212p34.telia.com [195.204.226.94])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id OAA17497
	for <alsa-user@alsa.jcu.cz>; Sun, 10 Jan 1999 14:27:31 +0100
Received: from localhost (ahermans@localhost)
	by pluto.andeby (8.8.7/8.8.7) with ESMTP id OAA02935;
	Sun, 10 Jan 1999 14:27:33 +0100
Date: Sun, 10 Jan 1999 14:27:32 +0100 (CET)
From: Anders Semb Hermansen <ahermans@vf.telia.no>
To: Thomas Adams <tadams@pobox.com>
cc: alsa-user@alsa.jcu.cz
Subject: Re: alsa-lib-0.3.0pre2
In-Reply-To: <19990110010604.A4678@cat.ping.de>
Message-ID: <Pine.LNX.4.04.9901101421500.2845-100000@pluto.andeby>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

On Sun, 10 Jan 1999, Thomas Adams wrote:

> On Sat, Jan 09, 1999 at 06:47:41PM +0100, Anders Semb Hermansen wrote:
> 
> > aclocal ; automake --foreign ; autoconf
> > and the configure script will appear and you can run your './configure'
> > script as normal
> 
> Yes, thanks. This worked. One last question: What does the alpha sequencer 
> support mean? I upgraded my driver and libs solely because I read this and 
> thought I could run playmidi afterwards to hear MIDIs on my GUSMAX. But I 
> can't. What am I missing? Before anybody asks: Yes, I used the 
> ...sequencer=yes switch of ./configure

The sequencer is not done yet, and it does not (yet) work with any synth
device. If you want sound you'll have to use an external midi device. All
you can do is to be patient and wait for Jaroslav and others to make the
best sequencer on linux ever :-)

> 
> No, I lied: _This_ is my last question: Where do I find the documentation? The 
> doc directories contain as far as I can tell information for programming. But 
> I would like to know what to write into /etc/conf.modules so that the driver 
> is started at boot time. I seem not to find this information within the driver 
> package nor on the website. How come?

The documentation is not yet done either. I think I saw a posting about
this some time ago, that someone is working on doc's for the 2.0 release.
If you want ALSA to be started at boot time you should use the alsasound
script that is in the utils dir in the driver package.
If you use redhat just copy it to /etc/rc.d/init.d and run the command
"chkconfig --add alsasound".


Regards,
Anders

--
Anders Semb Hermansen
E-Mail: <ahermans@vf.telia.no>
Cellmail: <93802837@sms.netcom.no>



