> The update itself seems fine; my only reservation is that the original bug
> doesn't seem serious enough to justify the inherent risk factors of an
> update. It seems that it would affect only a very small number of users (on
> particular hardware and doing stereo audio capture?).
As I understand it, the bug affects the vast majority of PC audio
hardware. Most on-board audio chipsets use the buggy "simple mixer" and
so do the majority of consumer-grade PCI sound cards. (Higher-end
[Audigy] and other specialty audio hardware use different mixer code and
are not affected.)
I suppose any update is a risk factor, but the changes to the existing
package are minimal and completely isolated. This is much less of a
risk than upgrading the whole library to 1.0.11 would be.
Matt Zimmerman wrote:
> The update itself seems fine; my only reservation is that the original bug
> doesn't seem serious enough to justify the inherent risk factors of an
> update. It seems that it would affect only a very small number of users (on
> particular hardware and doing stereo audio capture?).
As I understand it, the bug affects the vast majority of PC audio
hardware. Most on-board audio chipsets use the buggy "simple mixer" and
so do the majority of consumer-grade PCI sound cards. (Higher-end
[Audigy] and other specialty audio hardware use different mixer code and
are not affected.)
I suppose any update is a risk factor, but the changes to the existing
package are minimal and completely isolated. This is much less of a
risk than upgrading the whole library to 1.0.11 would be.