[gmpi] Re: entity naming

On Wednesday, November 30, 2005 2:34 AM [GMT+1=CET],
Michael Gogins <xxxgogins@xxxxxxxxxxxxxxx> wrote:

> How about, "audio input", "audio output," "control input", and "control
> output?"
>
> When people say "What do we call 'x'?", they are already calling 'x', 'x'.

I think you're right.

The places where data enters or leaves the plugin:
- audio inputs
- audio outputs
- control inputs
- control outputs

Without specifying a particular direction:
- audio IOs
- control IOs

Without specifying the type:
- inputs
- outputs

And even more generally, not specifying type nor direction:
IOs

The data that passes through control IOs = event buffers.
The data that passes through audio IOs = audio buffers.

One element from an event buffer = event.
One element from an audio buffer = sample frame.

Events in an event buffer are timestamped.
Sample frames in an audio buffer are not timestamped, but the audio buffer
has an associated sample rate and a timestamp for the first sample frame.

Something like that?

Koen


> The other choices offered are no shorter, and in my opinion not quite as
> clear either. We'd ahve to say not just "parameter", but "input
> parameter," and not just "pin," but "output pin".
>
> Regards,
> Mike
>
> ----- Original Message -----
> From: <thockin@xxxxxxxxxx>
> To: "GMPI list" <gmpi@xxxxxxxxxxxxx>
> Sent: Tuesday, November 29, 2005 7:39 PM
> Subject: [gmpi] entity naming
>
>
>> I hate these decisions.  We've talked a bit recently about parameters vs
>> control ports.  Pins vs ports vs IOs vs controls.
>>
>> Let's decide a name and stick with it.
>>
>> What do we call an audio input/output?
>> What do we call a control input/output?
>> Can the two use fundamentally the same naming?
>>
>> I've heard used:
>> Audio pins and control pins
>> Audio ports and control ports
>> Audio jacks and control jacks
>> Audio ports and parameters
>> Audio ports and controls
>> Ports and parameters
>> IOs and controls
>> Connections and controls
>>
>> Which of these makes the most sense?  Let's choose and stick with it.
>>
>> 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: http://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: http://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: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: