beatscore
A small libary that converts structured text into short music clips by mapping properties of the input (intensity, repetition, pace, tone, coherence) into promptable audio generation using the ElevenLabs Music API
The goal is to experiment how differences in source material can be perceptible in sound.
Example
- Opinionated text → more forceful, higher energy
- Neutral news → more structured, calmer
- Fragmented text → faster, less predictable
API
run_digest(sources, source_type, output_dir)
where:
- sources: a dictionary of articles, feeds, or any text.
- source_type: one of 'news' or 'speech'. News expects sources to be a dictionary of rss feeds.
- output_dir: the location for generated files
News RSS Example:
from beatscore import run_digest
sources = {
"reuters": "http://feeds.reuters.com/reuters/topNews",
"bbc": "http://feeds.bbci.co.uk/news/rss.xml",
"nyt": "https://rss.nytimes.com/services/xml/rss/nyt/HomePage.xml",
"rollingStone": "https://www.rollingstone.com/feed/"
}
run_digest(sources, "news", output_dir="./output")
Speech example:
from beatscore import run_digest
sources = {
"mlk_dream": "https://kr.usembassy.gov/martin-luther-king-jr-dream-speech-1963/", #https://www.americanrhetoric.com/speeches/mlkihaveadream.htm",
"gettysburg": "https://www.abrahamlincolnonline.org/lincoln/speeches/gettysburg.htm",
"churchill_beaches": "https://winstonchurchill.org/resources/speeches/1940-the-finest-hour/we-shall-fight-on-the-beaches/",
}
run_digest(sources, "speech", output_dir="./output")
Setup
You'll need three API keys:
ELEVENLABS_API_KEY— for music generationHF_TOKEN— for embeddings and emotion modelsANTHROPIC_API_KEY— for prompt engineering with Claude
Set them as environment variables or pass directly to functions.
Installation
Install latest from the GitHub repository:
$ pip install git+https://github.com/funkstop/beatscore.git
or from pypi
$ pip install beatscore
Documentation
Documentation can be found hosted on this GitHub repository's pages. Additionally you can find package manager specific guidelines on pypi.
Metadata
Release files for beatscore 0.0.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 |
|---|---|---|---|---|
| beatscore-0.0.1.tar.gz | 15.6 kB | Without provenance | Details for beatscore-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| beatscore-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for beatscore-0.0.1-py3-none-any.whl |
Total release size: 31.4 kB
Release files / beatscore-0.0.1.tar.gz
| Download URL | beatscore-0.0.1.tar.gz |
|---|---|
| Size | 15.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
522e9da816d97a9694e6dcdb9482e717203ee7c112eada436b72c783c137b657
|
|
BLAKE2b-256 checksum How to use checksums |
77ae4215fb3ce5f69161b036a183eff9f8bf0f88bde3390cf893d420b6617e4b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / beatscore-0.0.1-py3-none-any.whl
| Download URL | beatscore-0.0.1-py3-none-any.whl |
|---|---|
| Size | 15.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a625568ea0efb0bfe074ce50104b4013de5cd7e58de694de26a2260df21ba45a
|
|
BLAKE2b-256 checksum How to use checksums |
a951617e0a32f28df7a5179071f1dc24e7122ebcffa9a3628c092676dd91420e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for beatscore 0.0.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.