From: gqrxzy8974@ftml.net
To: sox-devel@lists.sourceforge.net
Subject: Re: sox src/coreaudio device name truncation fix
Date: Wed, 15 Jun 2016 07:09:31 -0700 [thread overview]
Message-ID: <1465999771.747479.638486129.3DC41500@webmail.messagingengine.com> (raw)
In-Reply-To: <20160615072252.GA13636@dcvr.yhbt.net>
> Seems reasonable. Can you test this?
> (or provide at least provide a documentation reference).
The AudioDeviceGetProperty function is documented in the
CoreAudio header file AudioHardwareDeprecated.h and it is
very clear that property_size needs to be the size of the
receiving area on the call and gets set to the length of the
data returned by the call.
@function AudioDeviceGetProperty
@abstract Queries an the AudioDevice object to get the data of
the given property and
places it in the provided buffer.
@discussion Note that the same functionality is provided by the
function
AudioObjectGetPropertyData().
@param inDevice
The AudioDevice to query.
@param inChannel
The channel of the property to query where 0 is
the master channel.
@param isInput
Which section of the AudioDevice to query.
@param inPropertyID
The AudioDevicePropertyID of the property to
query.
@param ioPropertyDataSize
A UInt32 which on entry indicates the size of
the buffer pointed to by
outData and on exit indicates how much of the
buffer was used.
@param outPropertyData
The buffer into which the object will put the
data for the given property.
@result An OSStatus indicating success or failure.
*/
extern OSStatus
AudioDeviceGetProperty( AudioDeviceID inDevice,
UInt32 inChannel,
Boolean isInput,
AudioDevicePropertyID inPropertyID,
UInt32* ioPropertyDataSize,
void* outPropertyData)
PS: Changing from using the deprecated CoreAudio interfaces would be a
larger change...
--
http://www.fastmail.com - Same, same, but different...
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
next prev parent reply other threads:[~2016-06-15 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 18:36 sox src/coreaudio device name truncation fix gqrxzy8974
2016-06-15 7:22 ` Eric Wong
2016-06-15 14:09 ` gqrxzy8974 [this message]
2016-06-16 2:50 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1465999771.747479.638486129.3DC41500@webmail.messagingengine.com \
--to=sox-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).