• 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: aupreset values
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: aupreset values


  • Subject: Re: aupreset values
  • From: Sven Thoennissen via Coreaudio-api <email@hidden>
  • Date: Tue, 19 May 2020 15:42:54 +0200

Hi Brad,

A while ago I have wondered the same because it would be nice to control the
volume envelope with MIDI CCs.
I took the same approach like you did, and managed to write a small test
program that maps CC#72 to the VolEnvRelease parameter.

I used Logic Pro X and created a track with the AUSampler instrument (AU
Instruments -> Apple -> AUSampler). In the sampler I created a connection and
saved the preset, I guess this is what you did in AULab.

It still seems to work with iOS 13.
Though it seems kind of a hack to read, modify, and write back to the AU
fullState.

If you are interested I can send you the project. It’s a 4.9 MB zip file.

Best,
Sven

> Am 18.05.2020 um 10:31 schrieb Brad Howes via Coreaudio-api
> <email@hidden>:
>
> Hi,
>
> I’m wondering if there is any documentation for the values one finds in an
> ‘aupreset’ file? In particular the constants for ‘control’, ‘destination’,
> 'scale’, ‘source’, and ‘transform’ values in a ‘Connections’ array. I suspect
> these are all just internal values to the audio units being used. I am using
> the modern AVAudioSampler in an iOS app and I would like to offer controls
> for the shape of the envelope that is used by the instrument when it
> generates output. I know from experiments with AU Lab what destination values
> to use (I think):
>
> attack time - 570425244
> hold time - 571473920
> decay time - 572522496
> release time - 573571072
> sustain level - 574619649
>
> In AULab there are also some ‘* Factor’ destinations for the above times, but
> I am not clear how these affect the final envelope.
>
> As mentioned, my ultimate goal is to allow the user to adjust the filter
> shape with performance parameter changes, just like in AU Lab, by performing
> the following steps:
>
> Load a soundtont file
> Fetch the preset definition from AVAudioSampler via
> kAudioUnitProperty_ClassInfo property
> Modify preset with the proper parameter definitions and connections as
> gleaned from AU Lab presets
> Update the AUAudioSampler with the changed preset definition
>
> Does this seem reasonable? Thanks in advance for any doc / reference links
> you can provide.
>
> Regards,
>
> Brad
>
> _______________________________________________
> 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: 
 >aupreset values (From: Brad Howes via Coreaudio-api <email@hidden>)

  • Prev by Date: Volume control of CoreAudio USB device
  • Next by Date: iOS 13 is not bit-accurate; previous versions were
  • Previous by thread: aupreset values
  • Next by thread: Volume control of CoreAudio USB device
  • Index(es):
    • Date
    • Thread