24 Jan
2004
24 Jan
'04
6:13 p.m.
Hi all,
TAP (Tom's Audio Plugins) 0.1-0 is released.
Currently four LADSPA plugins are available.
You can check them out at:
http://www.hszk.bme.hu/~st444/tap/tap.html
Key features:
* TAP Equalizer
8 channel equalizer with adjustable band center
frequencies.
* TAP Reverberator
Actually no less than 38 reverberator effects,
ranging from Afterburn to Warehouse, including
small/medium/large rooms, halls, plates...
and more!
* TAP Stereo Echo
Supports conventional mono and stereo delays,
ping-pong (cross) delays and the Haas effect.
* TAP Tremolo
The newest incarnation of an ancient effect.
The plugins have been developed and tested
primarily with Ardour as a host in mind, but
should be functional with any LADSPA-capable
host.
A thorough manual is provided in HTML format,
including detailed information, CPU usage metrics,
usage tips & more about each plugin.
Enjoy!
Tom Szilagyi
24 Jan
24 Jan
7:21 p.m.
New subject: [linux-audio-dev] LADSPA presets was: [ANN] new LADSPA plugins
On Sat, 2004-01-24 at 23:09, Tom Szilagyi wrote:
Hi all,
TAP (Tom's Audio Plugins) 0.1-0 is released.
Currently four LADSPA plugins are available.
You can check them out at:
http://www.hszk.bme.hu/~st444/tap/tap.html
Hi Tom,
nice work!
I tested your plugins with Visecas (i. e. Ecasound) and I just wanted to
let you know that the way you set the MODE port_name for your TAP
Reverberator (as long as _SHOW_PRESET_NAMES_IN_GUI_ is defined) confuses
Ecasound's map-ladspa-list. (Without the #define there was no problem)
I had a look at ladspa.h and it doesn't say anything about newlines in
port names so I must suppose it is 'officially correct'.
Nevertheless I'd guess that there are other LADSPA hosts which
implicitly assume that port names do not contain newlines (maybe I'm
wrong here, though).
Which leads to a for more interesting question:
Is this the way to deal with LADSPA presets?
For those of you who did not have a look at Tom's screenshots:
His TAP Reverberator has a port which makes it possible to select a
builtin preset.
While this is obviously possible I feel a little uncomfortable seeing
this.
After all many LADSPA hosts come with their own presets system (Ardour,
Ecasound, ...).
At least Tom's way makes sure that his presets can be used by all of
them. :)
So once more (I know this has been talked over before on this list):
Wouldn't it be very cool if all LADSPA hosts spoke the same language
with respect to effects presets?
What is the best way to handle them?
Is a common file syntax enough or do we need a shared library for this
purpose?
Or will this lead to yet another daemon serving LADSPA hosts with preset
values? ;)
Jan
25 Jan
25 Jan
6:15 a.m.
New subject: [linux-audio-dev] LADSPA presets was: [ANN] new LADSPA plugins
On Sun, 25 Jan 2004 00:17:29 +0100
Jan Weil <Jan.Weil(a)web.de> wrote:
On Sat, 2004-01-24 at 23:09, Tom Szilagyi wrote:
There already is, in the form of liblrdf (http://plugin.org.uk/lrdf).
This provides a way of:
* Arranging plugins into a hierarchy (Simulators/Reverbs, Time/Delays,
Frequency/Filters/Low Pass and so on)
* Defaults and Presets
* Labelling of port values (as in the TAP Reverb Presets port)
Host support of the hierarchy is fairly extensive, but the other featues
aren't AFAIK.
An example of how that Preset port could be expressed:
<ladspa:ReverbPlugin rdf:about="&ladspa;2412">
<dc:title>TAP Reverberator</dc:title>
<ladspa:hasPort>
...
</ladspa:hasPort>
<ladspa:hasPort>
<ladspa:InputControlPort rdf:about="&ladspa;2142.7"
ladspa:hasLabel="Presets">
<ladspa:hasScale>
<ladspa:Scale>
<ladspa:hasPoint>
<ladspa:Point rdf:value="0" ladspa:hasLabel="AfterBurn
(Short)" />
</ladspa:hasPoint>
<ladspa:hasPoint>
<ladspa:Point rdf:value="1" ladspa:hasLabel="AfterBurn
(Long)" />
</ladspa:hasPoint>
<ladspa:hasPoint>
<ladspa:Point rdf:value="2" ladspa:hasLabel="Drum
Chamber"
/>
</ladspa:hasPoint>
<ladspa:hasPoint>
<ladspa:Point rdf:value="3" ladspa:hasLabel="Garage"
/>
</ladspa:hasPoint>
...
</ladspa:Scale>
</ladspa:hasScale>
</ladspa:InputControlPort>
</ladspa:hasPort>
</ladspa:SimulatorPlugin>
A host could read in each of the Point values, and present them in a
drop-down list for example.
-
Myk
Hi all,
TAP (Tom's Audio Plugins) 0.1-0 is released.
Currently four LADSPA plugins are available.
You can check them out at:
http://www.hszk.bme.hu/~st444/tap/tap.html
Hi Tom,
nice work!
I tested your plugins with Visecas (i. e. Ecasound) and I just wanted
to let you know that the way you set the MODE port_name for your TAP
Reverberator (as long as _SHOW_PRESET_NAMES_IN_GUI_ is defined)
confuses Ecasound's map-ladspa-list. (Without the #define there was no
problem)
I had a look at ladspa.h and it doesn't say anything about newlines in
port names so I must suppose it is 'officially correct'.
Nevertheless I'd guess that there are other LADSPA hosts which
implicitly assume that port names do not contain newlines (maybe I'm
wrong here, though).
Which leads to a for more interesting question:
Is this the way to deal with LADSPA presets?
For those of you who did not have a look at Tom's screenshots:
His TAP Reverberator has a port which makes it possible to select a
builtin preset.
While this is obviously possible I feel a little uncomfortable seeing
this.
After all many LADSPA hosts come with their own presets system
(Ardour, Ecasound, ...).
At least Tom's way makes sure that his presets can be used by all of
them. :)
So once more (I know this has been talked over before on this list):
Wouldn't it be very cool if all LADSPA hosts spoke the same language
with respect to effects presets? 
8:16 a.m.
New subject: [linux-audio-dev] LADSPA presets was: [ANN] new LADSPA plugins
On Sun, Jan 25, 2004 at 10:13:21 +0000, Mike Rawes wrote:
Yes, the library doesnt contain much support for things other than
heirachy, which was the most serious ommision at the time (I think it has
vestigial support for defaults/presets too). If anyone has feedback from
the host side I'd be more than happy to add better support for the other
features.
My plugins would benefit a lot from the point/scale thing Mike posted and
a universal preset format would help a lot.
There is now (undocumented I think) support for hosts adding data to the
lrdf representation and telling it to write out individual presets to
disk. Its possible that ardour uses this for preset handling, but I'm not
sure.
- Steve
So once more
(I know this has been talked over before on this list):
Wouldn't it be very cool if all LADSPA hosts spoke the same language
with respect to effects presets?
There already is, in the form of liblrdf (http://plugin.org.uk/lrdf).
This provides a way of:
* Arranging plugins into a hierarchy (Simulators/Reverbs, Time/Delays,
Frequency/Filters/Low Pass and so on)
* Defaults and Presets
* Labelling of port values (as in the TAP Reverb Presets port)
Host support of the hierarchy is fairly extensive, but the other featues
aren't AFAIK. 
9:26 a.m.
New subject: [linux-audio-dev] LADSPA presets was: [ANN] new LADSPA plugins
On Sun, 2004-01-25 at 07:12, Steve Harris wrote:
There is now (undocumented I think) support for hosts
adding data to the
lrdf representation and telling it to write out individual presets to
disk. Its possible that ardour uses this for preset handling, but I'm not
sure.
No, Ardour saves presets to individual XML files in a preset directory
subdivided into plugin directories named by their id.
Taybin
8:43 a.m.
New subject: [linux-audio-dev] LADSPA presets was: [ANN] new LADSPA plugins
On Sun, 25 Jan 2004, Mike Rawes wrote:
Thank you, this is just what i was searching for :))
Is this a way that is portable between hosts?
If it is, i guess i have to have a closer look at lrdf...
Tom
So once more
(I know this has been talked over before on this list):
Wouldn't it be very cool if all LADSPA hosts spoke the same language
with respect to effects presets?
There already is, in the form of liblrdf (http://plugin.org.uk/lrdf).
This provides a way of:
* Arranging plugins into a hierarchy (Simulators/Reverbs, Time/Delays,
Frequency/Filters/Low Pass and so on)
* Defaults and Presets
* Labelling of port values (as in the TAP Reverb Presets port)
Host support of the hierarchy is fairly extensive, but the other featues
aren't AFAIK.
An example of how that Preset port could be expressed:
<ladspa:ReverbPlugin rdf:about="&ladspa;2412">
<dc:title>TAP Reverberator</dc:title>
<ladspa:hasPort>
...
</ladspa:hasPort>
<ladspa:hasPort>
<ladspa:InputControlPort rdf:about="&ladspa;2142.7"
ladspa:hasLabel="Presets">
<ladspa:hasScale>
<ladspa:Scale>
<ladspa:hasPoint>
<ladspa:Point rdf:value="0" ladspa:hasLabel="AfterBurn
(Short)" />
</ladspa:hasPoint>
<ladspa:hasPoint>
<ladspa:Point rdf:value="1" ladspa:hasLabel="AfterBurn
(Long)" />
</ladspa:hasPoint>
<ladspa:hasPoint>
<ladspa:Point rdf:value="2" ladspa:hasLabel="Drum
Chamber"
/>
</ladspa:hasPoint>
<ladspa:hasPoint>
<ladspa:Point rdf:value="3" ladspa:hasLabel="Garage"
/>
</ladspa:hasPoint>
...
</ladspa:Scale>
</ladspa:hasScale>
</ladspa:InputControlPort>
</ladspa:hasPort>
</ladspa:SimulatorPlugin>
A host could read in each of the Point values, and present them in a
drop-down list for example.
3:44 p.m.
New subject: [linux-audio-dev] LADSPA presets was: [ANN] new LADSPA plugins
On Sun, 25 Jan 2004, Mike Rawes wrote:
A host could read in each of the Point values, and present them in a
drop-down list for example.
Done it. Hope i didn't overlook anything. I'm not sure if Ardour uses RDF
info for anything other than displaying the category column in the plugin
selector dialog, but let's hope there will be at least 1 host for which
this will solve the presets displaying problem :)
Updated to tap-0.1-1, with the docs patched of course. If someone has the
nerve to check my RDF file, i would be very thankful! I don't feel like an
RDF wizard yet, and won't want to cause more confusion with it (in case
it's plain wrong) than without it at all...
If someone has any more suggestions about how to achieve better host
independency, please tell :)
Tom
4:03 p.m.
New subject: [linux-audio-dev] LADSPA presets was: [ANN] new LADSPA plugins
On Sun, Jan 25, 2004 at 08:40:54 +0100, Tom Szilagyi wrote:
On Sun, 25 Jan 2004, Mike Rawes wrote:
I dont think any hosts use RDF for anything other than cetegories yet, but
I'm sure they will now. I'l try to find time to mark up mine in the same
way.
A host could read in each of the Point values, and present them in a
drop-down list for example.
Done it. Hope i didn't overlook anything. I'm not sure if Ardour uses RDF
info for anything other than displaying the category column in the plugin
selector dialog, but let's hope there will be at least 1 host for which
this will solve the presets displaying problem :) Updated to tap-0.1-1, with the docs patched of course.
If someone has the
nerve to check my RDF file, i would be very thankful! I don't feel like an
RDF wizard yet, and won't want to cause more confusion with it (in case
it's plain wrong) than without it at all...
Er, wow. that must be the quickest learning of RDF I've ever seen - if
ardour didnt scream and shout then its probably be OK, RDF syntax is quite
strict. In a wierd way.
I'm a bit busy next week, but I'l try to find some time to look at your
plugins and RDF - they sound cool.
- Steve
5:59 p.m.
New subject: [linux-audio-dev] LADSPA presets was: [ANN] new LADSPA plugins
On Sun, 2004-01-25 at 20:40, Tom Szilagyi wrote:
On Sun, 25 Jan 2004, Mike Rawes wrote:
Tom, I've never written a LADSPA plugin myself, so beware!
Would it be possible to move everything from tap_reverb_presets.h to rdf
presets?
It seems you'd have to pass all your filter data through ports.
But doing so one could create new filter presets without a recompile.
Does that make sense?
Control ports communicate single values only.
Could audio ports be used to transfer the filter data?
Hmmm, my guts tell me this is not 'LADSPA-ish'.
Jan
A host could read in each of the Point values, and present them in a
drop-down list for example.
Done it. Hope i didn't overlook anything. I'm not sure if Ardour uses RDF
info for anything other than displaying the category column in the plugin
selector dialog, but let's hope there will be at least 1 host for which
this will solve the presets displaying problem :)
Updated to tap-0.1-1, with the docs patched of course. If someone has the
nerve to check my RDF file, i would be very thankful! I don't feel like an
RDF wizard yet, and won't want to cause more confusion with it (in case
it's plain wrong) than without it at all...
If someone has any more suggestions about how to achieve better host
independency, please tell :)
7:23 p.m.
New subject: [linux-audio-dev] LADSPA presets was: [ANN] new LADSPA plugins
On Sun, Jan 25, 2004 at 10:55:24 +0100, Jan Weil wrote:
Tom, I've never written a LADSPA plugin myself, so
beware!
Would it be possible to move everything from tap_reverb_presets.h to rdf
presets?
It seems you'd have to pass all your filter data through ports.
But doing so one could create new filter presets without a recompile.
Does that make sense?
Control ports communicate single values only.
Could audio ports be used to transfer the filter data?
Hmmm, my guts tell me this is not 'LADSPA-ish'.
Yeah, it would be a pain for hosts to support.
- Steve
26 Jan
26 Jan
4:09 a.m.
New subject: [linux-audio-dev] LADSPA presets was: [ANN] new LADSPA plugins
On Sun, Jan 25, 2004 at 08:40:54PM +0100, Tom Szilagyi wrote:
On Sun, 25 Jan 2004, Mike Rawes wrote:
can you please change your versioning scheme to 0.1 0.2 ...
gentoo does not handle such versions very well.
now off to make an ebuild.
and then test the plugins with gAlan...
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
A host could read in each of the Point values, and present them in a
drop-down list for example.
Done it. Hope i didn't overlook anything. I'm not sure if Ardour uses RDF
info for anything other than displaying the category column in the plugin
selector dialog, but let's hope there will be at least 1 host for which
this will solve the presets displaying problem :)
Updated to tap-0.1-1, with the docs patched of course. If someone has the
nerve to check my RDF file, i would be very thankful! I don't feel like an
RDF wizard yet, and won't want to cause more confusion with it (in case
it's plain wrong) than without it at all... 
5:52 a.m.
New subject: [linux-audio-dev] LADSPA presets was: [ANN] new LADSPA plugins
Hallo,
torbenh(a)informatik.uni-bremen.de hat gesagt: // torbenh(a)informatik.uni-bremen.de wrote:
can you please change your versioning scheme to 0.1
0.2 ...
gentoo does not handle such versions very well.
Debian neither, it probably would become 0.1.0 and 0.1.1 anyways
there. ;)
ciao
--
Frank Barknecht _ ______footils.org__
25 Jan
25 Jan
6:28 a.m.
New subject: [linux-audio-dev] LADSPA presets was: [ANN] new LADSPA plugins
Hallo,
Jan Weil hat gesagt: // Jan Weil wrote:
On Sat, 2004-01-24 at 23:09, Tom Szilagyi wrote:
There are hosts which cannot use (white-)spaces at all when
communicating with LADSPA plugins, an example is Pd.
In Pd at least there is the alternative way to communicat which is by
using numbered portnames like "#1", "#2", ...
ciao
--
Frank Barknecht _ ______footils.org__
TAP (Tom's Audio Plugins) 0.1-0 is released.
Currently four LADSPA plugins are available.
Which leads to a for more interesting question:
Is this the way to deal with LADSPA presets?
For those of you who did not have a look at Tom's screenshots: His
TAP Reverberator has a port which makes it possible to select a
builtin preset. While this is obviously possible I feel a little
uncomfortable seeing this. After all many LADSPA hosts come with
their own presets system (Ardour, Ecasound, ...).
At least Tom's way makes sure that his presets can be used by all of
them. :)
8:40 a.m.
New subject: [linux-audio-dev] LADSPA presets was: [ANN] new LADSPA plugins
On Sun, 25 Jan 2004, Jan Weil wrote:
Hi Tom,
nice work!
I tested your plugins with Visecas (i. e. Ecasound) and I just wanted to
let you know that the way you set the MODE port_name for your TAP
Reverberator (as long as _SHOW_PRESET_NAMES_IN_GUI_ is defined) confuses
Ecasound's map-ladspa-list. (Without the #define there was no problem)
Yes, actually i was sure that the way i get the presets list displayed is
anything but not legal :)) But i didn't find any better way by looking at
ladspa.h (and the whole ladspa sdk), so this was the best i could think
of at the moment...
I had a look at ladspa.h and it doesn't say anything about newlines in
port names so I must suppose it is 'officially correct'.
Nevertheless I'd guess that there are other LADSPA hosts which
implicitly assume that port names do not contain newlines (maybe I'm
wrong here, though).
Which leads to a for more interesting question:
Is this the way to deal with LADSPA presets?
Certainly no... i have to apologise, because there certainly has to be a
better way than this that i don't know of at the moment.
Sorry for that, i know it's wrong and i'm seeking for solutions.
Tom
7:53 a.m.
Hallo,
Tom Szilagyi hat gesagt: // Tom Szilagyi wrote:
* TAP Reverberator
Actually no less than 38 reverberator effects,
ranging from Afterburn to Warehouse, including
small/medium/large rooms, halls, plates...
and more!
I cannot hear it. :( I'm testing the reverb in Pd but although I crank
up decay times and played with dry/wet I cannot hear a reverb. I can
hear a bit of (seemingly high pass) filtering, but no real
reverbaration at all. I should hear a hall when selecting say "Smooth
Hall", shouldn't I? Changing presets seems to work, as the filtering
gets different when changing presets, but here I wouldn't call this a
reverb. Maybe someone could provide a small ogg which shows what I
should hear?
ciao
--
Frank Barknecht _ ______footils.org__
8:49 a.m.
On Sun, 25 Jan 2004, Frank Barknecht wrote:
Hallo,
Tom Szilagyi hat gesagt: // Tom Szilagyi wrote:
Is it possible that the comb and/or allpass filters are turned off? I
don't know how Pd displays plugins (i don't know Pd at all, maybe i should take
a look) but there should be 4 toggle buttons somewhere saying "Comb
Filters", "Allpass Filters", "Bandpass Filter", "Enhanced
Stereo".
If all buttons are on, i don't have an idea right now, but think, think...
Tom
* TAP Reverberator
Actually no less than 38 reverberator effects,
ranging from Afterburn to Warehouse, including
small/medium/large rooms, halls, plates...
and more!
I cannot hear it. :( I'm testing the reverb in Pd but although I crank
up decay times and played with dry/wet I cannot hear a reverb. I can
hear a bit of (seemingly high pass) filtering, but no real
reverbaration at all. I should hear a hall when selecting say "Smooth
Hall", shouldn't I? Changing presets seems to work, as the filtering
gets different when changing presets, but here I wouldn't call this a
reverb. Maybe someone could provide a small ogg which shows what I
should hear?
9:15 a.m.
Hallo,
Tom Szilagyi hat gesagt: // Tom Szilagyi wrote:
On Sun, 25 Jan 2004, Frank Barknecht wrote:
In Pd, as it cannot use controls with spaces, you send messages like
"control #1 4" to set the first control to 4. I did set the Filter
controls this way to several values like 13 or 17. Should this turn
them on?
BTW: The other TAPs are working fine, http://footils.org/snd/echos.ogg
is a pluck playing through the stereo echo in Pd. (It's a bit big,
7.3M, currently uploading.)
ciao
--
Frank Barknecht _ ______footils.org__
I cannot hear it. :( I'm testing the reverb
in Pd but although I crank
up decay times and played with dry/wet I cannot hear a reverb. I can
hear a bit of (seemingly high pass) filtering, but no real
reverbaration at all. I should hear a hall when selecting say "Smooth
Hall", shouldn't I? Changing presets seems to work, as the filtering
gets different when changing presets, but here I wouldn't call this a
reverb. Maybe someone could provide a small ogg which shows what I
should hear?
Is it possible that the comb and/or allpass filters are turned off? I
don't know how Pd displays plugins (i don't know Pd at all, maybe i should take
a look) but there should be 4 toggle buttons somewhere saying "Comb
Filters", "Allpass Filters", "Bandpass Filter", "Enhanced
Stereo".
If all buttons are on, i don't have an idea right now, but think, think... 
9:44 a.m.
hi frank,
I read:
"control #1 4" to set the first control to
4. I did set the Filter
controls this way to several values like 13 or 17. Should this turn
them on?
analyseplugin says:
"Comb Filters" input, control, toggled, default 1
.
.
so #4 - #7 should be set to 1 I put a patch that works for me here:
http://test.pilot.fm/nolink/ladspa_tap_rev.pd
HTH
x
--
chris(a)lo-res.org Postmodernism is german romanticism with better
http://pilot.fm/ special effects. (Jeff Keuss / via ctheory.com)
10:29 a.m.
Hallo,
CK hat gesagt: // CK wrote:
analyseplugin says:
"Comb Filters" input, control, toggled, default 1
so #4 - #7 should be set to 1 I put a patch that works for me here:
http://test.pilot.fm/nolink/ladspa_tap_rev.pd
Ah, thank you, now it is working. Somehow I was under the impression,
that the filter controls set *how many* filters are in use... It
seems, also the other values should be set to decent values.
I do get warnings with some of your example values which exceed the
boundaries set by tap_reverb. I changed this and added a preset name
display (using the Pd external "pool") to an archive here:
http://footils.org/pkg/ladspa_tap_rev.tgz
Tom, although I only shortly listened to it: This is a wonderful
sounding and highly flexible reverb, something that was sorely missing
before. I don't like freeverb and gverb very much, but this will
become a favourite, a classic, I'm confident. So cool. Thank you a
lot.
ciao
--
Frank Barknecht _ ______footils.org__
10 Feb
10 Feb
11:38 p.m.
New subject: [linux-audio-dev] java-vst
Just ran across this at http://www.kvr-vst.com/index.php
http://sourceforge.net/projects/jvstwrapper/
I was thinking it might be useful to some{every}one.
26 Jan
26 Jan
5:26 p.m.
On Sat, Jan 24, 2004 at 11:09:42PM +0100, Tom Szilagyi wrote:
Hi all,
TAP (Tom's Audio Plugins) 0.1-0 is released.
Currently four LADSPA plugins are available.
You can check them out at:
http://www.hszk.bme.hu/~st444/tap/tap.html
I just checked the RDF and its fine, host authors using the soon to be
released 0.3.4 version of liblrdf should be able to render for eg. the
reverb presets as a dropdown list, hint hint :)
FWIW I wrote a quick perl script:
http://plugin.org.uk/src/metadata/txt2scale.pl and textfile:
http://plugin.org.uk/src/metadata/scale-points.txt to make generating the
scale RDF easier.
- Steve
7375
days inactive
7392
days old
linux-audio-dev@lists.linuxaudio.org
20 comments
9 participants
participants (9)
-
CK -
Frank Barknecht -
Jan Weil -
Mike Rawes -
RTaylor -
Steve Harris -
Taybin Rutkin -
Tom Szilagyi -
torbenh＠informatik.uni-bremen.de