Re: : Strange USB-MIDIMAN Problem, help badly needed !
Re: : Strange USB-MIDIMAN Problem, help badly needed !
- Subject: Re: : Strange USB-MIDIMAN Problem, help badly needed !
- From: Pete Gontier <email@hidden>
- Date: Thu, 23 May 2002 11:06:47 -0700
I don't want to turn this list into a MIDIMAN support channel, so I will
keep this brief. I'm willing to bet that given that the 9 drivers work,
there is no hardware problem. MIDIMonitor has never been faulty in any way
that I've seen, so I am reluctant to blame it as well. This is likely to be
a problem in our X driver. For masochists, here is as brief an explanation
as I could write.
One of the issues I had to address with Quattro in our 9 MIDI driver was
that the Quattro audio driver needs to take the device offline to
reconfigure it. This is due to some to some complex cross-platform
interaction which I don't remember well right at the moment, but it is
something with which the MIDI driver needs to cope. I worked with our audio
driver guys to make sure our 9 MIDI driver copes, but so far the X MIDI
driver does not cope. I'm sorry the beta drivers aren't working for you; I
will certainly be working hard in the near future to make this problem go
away. In the meantime, you may be able to make MIDI work as long as you
don't use audio, which I realize is an unacceptable constraint given the
nature of Quattro, but I thought I'd make the suggestion anyway in the off
chance it helps someone. I won't really know more about this issue until I
dive back in to the X drivers Real Soon Now.
circa 5/23/02 3:02 AM, Uwe Kuhlmann <email@hidden> wrote:
>
Hi ,
>
>
refering to Pete Gontiers post I feel that this is the place to report
>
on a strange problem I face since I've bought the Midiman AudioQuattro
>
USB interface. I'm using a powerbook 550 and OS 10.1.4. The audio part
>
is runnig fine with MIDIMANs recently released beta audio drivers.
>
However, with the mididriver released in feb. I have only MIDI out, and
>
by no means I was able to activate MIDI in. What is really strange about
>
that is
>
1. The interface works with OS 9.2 (MIDI in and out) so the hardware
>
seems to be ok! (right ??)
>
2. even more weird : it worked for some minutes after installing the
>
midi drivers and than never more. Unfortunately I cannot remember the
>
details (shock) how this happend. I first suspected the MIDIMonitor to
>
be responsible for that, because it seemed MIDI in passed when I startet
>
it. Meanwhile I' m through with a complete reinstall of my system and ,
>
surprise surprise, ... no MIDI in !
>
Of course the MIDI monitor shows no MIDI in signal, MIDI out is truely
>
logged. The console messages indicate me that the MIDI driver is
>
properly activated (MIDI start ...etc ) when I start MIDI software but
>
there was no trace of :
>
....
>
>>>>>> MIDIReceived because we have 1 packets;
>
intf->mSources[prevInputPort] is
>
>>>>>> 0x0981000A
>
> i>>>>>nputPort 0 bytesInPacket 1: FE 00 00 01
>
>>>>>>> new status FE, remainingBytesInMsg = 0
>
....
>
Since no on from either MIDIMAN-support, which I phoned here in Germany,
>
nor the people in our local music hardware store (they seem to detest
>
OS X) could help me, this is maybe the place for this weird problem.
>
>
My questions are:
>
>
1) Is my conclusion right that the hardware is ok, Pete, can the
>
hardware work with OS 9 and yet fail with OS X by hardware error ?
>
2) Has anyone ever faced a problem like that ?
>
3) How can I further encircle the cause of my problem ?
>
>
hints, comments etc. welcome, I'm really at the end of my wisdom .-(
--
Pete Gontier -- pete at midiman dot net -- <
http://www.midiman.net/>
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.