Re: CoreAudio and Vendor ID and Product ID of a sound device
Re: CoreAudio and Vendor ID and Product ID of a sound device
- Subject: Re: CoreAudio and Vendor ID and Product ID of a sound device
- From: Matthias Hänel <email@hidden>
- Date: Wed, 21 Oct 2015 10:15:29 +0200
Hey Brian,
yes, you are right that user defined speaker mapping is not detectable by this procedere.
I believe Fireface 400 is not a good example for the problem. Please imagine a Pioneer DDDJ-SX for example.
Nevertheless, in our audio field (Midi/Hid Controllers with audio interface) the sound devices
are pretty much fix and not configurable. That's why it is a good idea to detect what we have and
to set up the sound device correctly.
The question is still, how I can retrieve the USB IDs or even IEEE1394 or even PCI ids from an upper
layer sound device. I know, this is capsulated in driver layers to have a seamless audio interface
and almost nobody needs this information :)
It took me months to find a solution for Windows, because the driver layers are also (correctly) astract the
interfaces to a higher layer.
any help is still welcome :)
Matthias
> Am 19.10.2015 um 19:10 schrieb Brian Willoughby <email@hidden>:
>
> Matthias,
>
> What do you mean by "channel detection is always successful" with the Fireface 400?
>
> What if the user plugs nothing but the SPDIF output into their surround system DAC? Does the system detect the channel successfully? Does the Fireface 400 send the same audio to both the analog and digital outputs?
>
> What if the user plugs their stereo cables in the analog channels 5 & 6? Will the system detect the channel?
>
> My understanding is that the Fireface 400 has complete user control over routing between inputs (like Firewire) and outputs. Are you saying that system is always successful at playing audio, no matter what routing had been set up? What if someone runs more than one piece of audio software and the second piece of software changes the routing?
>
> I don't think Paul is saying that automatic selection is a bad idea. He's pointing out that it's not possible in many situations. I just gave a few examples with the Fireface 400 where a non-technical user might not get any sound at all, even if your software existed.
>
> Basically, many high-end audio interfaces are unique in their routing, and it's impossible for a non-technical person to connect everything correctly without at least reading a few User Manual pages.
>
> Some interfaces, like the MOTU 896HD, have fixed routing options. If you want the Main output pair, or the headphones, or the digital outputs, then it's easy to select those by name in generic software. Other interfaces, like the Metric Halo Labs MIO, have flexible routing between the Firewire I/O and the audio I/O, such that you never know which Firewire channel corresponds to which audio output. Sometimes, a Firewire channel will merely be connected to an internal mixing bus without a direct output. With the MH gear, your automatic system will not work unless you incorporate the MH Console Connect plugin.
>
> Brian Willoughby
> Sound Consulting
>
>
> On Oct 19, 2015, at 12:41 AM, Matthias Hänel <email@hidden> wrote:
>> Hey Paul,
>>
>> thanks for your fast answer.
>> I am not sure what you are trying to tell me :)
>>
>> You don't seem to believe it is a good idea in general.
>>
>> Well, some of our competitors do exactly this behaviour.
>> I think it is good to have a solution like this since many of our users
>> are not quite fimiliar with any technical stuff, they just want to play
>> music. That's why automatic selection is a good idea from my point.
>>
>> I also have a fireface 400 here :) This is one good example where channel detection
>> is always successful. I believe the overall problem is wrong firmware.
>>
>> regards
>> Matthias
>>
>>
>>>> Am 15.10.2015 um 13:25 schrieb Paul Davis <email@hidden>:
>>>>
>>>> On Thu, Oct 15, 2015 at 3:29 AM, Matthias Hänel <email@hidden> wrote:
>>>>> Hey Brian,
>>>>>
>>>>>
>>>>> thanks for your fast answer.
>>>>>
>>>>> You are right Apple almost delivers an option for the final solution :)
>>>>>
>>>>> I am quite sure there is not.
>>>>>
>>>>> The main goal of this procedure is to setup the sound device settings
>>>>> without user interaction. Some or even many sound devices come with more than one stereo channel.
>>>>> This setting is not always correctly detected by Core Audio. The user has to go to
>>>>> "Audio-MIDI-Setup" and has to select the correct Output-Mode like "quadrophonic" or higher.
>>>>>
>>>>> I know that I can force this setting by software and therefore I have to know which sound device
>>>>> is attached. Well, we have to have a big list with VID/PID and speaker-modes, but that would be
>>>>> sufficient even for native supported soudn devices and MIDI controllers.
>>>>
>>>> To be honest, I think this is a fools errand.
>>>>
>>>> There are MANY devices with large numbers of channels. The way these
>>>> devices are connected to speakers is not defined anywhere. You can
>>>> also forget jack-sensing and stuff like that. Even sitting right next
>>>> to me is a fireface 400, with 18 channels of output. You have no idea
>>>> how this is wired up in my office/studio, and there's nothing you can
>>>> do to find out except ... ask me.
>>>>
>>>> the "output modes" in audio/MIDI setup have essentially nothing to do with this.
>
_______________________________________________
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