Installation/Requirements
All requirements are in requirements.txt. They are numpy for array manipulations, librosa for audio processing, and scipy for it's wavefile export.
Installation, currently, is all via github. To download the cli tool run
pip3.6 install tuning-fork-cli
or, if you just want the Python Library Code, run
pip3.6 install tuning-fork
This project does require python3.6 since I use mypy annotations to help me out.
CLI Usage
usage: tuning-fork [-h] [--bpm BPM] [--out OUT] [--play] wavfile musicfile
Autotune a wavfile to a .music file
positional arguments:
wavfile The path to the wavfile you want to autotune.
musicfile The path to the music file you want the wavfile autotuned to.
optional arguments:
-h, --help show this help message and exit
--bpm BPM The bpm you want the song to play at.
--out OUT The desired output file.
--play Automatically play after wavfile is created.
Python Usage
To import the entire package just include
import tuning_fork ((as tf))
in your imports and all code will be loaded!
tuning_fork itself contains methods for pitch shifting, so, to shift a wav to a .music, you can run
TF = tf.TuningFork
TF.sampleWAVFileIntoMusic("wavfilename", "musicfilename", (bpm))
and that will return a librosa style ndarray that represents the WAV encoding of the autotuned song.
Along with normal functions, tuning_fork also exposes analysis and parseMusic.
-
analysis
- Available via
from tuning_fork.tools.analysis import Analysis - Deals with the analysis of a wavfile.
- Most useful exports are
startingNoteandstartingNoteFromFile- These methods take in some reference to a wavfile (depending on the function) and returns the approximate starting note frequency of the song.
- Available via
-
parseMusic
- Available via
from tuning_fork.tools.parseMusic import ParseMusic - Deals with parsing .music files
- Fairly useful all around, take a look around the source or the
help(parseMusic)to find what will fit you!
- Available via
Metadata
Release files for tuning-fork 1.7.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tuning_fork-1.7.1.tar.gz | 6.3 kB | Without provenance | Details for tuning_fork-1.7.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tuning_fork-1.7.1-py3-none-any.whl | Python 3 | none | any | Details for tuning_fork-1.7.1-py3-none-any.whl |
Total release size: 14.1 kB
Release files / tuning_fork-1.7.1.tar.gz
| Download URL | tuning_fork-1.7.1.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e30bcf3fbd7a11d25e55266919af12a3726620fb7b8c8f3ca9d014441aca158
|
|
BLAKE2b-256 checksum How to use checksums |
4c1e5c8ef3f46783fbab57ee1053c6918d31729d5b02a4554296cc239e3518bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / tuning_fork-1.7.1-py3-none-any.whl
| Download URL | tuning_fork-1.7.1-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a6a03f230b871fed29635762138c4300da411d69b6f39a770ca9f610427c811f
|
|
BLAKE2b-256 checksum How to use checksums |
6c521ad7c306a51da753b911459263d51b962ce02b7c2d4d5faa99688d4b90aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for tuning-fork 1.7.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.