repitch | a MIDI-controlled audio harmonizer | Audio Utils library

by maxwellpollack C++ Version: v1.0.2 License: No License

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | repitch Summary

repitch is a C++ library typically used in Audio, Audio Utils applications. repitch has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

a MIDI-controlled audio harmonizer

Support

Quality

Security

License

Reuse

Support

repitch has a low active ecosystem.

It has 35 star(s) with 1 fork(s). There are 1 watchers for this library.

It had no major release in the last 12 months.

repitch has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of repitch is v1.0.2

Quality

repitch has no bugs reported.

Security

repitch has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

repitch does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

repitch releases are available to install and integrate.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of repitch

Get all kandi verified functions for this library.

repitch Key Features

No Key Features are available at this moment for repitch.

repitch Examples and Code Snippets

No Code Snippets are available at this moment for repitch.

Community Discussions

Trending Discussions on repitch

Lots of noise after repitching recorded file using raw audio data and simpleaudio

Both fast and very slow scipy.signal.resample with the same input size

QUESTION

Lots of noise after repitching recorded file using raw audio data and simpleaudio

Asked 2020-Dec-01 at 11:53

I have written a very basic script to repitch an audio file, which I import using simpleaudio. I am not worried about preserving audio speed; all I need is a simple pitch-shift.

What I am doing is resampling the audio using linear interpolation, and from what I've read, this should be enough. For example, you can see here that the pitch of the audio is shifted, but it retains a very similar shape:

The blue line is the initial waveform, the orange is the pitch-shifted waveform. It all looks exactly how I would expect.

So far so good. However, when playing it back through simpleaudio's interface, the shifted wave is really really noisy. Interestingly though, this doesn't happen if I shift by an integer ratio.

See the code below for my implementation (there's not much, I promise):

...

ANSWER

Answered 2020-Dec-01 at 11:53

wav files are little-endian, not big-endian.

struct should be using ", not ">h".

This wasn't a problem when using integer pitch-shift ratios, because there wasn't actually any interpolation happening in that case - it was just selecting every nth sample. And since each conversion function was the reverse of the other, it was like nothing had every changed.

But as soon as you start to interpolate, you get problems, because you're now working with 'reversed' data in a non-reversed way.

Anyway, my algorithm now works perfectly.

Source https://stackoverflow.com/questions/63092252

QUESTION

Both fast and very slow scipy.signal.resample with the same input size

Asked 2019-Feb-22 at 20:54

According to the documentation of scipy.signal.resample, the speed should vary according to the length of input:

As noted, resample uses FFT transformations, which can be very slow if the number of input samples is large and prime, see scipy.fftpack.fft.

But I have very different timings (factor x14) with the same input, and only a small variation of desired output size:

...

ANSWER

Answered 2018-Sep-14 at 19:59

The docstring, somewhat misleadingly, states one part of the story. The resampling process consists of FFT (input size), zero-padding, and inverse FFT (output size). So an inconvenient output size will slow it down just as much as an inconvenient input size will.

Cris Luengo suggested using direct interpolation in the spatial domain, which should be faster here. For example, ndimage.zoom uses it (cubic spline interpolation by default):

Source https://stackoverflow.com/questions/52336754

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install repitch

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: