On Fri, May 14, 2004 at 04:50:31 +0200, Alfons Adriaensen wrote:
> I don't mind *IFF* the metadata file has a simple, human readable
> syntax (no XML please) that can be parsed line by line.
Human readable and line by line parsable are pretty much mutually
exclusive - try expressing any complex st
On Thu, May 06, 2004 at 11:20:38 -0400, Dave Phillips wrote:
> Taybin Rutkin wrote:
>
> >What is the problem with JACK and AMD cpus? I haven't heard of one.
> >
> >
> >
> Not so long ago a release of qjackctl in Planet C failed due to (IIRC)
> JACK getting compiled with an SSE call (or calls) t
On Thu, May 06, 2004 at 10:44:13 -0400, Dave Phillips wrote:
> Greetings:
>
> A client has asked me to get some opinions regarding AMD CPUs and
> recommended motherboards. He's planning to replace an SMP system that
> has apparently never worked quite right. He doesn't want another SMP
> mobo,
On Wed, May 05, 2004 at 08:52:57 +0300, Juhana Sadeharju wrote:
> >From: Christian Henz <[EMAIL PROTECTED]>
> >
> >So far I've been using an Observer pattern
>
> Are all these patterns described somewhere in the web?
> People refers mostly to some book(s) but that is not
> available for me.
You s
On Wed, May 05, 2004 at 01:57:10 +, Pall Thayer wrote:
> It would be nice if SVG became more widespread. I wonder why Mozilla doesn't
> include it in the normal releases. Since the source is available, it couldn't
> be too difficult to make a free plugin version, could it? There was talk
> a
These are just my thoughts and some notes about "LADSPA 2.0", the mail I
sent yesterday was the notes I made in the meeting that everyone agreed
to, so I didn't want to add my personal thoughts.
Mentally prefix everything below with "I think...".
I wasn't particuarly happy with the tone of the me
On Tue, May 04, 2004 at 03:25:45 +0200, Francois Dechelle wrote:
> I've searched a little bit for SVG, but right now I have not found a GPL
> implementation of a SVG viewer. Neither a SVG plug-in for mozilla
> (Mozilla has SVG support integrated, but it is not enabled in standard
> compilations; co
This is a quick report back from the LADSPA bird-of-a-feather session that
happened on Friday morning at the LA Conference. Attendees of the session
can expand on any details that aren't clear here once they recover :)
The atendees signed off on the text that has unanimous agreement, but not
on the
On Mon, May 03, 2004 at 12:50:56 +0200, Tim Goetze wrote:
> [Steve Harris]
> >On Sat, May 01, 2004 at 03:33:14 +0200, Tim Goetze wrote:
> >> i'm inclined to think that free-form docs are sufficient. it would be
> >> nice to have a complete conf language but the
On Sat, May 01, 2004 at 03:33:14 +0200, Tim Goetze wrote:
> i'm inclined to think that free-form docs are sufficient. it would be
> nice to have a complete conf language but the effort implementing that
> is likely to be huge or require yet another library or both, and maybe
> not even worth it.
Y
On Sat, May 01, 2004 at 12:38:43 +0200, Tim Goetze wrote:
> [Steve Harris]
>
> >Everything that goes over configure() is/can be prietary to the plugin, it
> >would be up to the plugin author wether they documented or not.
> >
> >The only requirement is that data
On Fri, Apr 30, 2004 at 06:18:35 +0200, Tim Goetze wrote:
> [Steve Harris]
>
> >On Thu, Apr 29, 2004 at 12:32:14 +0200, Tim Goetze wrote:
> >> i'm not too intimate with liblo/OSC, so sorry for asking an RTFM
> >> question: does OSC provide some sort of alternat
On Thu, Apr 29, 2004 at 12:32:14 +0200, Tim Goetze wrote:
> [Chris Cannam]
> >The assumption is that the host just passes on whatever the GUI
> >selects, and it's up to the GUI (which of course is provided by the
> >plugin author, or at least built to match the plugin) to understand
> >the key valu
I cant really comment on the MIDI thing, thats Chris' area, I dont know
enough about it, but N.B. the midi method is optional and the program one
is not.
On Wed, Apr 28, 2004 at 12:24:17 +0200, Jens M Andreasen wrote:
> | 2. Discovery and Startup ...
>
> .. it would be so much much simpler to jus
On Mon, Apr 19, 2004 at 06:43:46PM +, [EMAIL PROTECTED] wrote:
> All chopping and munging was done in cheesetracker, even the crunchy
> bass was made from the smooth one by over amplifying and then
> filtering out the nasties. Lots of ladspa effects helped, too,
> although the ones I most want
On Wed, Apr 14, 2004 at 11:19:50 +0200, David Olofson wrote:
> That said, I don't know which is better in terms of hardware and
> drivers; 1394 or ethernet... AFAIK, both are essentially high speed
> serial bus interfaces, but it might be that 1394 doesn't have
> collision detection h/w and stuf
On Fri, Apr 09, 2004 at 04:47:59 +0200, Alfons Adriaensen wrote:
> > I can't see how that, or any other process, would agree on any of the
> > proposed fixes given the current lack of concensus.
>
> The advantage of having a real dictator is that no concensus is needed :-)
I think the word "benev
On Fri, Apr 09, 2004 at 02:53:10 +0200, Alfons Adriaensen wrote:
> > * maybe for that reason, there has been some imho ill-advised
> > rhetoric towards fait-accompli tactics.
>
> I have so far presented three proposals. One of them was just a matter
> of interpretation. The two others would have
On Thu, Apr 08, 2004 at 08:15:41 +0200, Frank Barknecht wrote:
> Hallo,
> Frank NEUMANN hat gesagt: // Frank NEUMANN wrote:
>
> > just a little update on what's going on with the upcoming Linux Audio
> > Conference in Karlsruhe on April 29th - May 2nd: The programme is now
> > available as a PDF,
On Thu, Apr 08, 2004 at 12:04:20 +0200, Mr.Freeze wrote:
> Hi,
> Quirky question: is it possible to run PureData (or another
> *modular*) on a DSP (or, still, another
> microcontroller) under a port of Linux?
>
> I was thinking of building an hardware expander that would share the patches of
>
On Thu, Apr 08, 2004 at 01:02:50 +0200, Christian Schoenebeck wrote:
> > Section 1 - appropriate copyright notice
> > Section 3 - accompany it with source code when copying/distributing or
> > make a written offer
> > Section 2 might apply aswell as i doubt they'd be using vanilla stuff...
>
> The
On Wed, Apr 07, 2004 at 12:44:34 -0400, Paul Davis wrote:
> >But ST doesnt support plugins, and I need to be able to do a "quick and
> >dirty" pitchshift on the samples to see if it's gunna fit musically in the
> >track.
>
> steve harris' plug
On Tue, Apr 06, 2004 at 11:28:28 +0200, Florian Schmidt wrote:
> On Tue, 6 Apr 2004 07:33:50 +1000
> Erik de Castro Lopo <[EMAIL PROTECTED]> wrote:
>
> > On Tue, 06 Apr 2004 00:59:39 +0200
> > Marek Peteraj <[EMAIL PROTECTED]> wrote:
> >
> > > Hi Erik,
> > >
> > > On Mon, 2004-04-05 at 22:25, Er
On Tue, Apr 06, 2004 at 11:11:22 +0300, Jorma R wrote:
> Hi,
>
> I don't know whether this is old news but interesting anyway: a mixing
> interface in which you handle the pan and gain settings by placing
> "balls" that represent the instruments (or tracks from a recorder) in a
> 3D space.
>
>
http://plugin.org.uk/lrdf/
Liblrdf is a library for handling RDF descirption of plugins and presets.
Version 0.3.7 adds bugfixes to the scale reading convienience function
and adds helpful return values from the preset creation and rdf fragment
saving functions, thanks to Taybin Rutkin.
- Steve
liblo is a easy to use OSC (Open Sound Control) implementation written in C.
http://plugin.org.uk/liblo/
See the website for docs and example code.
Changes since last release:
bugfixes
OSC URL handling
better IPV6 support
real documentation
better example
On Wed, Mar 24, 2004 at 02:39:28 +0100, Richard Spindler wrote:
> Am Mittwoch 24 März 2004 13:38 schrieb Steve Harris:
> > Have .so files (similar to LADSPA plugins, but different API) that contain
> > functions that can be called to inspect audio files on disk to determine
> &g
Conrads announcement just reminded me, but a freind of mine sugessted this
for Linux months ago (I think he nicked it off the way Amigas
filetype-drivers did generic file i/o) and I've been meaning to post about
it ever since.
The Idea
Have .so files (similar to LADSPA plugins, but different API)
On Tue, Mar 23, 2004 at 05:16:01 -0500, Paul Davis wrote:
> >It seems that there is documentation (and even an implementation) for
> >A/M, but nothing for Connection Management. Has anyone tried recently
> >to get documentation? Based on
> >http://www.yamaha.co.jp/tech/1394mLAN/english/ptt.html ,
On Mon, Mar 22, 2004 at 07:49:49 -0800, Jay Dolan wrote:
> You are dead on with the downsampling issue. With a
> downsampleFactor of 1 or 2 the program works great for
> me now - 50 was way too high. I know jack sh!t about
> filtering..or PCM in general. But the program, while
> slower, is now a
On Mon, Mar 22, 2004 at 02:44:13 -0500, Paul Davis wrote:
> Unfortunately, the ZKM meeting is basically a 100% overlap with the
> musikmesse. I don't see any feasible way to do a meeting with Yamaha
> that weekend.
I dont think it overlaps, though it did last year:
2nd Linux Audio Developers Con
On Mon, Mar 22, 2004 at 04:33:57PM +0100, Cournapeau David wrote:
> >Linux is lacking efficient, high-quality standalone EQs for example.
> >
> >
> What do you mean by standalone ? Something like a jack client ? Or totally
> independant (portaudio client, etc...) What would
> be the differences co
On Sat, Mar 20, 2004 at 02:06:50 +0100, Cournapeau David wrote:
>
> Hi there,
>
>I am currently a DSP student, and want to program some stuff to
> improve my programming skills on linux plateform. As several musicians
> friends told me they would want a RME
> totalyser -like software (see
On Fri, Mar 19, 2004 at 06:49:55 +0100, d wrote:
> hi everyone!
> this is the announcement of my first standalone soundapp "kluppe".
> it's a jackified gtk-based loopplayer for files and live-input,
> supporting various playmodes.
>
> you can find it at
> http://dieb13.klingt.org/content/projects
On Mon, Mar 15, 2004 at 10:13:25 -0300, Ricardo Cirigliano wrote:
> Hi! I´m using portaudio to capture continous voice using buffers of
> 200ms. I´m using 2 buffers in order to be able to make some process
> in one of them while I capture voice with the other one. However,
> every time I change the
On Sun, Mar 14, 2004 at 11:54:53AM +0100, Alex Marandon wrote:
> I've made some tries with simply dividing the sum of samples by the
> number of sample (ie: buffer1[i] + buffer2[i] / 2) and the result is not
> so bad.
If the number of channles is constant anbd low (eg. 2) then this is OK,
but if i
On Wed, Mar 10, 2004 at 03:34:47 +0100, Alfons Adriaensen wrote:
> On Wed, Mar 10, 2004 at 02:30:23PM +0000, Steve Harris wrote:
> > On Wed, Mar 10, 2004 at 03:22:33 +0100, Alfons Adriaensen wrote:
> > > On Wed, Mar 10, 2004 at 01:57:21PM +, Steve Harris wrote:
> > >
On Wed, Mar 10, 2004 at 03:22:33 +0100, Alfons Adriaensen wrote:
> On Wed, Mar 10, 2004 at 01:57:21PM +0000, Steve Harris wrote:
>
> > There is a formal approval mecahnism, its whatever Richard will bless.
> > He contacted me off-list: he is still around but hasnt been activily
On Wed, Mar 10, 2004 at 01:55:55 +0100, Alfons Adriaensen wrote:
> On Wed, Mar 10, 2004 at 11:22:36AM +0000, Steve Harris wrote:
>
> > A variety of non-standard implenentations at this point would be a very
> > bad thing, and I *will not* be coerced into supporting some illconce
On Wed, Mar 10, 2004 at 02:42:00 +0100, Alfons Adriaensen wrote:
> On Wed, Mar 10, 2004 at 11:44:26AM +0000, Steve Harris wrote:
>
> > But it will use up two flags that may be needed later and may clash with
> > future extensions, or produce binary imcompatibility. Not to ment
On Wed, Mar 10, 2004 at 12:47:32 +0100, Jan Weil wrote:
> Quoting Fons' proposal:
> If there are any ports using LADSPA_HINT_SWITCHED, then their
> label strings follow after all port names (i.e. the port names
> remain in their normal place). In this case the range of valid
>
On Wed, Mar 10, 2004 at 12:21:17 +0100, Jan Weil wrote:
> I've been using my favourite LADSPA plugin AudioTwingTwang in Sweep
> 0.8.2 for a long time. I have to admit it's UI looks a little odd but I
> really love this effect.
> Now I'm trying to record some of my music which no longer fits into my
On Wed, Mar 10, 2004 at 11:46:03 +0100, Dr. Matthias Nagorni wrote:
> I hope that Tom will follow your suggestion in his plugin, so that
> I can modify AlsaModularSynth to support Combobox selectors for LADSPA
> plugin GUIs.
Dont you think its a bit counter-productive to encourage people
On Wed, Mar 10, 2004 at 11:14:02 +0100, Jan Weil wrote:
> Well, since these are _hints_ I'd suggest to just ignore
> LADSPA_HINT_SWITCHED in this case. Otherwise a simpler minded host
> (applyplugin) might let you use this plugin without problems while your
> sophisticated pro app refuses to touch
On Wed, Mar 10, 2004 at 10:38:59 +0100, Alfons Adriaensen wrote:
> I'm in favour of dropping that 'slightly wider' requirement. I've never
> followed it in my own plugins, and never will.
Me too, and agreed.
- Steve
On Wed, Mar 10, 2004 at 09:36:42 +0100, Jens M Andreasen wrote:
> Uhmm .. So where do I find the midistream?
You dont, LADSPA doesnt do MIDI.
- Steve
On Wed, Mar 10, 2004 at 07:49:29 +0100, Jens M Andreasen wrote:
> 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 se
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
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 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
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 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 "Frequen
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 possibili
On Tue, Mar 09, 2004 at 01:51:56 +0100, Alfons Adriaensen wrote:
> On Tue, Mar 09, 2004 at 08:43:18AM +0000, 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
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
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 Tue, Mar 09, 2004 at 10:30:09 +0100, Alfons Adriaensen wrote:
> On Tue, Mar 09, 2004 at 08:43:18AM +0000, 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,
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 +0000, 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
On Mon, Mar 08, 2004 at 08:23:32 +0100, Fons Adriaensen wrote:
> > MOMENTARY: a push button, sending 'yes' when pressed and 'no' when
> > released.
>
> 'when' or 'while' ?
Momentary switches are "high" while the control is held, and low when its
not. This subsumes what Tim describes as a trigger
On Mon, Mar 08, 2004 at 05:51:28 +0100, Tim Goetze wrote:
> [Steve Harris]
> >> it also clutters one field (the name) by using it for two orthogonal
> >> purposes, which must be a nightmare for somebody using as strict a
> >> distinction of data modes as you do.
&
On Mon, Mar 08, 2004 at 04:41:19 +0100, Dr. Matthias Nagorni 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
On Mon, Mar 08, 2004 at 05:53:08 +0100, Alfons Adriaensen wrote:
> > It would send short trigger signals. I use ports like this in ams modules
> > that have a trigger output. And these ports are e.g. connected to a
> > "retrigger" port of an envelope or the "reset" port of a LFO.
>
> Why should
On Mon, Mar 08, 2004 at 04:18:11 +0100, Tim Goetze wrote:
> ok, after going over tap_limiter.c in detail i see the point of
> communicating latency information to the host at runtime (and neither
> a dedicated descriptor member, nor RDF will ever succeed in trying to
> accommodate the behaviour).
>
On Mon, Mar 08, 2004 at 03:48:22 +0100, Tim Goetze wrote:
> [Steve Harris]
> >On Mon, Mar 08, 2004 at 01:39:36AM +0100, Tim Goetze wrote:
> >> * a patch moving ladspa.h 1.1 to 2.0
> >
> >Why 2.0? I thought we were aiming for binary compatibility. 1.2 seems more
&
On Mon, Mar 08, 2004 at 03:22:57 +0100, Tom Szilagyi wrote:
> Fixed latency is not a big issue because a plugin can report the maximum
> latency it could ever reach, and if the actual latency is lower it can
> artificially delay its output internally. But i think this is ugly,
> particularly bec
On Mon, Mar 08, 2004 at 09:46:26AM +0100, Jens M Andreasen wrote:
> On mån, 2004-03-08 at 01:39, Tim Goetze wrote:
> > attached you'll please find three files:
> >
> > * a patch moving ladspa.h 1.1 to 2.0
> > * a program showing how a host evaluates 2.0 extensions
> > * a thoroughly documented exa
On Mon, Mar 08, 2004 at 02:58:54AM -0500, Dave Robillard wrote:
> SSM does indeed have some really cool plugins like this. I know scaling
> is equivalent to amplifying, sum = mixer, etc. but I was hoping someone
> out there had a collection of math plugins, say division, add/sub a
> constant, trig
On Mon, Mar 08, 2004 at 07:18:26AM +, Steve Harris wrote:
> On Mon, Mar 08, 2004 at 01:57:24AM -0500, Dave Robillard wrote:
> > Are there any simple math plugins for LADSPA? Like, scaling of a
> > signal, sum of signals, dif of signals, etc. etc.
>
> scaling is an am
On Mon, Mar 08, 2004 at 01:57:24AM -0500, Dave Robillard wrote:
> Are there any simple math plugins for LADSPA? Like, scaling of a
> signal, sum of signals, dif of signals, etc. etc.
scaling is an amp (eg. amp_mono, 1048)
sum is a mixer (eg. mixer, 1071)
dif is a signed mixer (dunno if there is o
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/ammount (%)"
"lfo 1/wave"
"lfo 1/frequency"
"lfo 2/ammount (%)"
"lfo 2/wave"
"lf
On Mon, Mar 08, 2004 at 01:39:36AM +0100, Tim Goetze wrote:
> attached you'll please find three files:
>
> * a patch moving ladspa.h 1.1 to 2.0
Why 2.0? I thought we were aiming for binary compatibility. 1.2 seems more
technically correct and less offputting to developers.
Having thought about i
On Sat, Mar 06, 2004 at 09:01:59PM +0100, Arnold Krille wrote:
> On Saturday 06 March 2004 19:59, Steve Harris wrote:
>
> > Yes, but the difference to new developers is huge, they must understand
> > everything in the .h file before thay can write a plugin or host.
>
> I
On Sat, Mar 06, 2004 at 05:45:03 +0100, Tim Goetze wrote:
> [Steve Harris]
> >If you look back through the archives you'l see that my attitude changed
> >form "yay, more features, cram them in" (luckily rained in by Paul and
> >Richard) to a more considered
On Sat, Mar 06, 2004 at 03:26:04 +0100, Tim Goetze wrote:
> [Fons Adriaensen]
> >On Fri, Mar 05, 2004 at 09:56:01PM +0100, Tom Szilagyi wrote:
> >
> >> I think the "dead end" has just been reached...
> >
> >Yes. Steve has made his position very clear: he opposes any change
> >to ladspa.h. Much as I
On Sat, Mar 06, 2004 at 02:28:20 +0100, Tim Goetze wrote:
> >> * everything labeled 'meta' in the above thought experiment becomes
> >> 'not meta', except for the presets.
> >> * knowing that 0.5 = half a second is 'not meta'.
> >> * knowing that 0 = sin, 1 = tri, 2 = saw is vital, thus 'not meta
On Sat, Mar 06, 2004 at 02:52:43 +0100, Tim Goetze wrote:
> >You just use a regular control port to specify
> >your threshold/amplitude. The trigger port just does the "triggering".
>
> the proposed patch fits this model well: a plugin need only specify
> TOGGLED in addition to TRIGGER.
>
> at t
On Fri, Mar 05, 2004 at 02:50:09 -0800, Tim Hockin wrote:
> On Fri, Mar 05, 2004 at 10:19:47PM +0000, Steve Harris wrote:
> > > hrrmm...I doubt if it is due to IRQ priorities. I mean, really, any modern
> > > CPU can handles 10s or 100s of thousands of IRQs per second..
>
On Fri, Mar 05, 2004 at 06:19:42 -0500, Jesse Chappell wrote:
> > Variable-amplitude triggers would be really cool though. You could,
> > say, make a synthed snare generator plugin that is velocity-sensitive.
> >
> > Actually, something like that would be out of the LADSPA domain I
> > suppo
On Fri, Mar 05, 2004 at 11:21:32 +0100, Tim Goetze wrote:
> like others, i'm not quite sure discussing this any further is going
> to be particularly fruitful, but here goes anyway.
Agreed. I think we should all sleep on it for a few days at least.
> i would like to carry your definition to the
On Fri, Mar 05, 2004 at 01:54:00 -0800, Tim Hockin wrote:
> On Fri, Mar 05, 2004 at 08:35:06PM +0000, Steve Harris wrote:
> > No, I hadn't used the ALSA modules :) The interrupts get through unless
> > I use < 2048 samples / period, if I do ALSA reports lost interrupts
>
On Fri, Mar 05, 2004 at 11:03:46 -0800, Tim Hockin wrote:
> >CPU0
> > 0: 12578480 XT-PIC timer
> > 1: 22347 XT-PIC keyboard
> > 2: 0 XT-PIC cascade
> > 5: 0 XT-PIC Maestro3
> > 8: 1 XT-PI
On Fri, Mar 05, 2004 at 08:15:24 +0100, Dr. Matthias Nagorni wrote:
> We do not lose anything if we accept either the proposal by Tim or Fons or
> something in between. Both proposals are binary compatible with the
> current standard. Plugin-writers and host-developers would still have the
> cho
On Fri, Mar 05, 2004 at 07:14:41 +0100, Tom Szilagyi wrote:
> I like this new LADSPA spec. very much, thanks to Tim Goetze for working
> it out! However, i have one bit of concern:
>
> /* This member indicates the delay, in 1 / (sample rate) time units,
> the plugin imposes upon processed s
On Fri, Mar 05, 2004 at 09:09:31AM -0800, Tim Hockin wrote:
> On Fri, Mar 05, 2004 at 03:06:27PM +0000, Steve Harris wrote:
> > It used to be possible (in the 2.0 kernel series) to the rotate priority of
> > IRQs on the two controllers. This sounds really good as on my laptop the
&
On Fri, Mar 05, 2004 at 05:57:28PM +0100, Tim Goetze wrote:
> [Richard Spindler]
>
> >Is it possible to use this Rdf-Stuff to add all the Features ladspa
> >seems to be missing?
> >
> >And If so, you'll all hopefully agree, that this implementation _works_.
> >
> >And if it works, I do not see any
On Fri, Mar 05, 2004 at 04:48:35PM +0100, Alfons Adriaensen wrote:
> On Fri, Mar 05, 2004 at 03:30:46PM +0000, Steve Harris wrote:
>
>
> > I still dont think that listing
> > some hardcoded presets in an integer control port is a good way to have
> > presets. It s
On Fri, Mar 05, 2004 at 11:44:24AM -0500, Taybin Rutkin wrote:
> TRIGGER, or MOMENTARY in my patch (http://www.mail-archive.com/[EMAIL
> PROTECTED]/msg11074.html), should really be 804, because it implies TOGGLED.
And also RANDOMIZABLE, which is also important.
- Steve
On Fri, Mar 05, 2004 at 05:54:52PM +0100, Tim Goetze wrote:
> [Taybin Rutkin]
>
> >TRIGGER, or MOMENTARY in my patch
> >(http://www.mail-archive.com/[EMAIL PROTECTED]/msg11074.html),
> >should really be 804, because it implies TOGGLED.
>
> yes, i thought about this, but came to the conclusion tha
On Fri, Mar 05, 2004 at 04:11:35 +0100, Dr. Matthias Nagorni wrote:
> On Fri, 5 Mar 2004, Steve Harris wrote:
>
> > OK, thats a reasonable definition for enumerations, but its missing the
> > non-ionteger eqivalent, "scale points" or whatever you want to callthem,
On Fri, Mar 05, 2004 at 03:57:39 +0100, Dr. Matthias Nagorni wrote:
> > That is not complete, you also need strings, push-to-make (momentary)
>
> Yes, triggers would be helpful as well. But somehow they can be
> "approximated" by toggles, although it's not ideal. So why not also add
> a HINT_TRIG
Hi all,
This has been discussed briefly before:
http://www.music.columbia.edu/pipermail/linux-audio-user/2003-March/002834.html
It used to be possible (in the 2.0 kernel series) to the rotate priority of
IRQs on the two controllers. This sounds really good as on my laptop the
soundcard is welded
On Fri, Mar 05, 2004 at 02:40:08 +0100, Alfons Adriaensen wrote:
> > eg. gate(1410) has -1.0 -> "key listen", 0.0 -> "gate", 1.0 -> "bypass"
> > and you might reasonably want non integer values for enumerations.
> >
> > - Steve
>
> HINT_ENUMERATED must always be used together with HINT_INTEGER.
>
On Fri, Mar 05, 2004 at 01:11:29PM +0100, Alfons Adriaensen wrote:
> And all it takes is just one hint bit saying that the port is enumerated.
> The strings themselves are placed in the portnames array, after all the
> portnames, so no new fields are required. The existing range hints will
> tell t
On Fri, Mar 05, 2004 at 12:21:42 +0100, Dr. Matthias Nagorni wrote:
> > Because they weren't thought of at design time. There is allready
> > enumerated value support in RDF. Very simple hosts do not need it.
>
> Steve, I can not agree with any of these three sentences. My experience with
> ams a
On Fri, Mar 05, 2004 at 02:02:10 +0100, Fons Adriaensen wrote:
> > Agreed. I basically believe that the ladSpa spec. is almost completely
> > OK. However, one thing i would change is that i can't specify an
> > arbitrary default for a control but only fixed ones eg. 0, 1, 100, 440.
> > It would be
501 - 600 of 1876 matches
Mail list logo
