Closed siefkenj closed 3 years ago
Hey Jason,
Thank you for yet another contribution! :) Just wanted to let you know I'm in the middle of a big move and wasn't able to look at it yet. Give me a few more days to settle in and I'll review/merge it. After that it would probably a good opportunity to tag a new release to Cargo, since we have the new detector and the improved docs
Good luck on the move!
I think another nice-to-have for the next release would be a query interface so Javascript code could get a list of all available algorithms.
I'm currently working on setting up some benchmarks (similar to the ones done in the original YIN/etc. papers), and I've gotten a bit distracted updating plotters
to make prettier charts...
@alesgenova Any update on this?
This PR adds basic documentation for the pitch detectors.
It needs a rust version >=
1.48
to compile the docs correctly. I used tips from rust-latex-doc-minimal-example to allow the rendering of LaTeX formulas in the docs. Unfortunately, because of the configuration, only the docs ofpitch-detection
can be built...That is, you must use the commandto successfully build the docs.
I had some questions/comments when going through and documenting things.
internals
from the docs. But, it is still exported aspub
. Should this be the case? It would be good if people don't rely on internals...Pitch
frominternals
, since I hidinternals
.utils
be exported publicly?::new()
function. Should this be moved to thePitchDetector
trait? I don't know the convention in Rust about having::new()
on a general trait vs. just doing it as a struct-specific trait each time...