Re: Do not want multiple clients mixing my audio
Re: Do not want multiple clients mixing my audio
- Subject: Re: Do not want multiple clients mixing my audio
- From: Paul Davis <email@hidden>
- Date: Fri, 14 May 2010 16:11:48 -0400
On Fri, May 14, 2010 at 3:21 PM, John Johnson
<email@hidden> wrote:
The thing about this list and a couple other lists around here is that before help is given, the reason must be approved. I have several times been frustrated with going through this "approval process" in order to get a question answered. This is mainly because these lists are a last resort and I only turn to them when I've beat my head against the wall for several days already. Typically it's me doing something outside the normal way. Yep, just me thinking outside the box again :) Oftentimes, people say "don't do that, it doesn't work like that" and I find out that they are wrong. But hey, it's not their job to write my programs for me, so I chalk it up to lesson learned. The ONLY way to learn in the programming world, IMO.
the number of people who show up on mailing lists like this and attempt to make it sound as though they really know what they are doing, but want to do something a little unusual, is roughly equal to the number of people who really don't know what they are doing, and if they did, wouldn't decide to do something unusual at all.
there's no way when someone shows up whether they fit into this category or are one of the rare exceptions who match their own self-image. one of the best ways to do that is to ask questions that seek to get the person to justify/explain why they think they need to take a particular (unusual) approach. sometimes (not often) it turns out that the person really does have a solid grip on how everything works and what they need to do.
when you're sending to a mailing list about an OS X API and receiving answers from the guys who designed and maintain that API (Bill Stewart, Jeff Moore, James Mccartney and others), and they are telling you that the way you're approaching this seems, well, maybe not the most obvious, i think you should perhaps take it as a sign that its worth revisiting your own certainty about what is an option or not.
perhaps you haven't ever developed an API that is widely used as something like CoreAudio - when you do, you'll find that its typical to get all kinds of people using it who for one reason or another (possibly through a failure to adequately document it) simply misunderstand significant aspects of how it is intended to be used. i'm not saying that this is true in your case - i'm just saying that its pretty common for this to be the case, so people are just trying to be gentle in seeking to establish that you really do know what you're talking about when you assert, for example, that you have "no option" but to be in kernel space. that's certainly a claim i've seen made by other people, and despite their adamant insistence on the issue, they were simply wrong. again, that may not be the case here. we're just a little skeptical because of such claims in the past and the absence of any specific reasons in your case. when you end up not doing things in the way that matches (in this case) Apple's intent, it becomes a lot more likely that changes that they make in the future will break what you've done. this happened with JACK and it was only by carefully listening to what Jeff & Bill (among others) had to say that we eventually got things right there.
so, if you get upset about people trying to save you from yourself, try not to be. that's all it really is :)
--p
_______________________________________________
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