• 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
AUBase preset handling change
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AUBase preset handling change


  • Subject: AUBase preset handling change
  • From: William Stewart <email@hidden>
  • Date: Fri, 6 May 2005 18:11:27 -0700

In the base classes we provide for implementing an Audio Unit, we currently do a sanity check (AUBase::RestoreState) on the preset an AU is given by checking that:
The Type, SubType and ManuID match the particular AU.


We'd like to propose a slight modification to this test - to avoid checking that the AU type matches, but rather just check that the subtype and manuID match.

We believe this is a good change because identical AU's can be published as different AU types, and it seems rather silly to reject what would otherwise be a totally appropriate and valid preset.

For example, we ship two versions of AUTimePitch in Tiger; an 'aufc' (Format Converter) version (so it can be used in a real-time like context), and an 'auol' (Offline version) - which is of course much better to use in an offline processing situation. In both of these cases, the processing and parameter structure of the AU is identical, so the presets could be shared between these two AU's. The same applies to the AUVarispeed.

In these two cases the constants are:
aufc, vari, appl
auol, vari, appl
aufc, tmpt, appl
auol, tmpt, appl

This would require of course that an AU that shares the same manuID and subtype would be able to parse and read the presets - both of these fields are defined by the manufacturer, so this is totally within the control of the manufacturer to manage.

If there are no objections to this, we'd make this change available in the next SDK we release (sometime after WWDC)

Thanks

Bill

--
mailto:email@hidden
tel: +1 408 974 4056
________________________________________________________________________ __
"Much human ingenuity has gone into finding the ultimate Before.
The current state of knowledge can be summarized thus:
In the beginning, there was nothing, which exploded" - Terry Pratchett
________________________________________________________________________ __


_______________________________________________
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


  • Follow-Ups:
    • Re: AUBase preset handling change
      • From: Urs Heckmann <email@hidden>
  • Prev by Date: writing M4A/AAC, use AudioFileWriteBytes or AudioFileWritePackets?
  • Next by Date: Combining AUHAL input and an AudioConverter
  • Previous by thread: writing M4A/AAC, use AudioFileWriteBytes or AudioFileWritePackets?
  • Next by thread: Re: AUBase preset handling change
  • Index(es):
    • Date
    • Thread