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

Exporting the excite function to Python #31

Merged
merged 3 commits into from
Nov 26, 2015
Merged

Conversation

jfsantos
Copy link
Contributor

This, together with r9y9/SPTK#11, adds the pulse excitation method from SPTK to pysptk.

@jfsantos
Copy link
Contributor Author

Note: tests are breaking because this is still getting the version of SPTK without the changes I made. I expect these tests to pass as soon as you accept r9y9/SPTK#11.

@r9y9
Copy link
Owner

r9y9 commented Oct 21, 2015

This is great! I don't have much time right now, but I will review this and r9y9/SPTK#11 in a few days. Thanks!

@jfsantos
Copy link
Contributor Author

I will also need the RAPT pitch estimator for my current project, so I'll
probably submit a PR for exporting it as well soon. It seems it will be
easier than this one :)

João Felipe Santos

On 21 October 2015 at 08:49, Ryuichi YAMAMOTO notifications@github.com
wrote:

This is great! I don't have much time right now, but I will review this
and r9y9/SPTK#11 r9y9/SPTK#11 in a few days.
Thanks!


Reply to this email directly or view it on GitHub
#31 (comment).

@@ -2637,6 +2637,18 @@ def mglsadf(x, np.ndarray[np.float64_t, ndim=1, mode="c"] b not None,

return _mglsadf(x, &b[0], order, alpha, stage, &delay[0])

### Excitation ###
def excite(np.ndarray[np.float64_t, ndim=1, mode = "c"] pitch, frame_period=100, interp_period=1, gaussian=False, seed=1):
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hopsize instead of frame_period? or rename hopsize to frame_period in swipe for naming consistency.

@r9y9
Copy link
Owner

r9y9 commented Oct 23, 2015

Could you add docstrings similar to other functions? The docstrings format in pysptk is under numpydoc style, I believe. In particular, I would like to document what pitch really means, since the SPTK pitch command outputs three kinds of pitch (see /bin/pitch/pitch.c#L71-L74) and I guess pysptk.excite assumes output format 0. It is actually different from that of pysas's excite assumes.

As for the docs, docstrings are automatically retrieved by sphinx and doc is generated if autosummary directive is found in the module __doc__. See example for sptk.pyx#L74-L79. Thanks!

@r9y9 r9y9 added this to the 0.1.4 milestone Oct 23, 2015
@jfsantos
Copy link
Contributor Author

Now we're just missing docstrings. I'll get that sorted out soon!

@r9y9
Copy link
Owner

r9y9 commented Nov 26, 2015

@jfsantos Can I merge this? If you don't have time, I can add docstrings after merging.

@jfsantos
Copy link
Contributor Author

jfsantos commented Nov 26, 2015 via email

r9y9 added a commit that referenced this pull request Nov 26, 2015
Exporting the excite function to Python
@r9y9 r9y9 merged commit c9dca94 into r9y9:master Nov 26, 2015
@r9y9
Copy link
Owner

r9y9 commented Nov 26, 2015

Thanks for your contribution!

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

Successfully merging this pull request may close these issues.

2 participants