Re: [midishare-devel] Input from MIDI device

[<le...@gr...>]

Le 10 juin 05 =E0 14:49, Jay Vaughan a =E9crit :

>> I have tried various setups in msDrivers.  (I believe the correct
>> setup should be for port 0 to take input from "EDIROL PCR 1" and
>> "EDIROL PCR 2", and output to "QuickTime GM Synth".)
>> My ~/Library/Preferences/MidiShare/midishare.ini file contains the
>> following line (among others):
>> active=3D msQTDriver.so msMidiDriver.so
>> I was expecting to be able to play the QuickTime synth from the
>> controller keyboard by setting an appropriate configuration in
>> msDrivers.  I thought perhaps I'd also need to run msEcho to achieve
>> this.  But nothing happens either way.
>>
>
> fire up msDrivers and msDisplay.  set port 0 on msDrivers (click =20
> the square), then set the EDIROL interfaces.
>
> turn a knob on EDIROL - you should see data in msDisplay.  if you =20
> don't, get MIDI Monitor (OSX App) and use it to see if MIDI data is =20=

> being received as well.
>

Note that the MidiShare port  to device mapping (defined in =20
msDrivers) has to be done while *no* other  MdiiShare applications =20
are running, otherwise other applications will *not* see the new =20
state, the reason is that in the nono-application version, the =20
MidiShare context is not really shared among all applications...

Thus you should :

- lauch msDrivers

- do the connection EDIROL PCR 1" and "EDIROL PCR 2" to MidiShare port 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)

You should see input event coming then.


> i have found under OSX that sometimes you have to wait a second or =20
> two before the MS subsystem gets initialized and set up properly, =20
> upon starting a MidiShare client app .. so get msDrivers and =20
> msDisplay working first, then fire up msEcho, and away you go ..

You cannot setup a Midi thru only by using msDrivers, you would have =20
to have a MidiShare client that redirect all incoming events on the =20
its output.

>
>
>> Again, I have been successful with various other applications on my
>> Mac, but not with MidiShare.
>>
>
> the msDrivers interface is sometimes a little confusing.  when you =20
> first start it, there should be 'blue' squares in the middle - any =20
> one of these blue squares is a configured MidiShare port.  if you =20
> don't have any, then you don't have the ports set up properly ...
>
> --=20


Stephane Letz=