Hi everybody,
I ported http://www.katjaas.nl/compander/compander.html to Faust.
It's a very nice sounding cross between an expander, compressor and
limiter.
Here it is: https://github.com/magnetophon/qompander
Enjoy, and let me know what you think of it!
Greetings,
Bart.
--
Hi Bart,
I think there is a confusion in the order of the values declared in your
sliders. Could you verify the declarations with :
hslider(str,cur,min,max,step).
Greetings,
Sarah
Le 2014-06-04 15:35, Bart Brouns a écrit :
> Hi everybody,
>
>
>
> I ported http://www.katjaas.nl/compander/co
x27;t know what you mean.
If those where your issues, they are solved now. :)
Otherwise, please explain.
Cheers,
Bart.
> Date: Thu, 05 Jun 2014 08:41:17 -0500
> From: sden...@grame.fr
> Subject: Re: [Faudiostream-users] qompander: A great sounding
> compressor/expan
Hi Sarah,
What I mean is: I don't care how small the steps are.
It seems to work for faust2jack.
Does it give you problems on other architectures?
Are there other reasons for not doing this?
I did notice nobody else is doing it...
Cheers,
Bart.
On Wed, 2014-06-11 at 09:27 +0200, Sarah Denoux wr
Ok I see want you mean. The problem is that most architectures don't support
null steps. We are discussing what to do with them, but for now, I think you
should better specify a non-null step.
Cheers,
Sarah
Le 11 juin 2014 à 09:34, Bart Brouns a écrit :
> Hi Sarah,
>
> What I mean is: I don'
Right. Thanks.
Fixed it, so finally everyone can have a listen, and tell me what they
think ;)
That reminds me of another question: sometimes it is useful to have an
expression denoting the smallest possible float bigger than 0.
Maybe this case is not the best example, but still.
I assume it's v
[ Oops, switched out of the list with last answer, back to it in case it
is of interest for the community ;) ]
Bart, yes I am linking that to the smallest number question, as it
allows you to get not only *small numbers* but numbers *as close to
zero* as you want, without dividing by zero. You
Doesn't that just change the problem from finding the smallest number to
finding the max clipping value?
I mean it's easy getting a small number, but I'd like an architecture
independent way of finding the smallest.
Or did I miss YOUR point? :)
On Fri, 2014-06-13 at 21:21 +0200, Vincent G. Liste
