On mån, 2004-03-08 at 10:00, Steve Harris wrote:
> In LADSPA the host handles MIDI mapping.
Would it be OK if my plugin listened to a named pipe instead of the
default /dev/midi? If so, then a sequencer could write a midistream to
the pipe just like any other midi device, and the problem ceases t
On Wed, Mar 10, 2004 at 12:36:54 +0100, Jan Weil wrote:
> On Tue, 2004-03-09 at 21:52, Fons Adriaensen wrote:
> > /* This hint must be used only together with LADSPA_HINT_INTEGER.
>
> [snip explanation on multiway switches]
>
> > #define LADSPA_HINT_SWITCHED0x400
>
> Since this is a spe
[Jens M Andreasen]
>Tim, for several days you have been posting in lower case. Some of us
>believe you need a few hours of sleep, no?
thanks, i'm moved by your concern. to tell the truth, the shift keys
on this keyboard are broken. :)
vänligt,
tim
On Tue, 2004-03-09 at 21:52, Fons Adriaensen wrote:
> /* This hint must be used only together with LADSPA_HINT_INTEGER.
[snip explanation on multiway switches]
> #define LADSPA_HINT_SWITCHED0x400
Since this is a special hint which implies LADSPA_HINT_INTEGER,
shouldn't this be made clea
Tim, for several days you have been posting in lower case. Some of us
believe you need a few hours of sleep, no?
> amicalement,
>
> tim
hmmm, sure ...
/jens
On Tue, Mar 09, 2004 at 11:45:21 +0100, Fons Adriaensen wrote:
> More generally, once a 'version' bit is introduced, you can in fact
> change whatever you want, and go much beyond what you proposed. In that
> case all open questions should be reviewed and a structured and unified
> solution should
On Tue, Mar 09, 2004 at 09:52:58 +0100, Fons Adriaensen wrote:
> /* This hint must be used only together with LADSPA_HINT_INTEGER.
>It indicates that the port corresponds to a multiway switch selecting
>between options that have no natural numerical value. A port using this
>option wou
On Tue, Mar 09, 2004 at 09:05:16PM +0100, Tim Goetze wrote:
> if you don't even see compactness as a virtue, there's only elegance
> remaining to recommend your proposal. elegance at the cost of
> increased complexity in understanding and implementation, no matter
> how you look at it.
It *is* co
Hello list,
After much debate, I propose to extend the current LADPSA 1.1 interface
specification in the way documented below. Two new LADSPA_HINT bits are
introduced. Both can be ignored by existing hosts without any ill
consequences.
The purpose of the first new bit is to allow simple hosts tha
[Fons Adriaensen]
>> without making an absolute estimate of the complexity of your snippet,
>> and presuming it will compile and work flawlessly, i think it is safe
>> to say it is more complex than the PortInfo proposal.
>
>But still trivially simple. If someone writing a host falls over this,
>he
On Tue, Mar 09, 2004 at 06:49:46PM +0100, Tim Goetze wrote:
> thanks for providing the code. i'll not argue it is not complete
> seeing that it seems impossible to obtain ladspa.h or gcc from your
> workplace. :)
It's not impossible to get them, and in fact I'm using five versions
(for different
[Alfons Adriaensen]
>On Tue, Mar 09, 2004 at 04:46:58PM +0100, Tim Goetze wrote:
>
>> understood. now please consider the implications for a host: it needs
>> to find the offset into the string array where the labels for the
>> first ENUMERATED port start. no problem, we use PortCount. then it
>>
On Tue, Mar 09, 2004 at 04:46:58PM +0100, Tim Goetze wrote:
> understood. now please consider the implications for a host: it needs
> to find the offset into the string array where the labels for the
> first ENUMERATED port start. no problem, we use PortCount. then it
> needs to compute how many l
[Alfons Adriaensen]
>On Tue, Mar 09, 2004 at 02:46:47PM +0100, Tim Goetze wrote:
>> [Alfons Adriaensen]
>
>> >I think that in a case like this, you will always be able to map the
>> >'important points' to integers.
>
>> ok. since we don't have any code to base our judgement of this
>> proposal on,
[Steve Harris]
>On Tue, Mar 09, 2004 at 03:15:13 +0100, Tim Goetze wrote:
>> >You said "a pushbutton emitting the default value for the port is a
>> >possibility", I was responding to that.
>>
>> in that case, sorry for being vague. i'm trying to say that removing
>> the redundant default=0 constr
On Tue, Mar 09, 2004 at 02:46:47PM +0100, Tim Goetze wrote:
> [Alfons Adriaensen]
> >I think that in a case like this, you will always be able to map the
> >'important points' to integers.
> ok. since we don't have any code to base our judgement of this
> proposal on, i'll quote an earlier post
[Alfons Adriaensen]
>On Tue, Mar 09, 2004 at 04:29:55AM +0100, Tim Goetze wrote:
>> suppose you want to trigger twice, in two consecutive run() cycles.
>> you have to 'bring the line down' inbetween to accomplish this if you
>> only have MOMENTARY, not TRIGGER. how do you do it? you have to split
>
On Tue, Mar 09, 2004 at 03:15:13 +0100, Tim Goetze wrote:
> >You said "a pushbutton emitting the default value for the port is a
> >possibility", I was responding to that.
>
> in that case, sorry for being vague. i'm trying to say that removing
> the redundant default=0 constraint frees the defaul
[Steve Harris]
>> it's still a wart. if you shun the work of changing swh-plugins, i'll
>> happily offer to patch it to remove the unit references.
>
>The work is not a problem (its a disposable perl script and some tidying),
>it just changes something in LADSPA that probably should not be changed
[Steve Harris]
>On Tue, Mar 09, 2004 at 02:06:16 +0100, Tim Goetze wrote:
>> [Steve Harris]
>>
>> >On Mon, Mar 08, 2004 at 05:09:21 -0500, Jesse Chappell wrote:
>> >> Tim Goetze wrote on Mon, 08-Mar-2004:
>> >> > a pushbutton emitting the default value for the port is a possibility.
>> [...]
>> >
On Tue, Mar 09, 2004 at 02:08:05 +0100, Tim Goetze wrote:
> [Steve Harris]
>
> >On Tue, Mar 09, 2004 at 12:53:33 +0100, Tim Goetze wrote:
> >> however, the behaviour connecting a TOGGLED or INTEGER port to a
> >> continuous signal source is undefined and relies on the host and/or
> >> plugin round
On Tue, Mar 09, 2004 at 02:28:41 +0100, Tim Goetze wrote:
> [Steve Harris]
>
> >On Mon, Mar 08, 2004 at 05:51:28 +0100, Tim Goetze wrote:
> >> and to repeat: if you don't want units to appear in the plugin
> >> sources, why are you satisified with "Frequency (Hz)"?
> >
> >I'm only satisfied with i
On Tue, Mar 09, 2004 at 02:06:16 +0100, Tim Goetze wrote:
> [Steve Harris]
>
> >On Mon, Mar 08, 2004 at 05:09:21 -0500, Jesse Chappell wrote:
> >> Tim Goetze wrote on Mon, 08-Mar-2004:
> >> > a pushbutton emitting the default value for the port is a possibility.
> [...]
> >> Also, to take an exam
On Tue, Mar 09, 2004 at 01:51:56 +0100, Alfons Adriaensen wrote:
> On Tue, Mar 09, 2004 at 08:43:18AM +, Steve Harris wrote:
>
> > I disagree: if I have a control thats "wave, INTEGER where 1=sin, 2=tri,
> > 3=sqa, 4=saw" and one which is the same less the INTEGER hint (ie. it
> > crossfades)
[Alfons Adriaensen]
>On Tue, Mar 09, 2004 at 08:43:18AM +, Steve Harris wrote:
>
>> I disagree: if I have a control thats "wave, INTEGER where 1=sin, 2=tri,
>> 3=sqa, 4=saw" and one which is the same less the INTEGER hint (ie. it
>> crossfades) then the enumeration points are no less important
[Steve Harris]
>On Mon, Mar 08, 2004 at 05:51:28 +0100, Tim Goetze wrote:
>> and to repeat: if you don't want units to appear in the plugin
>> sources, why are you satisified with "Frequency (Hz)"?
>
>I'm only satisfied with it because its allready widely used, in in
>practice its bascily OK. Not
[Steve Harris]
>On Tue, Mar 09, 2004 at 12:53:33 +0100, Tim Goetze wrote:
>> however, the behaviour connecting a TOGGLED or INTEGER port to a
>> continuous signal source is undefined and relies on the host and/or
>> plugin rounding convention, and whether one is in place.
>
>Just the plugin - INTE
[Steve Harris]
>On Mon, Mar 08, 2004 at 05:09:21 -0500, Jesse Chappell wrote:
>> Tim Goetze wrote on Mon, 08-Mar-2004:
>> > a pushbutton emitting the default value for the port is a possibility.
[...]
>> Also, to take an example from sooperlooper, its multicontrol port
>> would be a MOMENTARY and
On Tue, Mar 09, 2004 at 08:43:18AM +, Steve Harris wrote:
> I disagree: if I have a control thats "wave, INTEGER where 1=sin, 2=tri,
> 3=sqa, 4=saw" and one which is the same less the INTEGER hint (ie. it
> crossfades) then the enumeration points are no less importanti in the
> non-INTEGER cas
ZynAddSubFX is using XML files
Hi.
I am Paul, the author of zynaddsubfx.
For those who you don't know about it: is a software
synthsizer for linux and windows and is located at
http://zynaddsubfx.sourceforge.net
I added many things from 1.4.3. The most notable is
the XML support.
I have the inten
On Tue, Mar 09, 2004 at 12:53:33 +0100, Tim Goetze wrote:
> however, the behaviour connecting a TOGGLED or INTEGER port to a
> continuous signal source is undefined and relies on the host and/or
> plugin rounding convention, and whether one is in place.
Just the plugin - INTEGER is a hint to the h
[Alfons Adriaensen]
>Another aspect of this is that the period size set by the audio interface
>or JACK need not necessarily correspond to a soft synth's internal control
>rate. CSound is one example of this. The new AMS I'm currently thinking
>about will be another. In this case the designer has
[Steve Harris]
>On Mon, Mar 08, 2004 at 10:06:25 +0100, Tim Goetze wrote:
>> [Fons Adriaensen]
>> >On Mon, Mar 08, 2004 at 06:30:01PM +0100, Tim Goetze wrote:
>> >> we're already requiring hosts to police connections for value
>> >> conversions.
>> >
>> >Can you point me to some document that cont
[Steve Harris]
>> that both could be in the RDF only. And other than AUDIO / CONTROL which are
>> not compatible at the 'physical' level, I think there should be no port typing
>> in LADSPA.
>
>I agree about no port typing.
so do i fwiw.
vriendelijk,
tim
On Tue, Mar 09, 2004 at 11:50:03 +0100, Alfons Adriaensen wrote:
> Another aspect of this is that the period size set by the audio interface
> or JACK need not necessarily correspond to a soft synth's internal control
> rate. CSound is one example of this. The new AMS I'm currently thinking
> about
On Mon, Mar 08, 2004 at 04:32:53PM -0500, Jesse Chappell wrote:
> BTW, this is exactly why no generic host can use the sooperlooper
> plugin... i had to treat one control port as effectively MOMENTARY
> and arbitrary valued. It expected the host to take the port out
> of range for a run() cycle be
On Tue, Mar 09, 2004 at 10:30:09 +0100, Alfons Adriaensen wrote:
> On Tue, Mar 09, 2004 at 08:43:18AM +, Steve Harris wrote:
>
> > I understand where you're coming from here. There are a few cases where
> > the current system fails (not many, and not seriously, but they are
> > there).
>
> In
On Tue, Mar 09, 2004 at 04:29:55AM +0100, Tim Goetze wrote:
> what makes you presume an LFO is always running at audio rate? running
> a network at 64 or 32 frames blocksize is common, and good enough for
> many k-rate (control) signals.
> there also are a lot of other good k-rate sources besides
On Mon, Mar 08, 2004 at 06:39:48AM +, Steve Harris wrote:
> Something that was suggested for GMPI, and might be applicable for LADSPA
> is a convetion where port names can be written as paths, eg for a delay
> line you might have
>
> "delay/base delay (ms)"
> "delay/feedback (%)"
> "lfo 1/ammo
On Tue, Mar 09, 2004 at 08:43:18AM +, Steve Harris wrote:
> I understand where you're coming from here. There are a few cases where
> the current system fails (not many, and not seriously, but they are
> there).
Interesting. Do you have an example ?
--
FA
galan-0.3.0_beta5 is released.
For those who know it already:
One of the new features include cloning. you can now select a bunch of
components and clone them. (This will be changed to a full blown
copy/paste mechanism soon) And the polyphony option will be added soon.
galan is a modular syn
On Tue, Mar 09, 2004 at 04:29:55 +0100, Tim Goetze wrote:
> in addition, to correctly render these consecutive trigger signals,
> you have to know future data (the next trigger). the alternative is to
> delay the next trigger, either in similar fashion by breaking up the
> second run() cycle, or by
On Tue, Mar 09, 2004 at 03:10:54 +0100, Fons Adriaensen wrote:
> > >It's two different problems that happen to map to similar data structures.
> >
> > so what's against supplying one solution to two problems?
>
> They are different, and require different solutions.
> Functionality : one is essent
On Mon, Mar 08, 2004 at 10:06:25 +0100, Tim Goetze wrote:
> [Fons Adriaensen]
> >On Mon, Mar 08, 2004 at 06:30:01PM +0100, Tim Goetze wrote:
> >> we're already requiring hosts to police connections for value
> >> conversions.
> >
> >Can you point me to some document that contains that requirement ?
On Mon, Mar 08, 2004 at 05:09:21 -0500, Jesse Chappell wrote:
> Tim Goetze wrote on Mon, 08-Mar-2004:
>
> > [Taybin Rutkin]
> >
> > >How should a host deal with a port that is MOMENTARY, but not
> > >TOGGLED? What would the UI be?
> >
> > a pushbutton emitting the default value for the po
On Mon, Mar 08, 2004 at 10:29:51 +0100, Fons Adriaensen wrote:
> On Mon, Mar 08, 2004 at 05:58:48PM +, Steve Harris wrote:
>
> > I dont think that scale markings, / enumerations, defaults and units are
> > logically connected to the same extent that upper and lower bounds are.
> > That is a ma
46 matches
Mail list logo
