• 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
'vectors' of AudioUnit Parameters
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

'vectors' of AudioUnit Parameters


  • Subject: 'vectors' of AudioUnit Parameters
  • From: Andrew Kimpton <email@hidden>
  • Date: Thu, 23 Oct 2003 21:18:00 -0700

I did a search through the list archives and saw a few posts from James Coker and responses from Bill Stewart and Chris Rogers at Apple at the beginning of August 2003 that sort of addressed this topic but I don't think a clear solution was proposed or reached.

I have a plugin which processes to and from the frequency domain, the FFT has 512 bands with two control points for each band so I have 1024 'control values' in my algorithm. Internally I store this as two vectors (buffers) of 512 floating point values (0 - 1.0). In order to present this to the user I reduce the values to two vectors each with 12 floating point values and have a process to convert between the 12 <-> 512.

I 'view' the 12 <-> 512 reduction to be 'part' of the UI not part of DSP processing, after all what's 12 today might need to be 24 in the future, and that's more of a UI/presentation problem than a processing problem.

I'd like to be able to 'publish' these two vectors as parameters but it seems that there is no support for such a parameter type right now. I understand I could use the element ID mechanism but that seems a little clumsy for so many data points.

Is there another way ? Or do I have to just resort to placing the 12 <-> 512 logic within the DSP portion and only publish two groups of 12 values (in this case element ID seems fine).

I think properties would do this - but then I guess I'd lose any automation mechanisms and such like ?

Andrew 8-)

P.S. There's also a third 'read only' buffer of power level for each of the 512 bands (again usually reduced to 12)

P.P.S. Just to really 'fire things up' there's also 2 more buffers of 512 attack/release times - however they're commonly set to a single value for all bands, or set to a ramp across the bands (but hey - someday someone might want more flexibility !)
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
  • Prev by Date: Re: AudioDevice AudioChannelLayout
  • Next by Date: Question about setting sampling rate of sound input
  • Previous by thread: Re: MusicEventIteratorHasNextEvent
  • Next by thread: Question about setting sampling rate of sound input
  • Index(es):
    • Date
    • Thread