Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ytmusic: unavailable video stalls playback instead of skipping to next track

Closed
#540 0 comments 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 6 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
66/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
cli

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

bug

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

  1. Set provider to ytmusic.
  2. Queue or play a track whose backing video has been taken down or made unavailable on YouTube.
  3. 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bjarneo/cliamp

All issues in bjarneo/cliamp

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.