17 Jan
2013
17 Jan
'13
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