[Clam-devel] CLAM_OPTIMIZE bug fixed

Pau Arumi parumi at iua.upf.edu
Fri Sep 7 01:16:51 PDT 2007


En/na Hernán Ordiales ha escrit:
> On 9/6/07, Pau Arumi <parumi at iua.upf.edu> wrote:
>> En/na Hernán Ordiales ha escrit:
>>> On 9/5/07, Hernán Ordiales <h at ordia.com.ar> wrote:
>>> [snip]
>>>>>> After some testing I reverted a change on FundFreqDetectConfig that
>>>>>> created artifacts when setting
>>>>>> the CLAM_OPTIMIZE flag. All other optimizations sound good to me but I
>>>>>> am testing offline (non-Network mode)
>>>>>> so further testing may be needed.
>>>> nice, i will check how sounds now
>>> yes, definitely sounds much better now (tested at NE with harmonizer
>>> and pitch-shift networks)
>>> (optimize_and_lose_precision flag)
>> example online?
> 
> ok :-)
> 
> here you have both versions pitch-shifted with values 1 , 1.3 and 1.5:
> http://h.ordia.com.ar/tmp/clam/index.php?folder=Y29tcGFyaXNvbg==
> 

But still sounds with artefacts and bubbling effect in contrast to
the SMSTools one. Both versions (default, optimize) seems very
similar to me.

I think we should need to compare the processing done in SMSTools
--segment wise-- and the one in streaming --independent frames.

Pau





More information about the clam-devel mailing list