Re: kNewTimePitchParam_Overlap and kNewTimePitchParam_EnablePeakLocking
Re: kNewTimePitchParam_Overlap and kNewTimePitchParam_EnablePeakLocking
- Subject: Re: kNewTimePitchParam_Overlap and kNewTimePitchParam_EnablePeakLocking
- From: Edward Agabeg <email@hidden>
- Date: Fri, 22 Jan 2016 23:08:53 -0500
|
Hello all,
Does anybody know what kNewTimePitchParam_EnablePeakLocking and kNewTimePitchParam_Overlap time scale parameters are and more important how do they influence the result of the time scale. There is little to none documentation regarding it and I suspect prior knowledge of the time scale algorithm is required to fully understand these without the docs.
Overlapping could refer to window overlapping? But that’s just a wild guess. As for peak locking, I have no idea.
Peak locking enforces phase coherence of spectral peaks. The results are a less "phasey" or reverberant sound, sometimes also called loss of presence. Turning on this option does add some additional expense.
And yes, overlap is the number of overlapped spectral windows that are used to produce the output. The value of overlap is directly proportional to CPU cost. More overlaps can make smooth passages sound smoother. For percussive sound, a lower overlap may be better.
regards,
edward
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden