gapless playback hiccups
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- go, linux
- Domain
- audio-video-rtc, cli
Research direction
Start by running cliamp 2.2.0 on Arch Linux with ALSA and a local, truly gapless track list, as described in the reproduction steps. Then trace the track-transition and audio playback paths to locate where the hiccup occurs; the issue names no files or tests. Done means transitions between gapless tracks are seamless and the behavior can be reproduced and verified.
Written by the indexing model from the issue text.
Description
What happened
I've noticed that sometimes it seems like when transitioning to a new track there is a slight hiccup. This is most noticable with live recordings that are truly gapless. It is subtle, and sometimes I don't notice it, but certain transitions will exhibit the behaviour. I'm not entirely sure this isn't source related? I'm trying to figure that out and will update this issue if I find that to be true.
Steps to reproduce
- Play a truly gapless list of tracks from local disc (this eliminates any service provider issues). It is sometime noticable when the track changes to the next one.
Expected behavior
Truly seemless track transition.
- cliamp version (
cliamp --version): V2.2.0 - OS: Arch linux
- Audio backend (PipeWire / PulseAudio / ALSA): ALSA
- Provider(s) involved:None
- Dominant language
- Go
- Stars
- 4.4k
- Forks
- 307
- Avg merge
- 3d 10h
- 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
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Windows source build needs CGO and MinGW even without SpotifyPossibly taken @SomSamantray claimed this 10 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Show the Podcast episodes in newest first orderPossibly taken @lchojnack claimed this 3 days ago. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
Go back to previous equalizer instead of loopingPossibly taken @SomSamantray claimed this 10 days ago. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
Similar issues
-
confirmed enhancement go
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
DennisVlaanderen/aerendil#154 ·
Maintainers usually reply within 1 day
-
Generated README and SKILL omit HTTP-transport security settings and what local data the CLI keepsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
mvanhorn/cli-printing-press#5181 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
Adyen/agent-marketplace#922 ·
Maintainers usually reply within 1 day
-
filer.remote.sync writes the S3 bucket-owner index (<buckets>/.system/owners/...) to remote storageOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day