th type of launch, but …the glitches tend to take
>>> a
>>> few hours/days of running to present themselves (!), so I’ll just try
>>> ditching launchd for a few days & see if the random glitching disappears
>>> (that’s how that attached ’things I’ve tried' matrix ca
Hi Michael,
Your matrix makes me wonder: are you trying to play from a launchd daemon?
Try taking an Instruments trace that captures thread scheduling activity. It
sounds like the daemon is in a throttled state, which would show in a kernel or
Instruments trace as having its threads running at
r threads seem to have the same priorities
> regardless of how the app’s launched though)
>
> Michael
> +447595247282
>
>> On 26 Dec 2015, at 18:34, Doug Wyatt <dwy...@apple.com> wrote:
>>
>> Hi Michael,
>>
>> Your matrix makes me wonder: ar
Possibly the buffer list's mNumberBuffers is inconsistent with the output bus's
format, or its mBuffers' mDataByteSize members are inconsistent with the
supplied frame count.
The rule of thumb for AudioBufferList function parameters is: if the API is
going to store something into the buffer
Hi,
There should be a new seed before very long; can you please check with that and
either write a Radar or email me off-list if the problem persists?
Thanks,
Doug
> On Aug 15, 2016, at 12:09 , Roman wrote:
>
> Hi guys,
>
> I’ve encountered a problem that all of my audio
Yes, this gets into the messy history of how AUParameterListener was bolted on
after the fact ... according to a strict reading of the header comments, maybe
the AU ought to be pushing notifications, but it doesn't, and that's unlikely
to change.
Since the use case for observing that kind of
Hi Charles,
If you could please write a bug report and attach a crash log, we'll look into
it. I have successfully written a small number of markers to a CAF file...
Thanks,
Doug
> On Sep 16, 2016, at 1:17 , Charles Constant wrote:
>
> Judging by the lack of mentions
> On Oct 23, 2016, at 11:48 , John Ruf wrote:
>
> We have been experiencing very rare random delays in the audio buffers in
> core audio. This is occurring in our audio mixer application which runs
> flawlessly on Snow Leopard and Mountain Lion.
> This problem has been noted
You should be able to use AudioUnitGetPropertyInfo instead of
AudioUnitGetProperty with a null pointer when wanting to fetch a property's
size.
We added __nullable to AudioUnitConnection.sourceAudioUnit recently.
One of the design goals of the AUAudioUnit API was to provide a replacement API
On Dec 10, 2016, at 4:17 , Andreas Falkenhahn wrote:
> I think all I'd need to know is this:
>
> Do the render callback as installed by a call to
>
>AudioUnitSetProperty(mixerAudioUnit, kAudioUnitProperty_SetRenderCallback,
> kAudioUnitScope_Input, chan, ,
In the case of anything else built on AUBase, including AUMultiChannelMixer,
it's not a matter of the property being changed asynchronously and waiting for
a notification (I'm reinstalling Xcode at the moment, hard to look at code, but
from memory, setting the render callback might not send a
As of iOS 11 the "inter-app-audio" entitlement is required to able to scan the
plug-ins installed on the system.
> On Oct 14, 2017, at 13:04 , Lucas Goossen wrote:
>
>
> AVAudioUnitComponentManager.shared().components(passingTest: {
> (components, _) -> Bool in
Hi all,
I realize that to our developers, Radar can sometimes seem like an opaque black
hole, but to be honest, this mailing list is worse :-P If someone would like to
please write a Radar, we can look at it. While in the case of things like
crashing bugs, a reproduction case helps a lot, in
I don't think we ever really knew when the deprecation be official. There are
yet a few things we want to add to AVAudioEngine for more feature parity, and
we don't want folks to be seeing warnings until that's done.
I can say that there is now an availability mechanism so that we can mark
> On Jul 13, 2018, at 13:17 , Admiral Quality wrote:
>
> Meanwhile we can still run Windows software written in 1995 on their latest
> OS.
>
> I can't wait to see you people go out of business.
>
> - AQ
Deprecation doesn't mean removal.
Carbon components have been deprecated for many
AUHAL does not support non-PCM formats. There are other higher-level API’s to
accomplish what it sounds like you’re trying to do, e.g. AVAudioRecorder and
AVAudioEngine with an AVAudioFile.
Doug
# sent from my iPhone
> On Feb 28, 2018, at 15:48, Pierre Pasquet wrote:
>
The API food chain is AVAudioFile -> ExtendedAudioFile ->
AudioFile+AudioConverter -> AudioCodec.
So yes, an AudioCodec would be most generally useful and extensible.
> On Apr 8, 2020, at 12:07 , Stephen F. Booth via Coreaudio-api
> wrote:
>
> I'm interested in adding support for additional
17 matches
Mail list logo