16 Jan
2013
16 Jan
'13
12:14 p.m.
This release of CAPS, likely to be the last for some time unless major
bugs surface, brings
* performance and sound improvements for AmpVTS,
* selection of peak or RMS measurement in Compress,
* 4x128 saturating mode for Compress,
* 2x,4x and 8x oversampling for AutoFilter, and
* more filter types for AutoFilter.
The bug in 0.9.4 that rendered the AmpVTS tonestack selection control
inoperative has been rectified.
Probably appreciated only by its author or other digital
palaeontologists, the CabinetIII plugin has been reintroduced.
CabinetIV is still recommended over it because of the wider range of
models, sample rate independency and lesser computational demands.
Sample rate dependencies have been removed from NoiseGate, and its
attack time is now configurable.
http://quitte.de/dsp/caps.html
http://quitte.de/dsp/caps.html#AmpVTS
http://quitte.de/dsp/caps.html#Compress
http://quitte.de/dsp/caps.html#AutoFilter
http://quitte.de/dsp/caps.html#NoiseGate
16 Jan
16 Jan
12:37 p.m.
Hello Tim1
Thanks a lot for this release. I'm looking forward to test the ampVTS. I
haven't yet checked out the cabinetIV, but it is up on my list. I decided to
give Caps the advantage over buying a V-Amp3, good as it might be. Probably
not as many settings, but quite nice for a synth. :-)
Warm regards
Julien
----------------------------------------
http://juliencoder.de/nama/music.html
12:40 p.m.
Hello again!
I'm sorry for a hasty send there. I already have a compilation error. It's
all about click.cc. Starting in line 154. It seems, that you introduced a
template <int waves>, but didn't specify the template parameter.
Best wishes
Julien
----------------------------------------
http://juliencoder.de/nama/music.html
10:24 p.m.
Hello
I think the AutoFilter has something wrong.
Whatever settings I use it always yields the same low frequency sound, as
low pass filter. It happens even with the other mode - bandpass.
According to the webpage doc, in default settings it should work as a
AutoWah but it doesn't.
Any ideas?
Kind regards
Gianfranco
2013/1/16 Tim Goetze <tim(a)quitte.de>
This release of CAPS, likely to be the last for some
time unless major
bugs surface, brings
* performance and sound improvements for AmpVTS,
* selection of peak or RMS measurement in Compress,
* 4x128 saturating mode for Compress,
* 2x,4x and 8x oversampling for AutoFilter, and
* more filter types for AutoFilter.
The bug in 0.9.4 that rendered the AmpVTS tonestack selection control
inoperative has been rectified.
Probably appreciated only by its author or other digital
palaeontologists, the CabinetIII plugin has been reintroduced.
CabinetIV is still recommended over it because of the wider range of
models, sample rate independency and lesser computational demands.
Sample rate dependencies have been removed from NoiseGate, and its
attack time is now configurable.
http://quitte.de/dsp/caps.html
http://quitte.de/dsp/caps.html#AmpVTS
http://quitte.de/dsp/caps.html#Compress
http://quitte.de/dsp/caps.html#AutoFilter
http://quitte.de/dsp/caps.html#NoiseGate
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
--
Antes de imprimir pense em sua responsabilidade e compromisso com o MEIO
AMBIENTE!
17 Jan
17 Jan
9:57 a.m.
Ciao Gianfranco,
I think the AutoFilter has something wrong.
[...]
According to the webpage doc, in default settings it
should work as a
AutoWah but it doesn't.
You're right, the last round of changes have reduced the range of
automatic filter modulation to the point of it being virtually
inaudible. Sorry!
The attached patch restores the modulation range (and it increases the
default filter gain) so the effect becomes much more pronounced.
Grazie,
Tim
4:58 p.m.
That worked fine!!! Thanks!
One more thing. The new Cabinets have their gain limited to 0 dB.
The old ones had 24 dB as the upper limit, which was very practical, since
enabling the plugin would give me the tone improvement with a cost os some
atenuation which would be compensated with some extra gain (about 9dB in my
use).
Is there a reason for this new limit of 0 dB?
Cheers
Gian
2013/1/17 Tim Goetze <tim(a)quitte.de>
Ciao Gianfranco,
--
Antes de imprimir pense em sua responsabilidade e compromisso com o MEIO
AMBIENTE!
I think the AutoFilter has something wrong.
[...]
According to the webpage doc, in default settings
it should work as a
AutoWah but it doesn't.
You're right, the last round of changes have reduced the range of
automatic filter modulation to the point of it being virtually
inaudible. Sorry!
The attached patch restores the modulation range (and it increases the
default filter gain) so the effect becomes much more pronounced.
Grazie,
Tim
5:19 p.m.
[Gianfranco Ceccolini]
One more thing. The new Cabinets have their gain
limited to 0 dB.
The old ones had 24 dB as the upper limit, which was very practical, since
enabling the plugin would give me the tone improvement with a cost os some
atenuation which would be compensated with some extra gain (about 9dB in my
use).
Is there a reason for this new limit of 0 dB?
There's no technical reason, and it's safe to change the upper limit,
line 397 in Cabinet.cc.
Cheers, Tim
5:22 p.m.
Great!
Thanks for your attention
2013/1/17 Tim Goetze <tim(a)quitte.de>
[Gianfranco Ceccolini]
--
Antes de imprimir pense em sua responsabilidade e compromisso com o MEIO
AMBIENTE!
One more thing. The new Cabinets have their gain
limited to 0 dB.
The old ones had 24 dB as the upper limit, which was very practical, since
enabling the plugin would give me the tone improvement with a cost os some
atenuation which would be compensated with some extra gain (about 9dB in
my
use).
Is there a reason for this new limit of 0 dB?
There's no technical reason, and it's safe to change the upper limit,
line 397 in Cabinet.cc.
Cheers, Tim
6:21 p.m.
Hi Tim,
Is there any special reason for you to set the Properties variable
inside ChorusI::setup() method? The setup() will always call the
autogen() method that will set Properties = HARD_RT anyway.
I ask this because ChorusI is the only plugin that sets it inside
setup() and it will break when I use a different Descriptor that
doesn't support the Properties attribute (talking about porting to LV2
here :)), and since it isn't doing much (unless I am missing something
here), it's ok to remove that line from the plugin code and let it to
the descriptor. What do you think?
Thanks for the amazing suite :D
Bruno
On Thu, Jan 17, 2013 at 2:21 PM, Gianfranco Ceccolini
<franconassis(a)gmail.com> wrote:
Great!
Thanks for your attention
2013/1/17 Tim Goetze <tim(a)quitte.de>
--
Bruno Gola <brunogola(a)gmail.com>
http://bgo.la/ | +55 11 9-5552-3599
[Gianfranco Ceccolini]
--
Antes de imprimir pense em sua responsabilidade e compromisso com o MEIO
AMBIENTE!
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
One more thing. The new Cabinets have their gain
limited to 0 dB.
The old ones had 24 dB as the upper limit, which was very practical,
since
enabling the plugin would give me the tone improvement with a cost os
some
atenuation which would be compensated with some extra gain (about 9dB in
my
use).
Is there a reason for this new limit of 0 dB?
There's no technical reason, and it's safe to change the upper limit,
line 397 in Cabinet.cc.
Cheers, Tim
9:05 p.m.
[Bruno Gola]
Is there any special reason for you to set the
Properties variable
inside ChorusI::setup() method? The setup() will always call the
autogen() method that will set Properties = HARD_RT anyway.
Perfectly OK to remove that line, it's only there because ChorusI got
backforwardported, and I didn't remember it's not necessary anymore.
Thanks for the amazing suite :D
Thanks for liking it :D
Tim
4281
days inactive
4282
days old
linux-audio-dev@lists.linuxaudio.org
9 comments
4 participants
participants (4)
-
Bruno Gola -
Gianfranco Ceccolini -
Julien Claassen -
Tim Goetze