From alsa-devel-owner@alsa.jcu.cz  Sat Feb 20 16:00:16 1999
Received: from entry.jcu.cz (IDENT:perex@entry.jcu.cz [160.217.1.111])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id QAA18412;
	Sat, 20 Feb 1999 16:00:01 +0100
Date: Sat, 20 Feb 1999 16:00:01 +0100 (CET)
From: Jaroslav Kysela <perex@jcu.cz>
To: Yamahata Isaku <yamahata@kusm.kyoto-u.ac.jp>
cc: alsa-devel@jcu.cz
Subject: Re: sending active sencing when closing sequencer port
In-Reply-To: <19990220192645.A11204@smdoc2.kusm.kyoto-u.ac.jp>
Message-ID: <Pine.LNX.3.96.990220155642.29496G-100000@entry.jcu.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

On Sat, 20 Feb 1999, Yamahata Isaku wrote:

> Hello.
> On the behavier of ALSA sequencer client of raw midi device when unused.
> (static int midisynth_unuse(void *private_data) @ kernel/seq/seq_midi.c).
> 
> Suppose that we created an ALSA sequencer client and are sending midi event
> to a sequencer client of a raw midi device.
> When our sequencer client exits, eventually ALSA driver call midisynth_unuse
> for destination client and the destinaiton client will close the associated
> raw midi device.
> But if the sequencer client exited abnomally, a midi device which is
> connected to the midi port of the raw midi device would countinue to
> pronouce forever.
> 
> This problem can be solved by sending active sencing midi event (0xFE)
> before closing raw midi device. Patch is attached.

Applied.

> But there is a question.
> Is it an appropreate behavior?

My answer is yes. Until anyone have got better idea how can be stopped
external synthesizer...

							Jaroslav

-----
Jaroslav Kysela <perex@jcu.cz>
Academic Computer Centre, University of South Bohemia
Branisovska 31, C. Budejovice, CZ-370 05 Czech Republic


