Re: MIDI USB Class driver problem from reset
Re: MIDI USB Class driver problem from reset
- Subject: Re: MIDI USB Class driver problem from reset
- From: Mark Cookson <email@hidden>
- Date: Fri, 30 Sep 2005 14:54:51 -0500
- Thread-topic: MIDI USB Class driver problem from reset
Just out of curiosity, will this reset MIDI for every MIDI device on the
system, or just ours? While MIDIRestart() doesn't take any parameters, it
doesn't work if you just call it out of the blue, returning
kMIDIServerStartErr. We're trying to just use MIDIClientCreate then
MIDIRestart, then MIDIClientDispose to see if that gets MIDIRestart working,
but since none of those calls take a specific device or instance, we're a
little worried that we'll be affecting other devices/drivers.
Is the USB MIDI Class driver likely to loose MIDI data across this call? If
it isn't, great, no worries. But if it is going to loose data, is there a
more surgical way of doing this to just our device's driver?
Thanks,
Mark
--
Mark Cookson
M-Audio, a part of Avid
225 Locust St.
Hudson, WI 54016
On 9/30/05 12:13 PM, "Doug Wyatt" <email@hidden> wrote:
> On Sep 30, 2005, at 7:58, Mark Cookson wrote:
>> Is there some call that we can make from the audio driver to the
>> MIDI driver
>> to tell it to reset? Is there some other way, aside from removing the
>> reset, that might be able to mitigate this issue?
>
> Hi Mark,
>
> Have you tried calling MIDIRestart()? This will shut down and restart
> all the MIDI drivers. That's what the Rescan button in AMS does.
>
> If that doesn't work I'd be interested in figuring out why...
>
> Doug
>
> --
> Doug Wyatt
> Core Audio, Apple
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden