Re: [midishare-devel] Input from MIDI device

[Jay V. <ja...@sy...>]

>
>Here are some answers to your questions, Jay... I'm talking about 1.90 now:
>

does this mean you installed 1.88, got a config file, and then 
installed 1.90 on top, and it now works?

one thing: run the disk tools "fix permissions" function on your 
system now, and see if that changes something.



>Unless msDisplay (or Apple's Audio MIDI Setup app) is running before
>I launch msDrivers, I don't see the EDIROL interface.  I've tried
>waited several minutes for the interface to refresh!
>

.. but the weird thing is that if msDisplay is running, you -do- see 
things?  are you then able to use msDrivers to add a driver, and then 
run a MidiShare client app and have it work?

>(Note from above that in 1.90, the msMidiDriver.ini file is not
>created, which appears to be the cause of my problem.)
>

msMidiDriver.ini is where all the connections-per-port information is 
stored, and gets created after you've successfully used msDrivers to 
tell it what to do... check to see if this file gets created when you 
fire up msDisplay first, then msDrivers .. config .. check if file 
exists and contains entries pointing to your EDIROL interface ..


>
>This is my first install.
>

but, it works with 1.88?  then i would say, get 1.88 working first, 
then try to upgrade to 1.90 over the top of it ..

>... so now I have a working 1.88 installation.  I guess this is OK
>to use for experimental development.  I'm willing to try other
>experiments to try and diagnose the problem in 1.90 -- let me know
>what to try.

i've used MidiShare on OSX since 1.86, so i'm afraid i can't help 
much on whether the 1.90 driver is working by itself .. all my 
configs have 'come with me' as i've upgraded..

-- 

;

Jay Vaughan