Slow Seeking/Pausing #346

Open
opened 2023-02-24 00:15:36 -03:00 by kyleerhabor · 10 comments
kyleerhabor commented 2023-02-24 00:15:36 -03:00 (Migrated from github.com)

Describe
Hello, when seeking, pausing, or, in general, interacting with a song, there's a noticeable delay from when it happens to when the song continues (e.g. 0.5-2 seconds). For me personally, it's very noticeable since I like to scrub through songs via my Touch Bar.

To Reproduce

  1. Load a song
  2. Start playing it
  3. Seek to some position
  4. See it take a second or longer for the song to continue

Expected behavior
Continue the song at the position quickly / nearly instantaneous.

Screenshots
N/A

Version information:

  • macOS version: 13.2.1 (Ventura)
  • Cog version: 2732 (2732-g4131d4ea)

Additional context
N/A

**Describe** Hello, when seeking, pausing, or, in general, interacting with a song, there's a noticeable delay from when it happens to when the song continues (e.g. 0.5-2 seconds). For me personally, it's very noticeable since I like to scrub through songs via my Touch Bar. **To Reproduce** 1. Load a song 2. Start playing it 3. Seek to some position 4. See it take a second or longer for the song to continue **Expected behavior** Continue the song at the position quickly / nearly instantaneous. **Screenshots** N/A **Version information:** - macOS version: 13.2.1 (Ventura) - Cog version: 2732 (2732-g4131d4ea) **Additional context** N/A
DannyWalkman commented 2023-06-27 10:27:28 -04:00 (Migrated from github.com)

I have the same issue, and it gets much worse on bluetooth headphones. Up to 2 seconds of delay on each seek (!).

I have the same issue, and it gets much worse on bluetooth headphones. Up to 2 seconds of delay on each seek (!).
kode54 commented 2023-07-01 03:16:51 -04:00 (Migrated from github.com)

Sorry for being so rude the other day, I've been feeling really down lately, and made the mistake of taking that out on you and your issue.

If we could get a report of which hardware you two have in common, that would be swell. I need a report of exact Bluetooth devices you're experiencing the issue with.

Sorry for being so rude the other day, I've been feeling really down lately, and made the mistake of taking that out on you and your issue. If we could get a report of which hardware you two have in common, that would be swell. I need a report of exact Bluetooth devices you're experiencing the issue with.
yannick commented 2023-10-02 05:59:40 -03:00 (Migrated from github.com)

i have the same or similar issue since a few revisions.
when i load the player and press play it sometimes takes up to 10s of seconds until the audio starts. it is as if the filesystem lookup takes ages.

hardware: newest macbook pro, m2. does not depend on the audio output selected (macbook speakers, bluetooth, DAC)

if there is a debug build that i can run with DTrace i can probably do that.

i have the same or similar issue since a few revisions. when i load the player and press play it sometimes takes up to 10s of seconds until the audio starts. it is as if the filesystem lookup takes ages. hardware: newest macbook pro, m2. does not depend on the audio output selected (macbook speakers, bluetooth, DAC) if there is a debug build that i can run with DTrace i can probably do that.
jamesdrake101 commented 2025-02-25 08:23:05 -03:00 (Migrated from github.com)

@kode54 It's a whole lot worse for me: when seeking, I hear an interruption in the sound, then the track continues from the same position (not the seek destination!) for a second, then the sound breaks up again, and finally it starts playing from the seek destination.
But wait, there's more: if I am in the last 10-15 seconds of the track, seeking doesn't work at all.

@kode54 It's a whole lot worse for me: when seeking, I hear an interruption in the sound, then the track continues from the same position (not the seek destination!) for a second, then the sound breaks up again, and finally it starts playing from the seek destination. But wait, there's more: if I am in the last 10-15 seconds of the track, seeking doesn't work at all.
kode54 commented 2025-02-25 23:11:42 -03:00 (Migrated from github.com)

New version incoming, please test when it's available to you.

New version incoming, please test when it's available to you.
jamesdrake101 commented 2025-02-25 23:12:51 -03:00 (Migrated from github.com)

Will do.

Will do.
jamesdrake101 commented 2025-02-28 08:41:32 -03:00 (Migrated from github.com)

@kode54 Net improvement! What remains suboptimal (but I can cope) is:

  1. If I am near the end of the track (say 5 seconds from the end) and I seek all the way back to the beginning, it just stops.
  2. Seeking is now nice and fast, but very noisy (the typical fart-like sound of corrupted digital audio) which is something I have not experienced in a digital audio system in 25 years - hence my surprise.

Anyhow thanks for this and keep up the good work!

@kode54 Net improvement! What remains suboptimal (but I can cope) is: 1. If I am near the end of the track (say 5 seconds from the end) and I seek all the way back to the beginning, it just stops. 2. Seeking is now nice and fast, but very noisy (the typical fart-like sound of corrupted digital audio) which is something I have not experienced in a digital audio system in 25 years - hence my surprise. Anyhow thanks for this and keep up the good work!
kode54 commented 2025-02-28 22:14:42 -03:00 (Migrated from github.com)

The only way to stop the glitching on seeking is to completely stop and restart playback on every seek operation. Same goes for near end of track seeking, which is working for me already, by already doing this stopping and restarting thing.

The only way to stop the glitching on seeking is to completely stop and restart playback on every seek operation. Same goes for near end of track seeking, which is working for me already, by already doing this stopping and restarting thing.
jamesdrake101 commented 2025-02-28 22:27:10 -03:00 (Migrated from github.com)

Right, any reason why you're not doing that? 🙂

I admit I have never worked on this kind of stuff before, but I am a dev and if you want I can study the problem in detail and work on a PR for you.

It's definitely solvable, I didn't use to have any glitches seeking MP3s with Winamp on a Celeron 500 with 64MB RAM.

Tell me if I can help in any way.

Right, any reason why you're not doing that? 🙂 I admit I have never worked on this kind of stuff before, but I am a dev and if you want I can study the problem in detail and work on a PR for you. It's definitely solvable, I didn't use to have any glitches seeking MP3s with Winamp on a Celeron 500 with 64MB RAM. Tell me if I can help in any way.
kode54 commented 2025-02-28 23:46:12 -03:00 (Migrated from github.com)

I am now. Wait for version 3008 or possibly newer if I find something else to fix before you update.

I am now. Wait for version 3008 or possibly newer if I find something else to fix before you update.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: chris/Cog#346
No description provided.