On Wed, Oct 19, 2011 at 8:53 AM, Jeremy Jongepier <jeremy@autostatic.com> wrote:
On 10/19/2011 02:44 PM, Brett McCoy wrote:
 
>> Completely rebuilding Jamin with single plugins will consume even more cpu
>> than jamin itself. The reason is that jamin is actually built from plugins
>> (the look-ahead and the compressors are plugins) but also merges plugins
>> internally to optimize for speed...
>>
>
> I haven't had issues per se with CPU resources (whern I am using Jamin, I am
> not doing anything else except recording the output), but what are the
> alleged flaws in Jamin?
>

http://lists.linuxaudio.org/pipermail/linux-audio-user/2010-May/069653.html

I think it was explained in another thread but as I am no DSP expert I
could be wrong. This was the other thread:
http://lists.linuxaudio.org/pipermail/linux-audio-user/2010-September/072897.html

Sorry to dig this up and maybe I shouldn't say flaws, I guess it's about
different interpretations on how filtering is done.

Most of that is over my head. What does this translate to when I am mastering a stereo mix with Jamin?

--
Brett W. McCoy -- http://www.electricminstrel.com
------------------------------------------------------------------------
"In the rhythm of music a secret is hidden; If I were to divulge it, it would overturn the world."
    -- Jelaleddin Rumi