Re: Filing of User Presets
Re: Filing of User Presets
- Subject: Re: Filing of User Presets
- From: Urs Heckmann <email@hidden>
- Date: Fri, 25 Oct 2002 02:23:20 +0200
Bill Stewart:
>
Would you need separate keys in the AU class info for both of these, or
>
would they just generally fit into the 'vstdata' segment
Marc Poirer:
>
So yes, "vstdata" would be sufficient.
I think there is no need to deal with compatibility when the
preset/sound/bank of a foreign format has already made its way into the
AudioUnit's data array. After the vstdata chunk got parsed by the AU,
the host can save/restore state as usual. (One way tickets can be means
of catharsis?)
AU parameters feature those individual, different ranges which is quite
convenient. Other formats usually have parameters going from 0.0f to
1.0f. Hence a little conversion has to be made by the AU, not the host
or any dataimporter class.
However, not all AUs will have foreign sisters. I think there should be
a simple mechanism for an AudioUnit to tell the host what it likes to
get fed in addition to classInfo. There are not too many formats to
serve (mainly VST, MAS), so it would be easy to specify a general way
(that wouldn't even confuse Robert too much to add to his host :-)
Usual apps in earlier times could specify creator/type identifiers to
search for document files (which is now managed by the suffixes?).
Having a set of flags and a loading mechanism would certainly be way to
go.
(I remember I could open JPEGs even if I specified only PICT and
QuickTime did the rest for me without need to add any code to my app,
you see we're talking Apple tradition)
Cheers,
;) Urs
_______________________________________________
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.