voicecast-worker
VoiceCast Worker lends your Mac to VoiceCast Studio. It pulls bite-size jobs from the studio's one job queue, does them on your GPU, and hands the results back:
- pictures: FLUX.2 klein on Apple silicon with mflux, the model kept loaded (an M2 Ultra draws a picture in about 6 s, an M2 Max in about 20 s);
- narration: one paragraph at a time with sonic-forge (Kokoro, and cloned voices on the Apple GPU), assembled by the studio with the same seeded pauses as a whole narration;
- picture checks and whole renders: only on machines the studio owner trusts (renders need a checkout of the studio app).
Your own Mac makes your own videos first: the worker alternates one job for someone else, one of yours ("give one, take one"). It never opens a port: it calls the studio over HTTPS, and files travel by short-lived presigned URLs.
Install
pipx install 'voicecast-worker[pictures,voice,menubar]'
voicecast-worker join <join-token> --server https://voicecast.studio
Get the join token from the studio's Developers page ("Join a Mac"), or with voicecast worker join. Then run it in a
terminal (voicecast-worker run) or from the menu bar (voicecast-worker menubar: Pause/Resume, Start at login).
Extras: pictures (mflux), voice (sonic-forge + Kokoro), clone (sonic-forge cloned voices on the Apple GPU),
menubar (rumps), all.
When it works
voicecast-worker settings --gpu-max 35 # only while the GPU is quiet (someone else's model, a game)
voicecast-worker settings --user-idle 300 # only when you've been away 5 minutes
voicecast-worker settings --gpu-share 0.5 # rest as long as it worked
voicecast-worker settings --hours "22:00-08:00"
voicecast-worker pause / resume
voicecast-worker status
voicecast-worker doctor # which engines this Mac can run
voicecast-worker leave
State lives in ~/.voicecast/worker/ (an older ~/.video-maker-worker/ is still read) (config.json with the machine token, status.json, worker.log).
Privacy
What a machine may see depends on its trust, set by the join token: a person's own Mac (self) only takes their own
jobs; a community Mac only takes public, bite-size jobs, never a cloned voice's reference, a real person's portrait,
a presenter's take or a whole render. Work on a Mac is not encrypted while it runs there; that is why private and
personal work only goes to machines that may see it.
Metadata
Release files for voicecast-worker 0.2.0
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 |
|---|---|---|---|---|
| voicecast_worker-0.2.0.tar.gz | 30.6 kB | Without provenance | Details for voicecast_worker-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| voicecast_worker-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for voicecast_worker-0.2.0-py3-none-any.whl |
Total release size: 60.6 kB
Release files / voicecast_worker-0.2.0.tar.gz
| Download URL | voicecast_worker-0.2.0.tar.gz |
|---|---|
| Size | 30.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
166e6480bd7b7e7dcca9102090f69c52fab5ba906cc16db2d1c838b068a91bd3
|
|
BLAKE2b-256 checksum How to use checksums |
64488e3c2461bed507a6fabc84dad325669730cfa3e3689cb7b3b09bcf9dc217
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Release files / voicecast_worker-0.2.0-py3-none-any.whl
| Download URL | voicecast_worker-0.2.0-py3-none-any.whl |
|---|---|
| Size | 30.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f2f3c633161d900ba09f6b562ab924cf5e0866559421ec0498f5b9dd7ab9248e
|
|
BLAKE2b-256 checksum How to use checksums |
41ec20b874d27574d9f787668129397b9bf2ba0ff8defcc357e6c6e5814abd61
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Security for voicecast-worker 0.2.0
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.