Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#55976 - [deadbeef] ALSA output with Default Sound Device playing speed wrong.

Attached to Project: Community Packages
Opened by Roman Mikhayloff (rimf) - Friday, 13 October 2017, 08:52 GMT
Last edited by Antonio Rojas (arojas) - Monday, 17 May 2021, 11:18 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I play music through the ALSA output plugin. Playing speed is correct only with "HDA Intel PCH, ALC668 Analog Front speakers" output device. Other cases with output device "Default Sound Device" are plays music with wrong speed (faster).

Additional info:
* deadbeef-0.7.2-2-x86_64.pkg.tar.xz
This task depends upon

Closed by  Antonio Rojas (arojas)
Monday, 17 May 2021, 11:18 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Package was dropped to AUR
Comment by Roman Mikhayloff (rimf) - Tuesday, 31 October 2017, 14:54 GMT
The bug have an effect when in a window "Edit->Preferences->Plugins->ALSA output plugin->Configure" a control "Use ALSA resampling" has not checked, else plays with normal speed.
Comment by Ivy Foster (escondida) - Friday, 11 October 2019, 00:11 GMT
rimf, do you still experience this issue? Did it ever get reported upstream, since it sounds like an upstream bug?
Comment by Roman Mikhayloff (rimf) - Friday, 11 October 2019, 23:31 GMT
Yes, the problem is taking place now. I use a player with the "Use ALSA resampling" option enabled, in which case the problem does not occur. It seems I did not report the problem to the author of the player, I don’t remember exactly. Sorry, in 2017, I thought that package maintainers often do this themselves. The problem is minor and does not exist at default settings. Maybe it's better to just close the ticket.
Comment by Ivy Foster (escondida) - Saturday, 12 October 2019, 17:52 GMT
Thanks for getting back to me, rimf. Since it's still an issue, would you be willing to report it upstream? If the devs know about it they may be able to fix things up for the next version.

Loading...