Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Audible click at the end of a song on MacOS #3150

Open
nsvg opened this issue Feb 1, 2025 · 1 comment
Open

Audible click at the end of a song on MacOS #3150

nsvg opened this issue Feb 1, 2025 · 1 comment

Comments

@nsvg
Copy link

nsvg commented Feb 1, 2025

On MacOS Sequoia 15.3, using latest DeaDBeeF from either github or Sourceforge, I am facing the following issue: on certain files (always the same files though, but not 100% of the time), there is a loud click when the song ends. I checked the mp3 files using audacity to look for visible clicks at the end of the files, but there is nothing, just normal fadeout (usually). Additionally, this only happens when using macbooks pro speakers as the output, when using a DAC the issue disappears, when using headphones directly on the laptops jack the issue disappears. This only happens on Apple M silicon (M3 Max), on my intel mac (late 2020 i5) the issue does not exist.

Steps to reproduce:

  1. fire up deadbeef
  2. play danzig - cantspeak (for example)
  3. wait for song to move on to next song
  4. hear audible click when output set to macbook pro speakers

A second issue, on both intel and Apple M silicon, both using latest DeaDBeeF (either github or Sourceforge), I cannot add to playback queue anymore, there is only the 'Remove from playback queue' option.

Steps to reproduce:

  1. fire up deadbeef
  2. right click on any file
  3. no 'add to playback queue' option

Thanks in advance!

@Oleksiy-Yakovenko
Copy link
Member

Regarding the latter issue, the menu items have been renamed to "Play Next" and "Play Later", so you should still be able to add to playback queue.

The click issue -- I'll keep an eye on it, but since I don't own a similar or identical mac computer, it is highly unlikely that I would be able to reproduce or investigate. For now I can only suggest to try rebooting the mac, or doing other common workarounds -- such as look for any non-standard settings, plugins, applications which may interfere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants