Bug#689049: [libspeexdsp1] Resampler stops in the middle of run with multiple channels

[Ron]

On Wed, Oct 10, 2012 at 10:33:21AM +0200, Catherine Lowenstein wrote:
> On Tue, Oct 9, 2012 at 3:15 AM, Ron <ron at debian.org> wrote:
> >
> > Can you tell me more about the actual symptoms you were hearing with pulse?
> 
> I've installed pulseaudio since bluetooth audio headsets doesn't work
> anymore in wheezy without pulseaudio. After this installation I
> noticed a crackling sound in some of the stuff I am using. It went
> away after I changed the resample-method in /etc/pulse/daemon.conf to
> src-sinc-fastest. This was actually more an accident than an intended
> way to fix the clicking/crackling sound I had with some
> programs/sounds. So I started to search for the problem (just searched
> for speex and resampler) and found this bug.
> 
> I've applied this patch, changed the resampler in pulseaudio back,
> installed my package from libspeexdsp and tested it again. Voila this
> patch fixed the problem.

Ok, thanks for that.  This is exactly the sort of extra detail that I
was after.  Since so far you are the only person we're aware of who has
reported experiencing this with pulse, either to Debian or upstream,
you are kind of uniquely positioned for the moment as the only one who
could tell us more about what you heard, and how you connected that to
this bug.


> But I am starting to get really frustrated about speex/Debian. Why is
> this problem known, a fix known and nobody cares to incorporate this
> fix in speex or Debian? Are you happy about throwing other peoples
> time away? I know it takes a lot of time and effort to create
> something like a Distribution, but knowing about a problem _AND_ the
> fix and just don't care about it is just mindblowing.

Well ...  before your mail arrived, nobody was aware of this effecting
anything except 2 niche applications, and definitely not of it effecting
pulse.  And I replied to your mail about that asking for the details
above on the same day ...

In the meantime, I was also talking with some of the other upstream folk,
who could only report never having seen this, despite having used pulse
for quite some time now, and despite knowing full well exactly what the
symptoms would be if this bug did manifest there for them.

So yes, there are things about this which are mindblowing.  Like how has
nobody ever noticed this years ago?  In any of the *many* applications
that are using it ...  And why are you still so far the only person to
see it with pulse ...  The bug is newly discovered, but it's many years
gone from being an actually new bug.


The accusations of not caring you might want to rethink though.  There
are lots of useful and fun things I could be throwing my time away on
instead of following up on this for you - and not everyone that I need
to talk to get it fixed for more than just Debian are all in the same
timezone, or awake at the same time, or even able to drop everything
else on a minute's notice to make this their top priority.  Abusing
them isn't the best way to motivate them to care more urgently.

But the extra detail you've taken the time to give us is helpful, so
Thanks for that.  We're caring as fast as we can with the time and
manpower and information that is available to us.  If this is the only
bug that's currently wasting your time, then you can probably count
yourself Among The Lucky Ones.

  Ron