Update README.md
Browse files
README.md
CHANGED
|
@@ -1,3 +1,103 @@
|
|
| 1 |
-
|
| 2 |
-
|
| 3 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# AutoVol (Tray)
|
| 2 |
+
|
| 3 |
+
AutoVol is a zero-config Windows tray app that **learns when you turn volume down** and then **automatically ducks volume** when the system audio gets louder than your learned “too loud” levels.
|
| 4 |
+
|
| 5 |
+
It’s designed to be:
|
| 6 |
+
|
| 7 |
+
* **Zero-touch**: run it and forget it
|
| 8 |
+
* **Self-healing**: tries multiple ways to measure system loudness (loopback audio → peak meter fallbacks)
|
| 9 |
+
* **Non-destructive**: stores its data in your local profile folder, not in system locations
|
| 10 |
+
|
| 11 |
+
## What it does
|
| 12 |
+
|
| 13 |
+
* Monitors “how loud the system output is” (best effort loopback capture; fallback peak meters).
|
| 14 |
+
* When you manually turn volume **down**, AutoVol records the loudness level at that moment.
|
| 15 |
+
* Later, if it detects loudness above your learned threshold, it gently reduces volume.
|
| 16 |
+
* Optional speech gating (if available) can reduce ducking during speech-like audio.
|
| 17 |
+
|
| 18 |
+
## Requirements
|
| 19 |
+
|
| 20 |
+
* Windows 10/11 (Windows 11 recommended)
|
| 21 |
+
* No admin required (for normal use)
|
| 22 |
+
|
| 23 |
+
## Install / Run (Release)
|
| 24 |
+
|
| 25 |
+
AutoVol is typically shipped as a **folder** (PyInstaller *onedir* build).
|
| 26 |
+
|
| 27 |
+
1. Download the release zip.
|
| 28 |
+
2. Extract it anywhere (ex: `C:\Apps\AutoVol\`).
|
| 29 |
+
3. Run: `AutoVol.exe`
|
| 30 |
+
4. Look for the **tray icon** (system tray / “hidden icons” area).
|
| 31 |
+
|
| 32 |
+
> **Important:** If the release contains a folder like `AutoVol\AutoVol.exe`, you must keep the **whole folder** together. Do not move only the `.exe` out by itself.
|
| 33 |
+
|
| 34 |
+
## Tray Menu
|
| 35 |
+
|
| 36 |
+
Right-click the tray icon for:
|
| 37 |
+
|
| 38 |
+
* **Observe only (no changes)** — AutoVol will monitor/learn but won’t set volume
|
| 39 |
+
* **Pause / Resume** — stops AutoVol from making adjustments (can restore to your resting volume)
|
| 40 |
+
* **Reset learning** — clears learned “turn-down” history
|
| 41 |
+
* **Open data folder** — opens the app’s local data folder
|
| 42 |
+
* **Quit** — exits cleanly
|
| 43 |
+
|
| 44 |
+
## Data / Logs Location
|
| 45 |
+
|
| 46 |
+
AutoVol stores its runtime data under:
|
| 47 |
+
|
| 48 |
+
`%LOCALAPPDATA%\AutoVol`
|
| 49 |
+
|
| 50 |
+
You’ll typically see:
|
| 51 |
+
|
| 52 |
+
* `autovol.log` — rotating logs
|
| 53 |
+
* `autovol_learn.json` — learned “turn-down” samples
|
| 54 |
+
* `autovol_events.jsonl` — event stream (volume changes, sampler changes, etc.)
|
| 55 |
+
* `autovol_crash.txt` — created only if a crash occurs
|
| 56 |
+
|
| 57 |
+
## Command-line Options
|
| 58 |
+
|
| 59 |
+
You can run the exe with options (useful for debugging):
|
| 60 |
+
|
| 61 |
+
* `--observe`
|
| 62 |
+
Start in observe-only mode (no volume changes).
|
| 63 |
+
|
| 64 |
+
* `--force-dryvol`
|
| 65 |
+
Don’t touch system volume (debug mode; logs/stats still run).
|
| 66 |
+
|
| 67 |
+
* `--reset`
|
| 68 |
+
Reset learning before starting.
|
| 69 |
+
|
| 70 |
+
* `--no-autoinstall`
|
| 71 |
+
Disable auto-install of missing Python dependencies (mostly relevant when running from source).
|
| 72 |
+
|
| 73 |
+
Example:
|
| 74 |
+
|
| 75 |
+
```bash
|
| 76 |
+
AutoVol.exe --observe
|
| 77 |
+
```
|
| 78 |
+
|
| 79 |
+
## Building from Source (Developer)
|
| 80 |
+
|
| 81 |
+
Basic steps (example):
|
| 82 |
+
|
| 83 |
+
1. Create/activate a venv
|
| 84 |
+
2. Install requirements
|
| 85 |
+
3. Run:
|
| 86 |
+
|
| 87 |
+
```bash
|
| 88 |
+
python autovol_tray.py
|
| 89 |
+
```
|
| 90 |
+
|
| 91 |
+
If you package with PyInstaller, you’ll usually distribute the **onedir** output: `dist\AutoVol\`
|
| 92 |
+
|
| 93 |
+
## Troubleshooting
|
| 94 |
+
|
| 95 |
+
* **No tray icon:** Check the Windows tray “hidden icons” area.
|
| 96 |
+
* **No loudness detection / stuck on fallback:** Some machines/drivers don’t support loopback capture; AutoVol will fall back to peak meters. Check `%LOCALAPPDATA%\AutoVol\autovol.log`.
|
| 97 |
+
* **It’s too aggressive:** Use *Observe only* while it learns more “turn-down” events, or reset learning and re-train.
|
| 98 |
+
|
| 99 |
+
## License
|
| 100 |
+
|
| 101 |
+
MIT License.
|
| 102 |
+
|
| 103 |
+
|