Sound Chipmunks on playback with Jabra Evolve 65 UC Headset

Bug #1710060 reported by Pradeep Kumar
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
pulseaudio (Fedora)
Won't Fix
Low
pulseaudio (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Whenever I choose the Jabra Evolve 65 UC Headset as the playback device, there are sound chipmunks. The same was the case with Jabra Motion Headset as well. But those two headsets worked perfectly in Windows, Mac OS and Android.

There was a workaround mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1282285 by editing the contents of /etc/pulseaudio/daemon.conf :

Changing

     ;default-sample-rate=44100

to

     default-sample-rate=48000

and then running

     pulseaudio -k

made the sound on Jabra good (no more chipmunks). Also, when I opened the Sound Settings with the changes in daemon.conf in place, there seems to be some distortions in headset sound, which goes away few seconds after I close the sound settings window.

This problem should be fixed, as many new Linux users will find it difficult to edit files requiring root access, and those who do not use command line won't be okay with it.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.3
ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
Uname: Linux 4.4.0-89-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC2D0p: itachi 10880 F...m pulseaudio
 /dev/snd/controlC2: itachi 10880 F.... pulseaudio
 /dev/snd/controlC1: itachi 10880 F.... pulseaudio
 /dev/snd/controlC0: itachi 10880 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu Aug 10 21:11:18 2017
InstallationDate: Installed on 2016-08-27 (349 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/25/2014
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-78LMT-USB3 6.0
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: SEx
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-78LMT-USB3 6.0
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
modified.conffile..etc.pulse.daemon.conf: [modified]
mtime.conffile..etc.pulse.daemon.conf: 2017-08-10T21:07:55.637386

Revision history for this message
In , gizmo (gizmo-redhat-bugs) wrote :

Description of problem:
When playing audio through the Jabra Evolve 65 UC headset using either the USB cable or the Jabra Link 360 USB dongle, sound is played back too fast, with a 'chipmunk' effect. I don't know if the recording side is affected or not, but people have not commented on it if it is.

Version-Release number of selected component (if applicable):
Name : pulseaudio
Arch : x86_64
Epoch : 0
Version : 6.0
Release : 8.fc22
Size : 3.3 M
Repo : @System

Name : alsa-plugins-pulseaudio
Arch : i686
Epoch : 0
Version : 1.0.29
Release : 1.fc22
Size : 101 k
Repo : @System

How reproducible:
Always

Steps to Reproduce:
1. Plug in headset using USB cable.
2. Play audio

Actual results:
Audio plays fast. Buffered audio streams (like youtube) play without gaps, but realtime streams (like Skype, or Jabber) play with gaps.

Expected results:
Audio should play back at the normal rate with no gaps.

Additional info:
My Logitech USB headset plays just fine.

When using the Jabra headset in BlueTooth mode, audio playback is normal using either the A2DP audio profile or the HSP/HFP.

When connected with the USB cable lsusb reports the Jabra device as:
Bus 001 Device 008: ID 0b0e:030b GN Netcom

The Jabra device plays just fine on Windows, using the same computer.

System is running KDE with Phonon GStreamer and alsa.

I honestly don't know if this is a Pulse problem or an ALSA problem.

Revision history for this message
In , gizmo (gizmo-redhat-bugs) wrote :

This bug has been open now for 2 months with zero movement. Is there anything I can do to help out here? I'm willing to troubleshoot, I just have no idea what to do next.

Revision history for this message
In , wtaymans (wtaymans-redhat-bugs) wrote :

I'm pretty sure that this is an alsa problem. The driver probably configures the wrong samplerate or maybe it needs a tweak for this particular hardware.

Revision history for this message
In , joerg.pareigis (joerg.pareigis-redhat-bugs) wrote :

Exactly the same here.
Trying with newest version of Debian 8 and SuSE 42.1.

The headset plays too fast with a short gap every second. Regardless which connection is used. Directly via USB-Cable, or via BT-Dongle. Both with the same result.

It plays the correct speed when connected via Bluetooth to Android devices.
Connected at Windows PC it pays also without any spot.

Revision history for this message
In , gizmo (gizmo-redhat-bugs) wrote :

(In reply to Wim Taymans from comment #2)
> I'm pretty sure that this is an alsa problem. The driver probably configures
> the wrong samplerate or maybe it needs a tweak for this particular hardware.

Ok, so I've got the same question; what can I do to help troubleshoot this? Guys, I'm willing to be your eyes and hands here, but these eyes and hands need a brain to direct them. :)

Revision history for this message
In , bs.alex.mail (bs.alex.mail-redhat-bugs) wrote :

Hi. I've had the same problem.
Here is workaround that helped me:

In file

/etc/pulse/daemon.conf

replace
---
;default-sample-rate = 44100

|
v

with
---
default-sample-rate = 48000

And then reload pulseaudio

pulseaudio -k

Revision history for this message
In , gizmo (gizmo-redhat-bugs) wrote :

Just tried this, and it appears to work here as well.

Revision history for this message
In , bcotton (bcotton-redhat-bugs) wrote :

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Revision history for this message
Pradeep Kumar (pradeepsixer) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

"Chipmunks" sound implies that the audio is being played back at a higher sample rate than it was recorded at. Obviously this should not happen if all layers are aware of the recording sample rate and adjust playback accordingly. So you would need to find out what part of the system is using (or guessing) the wrong sample rate.

It could even be that the problem is right at the end -- if pulseaudio is outputting 44100Hz and the hardware for some reason is playing at 48000Hz. Perhaps even a hardware fault if not software. You would need to establish at what point the wrong sample rate or conversion has been chosen. Sorry I don't know the commands for that...

Changed in pulseaudio (Fedora):
importance: Unknown → Low
status: Unknown → Won't Fix
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pulseaudio (Ubuntu):
status: New → Confirmed
Revision history for this message
Sam Edney (0-sam-m) wrote :

For what its worth, I had this issue on Ubuntu 18.04 - but also on Antergos 18.7.

It happens with all audio playback that I have tested so far - including Slack, Firefox and Chrome audio.

Changing the sample rate in `/etc/pulse/daemon.conf` then running `pulseaudio -k` also resolves things.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sam,

With what hardware do you experience the problem?

Revision history for this message
Roshan (gmate-sunny) wrote :

Faced the same issue with following device and OS.
Jabra 65
Linux waimw030207 4.4.0-133-generic #159-Ubuntu SMP Fri Aug 10 07:31:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Fixed it by the workaround

tags: added: bionic
Revision history for this message
In , jorton (jorton-redhat-bugs) wrote :

I see this with the Jabra Evolve 65 headset as well in Fedora 30.

The workaround above to set the sample rate to:

default-sample-rate = 48000

in the default pulse config works for me, but how can we make this DTRT by default?

Revision history for this message
In , jorton (jorton-redhat-bugs) wrote :

pulseaudio-12.2-3.fc30.x86_64
alsa-lib-1.1.9-1.fc30.x86_64
$ uname -r
5.1.6-300.fc30.x86_64

Revision history for this message
In , jkysela (jkysela-redhat-bugs) wrote :

The device reports those supported sample rates:

        bSamFreqType 5 Discrete
        tSamFreq[ 0] 8000
        tSamFreq[ 1] 16000
        tSamFreq[ 2] 32000
        tSamFreq[ 3] 44100
        tSamFreq[ 4] 48000

Could you check all rates with the 'speaker-test' utility through the native ALSA device (like 'spaker-test -D plughw:J65 -f 44100')?

Revision history for this message
In , jorton (jorton-redhat-bugs) wrote :

Do you mean -r or -f ? I hear "pink noise" with all selected frequencies with either -r or -f.

$ speaker-test -D plughw:J65 -r 44100

speaker-test 1.1.9

Playback device is plughw:J65
Stream parameters are 44100Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Rate set to 44100Hz (requested 44100Hz)
Buffer size range from 90 to 262144
Period size range from 45 to 131072
Using max buffer size 262144
Periods = 4
was set period_size = 65536
was set buffer_size = 262144
 0 - Front Left
Time per period = 2.740062

$ speaker-test -D plughw:J65 -f 44100

speaker-test 1.1.9

Playback device is plughw:J65
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 96 to 262144
Period size range from 48 to 131072
Using max buffer size 262144
Periods = 4
was set period_size = 65536
was set buffer_size = 262144
 0 - Front Left
Time per period = 2.745972

does this help?

Revision history for this message
In , jkysela (jkysela-redhat-bugs) wrote :

Sorry, -r is the correct option, of course. If the problematic rate works with the direct ALSA interface, you may try to simulate stream parameters (buffers) like PA uses and use '-b -p -P' arguments for speaker-test to force them. The actual streaming parameters are in /proc/asound/card#/pcm0p/sub0 directory.

Changed in pulseaudio (Fedora):
status: Won't Fix → Confirmed
Revision history for this message
Vladimir Hidalgo (vlad88sv) wrote :

This is also an issue with Kubuntu 19.10 eoan 5.3.0-40-generic and pulseaudio 13.0

I use this headset interchangeably with Windows and it's not an issue there.

I have noticed that using the bundle Jabra link 370 makes the headset work perfectly, it's just an issue when using it as USB headphone.

Attached is the pulseaudio output from pacmd list-sinks

Revision history for this message
In , bcotton (bcotton-redhat-bugs) wrote :

This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 30 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Revision history for this message
In , bcotton (bcotton-redhat-bugs) wrote :

Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Revision history for this message
Snufkin (spuns-lab) wrote :

hello

I'have Ubuntu and this work around not work for me how can I fix it Please :(

below details:

Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal

Demons.conf:

# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see <http://www.gnu.org/licenses/>.

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out. Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = (depends on architecture)

; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa

; log-target = auto
; log-level = notice
; log-meta = no
; log-time = no
; log-backtrace = 0

; resample-method = speex-float-1
; avoid-resampling = false
; enable-remixing = yes
; remixing-use-all-sink-channels = yes
; remixing-produce-lfe = no
; remixing-consume-lfe = no
; lfe-crossover-freq = 0

; flat-volumes = no

; rescue-streams = yes

; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-core = -1
; rlimit-as = -1
; rlimit-rss = -1
; rlimit-nproc = -1
; rlimit-nofile = 256
; rlimit-memlock = -1
; rlimit-locks = -1
; rlimit-sigpending = -1
; rlimit-msgqueue = -1
; rlimit-nice = 31
; rlimit-rtprio = 9
; rlimit-rttime = 200000

; default-sample-format = s16le
; default-sample-rate = 48000
; alternate-sample-rate = 48000
; default-sample-channels = 2
; default-channel-map = front-left,front-right

; default-fragments = 4
; default-fragment-size-msec = 25

; enable-deferred-volume = yes
deferred-volume-safety-margin-usec = 1
; deferred-volume-extra-delay-usec = 0

Revision history for this message
Pradeep Kumar (pradeepsixer) wrote :

Snufkin, you need to remove the semicolon at the beginning of the line, and then run

pulseaudio -k

for the change to take effect.

Changed in pulseaudio (Fedora):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.