• 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: vDSP: performance costs of stride size != 1
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: vDSP: performance costs of stride size != 1


  • Subject: Re: vDSP: performance costs of stride size != 1
  • From: Gregory Wieber <email@hidden>
  • Date: Thu, 16 Feb 2012 16:27:42 -0800

Sounds like it's worth setting up a simple test and profiling...


On Thu, Feb 16, 2012 at 12:11 PM, Morgan Packard <email@hidden> wrote:
Hello list,
I understand it's preferable to keep stride size to 1 when using the vDSP functions of the accelerate framework. Does anyone have any experience (or numbers)  relating to performance and stride size of greater than one? I have a single-channel envelope signal that I'd like to apply to an interleaved stereo signal. If I can get much better performance by using a two-channel envelope signal (this keeping the stride to 1), I'll consider reworking my code.
thanks,
-Morgan

--
===============
Morgan Packard
cell: (720) 891-0122
aim: mpackardatwork


 _______________________________________________
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: 
 >vDSP: performance costs of stride size != 1 (From: Morgan Packard <email@hidden>)

  • Prev by Date: Re: Xcode 4.3 - Core Audio headers missing, or inside app bundle?
  • Next by Date: Receiving My Own MIDI Events
  • Previous by thread: vDSP: performance costs of stride size != 1
  • Next by thread: Re: vDSP: performance costs of stride size != 1
  • Index(es):
    • Date
    • Thread