Re: [midishare-devel] Input from MIDI device

[Ashley W. <as...@dc...>]

On 10 Jun 2005, at 2:02 pm, St=E9phane Letz wrote:
> Note that the MidiShare port  to device mapping (defined in msDrivers)=20=

> has to be done while *no* other  MdiiShare applications are running,=20=

> otherwise other applications will *not* see the new state, the reason=20=

> is that in the nono-application version, the MidiShare context is not=20=

> really shared among all applications...
>
> Thus you should :
>
> - lauch msDrivers
>
> - do the connection EDIROL PCR 1" and "EDIROL PCR 2" to MidiShare port=20=

> 0
>
> - output to "QuickTime GM Synth".
>
> - close msDrivers so that the new connections  state is saved
>
> - then open msDisplay (that will use the new connections state)

Wow this is a speedy mailing list :).  Many thanks for the reply,=20
St=E9phane.

Unfortunately the above sequence doesn't work for me.  At step 1, I=20
don't see the EDIROL input or output slots.

If msDisplay is running *before* I launch msDrivers, then I see the=20
EDIROL slots.  Also, if I have Apple's Audio MIDI Setup application=20
running before I launch msDrivers, I see the EDIROL slots.  If I just=20
launch msDrivers on its own, I don't get the EDIROL information and so=20=

can't make the connection to port 0.

Also the changes I make in msDrivers don't seem to be saved when I quit=20=

and restart it.  Should this be happening?  (I think you imply that it=20=

should, since you say that "the new connections state is saved".) =20
Where should the changes be saved to?  Perhaps there is a permissions=20
problem?

I've created a new test user to check for conflicts with my setup, and=20=

the results are the same.  I've also tried rebooting the machine.

Ashley.