Re: Setting Sample Rates
Re: Setting Sample Rates
- Subject: Re: Setting Sample Rates
- From: "Douglas Wright" <email@hidden>
- Date: Tue, 15 Jan 2002 01:08:25 -0800
- Organization: Bias, Inc.
>
> Exactly, that's why we need a name property for the streams.
>
>
I would argue that a name property is pretty useless except for display
>
purposes. You end up having to guess based on some arbitrary text that may
>
or may not have the information you are looking for in it. What if the
names
>
are all in Japanese, but you searching for some English text? What if the
>
text is misspelled or missing?
>
What you really want is some information about the category and transport
>
types of the stream as enumerated constants. This makes things a bit more
>
predictable.
My app doesn't care what the text says, the channel numbers are fine for me.
But at some point, the user wants to choose what channels they're going to
use, ideally without getting out the manual for the device to see what
stream 3 channel 14 is mapped to. It would have a name like Analog Input 14
or Globosonic Output 4. The app just lets the user choose. As you said
before, flexibility is good for the driver writer, so why are you trying to
limit it to a predefined list of types? What about the soon to be released
scubafone input. How do we identify it if it comes out after we build our
apps?
I suppose I was mixing up my streams and channels when I was asking for
stream names, since a name for every channel would be fine. Since the
streams aren't necessarily divided up by category or connector in the driver
based on the hardwares need, not naming the streams is probably a good
thing. But each individual channel should be identifiable by the user.
I just found out that I've been looking at an old version of the CoreAudio
headers (cfm-ized even, yuck.) None of the DataSource properties were
listed, and they aren't in any docs, new or old, so I didn't know what I was
missing. They have names associated with them, but are DataSources only for
inputs or for outputs too (DataSinks)? Where do you define that in the
driver? I couldn't find it in the driver docs, sorry if I missed it.
There are names for every IOControl you create, like gains for a channel,
and also for IOStreams (but we don't want those right), but not for
channels, so where are the DataSources and names defined?
thanks,
dug