Hi Richard, hi others,
at the moment I am porting over about 60 plugins from SoundFX (www.sonicpulse.de
- an AMIGA shareware I am still developing and which you can use with UAE!) to
ladspa. I have sucessfully got the ladspa-sdk working on the Amiga too (added a
small wrapper lib to fix
Eek. Quite right.
--Richard
[EMAIL PROTECTED] wrote:
[...]
Okay. I see. I was more wondering about the usage. Shouldn't:
#define LADSPA_IS_HINT_DEFAULT_LOW (((x) LADSPA_HINT_DEFAULT_MASK)
== LADSPA_HINT_DEFAULT_LOW)
actually be written as:
On Sun, 7 Jul 2002, Richard W.E. Furse wrote:
Please let me know if this looks alright - and if I've done anything stupid!
I'm a little confused about the purpose of the LADSPA_IS_HINT_DEFAULT_*
defines. Are they necessary? Are they just useful? Why concert A? Why
not concert C?
Taybin
might recommend a shrink.]
--Richard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Taybin
Rutkin
Sent: 15 July 2002 16:01
To: [EMAIL PROTECTED]
Subject: Re: [linux-audio-dev] LADPSA v1.1 SDK Provisional Release
On Sun, 7 Jul 2002, Richard W.E
On Mon, 15 Jul 2002, Richard W.E. Furse wrote:
Defaults hints are a bit of kludge, but the least kludgy of the offerings -
suggestion was we'd prefer a compromise like this in 1.1. When I coded 1.0 I
anticipated defaults within the remit of GUIs or 'standard patch' mechanisms
(prob. XML) - I
On Fri, Jul 12, 2002 at 02:40:36AM +0300, Kai Vehmanen wrote:
On Thu, 11 Jul 2002, Paul Winkler wrote:
Without breaking binary compatibility,
Can someone explain to me why that's important at this point in time?
Well, it's not _that_ important, but there are a few good reasons...
1) The
Well, it\'s not _that_ important, but there are a few good reasons...
1) The LADSPA API was not designed for ABI changes (most notably the
interface version is not exported by plugins). This means that
old plugins that you didn\'t remember to delete/recompile can
cause segfaults
On Fri, Jul 12, 2002 at 03:28:29 +0200, Martijn Sipkema wrote:
So, one vote for adding the version
to the API ?
I would like to add that old LADSPA plugins can be easily identified
because they lack the \'version\' symbol, so there really is not segfault
problem as far as I can see.
On Wed, Jul 10, 2002 at 07:34:13 +0200, Tim Goetze wrote:
i don't think it's appropriate for a public API in an open source
environment (especially one as narrow as linux audio) to choose
instant feature realization and/or binary compatibility over long-term
simplicity.
Without breaking
On Thu, Jul 11, 2002 at 11:46:52AM +0100, Steve Harris wrote:
On Wed, Jul 10, 2002 at 07:34:13 +0200, Tim Goetze wrote:
i don't think it's appropriate for a public API in an open source
environment (especially one as narrow as linux audio) to choose
instant feature realization and/or
On Thu, Jul 11, 2002 at 10:23:19 +0200, Richard Guenther wrote:
Well - why not just extend struct LADSPA_Descriptor by
/* This member indicates an array of default values for the ports,
if LADSPA_HINT_HAS_DEFAULTS is set. Valid indices vary from 0
to PortCount-1. */
float *
Steve Harris wrote:
On Thu, Jul 11, 2002 at 10:23:19 +0200, Richard Guenther wrote:
Well - why not just extend struct LADSPA_Descriptor by
/* This member indicates an array of default values for the ports,
if LADSPA_HINT_HAS_DEFAULTS is set. Valid indices vary from 0
to
Steve Harris wrote:
On Mon, Jul 08, 2002 at 02:27:25 +0200, Tim Goetze wrote:
On Sun, Jul 07, 2002 at 12:21:59 +0100, Richard W.E. Furse wrote:
I've put a provisional version of the LADSPA SDK including the LADSPA v1.1
header file at
http://www.ladspa.org/ladspa_sdk_dev.tgz
said
On Mon, Jul 08, 2002 at 02:27:25 +0200, Tim Goetze wrote:
On Sun, Jul 07, 2002 at 12:21:59 +0100, Richard W.E. Furse wrote:
I've put a provisional version of the LADSPA SDK including the LADSPA v1.1
header file at
http://www.ladspa.org/ladspa_sdk_dev.tgz
said it then, will say it
Hi,
I understand your objections, but I think the alternatives (that keep
binary compatibility) are just as bad in there own way.
Is binary compatibility really an issue right now? We have swh plugins,
cmt plugins, what
else?
It's all open source, so just recompile it.
Cheers, Alex
On Sun, Jul 07, 2002 at 12:21:59 +0100, Richard W.E. Furse wrote:
I've put a provisional version of the LADSPA SDK including the LADSPA v1.1
header file at
http://www.ladspa.org/ladspa_sdk_dev.tgz
Please let me know if this looks alright - and if I've done anything stupid!
Just did
Steve Harris wrote:
On Sun, Jul 07, 2002 at 12:21:59 +0100, Richard W.E. Furse wrote:
I've put a provisional version of the LADSPA SDK including the LADSPA v1.1
header file at
http://www.ladspa.org/ladspa_sdk_dev.tgz
Please let me know if this looks alright - and if I've done
-audio-dev] LADPSA v1.1 SDK Provisional Release
I've put a provisional version of the LADSPA SDK including the
LADSPA v1.1
header file at
http://www.ladspa.org/ladspa_sdk_dev.tgz
Please let me know if this looks alright - and if I've done
anything stupid!
Once this is sorted out
On Mon, Jul 08, 2002 at 02:27:25PM +0200, Tim Goetze wrote:
Steve Harris wrote:
On Sun, Jul 07, 2002 at 12:21:59 +0100, Richard W.E. Furse wrote:
I've put a provisional version of the LADSPA SDK including the LADSPA v1.1
header file at
http://www.ladspa.org/ladspa_sdk_dev.tgz
Richard Guenther wrote:
On Mon, Jul 08, 2002 at 02:27:25PM +0200, Tim Goetze wrote:
Steve Harris wrote:
On Sun, Jul 07, 2002 at 12:21:59 +0100, Richard W.E. Furse wrote:
I've put a provisional version of the LADSPA SDK including the LADSPA v1.1
header file at
On Sun, 07 Jul 2002, Richard W.E. Furse wrote:
I've put a provisional version of the LADSPA SDK including the LADSPA v1.1
header file at
http://www.ladspa.org/ladspa_sdk_dev.tgz
Please let me know if this looks alright - and if I've done anything stupid!
Once this is sorted out
21 matches
Mail list logo
