I'm not really sure what to do with the peak controller, though. It seems like it's not actually a "peak" controller - looking at the codebase, it actually takes the RMS of each period of audio, then updates the controller from that. I have a feeling it's written this way to overcome earlier limitations and lack of sample-exactness...
But now, I don't know if I should change that - I think it'd be better if it worked in a similar way to Dynamics Processor, keeping track of actual peaks, but if I change it so drastically now it might break earlier projects... So what to do - should we have a second, new peak controller? Rename the old one as "classic peak controller" or something... ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ LMMS-devel mailing list LMMS-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lmms-devel
