White Noise
An ambient noise machine for OVOS - "play white noise" for sleep or focus. White, pink, and brown noise, all generated, not recorded.
Usage
"play white noise"
"play pink noise"
"start some background noise"
"stop the noise"
"spil hvid støj" (Danish)
"stop støjen" (Danish)
Why no rain/ocean/fan sounds
The original brief mentioned rain and ocean waves too. Those need genuinely loopable recordings - a hard seam or click at the loop point would be very noticeable in a sustained ambient track, a stricter sourcing requirement than the short one-shot clips ovos-skill-sound-like uses. White/pink/brown noise sidesteps the problem entirely: noise has no coherent waveform pattern for the ear to lock onto, so a generated clip looping back to its own start is inherently seamless. Rain/ocean are a real future possibility, but need actual recordings sourced and vetted for clean looping - not built here.
How the noise is generated
- White: uniform random samples (flat spectrum).
- Pink: Paul Kellet's economy IIR filter approximation (1/f spectrum) - a well-known, publicly documented DSP technique, not sourced from any particular library or artist.
- Brown/red: a clamped random walk (1/f² spectrum).
All three use a fixed random seed, so regenerating a given noise type produces byte-identical audio - deterministic, same as every other generated sound in this project family (clicks, tones, drum hits), even though the underlying content is "random".
Why "stop" doesn't stop instantly
Same underlying reason as
ovos-skill-tuning-fork:
play_audio() has no reliable way to interrupt an already-playing
sound. Noise loops by repeatedly re-triggering a 20-second generated
clip - "stop" prevents the next clip from starting, but the clip
already playing rings out to its natural end. Worst case, that's up
to 20 seconds - noticeably longer than the metronome/rhythm-box's
"before the next beat" stop latency, and disclosed rather than
glossed over.
Install
pip install ovos-skill-white-noise
Development
See DEVELOPMENT.md.
Category
Utility
Tags
#ambient #sleep #focus #white-noise #relaxation
Release files for ovos-skill-white-noise 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 | |
|---|---|---|---|
| ovos_skill_white_noise-0.0.1.tar.gz | 24.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ovos_skill_white_noise-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 49.9 kB
Release files / ovos_skill_white_noise-0.0.1.tar.gz
| Download URL | ovos_skill_white_noise-0.0.1.tar.gz |
|---|---|
| Size | 24.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e00b541b57aab20e4f9fab3b154c17283e4c58585d3b129971f6caab555d582c
|
|
BLAKE2b-256 checksum How to use checksums |
9b747272d3f603384b0513bfd557f1b236cd758db354a4ad15323935a9bdcbd3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 16, 2026.
Transparency logRelease files / ovos_skill_white_noise-0.0.1-py3-none-any.whl
| Download URL | ovos_skill_white_noise-0.0.1-py3-none-any.whl |
|---|---|
| Size | 25.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
44b3b1b8f388e3f3395dabd5def6bdc7ec57b8d61ba53821cfd785226d18bb39
|
|
BLAKE2b-256 checksum How to use checksums |
4901a17f7619e89122acad6e44facac9aac303473231be069022296207d0a35e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 16, 2026.
Transparency log