From alsa-user-owner@alsa.jcu.cz  Fri Mar  5 20:37:03 1999
Received: from mail.cyberverse.com (80@brionne.cyberverse.com [209.151.224.34])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id UAA00651
	for <alsa-user@alsa.jcu.cz>; Fri, 5 Mar 1999 20:34:23 +0100
Received: (qmail 31803 invoked from network); 5 Mar 1999 19:32:46 -0000
Received: from brionne.cyberverse.com (2687@209.151.224.34)
  by brionne.cyberverse.com with SMTP; 5 Mar 1999 19:32:46 -0000
Date: Fri, 5 Mar 1999 11:32:46 -0800 (PST)
From: Batman <opiate@cyberverse.com>
To: alsa-user@alsa.jcu.cz
Subject: Re: Midi Question
In-Reply-To: <9903040838.AA14091@servww1.ww.uni-erlangen.de>
Message-ID: <Pine.LNX.4.04.9903051122320.29767-100000@brionne.cyberverse.com>
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


Argh, so close.

It was a problem with sound.o.. Removing the module and corresponding
lines from /etc/conf.modules fixed the problem.  I can now load and unload
the module fine.  I had forgotten to include the applicable lines from
/var/log/messages unfortunately.. Now, though, everything works -almost-
perfectly.  The module goes in cleanly, /proc/asound/ossseq appears, and
playmidi seems to find it when running it through external midi.  But,
alas, there is no sound output.  All channels are unmuted and at full
volume, all modules are loaded, and /proc/asound/ossseq (while running
playmidi), reads:

OSS sequencer emulation version 0.1.1
ALSA client number 128
ALSA receiver port 0

Number of applications: 1

Application 0: 
  port 1
  seq mode synth
  file mode write
  max queue length 1024
  write queue length 21
  output threshold 512
  current tick 502
  next tick 487
  system tick 486
  next system tick 487

Number of synth devices: 0

Number of MIDI devices: 1

midi 0: 0: ES1370
  client 64
  port 0
  capability read/write
  opened write

---------

Again, I hope I'm not just missing something obvious...

Thanks,

-John


