Re: Error Definitions
Re: Error Definitions
- Subject: Re: Error Definitions
- From: "K. Ware" <email@hidden>
- Date: Mon, 10 Nov 2003 23:09:34 -0500
Ooh - I know, I know, I know ...
kAudioUnitErr_InvalidFile
kAudioUnitErr_FileNotSpecified
kAudioUnitErr_Unauthorized
Actually on the last one, I have vague memories of a message stating
that this error was intended to indicate a copy protection failure in
Initialize(), but I'm having trouble finding anything to corroborate
this.
See below for the ref you're probably looking for regarding Not
Authorized Errors/kAudioUnitErr_Unauthorized. The others, I don't know.
-k
From: Bill Stewart <email@hidden>
Date: Wed Aug 13, 2003 7:00:05 PM US/Eastern
To: Chris Reed <email@hidden>
Cc: email@hidden, Urs Heckmann <email@hidden>, Marc
Poirier <email@hidden>
Subject: Re: Not authorised errors
OK
So, we've added this error code to AUComponent.h:
kAudioUnitErr_Unauthorized = -10847
Please discontinue the usage of -1 for this report, and replace it with
this result code (as this is what host apps will use to check against)
Bill
On Saturday, August 9, 2003, at 07:11 PM, Chris Reed wrote:
I had originally disabled saving in Ritmo, but I've turned it back on
now (in the 1.0.3 release) for several reasons.
Most importantly, if a potential customer is working on a song with
your demo plug-in it's a major pain to them to not be able to save the
song, purchase your plug-in, and re-open the song to continue where
they left off. I realise that it's common to disable saving for demo
modes, but I think audio plug-ins are a special case where it really
works against you (and the user).
Also, the host may save its own list of parameter values along with
the class info dictionary (Logic does this). Unless you have
additional data held in the class info, your plug-in state will be
restored anyway. And if you do have extra data, state will only
partially be restored--just the exported parameter values. This makes
it look a lot more like a bug (incomplete saving) than a disabled
feature.
Btw, Ritmo wasn't returning an error but it was returning an empty
dictionary. No hosts complained about this until DP.
Anyway, I think the Unauthorised error is a great idea. And I don't
think it is too much to ask to have developers update their code to
return the new error instead of -1.
-chris
_______________________________________________
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.