Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

F0, Failsafe F0 and wavelet F0 inaccurate results and limited range #70

Open
q-depot opened this issue Nov 6, 2014 · 1 comment
Open

Comments

@q-depot
Copy link
Contributor

q-depot commented Nov 6, 2014

Hi,

I noticed the none of the fundamental frequency features seems to work properly, I'm testing the function in 2 different ways:

  1. Classical music: I would expect it to be quite on spot with this kind of music, F0 simply doesn't detect anything it's always 0, the failsafe keep bouncing between 0 and a very large number which is definitely not even close to the actual value. Wavelet also rapidly bounce between 0 and an unrealistic value.
  2. Test audio track to swipe across a range: F0 only starts picking up the frequency near ~1700hz, the value then is accurate. Wavelet seem to be working fine with the test track, the value is accurate till ~1500hz, for higher frequencies it loose it dropping the value. Failsafe f0 as expected it reflects F0 or shows a huge number
@jamiebullock
Copy link
Owner

Hi, sorry it has been so long to reply, but I'm finally getting around to some LibXtract stuff. Do you still have the audio example you were testing with? If so can you post it somewhere? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants