(sorry for the double-message, paul. i forgot to send this to the mailing list)
thank you for your insightful and cordial response, considering the tone of my original responses. i will get back to you when i have more concrete questions. right now i think the onus is on me to figure out as much as i can. i’m going to try and organise all of these controls by accordingly adding an IOAudioPort, and then attaching them to it. while this is probably superficial and an organisational step, it would surely help others make more sense of what’s going on. and i agree with everything you’re saying about the scarcity of individuals with this expertise. unfortunately, in my opinion, the latest “API” shown at WWDC21 is a regression so i will never go down that road (that’s ignoring the fact they require entitlements to *try* and program PCI stuff—really??) Thanks, Gagan > On Dec 10, 2022, at 3:58 PM, Paul Davis <[email protected]> wrote: > > The number of people who know their way around both the CoreAudio and ALSA > APIs enough to answer questions like the ones you appear to want to ask is > likely in the single digits. At one time (say, 2005), I would have been one > of those people, but I'm not anymore (my main project has had its own > CoreAudio and ALSA backends in place for more than 15 years now, and I > haven't had to touch that stuff for a very long time thanks to the courageous > work of other people). Nevertheless, I still have one of the highest > google-ranked pages on basic of the ALSA API, and at one time used to answer > questions here as well. > > As you have probably noted, this mailing list has gone essentially completely > silent for several years now. That doesn't make it impossible that someone > might reply to your questions, but given your own observations about posting > frequency, specifically targeting an employee who hasn't been on this list in > a decade seems ... strange. > > Why not actually post the code or at least the concepts you're having issues > with? Nevetheless, you're going to need someone with a very, very specific > knowledge base, and I'd be willing to bet that they're not active on this > list anymore. > > > > On Sat, Dec 10, 2022 at 3:08 PM Gagan Sidhu via Coreaudio-api > <[email protected] <mailto:[email protected]>> wrote: > and just to really finish this point off: when i say “answer questions” it > has nothing to do with coding. > > it has to do with the coreaudioAPI. > > for example, how does one implement an SPDIF toggle? we could use an > IOAudioToggleControl, sure, but i noticed > kIOAudioSelectorControlSelectionValueSPDIF is in an enum. > > and if my usage is appropriate, another question would be about handling a > massive number of controls that involve monitor modes. > > right now we have a Level and Toggle control, and yes we can use the more > generic IOAudioControl::create, but it seems to me there hasn’t been anyone > asking questions of this nature. > > the closest was Yves in 2011: > https://lists.apple.com/archives/coreaudio-api/2011/Mar/msg00004.html > <https://lists.apple.com/archives/coreaudio-api/2011/Mar/msg00004.html> > > i found willoughby’s answer very interesting in terms of generalisation. for > example, ALSA’s snd_kcontrol_new requires an ‘info’ and ‘get’ function. > > yet for coreaudio there is no equivalent. it is almost as if, as long as we > can specify the hardware control for setting things (like alsa’s put), that > “coreaudio will take care of the rest”. > > this is a very forwarding thinking API and it irritates me someone with a > linux domain name thinks i wanted some assistance for monkey-work. stay in > your lane. > > if this ruins my chance at getting assistance from people who may actually > have the serious expertise to answer my question: so be it. > > right now, everyone is losing with apple’s current priorities and ecosystem. > > Thanks, > Gagan > > and P.S: jeff moore used to respond to MANY questions about coreaudio on the > mailing list, up until 2013. since that time, he has not posted (or from what > i’ve been able to find). > > wouldn’t surprise me if he left. doesn’t mean he still doesn’t read the > mailer and it’s not his baby. it’s pretty obvious that it is. > > >> On Dec 10, 2022, at 2:56 PM, Gagan Sidhu via Coreaudio-api >> <[email protected] <mailto:[email protected]>> wrote: >> >> and, yet, you said it. >> >> the term linuxaudiosystems evokes a guffaw. sorry to say. >> >> Thanks, >> Gagan >> >> p.s. it’s pretty clear the usage of ‘help’ is not to “write code” or >> anything of that nature, but to answer questions. >> >>> On Dec 10, 2022, at 2:10 PM, Paul Davis <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> It's really not for me to say, but I find it a little presumptuous that >>> anyone would think they can reach out directly to Jeff Moore (or anyone >>> else) for help with such an effort. Good luck. >>> >>> On Sat, Dec 10, 2022 at 1:51 PM Gagan Sidhu via Coreaudio-api >>> <[email protected] <mailto:[email protected]>> >>> wrote: >>> hi, >>> >>> testing to see if this works now. i sent a message a month ago and noticed >>> it didn’t appear on the archives. >>> >>> hoping it does now. >>> >>> if you’re reading this jeff, please holler at me! i would benefit from your >>> assistance in wrapping this ALSA code to coreaudio (i’m using osx < 11) >>> >>> https://github.com/i3roly/CMI8788 <https://github.com/i3roly/CMI8788> >>> >>> >>> Thanks, >>> Gagan >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Coreaudio-api mailing list ([email protected] >>> <mailto:[email protected]>) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/coreaudio-api/paul%40linuxaudiosystems.com >>> >>> <https://lists.apple.com/mailman/options/coreaudio-api/paul%40linuxaudiosystems.com> >>> >>> This email sent to [email protected] >>> <mailto:[email protected]> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Coreaudio-api mailing list ([email protected] >> <mailto:[email protected]>) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/coreaudio-api/broly%40mac.com >> <https://lists.apple.com/mailman/options/coreaudio-api/broly%40mac.com> >> >> This email sent to [email protected] <mailto:[email protected]> > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Coreaudio-api mailing list ([email protected] > <mailto:[email protected]>) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/coreaudio-api/paul%40linuxaudiosystems.com > > <https://lists.apple.com/mailman/options/coreaudio-api/paul%40linuxaudiosystems.com> > > This email sent to [email protected] > <mailto:[email protected]>
_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com This email sent to [email protected]
