Hi All,

I was working on some blue code to parse audio driver output for
Coreaudio to figure out what cards were available.  It took a while to
figure out as I had to look at source code and it looks like one has
to use -m1024 to list cards for Coreaudio.  I also saw that 0x400
(1024) is used in a number of the other drivers to show optional
messages.  I hadn't seen this flag before and don't see it in the 5.12
documentation online, could someone explain where it came from and
purpose so it can get documented?  Also would be useful for others to
know so that they can use it in code correctly.

Thanks!
steven

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Does anyone know anything about this flag?

On Sun, Mar 14, 2010 at 6:17 PM, Steven Yi  wrote:
> Hi All,
>
> I was working on some blue code to parse audio driver output for
> Coreaudio to figure out what cards were available.  It took a while to
> figure out as I had to look at source code and it looks like one has
> to use -m1024 to list cards for Coreaudio.  I also saw that 0x400
> (1024) is used in a number of the other drivers to show optional
> messages.  I hadn't seen this flag before and don't see it in the 5.12
> documentation online, could someone explain where it came from and
> purpose so it can get documented?  Also would be useful for others to
> know so that they can use it in code correctly.
>
> Thanks!
> steven
>

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

> Does anyone know anything about this flag?
>

Introduced in October 2007 as part of the OLPC project; tagged as "quieten"
in the CVS.  I think it was my editing at the request of Barry.  Sorry if
it did not get documented -- had totrally forgotten.  Also in sfont.c as
well as the rt* code

==John ff

> On Sun, Mar 14, 2010 at 6:17 PM, Steven Yi  wrote:
>> Hi All,
>>
>> I was working on some blue code to parse audio driver output for
>> Coreaudio to figure out what cards were available.  It took a while to
>> figure out as I had to look at source code and it looks like one has
>> to use -m1024 to list cards for Coreaudio.  I also saw that 0x400
>> (1024) is used in a number of the other drivers to show optional
>> messages.  I hadn't seen this flag before and don't see it in the 5.12
>> documentation online, could someone explain where it came from and
>> purpose so it can get documented?  Also would be useful for others to
>> know so that they can use it in code correctly.
>>
>> Thanks!
>> steven
>>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>



------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks for the info!  Should we use 0x400 then as a means for
diagnostic information?  I see it used for CoreAudio to enable listing
the available devices which is different from other drivers, so it
seems like it should be one way or the other.

Thanks!
steven

On Wed, Mar 17, 2010 at 2:10 AM,   wrote:
>> Does anyone know anything about this flag?
>>
>
> Introduced in October 2007 as part of the OLPC project; tagged as "quieten"
> in the CVS.  I think it was my editing at the request of Barry.  Sorry if
> it did not get documented -- had totrally forgotten.  Also in sfont.c as
> well as the rt* code
>
> ==John ff
>
>> On Sun, Mar 14, 2010 at 6:17 PM, Steven Yi  wrote:
>>> Hi All,
>>>
>>> I was working on some blue code to parse audio driver output for
>>> Coreaudio to figure out what cards were available.  It took a while to
>>> figure out as I had to look at source code and it looks like one has
>>> to use -m1024 to list cards for Coreaudio.  I also saw that 0x400
>>> (1024) is used in a number of the other drivers to show optional
>>> messages.  I hadn't seen this flag before and don't see it in the 5.12
>>> documentation online, could someone explain where it came from and
>>> purpose so it can get documented?  Also would be useful for others to
>>> know so that they can use it in code correctly.
>>>
>>> Thanks!
>>> steven
>>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>>
>
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net