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 13:31:02 +0200
Nikolaus Gerteis:
There is already a data member. It contains the preset data of the
plugin. Nothing else for the data I get from the ClassInfo property.
It exactly the same, isn't it? If you have a Audio Unit ported VST
plugin and put your data into the vstdata key, what remains for the
data key to contain? Or do you say you use it instead of the data key,
to identify the data as a VST chunk. Then I would prefer to write the
chunk data to the data key and add a thrid key like 'vst' or
'vstsetting' to identify the setting as a VST compatible one. Then a
host, that does not care about the VST-Audio Unit compatibility issue
can handle all presets in the same way.
However it is done,
I would not like to be forced to have identical data sections for VST
and AU. I think that data handling (or everything?) in AUs is more
comfortable than in VST and I (being a geeky non-conforming developer)
could easily imagine having different codebases for AU and VST versions
if I feel that I would like to add extra functionality to the AU
version. (I will have different chunk formats in VST mac/win, serving
different platforms indeed rises limitations)
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.