Hello again,
On Mon, 1 Sep 2008, Sergei Steshenko wrote:
>> So one option would be to remove the "clipping
>> detection" code altogether
>> from ecasound (as it's not as useful anymore, and
>> potentially misleading).
>
> Actually, I need clipping detection - this is because my plugins change
> peak level, furthermore, due to very complex nature of processing the
> change depends on input signal and is unpredictable.
but basicly the peak amplitude counter would be sufficient to you, or..?
Oh well, maybe I should just rename "Clipped samples" to "Possibly
clipped samples" or some such... any better naming ideas?
-- ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ecasound-list mailing list Ecasound-list@email-addr-hidden https://lists.sourceforge.net/lists/listinfo/ecasound-listReceived on Tue Sep 2 00:15:05 2008
This archive was generated by hypermail 2.1.8 : Tue Sep 02 2008 - 00:15:05 EEST