ExtAudioFile has been great for me.  I would be surprised if AVAudioFile
wasn't build on top of it.  Have you tried setting
kExtAudioFileProperty_IOBufferSizeBytes
to a higher value yet?

Dave

On Wed, Feb 14, 2018 at 2:02 PM, Arshia Cont <arshiac...@antescofo.com>
wrote:

> Huh.. Just needed some one else to say it.. back to basics.. :)
>
> Thanks Matt for taking time to reply.
>
> Sent from my iPhone
>
> > On 14 Feb 2018, at 21:31, Matt Ingalls <m...@8dio.com> wrote:
> >
> > OK I see what you are doing now.
> >
> > Sounds like increasing kExtAudioFileProperty_IOBufferSizeBytes could
> prevent an overflow.
> > but maybe doing your own async writes would be safer :).  ExtAudioFile
> is a pretty old API..
> >
> > -m
> >
> >> On Feb 14, 2018, at 11:24 AM, Arshia Cont <arshiac...@antescofo.com>
> wrote:
> >>
> >> Matt,
> >>
> >> Thanks for the reply! :)
> >>
> >> AVAudioFile would be one way to go except that I am recording live
> streams, and using AVAudioFile I should make the ‘write’ asynchronous
> myself and make sure the direct-to-disk stuff won’t hic the AudioIO thread.
> >>
> >> This is supposed to be the promise of ‘ExtAudioFileWriteAsync’.
> >>
> >> Has anyone tried playing around with the 
> >> kExtAudioFileProperty_IOBufferSizeBytes
> property of Extended Audio File Services? I have feeling that this is the
> way to go (increasing the buffer so that writing would occur less
> frequently.
> >>
> >> Apparently the kExtAudioFileError_AsyncWriteBufferOverflow is thrown
> when write requests are arriving faster than the system’s ability to access
> disk (can happen at any time and all of a sudden). The bad news is that
> when this is thrown it actually halts the IOThread! Can’t figure out why… .
> >>
> >> Hint that can help: I am recording two live streams (stereo) at the
> same time (i.e. two audio files).
> >>
> >> Any hints?
> >>
> >>> On 14 Feb 2018, at 19:01, Matt Ingalls <m...@8dio.com> wrote:
> >>>
> >>> Have you tried AVAudioFile?
> >>>
> >>>> On Feb 13, 2018, at 12:59 PM, Arshia Cont <arshiac...@antescofo.com>
> wrote:
> >>>>
> >>>> Hello list,
> >>>>
> >>>> This is my first post here so sorry if this is already asked!
> >>>>
> >>>> We have been using ExtAudioFileWriteAsync on iOS successfully to
> write two PCM Audio Streams to disk. We have been getting reports from
> users nagging on sudden audio drop outs on some [older] devices and during
> “performance”. We managed finally to find the root of the problem to the
> thrown kExtAudioFileError_AsyncWriteBufferOverflow exception which means
> (probably?) that ExtAudioFileWriteAsync is not keeping the pace with the
> system writing to disk.
> >>>>
> >>>> So I believe we must use lower level calls here (?).
> >>>>
> >>>> What would be an alternative for ExtAudioFileWriteAsync?
> >>>
> >>>>
> >>>> I have been looking at Audio Queue Services for months but
> documentation/examples are so old that it keeps me away from it… or should
> we dive in?
> >>>>
> >>>> Thanks in advance,
> >>>>
> >>>>
> >>>> Arshia Cont
> >>>> _______________________________________________
> >>>> Do not post admin requests to the list. They will be ignored.
> >>>> Coreaudio-api mailing list      (Coreaudio-api@lists.apple.com)
> >>>> Help/Unsubscribe/Update your Subscription:
> >>>> https://lists.apple.com/mailman/options/coreaudio-api/matt%408dio.com
> >>>>
> >>>> This email sent to m...@8dio.com
> >>>
> >>
> >
>  _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Coreaudio-api mailing list      (Coreaudio-api@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/coreaudio-api/
> oneill707%40gmail.com
>
> This email sent to oneill...@gmail.com
>
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (Coreaudio-api@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to