• 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: Private *properties* for AUs? (not parameters)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Private *properties* for AUs? (not parameters)


  • Subject: Re: Private *properties* for AUs? (not parameters)
  • From: Airy André <email@hidden>
  • Date: Sun, 30 Nov 2003 10:20:41 +0100

Of course you can add your properties.
From the AudioUnitProperties.h header :
// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~
// Properties
// Apple reserves property values from 0 -> 63999
// Developers are free to use property IDs above this range at their own discretion

Airy

Le 30 nov. 03, ` 09:39, Michael Ashton a icrit :

I've looked for earlier posts on this, but I think it's a little weird anyway, so I'll risk the ire of the list for asking dumb questions ... :)

I'd like to write an AudioUnit that functions as the recording half of a sampler. It will start sampling when the audio goes above a threshold, and stop when it goes below another threshold. The samples thus collected could be saved to disk as small AIFFs (or whatever).

My main intent is to use it to sample drum sounds that have been processed through an effects chain. By making it an AudioUnit, I can presumably use the increasingly cool effects that come with Logic, and most importantly I can save myself the trouble of writing an entire host - among other advantages.

The problem is that this AudioUnit would have some unusual parameters. One of the UI elements I'd like to provide is a list-box displaying the names/paths of collected samples, maybe with statistics like length, size etc. Needless to say, this information doesn't seem quite right for funnelling through floats!

Properties seem like the right mechanism for this sort of thing, but I can't figure out whether I'm allowed to invent my own properties. The docs I've read so far seem silent on this point. Can I make my own properties, or should I use some other mechanism to communicate with the UI? Suggestions (obviously) welcome ...

Thanks in advance
----
Michael Ashton <email@hidden>
"I'm really lucky that Microsoft set the bar so low for my profession ..."
--- My brother-in-law, a (very good) professional programmer
_______________________________________________
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.
_______________________________________________
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.

References: 
 >Private *properties* for AUs? (not parameters) (From: Michael Ashton <email@hidden>)

  • Prev by Date: Private *properties* for AUs? (not parameters)
  • Next by Date: Re: Private *properties* for AUs? (not parameters)
  • Previous by thread: Private *properties* for AUs? (not parameters)
  • Next by thread: Re: Private *properties* for AUs? (not parameters)
  • Index(es):
    • Date
    • Thread