9 Jan
2003
9 Jan
'03
9:01 a.m.
http://plugin.org.uk/releases/0.3.4/
Hods of changes, including:
* Bugfixes to GSM sim (Pascal Haakmat)
* Bugfixes to FM osc (Pascal Haakmat)
* Bugfixes to audio divider (Nathaniel Virgo)
* Added another compressor, SC4, stereo, no sidechain
* Added lookahead brickwall limiter
* Added L/C/R delay (requested by Marek Peteraj)
* Added Giant flanger (kind of requested by Patrick Shirkey)
* Added DJ Flanger (actually requested by Patrick Shirkey)
* Should now compile on FreeBSD
* Fixed syntax error in RDF metadata, works with Bob H's jack-rack now
I've updated the AUTHORS list, but I've undoubtedly forogtten people, so if
youre not in there and should be give me a shout.
SC4 is more-or-less like SC3, but has no sidechain and a subtly different
algorithm. The sidechain was confusing hosts.
The limiter has up to two seconds of lookahead, so can be very gentle.
The L/C/R delay might be a bit familiar to Korg Trinity users ;) I haven't
used it much bet it seems pretty cool.
The giant flanger was a mistake, but I left it in anyway.
The DJ flanger hjas controls for LFO period (instead of frequency as you
would have in a synth) and you can resync the LFO by clicking a toggled
control*.
- Steve
* This reminds me, there would be a use for a MOMENTARY hint (implying or
requiring TOGGLED) in LADSPA, that meant that a control port should only
be held high while the UI control was held down, otherise you have to
double click reset controls, which is confusing.
9 Jan
9 Jan
12:26 p.m.
Steve Harris wrote:
The DJ flanger hjas controls for LFO period (instead of frequency as you
would have in a synth) and you can resync the LFO by clicking a toggled
control*.
This flange is very good. You could pay $150 for a Boss pedal that has
less functionality. I have yet to see another flange allow a cycle upto
32 seconds.
Thanks Steve.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
1:48 p.m.
Thanks for the great plugins, Steve!
I've got a question for you about Dyson Compress. It appears to compress and
normalise in one go - is that right?
Setting compression to 1.0 I would expect to get no compression at all, ie 1:1
compression. Instead I'm getting the compression effect I want, but I just
can't understand the parameters! Is the compression value the ratio of input
to output level expressed as a decimal?
One compressor plugin I used (I think it was Cool Edit Pro) used a line graph
of input level versus output level. 1:1 compression was therefore a straight
diagonal line at 45 degrees. You could bend the curve with the mouse to get
the exact compression curve you wanted.
Cheers
Daniel
2:36 p.m.
On Thu, Jan 09, 2003 at 05:45:09 +0000, Daniel James wrote:
Thanks for the great plugins, Steve!
I've got a question for you about Dyson Compress. It appears to compress and
normalise in one go - is that right?
I dont know, its not my code it came from someone called Dyson ;) Id
recommend using the SC series, as I know they work.
- Steve
10 Jan
10 Jan
10:12 a.m.
I've got a
question for you about Dyson Compress. It appears to compress
and normalise in one go - is that right?
I dont know, its not my code it came from someone called Dyson ;) Id
recommend using the SC series, as I know they work.
12:11 p.m.
On Fri, Jan 10, 2003 at 02:09:42 +0000, Daniel James wrote:
What's the difference between SC1, SC2 and SC3? Is there any documentation for
them?
Some, yes:
http://plugin.org.uk/ladspa-swh/docs/ladspa-swh.html#id1425
Also availble in PDF and such at http://plugin.org.uk/ladspa-swh/docs/
Additions to the documentation are very welcome.
- Steve
I've got a question for you about Dyson Compress.
It appears to compress
and normalise in one go - is that right?
I dont know, its not my code it came from someone called Dyson ;) Id
recommend using the SC series, as I know they work.
2:08 p.m.
Additions to the documentation are very welcome.
I think they could benefit from more user friendly labels on the gui - I'm
using them within audacity. For example, instead of just
Knee radius (dB) 1.00000
you could have the words 'hard' and 'soft' at either end of the scrollbar
to
give the DSP-challenged an idea of which way to slide it!
Cheers
Daniel
3:30 p.m.
On Fri, Jan 10, 2003 at 06:05:34 +0000, Daniel James wrote:
Good point, the docs should at least tell you which is hard and which is
soft, but I also like having the real numbers myself.
The RDF schema is capable of describing scales for controls, but I haven't
actually defined any yet...
- Steve
Additions to
the documentation are very welcome.
I think they could benefit from more user friendly labels on the gui - I'm
using them within audacity. For example, instead of just
Knee radius (dB) 1.00000
you could have the words 'hard' and 'soft' at either end of the scrollbar
to
give the DSP-challenged an idea of which way to slide it!
13 Jan
13 Jan
10:58 a.m.
you could have
the words 'hard' and 'soft' at either end of the scrollbar
to give the DSP-challenged an idea of which way to slide it!
Good point, the docs should at least tell you which is hard and which is
soft, but I also like having the real numbers myself.
12:06 p.m.
On Mon, Jan 13, 2003 at 02:55:48PM +0000, Daniel James wrote:
Ideally, an effect should be as easy to understand and
use as a guitar pedal
or rack unit with three or four knobs on. Just labels like 'more' and
'less'
could make all the difference.
Yes, but without metadata theres no way for LADSPA to express this.
Currently only jack-rack can read LADSPA metadata.
A related request - could the names of the SC series
be changed to Simple
Compressor 1, 2, 3 etc for the benefit of users with drop-down LADSPA menus?
If you hadn't told me that SC was a compressor I might never have found it...
That's because your host wasn't categorising them. It doesn't stand for
Simple Compressor BTW, the're anything but.
I was poking fun at Wave's Cn series compressors, and never got round to
naming them.
- Steve
1:23 p.m.
Just labels
like 'more'
and 'less' could make all the difference.
Yes, but without metadata theres no way for LADSPA to express this.
Currently only jack-rack can read LADSPA metadata. > A related request - could the names of the SC
series be changed to Simple
> Compressor 1, 2, 3 etc for the benefit of users with drop-down LADSPA
> menus?
That's because your host wasn't categorising
them.
All the other plugins have descriptive names in Audacity though.
It doesn't stand for
Simple Compressor BTW, the're anything but.
My mistake... confused it with the one in the CMT library.
I was poking fun at Wave's Cn series compressors,
and never got round to
naming them.
Let's name them now - Steve's Compressor 1, 2 and 3!
Cheers
Daniel
21 Jan
21 Jan
1:26 p.m.
On Fri Jan 10 14:31:01 2003
linux-audio-user(a)music.columbia.edu (Steve Harris) wrote:
On Fri, Jan 10, 2003 at 06:05:34 +0000, Daniel James
wrote:
Good point, the docs should at least tell you which is hard and
which is soft, but I also like having the real numbers myself.
The RDF schema is capable of describing scales for controls, but I
haven't actually defined any yet...
Hmmm... Is there any way to provide gettext support for
LADSPA-plugins?
Alexandre
Additions
to the documentation are very welcome.
I think they could benefit from more user friendly labels on the
gui - I'm using them within audacity. For example, instead of
just
Knee radius (dB) 1.00000
you could have the words 'hard' and 'soft' at either end of the
scrollbar to give the DSP-challenged an idea of which way to
slide it! 
23 Jan
23 Jan
5:06 p.m.
On Wed, 22 Jan 2003, Steve Harris wrote:
On Tue, Jan 21, 2003 at 08:17:38 +0300, Alexandre
Prokoudine wrote:
gettext requires the executing code set the domainname so the gettext
engine knows which file to use for it's lookup. If the RDF is being
translated, we could rely on lrdf to be the intermediary. The only
problem is getting the domainname from the plugin in the first place.
Seems either use a convention to store it in the plugin or define a
varible in the RDF for it.
Taybin
--
http://www.piratesvsninjas.com
Hmmm... Is there any way to provide gettext
support for
LADSPA-plugins?
Probably. Depending on exactly what gettext requires. Interesting
question.
6:05 p.m.
On Thu, Jan 23, 2003 at 03:59:18 -0500, Taybin Rutkin wrote:
On Wed, 22 Jan 2003, Steve Harris wrote:
I was wondering of it was possible without RDF, with RDF there are a
number of solutions. It soulds like it would be, but it would make the
plugin depend on external data, which may or may not be a good idea.
- Steve
On Tue, Jan 21, 2003 at 08:17:38 +0300, Alexandre
Prokoudine wrote:
gettext requires the executing code set the domainname so the gettext
engine knows which file to use for it's lookup. If the RDF is being
translated, we could rely on lrdf to be the intermediary. The only
problem is getting the domainname from the plugin in the first place.
Seems either use a convention to store it in the plugin or define a
varible in the RDF for it. Hmmm... Is there any way to provide gettext
support for
LADSPA-plugins?
Probably. Depending on exactly what gettext requires. Interesting
question.
6:14 p.m.
On Thu, 23 Jan 2003, Steve Harris wrote:
I was wondering of it was possible without RDF, with
RDF there are a
number of solutions. It soulds like it would be, but it would make the
plugin depend on external data, which may or may not be a good idea.
How is it done now? Is a string hardcoded in a variable in the plugin?
If so, as long as the domainname of the plugin is known, the host can do
something like:
set_domainname(LC_ALL, plugin->domain);
label = gettext(plugin->label);
set_domainname(LC_ALL, host->domain);
gettext works by looking up the source's native string in the translation
file. As long as you can send gettext a known char*, it can look it up.
Taybin
--
http://www.piratesvsninjas.com
6:33 p.m.
On Thu, Jan 23, 2003 at 05:07:20 -0500, Taybin Rutkin wrote:
On Thu, 23 Jan 2003, Steve Harris wrote:
Effectivly.
I was wondering of it was possible without RDF,
with RDF there are a
number of solutions. It soulds like it would be, but it would make the
plugin depend on external data, which may or may not be a good idea.
How is it done now? Is a string hardcoded in a variable in the plugin? If so, as long as the domainname of the plugin is
known, the host can do
something like:
set_domainname(LC_ALL, plugin->domain);
label = gettext(plugin->label);
set_domainname(LC_ALL, host->domain);
Ah, OK I didn't realise thats how it worked. In that case it would work
fine. Anyone want to volunteer translations :)
- Steve
5 Feb
5 Feb
1:40 p.m.
On Thu, 23 Jan 2003 22:26:14 +0000
Steve Harris <S.W.Harris(a)ecs.soton.ac.uk> wrote:
On Thu, Jan 23, 2003 at 05:07:20 -0500, Taybin Rutkin
wrote:
Me :-) Sorry for reading it so late
Anyone else - come on, let's make it i180n-ized!
--
Alexandre Prokoudine
ALT Linux Documentation Team
JID: avp(a)altlinux.org
On Thu, 23 Jan 2003, Steve Harris wrote:
Effectivly.
I was wondering of it was possible without RDF,
with RDF there
are a number of solutions. It soulds like it would be, but it
would make the plugin depend on external data, which may or
may not be a good idea.
How is it done now? Is a string hardcoded in a variable in the
plugin? If so, as long as the domainname of the plugin is
known, the
host can do something like:
set_domainname(LC_ALL, plugin->domain);
label = gettext(plugin->label);
set_domainname(LC_ALL, host->domain);
Ah, OK I didn't realise thats how it worked. In that case it would
work fine. Anyone want to volunteer translations :)
7995
days inactive
8022
days old
linux-audio-user@lists.linuxaudio.org
17 comments
5 participants
participants (5)
-
Alexandre Prokoudine -
Daniel James -
Patrick Shirkey -
Steve Harris -
Taybin Rutkin