Playing any track currently results in 'buzzing' #5221

Closed
flocculant opened this Issue Jan 22, 2016 · 20 comments

Comments

Projects
None yet
6 participants

Hard to describe the sound I'm getting playing music currently.

I have tried various filetypes from mp3 to flac.

I am using Xubuntu 16.04 (obviously dev version) with both the standard repo version of Clementine and the version available via the clementine-dev ppa.

Any other player I try works fine. (Audibly at least)

Screencast of what I'm getting at https://sendvid.com/sa7b0i4n

Contributor

narunlifescience commented Jan 22, 2016

is equalizer enabled ?

No.

I've tried a clean install of xubuntu, followed by updates/upgrades xubuntu needed,then a clean install of clementine,.

Still the same.

So - install the 16.04, update it - install Clementine (either repo or ppa)

Hit this.

I did try looking back to see what else had upgraded when I first caught this (week or so ago) but given I run dev xubuntu, I was seeing gcc/python/qt/gstreamer all hitting about the same time.

elnull commented Jan 23, 2016

I've got same issue on Ubuntu 16.04 and Celementine 1.3.0rc1 from ppa.

Thanks - sort of :)

At least I now know it's not just a local issue. There is a launchpad bug - https://bugs.launchpad.net/ubuntu/+source/clementine/+bug/1537184/+affectsmetoo Though not sure if that was just superfluous.

The same here on Ubuntu 16.04 x64.
ALSA output works fine, problems only with PulseAudio output. But ALSA outputs cuts first 0.5-1s of playback, which is quite annoying.

This behavior happens for approximately 2 weeks now, thought something temporary, but looks like permanent.

Ferroin commented Jan 25, 2016

Just as another datampoint, I've been unable to reproduce this on a Gentoo box with the same version of PulseAudio as used in Ubuntu 16.04 (including copying all the build flags, and matching the compiler version used), so I'd say it's likely to be something Ubuntu specific, or PulseAudio itself is not directly responsible (possibly something it links to is).

From the changelog seems nothing changed with PA since December - on the other hand there were a slew of gstreamer changes happened (if memory serves correctly) at about the same time playback on Clementine went south.

gst-plugins-base1.0 - saw changes 11th January -
http://changelogs.ubuntu.com/changelogs/pool/main/g/gst-plugins-base1.0/gst-plugins-base1.0_1.7.1-1ubuntu1/changelog

gst-plugins-bad1.0 - saw changes 5th January http://changelogs.ubuntu.com/changelogs/pool/universe/g/gst-plugins-bad1.0/gst-plugins-bad1.0_1.7.1-1ubuntu1/changelog

Not found any other media/music player giving the same issue though

mmm - not able to test it with alsa, it won't keep alsa as the output

It always say AUTO (which is a bug, it actually correctly applies settings, so just select ALSA, save and start playing song again).

Then perhaps I'm seeing another issue.

If I set to alsa - apply, then play a track - all is good. If I then OK so the pref page closes then I end up with pa again and the buzzing.

For the record, I've purged and removed any local ~/home configs/caches and started Clementine up vanilla - both repo version and the dev ppa version.

Forget that last comment - seems to be ok after a complete purge.

Package and dependencies purging doesn't help and I do not want to loose all settings when purging user settings.

dkessel commented Feb 13, 2016

I have the same here on Xubuntu 16.04 x64

I can confirm, downgraded gstreamer1.0-plugins-base to 1.6.3-1ubuntu1 from Wily and Clementine now plays fine.

elnull commented Feb 16, 2016

On my Ubuntu 16.04, gstreamer1.0 version 1.7.1
gst-launch-1.0 filesrc location=01.mp3 ! mad ! audioconvert ! audioresample ! pulsesink
plays fine.

got new gstreamer base package today - reset clementine to use pulse - all working properly again here

Confirm, with gstreamer 1.7.2 everything works fine again.

elnull commented Feb 23, 2016

After gstreamer update to 1.7.2 clementine plays fine.

@flocculant, maybe we can close this issue now?

@flocculant flocculant closed this Feb 23, 2016

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