Music bot

Plays music in the room's call. Everyone in the call hears it, and each person sets the bot's volume just for themselves (right-click its name). It plays:

• links: YouTube, SoundCloud, Bandcamp and anything else yt-dlp opens (playlists too, up to 50 songs). Spotify, Deezer, Apple Music and Tidal song links become a search by the song's name;
• a search by name: !play popular monster plays the first result, and !search shows five to pick with the buttons;
• songs from a folder (mp3, flac, ogg, opus, m4a, wav...), found by name;
• files sent in the room: reply to the file with !play;
• online radios, from your own list.

It answers with cards: the "now playing" card has the cover, a progress bar that moves by itself and buttons (pause, skip, stop, shuffle, loop) that anyone in the room can click. The card changes in place when something changes, instead of filling the chat.

The sound goes as the bot's voice (stereo Opus, 128 kbit/s, 20 ms packets): the streamer pays nothing for it, and people watching from a browser hear it too.

Running it#

You need Python 3.10+, ffmpeg and the repository (or just the bots/musica folder with the SDK installed). yt-dlp is optional: without it the bot only plays the folder, room files, radios and direct audio links.

sudo apt install ffmpeg python3-venv        # (Arch: pacman -S ffmpeg python)
git clone https://github.com/RshaCuDeVidro/telinha
cd telinha
python3 -m venv .venv && .venv/bin/pip install ./sdk/python yt-dlp
.venv/bin/python bots/musica/musica.py "telinha://my.room:7777#password" --folder ~/Music

The Portuguese spellings of the options from 3.3 (--pasta, --nome, --canal, --token-bots, --prefixo) still work.

Commands#

The 3.3 Portuguese commands work as aliases (!tocar, !fila, !pular, !parar, !vem...).

Folder search ignores accents and case: !play cancao finds "Canção do Mar.mp3", and several words must all appear. The order is: a radio with that name, then the folder, then the internet.

Bringing the bot to any channel#

!join with no name brings the bot to the call of whoever asked. Since a command typed in a channel only reaches the bot if it's in that channel, from anywhere else send it in private:

/msg Música !join

Private messages reach the bot from any channel, and it comes to the call you're in (or to your channel, if you're not in a call). !join games also works from wherever the bot is. The name doesn't need the accent or the capital letter (/msg musica !join finds Música), and the app has a shortcut: right-click the bot → Bring to my call.

You don't even need !join: /msg Música !play song name from someone in a call brings the bot there and plays it (if it's playing for another call, the song goes to that queue and it tells you).

Radios#

A file with name = address per line:

# radios.txt
lofi = https://example.com/lofi.mp3
jazz = https://example.com/jazz.aac

python3 bots/musica/musica.py "telinha://..." --radios radios.txt

And in the room: !radio lofi, or !radios and a button. The repository has an example with SomaFM stations, bots/musica/radios-somafm.txt.

YouTube on a server#

YouTube refuses many data-center IPs ("Sign in to confirm you're not a bot"). When that happens the bot remembers it for 30 minutes and plays the same song from SoundCloud (by name), so !play keeps working; the card's footer says where the sound came from.

To have YouTube itself on a VPS, give the bot the cookies of a logged-in browser (preferably a throwaway account), exported in the Netscape format (the "Get cookies.txt LOCALLY" extension does this):

musica.py "telinha://..." --cookies /etc/telinha-yt-cookies.txt

Keeping it on a VPS#

Next to the dedicated server, with systemd. Create a user just for it and a music folder:

# /etc/systemd/system/telinha-musica.service
[Unit]
Description=telinha: music bot
After=network-online.target telinha.service
Wants=network-online.target

[Service]
User=musica
WorkingDirectory=/opt/telinha
EnvironmentFile=/etc/telinha-musica.env
ExecStart=/opt/telinha/.venv/bin/python bots/musica/musica.py
Restart=on-failure
RestartSec=10
# behind the server when fighting for CPU (on a 2-core VPS the relay comes first)
Nice=10
CPUWeight=50
MemoryMax=1G
# no writing to the system, no privilege gain
NoNewPrivileges=yes
ProtectSystem=full
PrivateTmp=yes

[Install]
WantedBy=multi-user.target

# /etc/telinha-musica.env  (chmod 600: it holds the room password)
TELINHA_CONVITE=telinha://127.0.0.1:7777#password
TELINHA_MUSICAS=/srv/music
TELINHA_TOKEN_BOTS=the-bot-token-if-any

sudo systemctl enable --now telinha-musica
journalctl -u telinha-musica -f

On the same machine as the server, the invite can use 127.0.0.1. Update yt-dlp now and then (.venv/bin/pip install -U yt-dlp): sites change and old versions stop opening them.

Troubleshooting#

• "precisa do ffmpeg" in the log (the SDK's messages are in Portuguese): install ffmpeg (with libopus, which almost every build has).
• "the room refused the bot": the room runs with --sem-bots, or asks for --token-bots and the token doesn't match.
• Links don't play: install (or update) yt-dlp in the bot's venv.
• Nobody hears it: the bot plays in the call it's in. Send it /msg Música !join from your call, and check nobody muted the bot (an admin, or its volume in your right-click menu).
• Old app: apps before 3.4 show the card as plain text (the song's name), without buttons; the commands still work.
• Choppy: it's the internet of the bot's machine (it sends ~130 kbit/s). On a VPS this goes away.