On Wed, Jan 15, 2003 at 10:23:37PM +, Steve Harris wrote:
> That sounds useful, but its a seperate issue. I cant think of a way of
> generalising it... maybe OPTIONAL? i.e. this plugin will still do
> something useful if this port isn't connected.
I just might be a bit late giving my 2cents to
On Tue, Jan 21, 2003 at 11:02:08 -0800, robbins jacob wrote:
> However, it seems that plugin writers are more comfortable interpreting
> port type=audio to mean that the rate of the port is audio rate. Steve
> suggests that it is splitting hairs to try to absolutely determine whether
> an audio-
To my own surprise I have to object to the suggestion: /*
AUDIO_RATE_CONTROL. Hints than an audio control should/could be controlled
by a high time res. slider or control data, but shouldn't be connected to
the next audio signal by default. I can't think of any simple examples off
hand, but c
On Sun, Jan 19, 2003 at 06:44:36PM +, Steve Harris wrote:
> My main concern abou htis hint is that it artificially introduces a
> distinction that isn't really there. Its fine as long as no modular host
> ever prevents me form wiring an audio output to hinted continuous control
> input or vice-
On Fri, Jan 17, 2003 at 10:28:44 -0800, robbins jacob wrote:
> To my own surprise I have to object to the suggestion:
> /*
> AUDIO_RATE_CONTROL. Hints than an audio control should/could be controlled
> by a high time res. slider or control data, but shouldn't be connected to
> the next audio sign
On Fri, 17 Jan 2003 10:28:44 -0800
"robbins jacob" <[EMAIL PROTECTED]> wrote:
> To my own surprise I have to object to the suggestion:
> /*
> AUDIO_RATE_CONTROL. Hints than an audio control should/could be
> controlled by a high time res. slider or control data, but shouldn't
> be connected to the
To my own surprise I have to object to the suggestion:
/*
AUDIO_RATE_CONTROL. Hints than an audio control should/could be controlled
by a high time res. slider or control data, but shouldn't be connected to
the next audio signal by default. I can't think of any simple examples off
hand, but comb
--- Jack O'Quin <[EMAIL PROTECTED]> wrote: > Steve Harris
<[EMAIL PROTECTED]> writes:
>
> > > On Wed, 15 Jan 2003 18:13:35 +
> > > Steve Harris <[EMAIL PROTECTED]> wrote:
> > >
> > > > AUDIO_RATE_CONTROL. Hints than an audio control should/could be
> controlled
> > > > by a high time res. sl
On Thu, Jan 16, 2003 at 10:19:38AM -0600, Jack O'Quin wrote:
> There's a syntactic ambiguity in the name AUDIO_RATE_CONTROL. Steve
> uses it to describe a Controller which runs at Audio Rate (i.e. sample
> clock speed). But, Janne understood it to mean a Controller *of* the
> Audio Rate, which is
On Thu, 16 Jan 2003 16:35:37 +
Steve Harris <[EMAIL PROTECTED]> wrote:
> On Thu, Jan 16, 2003 at 05:31:56PM +0200, janne halttunen wrote:
> > > No, I dont think so. An audio rate control is just one that has a value
> > > per sample, instead of a value per block. Its usful for things like FM
>
On Thu, 16 Jan 2003 10:58:40 -0500
Paul Davis <[EMAIL PROTECTED]> wrote:
> >On Wed, 15 Jan 2003 18:13:35 +
> >Steve Harris <[EMAIL PROTECTED]> wrote:
> >
> >> AUDIO_RATE_CONTROL. Hints than an audio control should/could be controlled
> >> by a high time res. slider or control data, but shouldn
On Thu, Jan 16, 2003 at 05:31:56PM +0200, janne halttunen wrote:
> > No, I dont think so. An audio rate control is just one that has a value
> > per sample, instead of a value per block. Its usful for things like FM
> > frequency which can be changed very quickly. Hey, I just thought of a use
> > f
Steve Harris <[EMAIL PROTECTED]> writes:
> > On Wed, 15 Jan 2003 18:13:35 +
> > Steve Harris <[EMAIL PROTECTED]> wrote:
> >
> > > AUDIO_RATE_CONTROL. Hints than an audio control should/could be controlled
> > > by a high time res. slider or control data, but shouldn't be connected to
> > > th
>On Wed, 15 Jan 2003 18:13:35 +
>Steve Harris <[EMAIL PROTECTED]> wrote:
>
>> AUDIO_RATE_CONTROL. Hints than an audio control should/could be controlled
>> by a high time res. slider or control data, but shouldn't be connected to
>> the next audio signal by default. I can't think of any simple
On Thu, 16 Jan 2003 13:58:58 +
Steve Harris <[EMAIL PROTECTED]> wrote:
> On Thu, Jan 16, 2003 at 02:38:53PM +0200, janne halttunen wrote:
> > On Wed, 15 Jan 2003 18:13:35 +
> > Steve Harris <[EMAIL PROTECTED]> wrote:
> >
> > > AUDIO_RATE_CONTROL. Hints than an audio control should/could b
On Thu, Jan 16, 2003 at 02:38:53PM +0200, janne halttunen wrote:
> On Wed, 15 Jan 2003 18:13:35 +
> Steve Harris <[EMAIL PROTECTED]> wrote:
>
> > AUDIO_RATE_CONTROL. Hints than an audio control should/could be controlled
> > by a high time res. slider or control data, but shouldn't be connecte
On Wed, 15 Jan 2003 18:13:35 +
Steve Harris <[EMAIL PROTECTED]> wrote:
> AUDIO_RATE_CONTROL. Hints than an audio control should/could be controlled
> by a high time res. slider or control data, but shouldn't be connected to
> the next audio signal by default. I can't think of any simple exampl
On Wed, Jan 15, 2003 at 07:48:48 +0100, David Olofson wrote:
> > AUDIO_RATE_CONTROL. Hints than an audio control should/could be
> > controlled by a high time res. slider or control data, but
> > shouldn't be connected to the next audio signal by default. I can't
> > think of any simple examples of
On Wednesday 15 January 2003 19.13, Steve Harris wrote:
> There have been a few suggestions recently, I'l try to summarise
> them for comment.
>
> MOMENTARY. A hint to suggest that a control should behave like a
> momentary switch, eg. on for as long as the user holds down the
> key/mouse button/wh
There have been a few suggestions recently, I'l try to summarise them for
comment.
MOMENTARY. A hint to suggest that a control should behave like a momentary
switch, eg. on for as long as the user holds down the key/mouse
button/whatever. Useful for reset or sync controls for example. Would be
use
20 matches
Mail list logo
