http://wiki.joanillo.org/index.php?action=history&feed=atom&title=MsAlsaSeq%3A_ALSA_driver_for_MidiShare 2026-08-30T12:02:35Z Historial de revisió per a aquesta pàgina del wiki MediaWiki 1.34.2 http://wiki.joanillo.org/index.php?title=MsAlsaSeq:_ALSA_driver_for_MidiShare&diff=2126&oldid=prev 2009-04-01T09:43:21Z

<p>New page: A Linux, hem de tenir instal.lada la llibreria MidiShare, d&#039;una banda, i tot el sistema de so ALSA, per l&#039;altra. ALSA és el que s&#039;encarrega de parlar amb els dispositius físics, la targe...</p> <p><b>Pàgina nova</b></p><div>A Linux, hem de tenir instal.lada la llibreria MidiShare, d'una banda, i tot el sistema de so ALSA, per l'altra. ALSA és el que s'encarrega de parlar amb els dispositius físics, la targeta de so. Aleshores el que fa MidiShare és proporcionar un driver ALSA, i d'aquesta manera els projectes MidiShare poden ''sonar''.<br /> <br /> =man MsAlsaSeq=<br /> &lt;pre&gt;<br /> MSALSASEQ(1) MidiShare User’s Manual MSALSASEQ(1)<br /> <br /> <br /> <br /> NAME<br /> msAlsaSeq - ALSA driver for MidiShare<br /> <br /> SYNOPSIS<br /> msAlsaSeq [options] [client-name]<br /> <br /> DESCRIPTION<br /> msAlsaSeq creates an ALSA sequencer client and a corresponding<br /> MidiShare client, both named client-name (&quot;MidiShare/ALSA Bridge&quot; by<br /> default) and establishes connections to other ALSA clients as given by<br /> the -i and -o options. MIDI input received by the ALSA client becomes<br /> the input of the MidiShare client, and output of the MidiShare client<br /> is sent to the output side of the ALSA client. This allows you to<br /> access ALSA devices and other ALSA clients from MidiShare applications,<br /> simply by connecting your MidiShare application to the input/and or<br /> output of the msAlsaSeq MidiShare client.<br /> <br /> You can just start the program as msAlsaSeq and establish connections<br /> to other ALSA clients manually with aconnect(1) or your favourite ALSA<br /> patchbay. Alternatively, you can specify the desired connections<br /> directly on the command line. For instance,<br /> <br /> msAlsaSeq -i 64:0 -o 64:0<br /> <br /> connects input and output to port 0 of client 64. Usually this corre‐<br /> sponds to the external MIDI interface of your first soundcard. To find<br /> out about the available ALSA sequencer clients and ports on your sys‐<br /> tem, run the ALSA program aconnect with the -i and -o options. You can<br /> also use the MidiShare msconnect program to connect your MidiShare<br /> applications with the MidiShare client created by msAlsaSeq.<br /> <br /> Instead of a numeric ALSA client id, you can also specify the client’s<br /> name. Shell wildcards (‘*’, ‘?’ etc.) are recognized as well. E.g.,<br /> <br /> msAlsaSeq -i ’Rawmidi*’:0<br /> <br /> connects the input to port 0 of the first client whose name starts with<br /> ‘Rawmidi’.<br /> <br /> By default, the MidiShare port number of a received event is always<br /> zero, and transmitted events are always sent to all connected ALSA<br /> clients, no matter which MidiShare port was specified. This behaviour<br /> is consistent with the other drivers supplied with the Linux version of<br /> MidiShare, and is convenient if you want to dynamically connect to dif‐<br /> ferent ALSA clients with the aconnect utility. If necessary, multiple<br /> instances of msAlsaSeq can be run to access different ALSA clients. In<br /> this case it is useful to specify the client-name parameter to distin‐<br /> guish the different clients. Example:<br /> <br /> msAlsaSeq &quot;ALSA Midi Port&quot; -i 64:0 -o 64:0<br /> msAlsaSeq &quot;ALSA Wavetable Synth&quot; -o 65:0<br /> <br /> Alternatively, you can also specify a mapping between ALSA client ports<br /> and MidiShare ports as follows:<br /> <br /> msAlsaSeq -i 64:0/0 -o 64:0/0 -o 65:0/1<br /> <br /> Here we configured one input port, which is mapped to MidiShare port 0,<br /> and two output ports which are mapped to the MidiShare ports 0 and 1,<br /> respectively. This provides some degree of compatibility with the MacOS<br /> and Windows versions of MidiShare (where you usually access different<br /> devices using corresponding port numbers, instead of connecting to<br /> different MidiShare clients), but is less versatile, as all input and<br /> output ports have to be specified in advance and cannot be changed<br /> dynamically.<br /> <br /> OPTIONS<br /> -h Prints a short usage message and exits.<br /> <br /> -i client:port[/msport]<br /> Establishes an input connection with the given ALSA client and<br /> port. The client can be given either by its numeric id or a pat‐<br /> tern for the client name. The MidiShare port number msport is<br /> optional. If present, it indicates that input is mapped to the<br /> given MidiShare port when an event is delivered to the MidiShare<br /> application.<br /> <br /> -o client:port[/msport]<br /> Establishes an output connection for the given ALSA client and<br /> port. If the MidiShare port number msport is given, only<br /> MidiShare events directed to that port will be output on this<br /> connection.<br /> <br /> BUGS<br /> Right now msAlsaSeq does not keep track of the original ALSA times‐<br /> tamps. The timestamp of a received event thus indicates the time at<br /> which the event was read by the driver.<br /> <br /> SEE ALSO<br /> aconnect(1), http://www.alsa-project.org<br /> http://www.grame.fr/MidiShare<br /> <br /> AUTHOR<br /> Albert Graef, University of Mainz. (Based on Grame’s msRawMidi driver.)<br /> <br /> <br /> <br /> May 2004 MSALSASEQ(1)<br /> &lt;/pre&gt;</div>

Joan