From alsa-devel-owner@alsa.jcu.cz  Wed Oct 28 18:33:32 1998
Received: from pat.bath.ac.uk (pat.bath.ac.uk [138.38.32.2])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id SAA26702
	for <alsa-devel@jcu.cz>; Wed, 28 Oct 1998 18:32:39 +0100
Received: (qmail 273 invoked from network); 28 Oct 1998 17:15:43 -0000
Received: from mary.bath.ac.uk (HELO bath.ac.uk) (138.38.32.14)
  by pat.bath.ac.uk with SMTP; 28 Oct 1998 17:15:43 -0000
Received: from tobi.bath.ac.uk by mary.bath.ac.uk id aa12682;
          28 Oct 98 17:15 GMT
Message-ID: <36375127.4487@bath.ac.uk>
Date: Wed, 28 Oct 1998 17:15:19 +0000
From: "P.J.Leonard" <P.J.Leonard@bath.ac.uk>
MIME-Version: 1.0
To: alsa-devel@jcu.cz
Subject: Re: AWE32 synth stuff
References: <9810281554.AA11410@servww1.ww.uni-erlangen.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

Takashi Iwai wrote:

> BTW, in the case of AWE32, the real-time patch loading is
> unrealistic.  Patch-loading consumes high CPU powers.  Then,
> preferrablly all the patches should be preloaded before playing
> actually.  It's also another matter for consideration.

 Correct I tried this in cantor and everything slows down until
the patch is loaded. Is there anyway that patch loading could be
done at a lower priority ?

> * device specific control:
> 
> Another question -- the device specific controls should be sent via
> sequencer device, or directly from application to device-clients?
> Above all, the former is possible (like SEQ_PRIVATE event on OSS)?

 All the controls that could be meaningful to the sound of a voice
should go through the sequencer so they can be used for real time
modulation. 

 What happens to a voice if it's patch gets replace by another
preset during playback ?
(I have managed to crash the OSS /dev/sequencer by clearing the AWE
memory
during playback !!!)


 cheers Paul.

