• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
RE: ExtAudioFileRead -- not reading enough frames
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: ExtAudioFileRead -- not reading enough frames


  • Subject: RE: ExtAudioFileRead -- not reading enough frames
  • From: "Edwards, Waverly" <email@hidden>
  • Date: Fri, 10 Sep 2010 22:10:13 -0500
  • Acceptlanguage: en-US
  • Thread-topic: ExtAudioFileRead -- not reading enough frames

Based on this information, it would have to be an optimization.  The buffer was the same size for the 32-bit version as it was for the 16-bit.
Yet the 32-bit integer version, the full file was read in at once.  I was actually caught by surprise because the full 16-bit file was not fully read.
This would explain why my data calculation were not as I expected because I didnt get all the data.  Since I intended to read the entire file,
I suppose all I can do is to ask for more frames than are present.

I now know that I did it correctly.  I just didnt get the desired result.


Thank you,


W.

________________________________________
From: Doug Wyatt [email@hidden]
Sent: Friday, September 10, 2010 8:37 PM
To: Edwards, Waverly
Cc: 'email@hidden'
Subject: Re: ExtAudioFileRead -- not reading enough frames

ExtendedAudioFile.h:

        @param          ioNumberFrames
                                        On entry, ioNumberFrames is the number of frames to be read from the file.
                                        On exit, it is the number of frames actually read. A number of factors may
                                        cause a fewer number of frames to be read, including the supplied buffers
                                        not being large enough, and internal optimizations. If 0 frames are
                                        returned, however, this indicates that end-of-file was reached.

Either your buffer list was only large enough for 440309 frames, or an optimization resulted in the read being reduced in size.

Doug

On Sep 10, 2010, at 17:33 , Edwards, Waverly wrote:

>
> Sorry, I need to add some clarification.  I only learned this week through another list member's posting that upon completion of
>
> result = ExtAudioFileRead(inExtAudFileRef, &framesToRead, bufList);
>
> framesToRead will have stored the number of frames actually read versus the number of frames requested.
> This is where I am getting a result of 440309 frames read, not 441000 as expected.  I am perplexed as to why
> there were only 440309 frames read.

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >ExtAudioFileRead -- not reading enough frames (From: "Edwards, Waverly" <email@hidden>)
 >RE: ExtAudioFileRead -- not reading enough frames (From: "Edwards, Waverly" <email@hidden>)
 >Re: ExtAudioFileRead -- not reading enough frames (From: Doug Wyatt <email@hidden>)

  • Prev by Date: Re: ExtAudioFileRead -- not reading enough frames
  • Next by Date: Re: Minimum frames per slice?
  • Previous by thread: Re: ExtAudioFileRead -- not reading enough frames
  • Next by thread: kAudioFormatFlagIsFloat sample range
  • Index(es):
    • Date
    • Thread