Radio Favorites not showing up
Maintainers usually reply within 6 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Start by tracing where radio favorites are saved to favorites.toml and where the radio browser loads favorites from radio_favorites.toml. Compare the two formats shown in the issue and identify the relevant persistence and browser-loading entry points. Done means a favorite saved by the app appears in the Favorites section without manually creating a second file.
Written by the indexing model from the issue text.
Description
What happened
On a fresh installation, I favourited a radio station. However, there seemed to be no way to access the favourite.
Steps to reproduce
- Find a radio station (e.g. by Browse genres & tags, entering a genre)
- Use
nto favourite a radio station. It has a heart now. - The radio browser has Countries, Stations and Catalog entries (no Favorites).
favorites.tomlis created in~\.config\cliamp\, with[[entry]]syntax.- Creating
radio_favorites.tomlwith[[station]]syntax made the Favorite section appear.
Expected behavior
The app should read the same file and format that it saved.
favorites.toml (written by the app)
[[entry]]
favorited_at = "2026-09-18T00:15:16Z"
path = "https://stream.laut.fm/conexiongirlsgroups"
title = "Conexion Kpop Girls groups [128k] · Peru"
genre = "kpop"
realtime = true
provider_meta.radio.bitrate = "128"
provider_meta.radio.state = "arequipa "
provider_meta.radio.country = "Peru"
provider_meta.radio.codec = "MP3"
radio_favorites.toml (expected by the app)
[[station]]
name = "Conexion Kpop Girls groups [128k] · Peru"
url = "https://stream.laut.fm/conexiongirlsgroups"
country = "Peru"
bitrate = 128
codec = "MP3"
Environment
- cliamp version (
cliamp --version): v2.2.0 - OS: Windows (using scoop)
- Audio backend (PipeWire / PulseAudio / ALSA): not sure (and not related)
- Provider(s) involved: radio
- Dominant language
- Go
- Stars
- 4.4k
- Forks
- 307
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 26
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bjarneo/cliamp
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 6 days
-
Show the Podcast episodes in newest first orderPossibly taken @lchojnack claimed this 7 days ago. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 6 days
-
No "Open YouTube Music provider" action (unlike every other provider)Possibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 6 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 6 days
Similar issues
-
[flaky test] TestValidatorCommitterDropsEmptyStatusBatch: submits to the mock VC before its stream is registeredPossibly taken @liran-funaro claimed this today. Opencoordinator flaky-test race-condition testing
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
hyperledger/fabric-x-committer#876 ·
Maintainers usually reply within 1 day
-
kind/features
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
TencentBlueKing/bk-nodemgr#3804 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cloudnative-pg/plugin-barman-cloud#1187 ·
Maintainers usually reply within 1 day
-
[deliverclient] Remove the unused common/deliverclient packagePossibly taken @liran-funaro claimed this today. Opencode-hygiene
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hyperledger/fabric-x-common#236 ·
Maintainers usually reply within 1 day
-
consensus feature I2 S4 U2
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day