Re: Ann: Serial MIDI Interfaces
Re: Ann: Serial MIDI Interfaces
- Subject: Re: Ann: Serial MIDI Interfaces
- From: Lachlan Deck <email@hidden>
- Date: Wed, 9 Oct 2002 02:02:32 +1000
Hi there,
On Tuesday, October 8, 2002, at 08:47 AM, Bill Stewart wrote:
on 7/10/02 12:16 PM, Doug Wyatt wrote:
I Wrote (some time):
Can I humbly suggest that instead of removing it, make it open source
and so allow its continued development with patches making their way
to the main source tree... There seems to be some willing to help out.
That's exactly what Bill's suggesting ... making it sample code is
effectively equivalent to open sourcing it, though without a
centralized maintenance structure -- though I think we can that here.
If the SDK release ends up being a problem, we can look at an
alternative
mechanism - one of the things we can do is to still remain a point of
arbitration... If developers who use this code and change it want to
send us
back those changes, we can look at them and then include it in any
future
SDK release.
Also, if there are any changes in the base classes of the MIDI drivers,
we
can ensure that we keep the sources for this up to date.
Sounds good. Thanks very much for clarifying that.
The main thing we are trying to avoid here is that we DON'T have the
time or
the support, given that (1) We no longer ship machines with this
capability
and (2) most users of X are not using this anyway, to continue to
maintain
this.
(1) not without removing the modem. So yes and no.
(2) == circular argument
segmentation fault ;-)
Hmm - most users of music systems (mac) aren't using Mac OS X fullstop,
considering that it's only very recent that such software has become
available (e.g., Logic). I personally don't see a completely valid
argument that says a user needs to update all peripherals in order to
use a new computer (or indeed a new OS). It just seems a bit backward -
but I do appreciate that there are priorities...
Perhaps the assumption is being made that someone who buys a new Apple
Computer doesn't have older peripherals that they need (not want) to
plug in. Midi Interfaces and Printers are two things that immediately
come to mind as devices which, other than their connection to the
computer, provide an identical service to the user. It seems wasteful to
replace such devices because of a software issue...
It's worth considering that people buy peripherals for their longevity.
This *IS* currently causing some developers problems in bringing their
products to market - that is bad...
As I said, I can appreciate this.
I simply note that, in many cases, the developers' customers include
those who have previously invested in devices of these same developers...
Is it not also bad if their devices are not supported? i.e., not all
customers are recent converts to daw...
That simply makes it harder for developers to support their loyal
customers...
As we can't spend the time qualifying
this (and to be honest don't want to - there are many other things
with a
much higher priority that really need the time) it seemed to us that the
best solution was to remove this from the shipping OS...
But, and I want to reassure those of you who do care about this, the
fact
that we are prepared to make this code available should be taken to
indicate
that we do understand that some people do have a valid use for this
code and
we would like to ensure that this continues to be supported (if not
ideally,
then at least adequately) for those developers.
Thanks again for taking the time and for the availability of the code...
Bill
with regards,
--
Lachlan Deck
email@hidden
_______________________________________________
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.