Re: Create MIDI device programmaticly without a MIDIDriver bundle
Re: Create MIDI device programmaticly without a MIDIDriver bundle
- Subject: Re: Create MIDI device programmaticly without a MIDIDriver bundle
- From: Nuno Santos <email@hidden>
- Date: Sat, 04 Jun 2011 13:07:57 +0100
Hi Brian,
Sometimes I don't understand this lists. My subject says "Create MIDI device programmaticly without a MIDIDriver bundle"
Between my first email and this one the only thing I got was basicly:
"why don't try this instead because it will be complex to do what you want"
I'm not a veteran developer however I had already some complex tasks on my hands which required a lot of digging in without to much information. I can refer for example the work of developing a custom Windows 7 kernel driver to handle with a USB multitouch device without never having developed a kernel driver for anything. Lots of complexity, lots of kernel panics (even in my head), lot of time digging out around thru google. But I have reached to a solution and none has made the code for me. I hate Windows and I prefer to learn about Apple technologies, however I'm professional developer and I work with any technology that fits my needs at a very specific moment.
Sometimes I think my questions in this kind of groups are interpreted as: give give give me code. I don't want solutions, I just want some guidelines to avoid losing endless hours looking for information that I sometimes can't find. I have already made some questions in this list a couple o years ago, and definetly, by that time I didn't have the knowledge neither the experience to do structured questions. I think now i'm doing it right. I have a look into documentation first, look for examples, if that isn't enough I go googling for info about it. Only if the refered steps have failed I ask in the list.
What I infer from your message is that it's possible to create a MIDI source sink without having a MIDIDriver bundle which connects to MIDI Server. If that is possible, that is what I want. However, this is not my first email regarding to this topic and no one told me that yet. If that was plain obvious from documentation in Apple Reference, I was not here asking that. CoreMIDI related documents are one of the less documented documents I have ever seen in Apple which usually has countless information on it's documentation.
Can you people please tell me just which classes or services I should look carefully into?
Basicly I just want to create a small app that creates a MIDI input/output which will be available in any audio program that uses MIDI.
Let the remaining complexity to me! I'm not asking you guys to give me solutions. Just guidelines. Isn't that the purpose of this list after all?
Thanks,
With my best regards,
Nuno Santos
A 2011/06/03, às 21:59, Brian Willoughby escreveu:
> I disagree that what you want to do is really simple. A MIDI Server is the last thing you should attempt to do, and the most difficult (apart from writing your own operating system). Instead, you should focus on application level CoreMIDI API, including the ability for an application to provide a MIDI source/sink for other applications. Even though you think you want to write a driver, you really should start with the application MIDI services and work with them for a while before you attempt writing a MIDI Server.
>
> Brian Willoughby
> Sound Consulting
>
>
> On Jun 3, 2011, at 04:07, Nuno Santos wrote:
>> I think that what I want to do is really simple, right now I just really wanted to understand the call sequence of MIDI Server when it founds a driver, since that doesn't seem obvious to me on the SampleUSBMIDIDriver.
>
>
> _______________________________________________
> 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
_______________________________________________
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