[gmpi] Re: Reqs draft
- From: "Michael Gogins" <gogins@xxxxxxxxxxxx>
- To: <gmpi@xxxxxxxxxxxxx>
- Date: Sat, 8 Nov 2003 09:28:30 -0500
I think a central registry is not required. I think a layered specification
is not required. Both ideas are against the more important idea of a simple
specification, and both will lead to future problems as operating systems
and host software change.
Instead of a central registry, hosts should scan a specific plugin directory
or directories (which CAN be in the registry/environment variable/default
location) and look for plugin registration functions.
Instead of a layered specification, the specification should mandate basic,
no-op, or simple implementations of all high-level functions. E.e.
multi-channel is the spec; mono plugs just copy the signal to every
requested channel; stereo plugs just follow some basic panning law.
============================================
Michael Gogins
gogins at pipeline period com
Irreducible Productions
Silence, a language for programming music and sound
Available at http://sourceforge.net/projects/silencevst/
============================================
----- Original Message -----
From: "Vincent Burel" <vincent.burel@xxxxxxxxxx>
To: <gmpi@xxxxxxxxxxxxx>
Sent: Saturday, November 08, 2003 6:52 AM
Subject: [gmpi] Re: Reqs draft
>
> ----- Original Message -----
> From: "Tim Hockin" <thockin@xxxxxxxxxx>
> To: "GMPI list" <gmpi@xxxxxxxxxxxxx>
> Sent: Friday, November 07, 2003 9:40 PM
> Subject: [gmpi] Reqs draft
>
>
> > Plugin Discovery
> > ---------------
> > * How are plugins discovered on the system?
> > - registration required in a central DB?
> > - a directory that must be scanned?
>
> somethink like the Windows Registry should list all the Plug-in registered
> (With CLSID concept and with the complete pathname of the related DLL).
>
> And also with further extra information for display purpose (for the user)
> or also for the host plug-in management :
>
> Misc Info
> -----------
> szName,
> szComapny
> szCopyright
> szVersion
>
> Supported Limit parameters :
> ---------------------------------------
> nbPinMin
> nbPinMax
> SampleRateMin
> SampleRateMax
>
> Feature Option....
> -------------------
> long HasGUI; //-1 not supplied, 0 = no GUI, 1= Has a GUI.
> long VS3Automation; //-1 not supplied, 0 = no vs3 automation , 1= vs3
> automation.
> long MultiGUI; //-1 not supplied, 0 = no , 1= support multi instance
of
> GUI.
> long MIDIsupport; //-1 not supplied, 0 = no MIDI, 1= MIDI support.
> etc...
>
> And category of the plug-in
> -------------
> #define PINFO_CAT_GENERAL 0 //generic
> #define PINFO_CAT_PEQ 1 //parametric EQ
> #define PINFO_CAT_GEQ 2 //Graphic EQ
> #define PINFO_CAT_COMP 3 //Compressor
> #define PINFO_CAT_EXPGAT 4 //Expander / Gate
> #define PINFO_CAT_LIM 5 //Limiter
> #define PINFO_CAT_MEA 6 //Measure plug
> #define PINFO_CAT_REV 7 //reverb
> #define PINFO_CAT_DELAY 8 //Delay
> #define PINFO_CAT_MOD 9 //Modulation (chorus , flanger, etc...)
> #define PINFO_CAT_HARMONIC 10 //Harmonic (distorsion, exciter etc...)
> #define PINFO_CAT_POSITION 11 //Position (pan, autopan, stereo expander,
> doppler etc...)
> #define PINFO_CAT_PSYCHO 12 //Psycho acoustic (surround effects, phase
> decorrelator etc...)
> #define PINFO_CAT_SCIENCE 13 //Scientific Filter (Filters used for
> technical purpose)
> #define PINFO_CAT_CODE 14 //Coding / Encoding filters...
> #define PINFO_CAT_PITCH 15 //Pitching
>
> #define PINFO_CAT_SIM 16 //Simulator / Emulator
> #define PINFO_CAT_STRETCH 17 //Time Stretching
> #define PINFO_CAT_CONVERT 18 //format Conversion
> #define PINFO_CAT_ROUT 19 //Rooting
> #define PINFO_CAT_TAPE 20 //Tape
> #define PINFO_CAT_SAMPLER 21 //Sampler
> #define PINFO_CAT_SYNTH 22 //Syntheciser
> #define PINFO_CAT_RYTHM 23 //R-Box
> #define PINFO_CAT_SEQ 24 //Sequencer
> #define PINFO_CAT_REMOTE 25 //Remote Controler
> #define PINFO_CAT_MISC 26 //Misc
>
>
>
> Regards
> Vincent Burel
>
>
> ----------------------------------------------------------------------
> 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
>
----------------------------------------------------------------------
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
Other related posts:
