ytmusic: unavailable video stalls playback instead of skipping to next track
Maintainers usually reply within 6 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 66/100
Research direction
Start by tracing the ytmusic playback path where cliamp invokes yt-dlp and handles a non-zero exit status; compare it with the related behavior described in issue #135. Reproduce with the unavailable video linked in the issue and check how queue advancement is handled after the error. Done means the error is logged and playback advances to the next queued track instead of stopping.
Written by the indexing model from the issue text.
Description
What happened
While playing from the ytmusic provider, some tracks fail to load because the underlying video is unavailable on YouTube.
Error shown in UI when trying to play this video
ERR: yt-dlp: exit status 1: ERROR: [youtube] YMwftR69o9w: Video unavailable
When this happens, cliamp gets stuck instead of moving to the next track. This is a related but separate case to #135, which covers a different yt-dlp failure (waiting for audio data: EOF) with the same fix request: don't stop the queue on a yt-dlp error, skip forward instead.
Steps to reproduce
- Set provider to ytmusic.
- Queue or play a track whose backing video has been taken down or made unavailable on YouTube.
- cliamp calls yt-dlp, gets a non-zero exit status, and playback stops there.
Expected behavior
cliamp catches the non-zero yt-dlp exit, logs the error, and skips to the next track in the queue instead of stalling.
Environment
- cliamp version: v2.0.1
- OS: Windows 11 Pro
- Audio backend: (not sure, will confirm if needed)
- Provider(s) involved: ytmusic
- 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 10 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 @yunaremaia claimed this 5 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bjarneo/cliamp#520 · 2 reactions ·
Maintainers usually reply within 6 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 6 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
google/go-containerregistry#2491 ·
Maintainers usually reply within 1 day
-
aiac enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
phase:v1 type:harness
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
scttfrdmn/burroughs#1181 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
compiler-explorer/ce-ci#28 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day