Re: auval and version
Re: auval and version
- Subject: Re: auval and version
- From: William Stewart <email@hidden>
- Date: Fri, 3 Apr 2009 19:07:50 -0700
There's two cases:
(1) The version number that you include when you build your AU's
resource
(2) The version number that is returned from ComponentBase::Version
The component mgr (which is what the AU is based on) for some reason
has two methods to get the version, so you have to support both.
We normally do this by defining a #define constant in a header
somewhere, and just use that in both cases
Bill
On Apr 2, 2009, at 11:32 PM, ezra buchla wrote:
hi, i have a very silly question, apologies in advance.
auval is failing my audio unit because of a version mismatch:
--------------------------------------------------
VALIDATING AUDIO UNIT: 'aufx' - 'noiz' - 'CATF'
--------------------------------------------------
Manufacturer String: catfact
AudioUnit name: sandbox
Component Info: sandbox
Component Version: 0.0.0 (0x0)
* * PASS
--------------------------------------------------
TESTING OPEN TIMES:
COLD:
Time to open AudioUnit: 20.177ms
WARM:
Time to open AudioUnit: 0.863ms
ERROR: Component Version mismatch: Res Vers = 0x0, Comp Vers = 0x1
i've read the extant advice on this topic but i cannot for the life
of me get that 0x1 to change. is auval caching it somewhere?
(besides the system cache, which i tried cleaning...)
in other respects, using the AU framework has been a breeze and
quite fun. what a humiliating place to get stuck! haha.
thanks much.
-eb
_______________________________________________
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