Re: [midishare-devel] Input from MIDI device

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

Le 13 juin 05 =E0 17:08, Ashley Ward a =E9crit :

> I haven't previously installed MidiShare.  When I sent my earlier =20
> emails, I was using 1.90.  I still have no luck with this version.
>
> However I've just tried the 1.88 version, and all seems fine -- the =20=

> behaviour of msDrivers is as Jay describes: changes I make there =20
> are remembered between launches, and msDisplay shows data from the =20
> controller keyboard :)
>
> I notice that 1.88 creates a ~/Library/Preferences/MidiShare/=20
> msMidiDriver.ini file, which 1.90 did not.  (This answers my =20
> question about where msDriver changes are saved to.)
>
> So there is a definite bug in 1.90 on my system.
>
> Both versions of the installer have a bug.  Given that both =20
> versions have it, it isn't the cause of my issue, but it is a =20
> problem.  The installer changes the permissions on my Applications =20
> folder to "Owner: system", meaning I then have only read =20
> permissions there.  The MidiShare folder is also owned by system.  =20
> I can fix this with "sudo chown -R ashley:admin /Applications/=20
> MidiShare" but that doesn't have any affect on my original (can't =20
> read data from controller keyboard) problem.
>
> Here are some answers to your questions, Jay... I'm talking about =20
> 1.90 now:
>
> On 10 Jun 2005, at 5:48 pm, Jay Vaughan wrote:
>
>>> Unfortunately the above sequence doesn't work for me.  At step 1, I
>>> don't see the EDIROL input or output slots.
>>>
>>
>> open 'audio/midi setup' and look for the driver there.  confirm =20
>> that it is there (okay, midi monitor saw it, fair enough).
>>
>
> Yup, the driver is there in Apple's Audio MIDI Setup application.
>
>
>> then .. open msDrivers and wait.  watch Console.app.  check the =20
>> midishare.log file in ~/Library/Preferences/MidiShare/ .. notice =20
>> all alerts/msgs.
>>
>> copy/cut/paste to the list for dissection ..
>>
>
> No clues here, I'm afraid.
>
> Every time I open msDrivers:
>
> * ~/Library/Preferences/MidiShare has a line added like this:
> [06/13/05 15:29:41]: MidiShare: open time interrupt using a timer - =20=

> time resolution is 1
>
> ... there isn't anything else in that file.
>
> * console.log (shown in Console.app) has a line added like this:
> ## Component Manager: attempting to find symbols in a component =20
> alias of type (regR/carP/x!bt)
>
> * There is nothing added to system.log (shown in Console.app).
>
>
>>> If msDisplay is running *before* I launch msDrivers, then I see the
>>> EDIROL slots.
>>>
>>
>> close msDisplay, open msDrivers all by itself.  msDrivers -should- =20=

>> see the EDIROL interface .. however, it can sometimes take a =20
>> second for the interface to refresh.
>>
>
> Unless msDisplay (or Apple's Audio MIDI Setup app) is running =20
> before I launch msDrivers, I don't see the EDIROL interface.  I've =20
> tried waited several minutes for the interface to refresh!
>
>
>>> Also, if I have Apple's Audio MIDI Setup application
>>> running before I launch msDrivers, I see the EDIROL slots.  If I
>>> just launch msDrivers on its own, I don't get the EDIROL information
>>> and so can't make the connection to port 0.
>>>
>>
>>
>>> Also the changes I make in msDrivers don't seem to be saved when I
>>> quit and restart it.  Should this be happening?
>>>
>>
>> yes, this is a clue.  check the permissions on your midishare.ini =20
>> file.  delete it, or move it out the way (mv) and try to start up =20
>> msDrivers again ..
>>
>
> ~/Library/Preferences/MidiShare/midishare.ini seems to be created =20
> if it doesn't already exist whenever msDrivers or msDisplay are =20
> launched.  However the state of the file never changes from the =20
> default.
>
> (Note from above that in 1.90, the msMidiDriver.ini file is not =20
> created, which appears to be the cause of my problem.)
>
>
>>> (I think you imply
>>> that it should, since you say that "the new connections state is
>>> saved".)  Where should the changes be saved to?  Perhaps there is a
>>> permissions problem?
>>>
>>
>> have you had earlier versions of MidiShare onboard, or is this =20
>> your first install?
>>
>
> This is my first install.
>
>
>>> I've created a new test user to check for conflicts with my setup,
>>> and the results are the same.  I've also tried rebooting the =20
>>> machine.
>>>
>>
>> check all logs, lets see if they provide a clue..
>>
>
> Logs provided above -- no clues, I'm afraid.
>
> ... so now I have a working 1.88 installation.  I guess this is OK =20
> to use for experimental development.  I'm willing to try other =20
> experiments to try and diagnose the problem in 1.90 -- let me know =20
> what to try.
>
> Ashley.


We will probably publish a new kit on OSX soon. We found some =20
problems in the installer script that may explain your problems and =20
also in the MidiShare framework when used with Common Lisp MCL on =20
Tiger....

Regards

Stephane