> 1) provide an encoding enum along with format enum. This is limited to only > a single encoding at a time, and I suppose it might be nicer to have a set > of properties that could be defined. Just something simple is best a config file witha list of formats and metadata. The encodings can be treated the same way as any other format, since they are truly mutually exclusive. It's not Stereo AND LtRt. It's LtRt. XML may be good for this file, though forcing hosts to parse XML might piss people off. Myself included. A simple format is simple enough. I'll even volunteer to write a lex/yacc parser. > Encoding enums, properties, whatever should be optional and can be ignored. How can they be ignored? All plugins will be forced to identify the formats they can accept. The host will HAVE to understand the encodings. Tim ---------------------------------------------------------------------- Generalized Music Plugin Interface (GMPI) public discussion list Participation in this list is contingent upon your abiding by the following rules: Please stay on topic. You are responsible for your own words. Please respect your fellow subscribers. Please do not redistribute anyone else's words without their permission. Archive: //www.freelists.org/archives/gmpi Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe