[midishare-devel] confused with 1.9 on fc4

[daniel j. m. <dmacd@u.washington.edu>]

Hi, I'm new to midishare (1.9, built from tarball on fc4). I'm just trying 
to play a few notes (a la the tutorial on SendNote samples) but I cant 
find a concise explanation of what needs to be loaded and configured for 
this to happen. From the docs its not clear to me what the user needs to 
do to make things go.

Alsa midi works, e.g.
'aplaymidi --port 65:0 test.mid'
does something.

I have
msAlsaSeq -o 65:0
running and run the msTutorial script everything checks out:


  <<<< WELCOME TO THE MIDISHARE TUTORIAL >>>>

--> use g or G to run the first test
g


  <TEST 1 : Check if MidiShare is installed>
--> use g or G to run the next test
g
MidiShare installed  : YES


<TEST 2> Get MidiShare version
--> use g or G to get the MidiShare version and go to the next test
g
MidiShare version : 1.90


<TEST 3> Count MidiShare client applications
--> use g or G to count MidiShare client applications and go to the next 
test
gg
Count of MidiShare client applications : 3


<TEST 4> Register as a client application
--> use g or G to register as a client application and go to the next test
MidiOpen succeed. Our reference number is : 3


<TEST 5> Count again MidiShare client applications
--> use g or G to count again MidiShare client applications and go to the 
next test
g
Count of MidiShare client applications : 4


<TEST 6> List every MidiShare client applications
--> use g or G to list every MidiShare client applications and go to the 
next test
g
List of MidiShare client applications
-------------------------------------
   1 : reference number  0, name : 'MidiShare'
   2 : reference number  1, name : 'MidiShare/ALSA Bridge'
   3 : reference number  2, name : 'msdisplay'
   4 : reference number  3, name : 'Linux_Tutorial'
-------------------------------------



<TEST 7> search the reference number of 'Linux Tutorial'
--> use g or G to search the reference number of 'Linux Tutorial' and go 
to the next test
g
Reference number of 'Linux Tutorial' : 3


<TEST 8> search the reference number of 'XYZ'
--> use g or G to search the reference number of 'XYZ' and go to the next 
test
g
Reference number of 'XYZ' : -4
A negative result means that the application was not found.


<TEST 9> change the name of client application 'Linux Tutorial' to 
'MidiShare Tutorial'
--> use g or G to change the name and go to the next test
g
List of MidiShare client applications
-------------------------------------
   1 : reference number  0, name : 'MidiShare'
   2 : reference number  1, name : 'MidiShare/ALSA Bridge'
   3 : reference number  2, name : 'msdisplay'
   4 : reference number  3, name : 'MidiShare_Tutorial'
-------------------------------------



<TEST 10> connect the output of 'MidiShare Tutorial' to 'MidiShare'
--> use g or G to make the connection and go to the next test
g


<TEST 11> test a connection
--> use g or G to test the connection and go to the next test
g
We are connected to the MidiShare output driver


<TEST 12> list the destinations of our application
--> use g or G to list the destinations of our application and go to the 
next test
g
List of destinations of 'MidiShare_Tutorial'
-------------------------------------
  --> reference number  0, name : 'MidiShare'
-------------------------------------



<TEST 13> list the sources of the MidiShare output driver
--> use g or G to list the sources of the MidiShare output driver and go 
to the next test
g
List of sources of 'MidiShare'
-------------------------------------
  <-- reference number  3, name : 'MidiShare_Tutorial'
-------------------------------------



<TEST 14> send a note
--> use g or G to send a note and go to the next test
g


<TEST 15> send many notes in the future
--> use g or G to send many notes in the future and go to the next test
g

<<<< no midi output >>>>


msdisplay also shows nothing during any of this...


I assume I am just missing an extra bit of configuration...apologies for 
the dumb question.

Daniel