From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: MIDI port names Date: Tue, 25 Feb 2003 17:11:38 +0100 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Jaroslav Kysela Cc: Pedro Lopez-Cabanillas , "alsa-devel@lists.sourceforge.net" , Clemens Ladisch List-Id: alsa-devel@alsa-project.org At Thu, 20 Feb 2003 21:19:19 +0100 (CET), Jaroslav wrote: > > On Thu, 20 Feb 2003, Takashi Iwai wrote: > > > At Thu, 20 Feb 2003 15:14:45 +0100 (CET), > > Jaroslav wrote: > > > > > > If there is a way to determine the connection between sequencer port and > > > rawmidi device, I'm ok with any solution. Otherwise, please, solve this > > > problem. > > > > one of the advantages of the sequencer is that it hides the lowlevel > > implementations, regardless of mpu401 or wavetable. hence, there > > is no explicit link between the lowlevel device and the sequencer > > client/port, so far. there are only bit flags indicating what kind of > > functions are supported by the port. > > > > it's not bad to have such an attribute, though. but if we have that, > > it will be an addition. > > We can use different name for client like: > > RawMIDI - %s > > Where %s is whatever you want ;-)) card->shortname, card->id or anything > else. The card number can be calculated from the client address and device > / subdevice from the port address. done. now everthing became more verbose :) Takashi ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf