• 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: Coreaudio-api Digest, Vol 12, Issue 4
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Coreaudio-api Digest, Vol 12, Issue 4

  • Subject: Re: Coreaudio-api Digest, Vol 12, Issue 4
  • From: Kevin Dixon <email@hidden>
  • Date: Tue, 06 Jan 2015 16:57:59 -0800
Thanks for the input all. We have users who report the issue with Adobe Audition-encoded files as well. The real problem is that all of the files in question apparently worked while running iOS 7, but now that they have upgraded to iOS 8, the issue presents itself.

The tools at my disposal do not indicate anything wrong with the files.

Is it plausible that AVAssetReader would use a different decoding path than the built in Music app?

Thanks.

Kevin

On Tue, Jan 6, 2015 at 2:10 PM, Paul Davis <email@hidden> wrote:


On Tue, Jan 6, 2015 at 5:02 PM, E Hartley <email@hidden> wrote:

My immediate suggestion is that the Lame encoding is at fault rather than the Apple decoder. There is an understanding in MPEG that decoder compliance is verified against reference bitstreams and that encoders must produce bit streams / files capable of being decoded by the reference software. No attempt is made to specify encoders. The fact that the fault is appearing at the end of the file makes me think that the encoder is not encoding the data or padding correctly for an audio file that is temporarily smaller than an integer number of encoding units. The way to verify this is either to dig into the MP3 file and inspect the structure or decode it against the reference software. Neither of these are entirely trivial.

You're seriously suggesting that the most widely used encoder in the world, one of the highest rated in almost all tests, and one whose source is all available has a problem? It isn't unbelievable but is an extraordinary claim. Compared to a bug that has nothing to do with the encoder or decoder, I'd wager on the latter.
 

 _______________________________________________
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

 _______________________________________________
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: 
 >Re: Coreaudio-api Digest, Vol 12, Issue 4 (From: E Hartley <email@hidden>)
 >Re: Coreaudio-api Digest, Vol 12, Issue 4 (From: Paul Davis <email@hidden>)

  • Prev by Date: Re: Coreaudio-api Digest, Vol 12, Issue 4
  • Next by Date: iOS AVAssetReader "This media may be damaged" issue
  • Previous by thread: Re: Coreaudio-api Digest, Vol 12, Issue 4
  • Next by thread: AVAudioFormat Standard format with Core Audio AudioGraph
  • Index(es):
    • Date
    • Thread