Bug#676167: WARN alsa: can't encode 0-bit Unknown or not applicable

2013-01-18 Thread Ulrich Klauer
Pascal Giard : > I'll probably just push a 14.4.0-5 with it (14.4.0-4 went to > experimental). The change is also in 14.4.1 (which will be out in two weeks' time), so a 14.4.0-5 isn't really necessary. Won't hurt either, of course. Ulrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...

Bug#676167: WARN alsa: can't encode 0-bit Unknown or not applicable

2013-01-18 Thread Pascal Giard
On Fri, Aug 24, 2012 at 3:03 AM, Ulrich Klauer wrote: > tags 676167 + patch > thanks > > >> It'd be interesting to know which driver causes the segfault on platforms >> without ALSA support; it might be alsa there too, or one of the following. > > > Apparently it is the oss format itself, which pa

Bug#676167: WARN alsa: can't encode 0-bit Unknown or not applicable

2012-08-24 Thread Ulrich Klauer
tags 676167 + patch thanks It'd be interesting to know which driver causes the segfault on platforms without ALSA support; it might be alsa there too, or one of the following. Apparently it is the oss format itself, which passes NULL to fileno(). I've attached a patch to replace the 01_d

Bug#676167: WARN alsa: can't encode 0-bit Unknown or not applicable

2012-08-23 Thread Ulrich Klauer
Bob Proulx : > Although I don't know about > coreaudio it probably doesn't hurt. (shrug) No, it isn't supposed to be compiled in at all on platforms other than MacOS. > Opening what driver produces the "WARN alsa: can't encode 0-bit > Unknown or not applicable" message? By the above and my ca

Bug#676167: WARN alsa: can't encode 0-bit Unknown or not applicable

2012-08-23 Thread Bob Proulx
Ulrich Klauer wrote: > Yes. If an audio driver is explicitly specified by the user (via the > AUDIODRIVER environment variable or the -t option), SoX will use > this and there's no problem. Otherwise, SoX will try possible > drivers in this (hard-wired) order: coreaudio (MacOS), pulseaudio, > alsa,

Bug#676167: WARN alsa: can't encode 0-bit Unknown or not applicable

2012-08-23 Thread Ulrich Klauer
Bob Proulx : Is there any clue as to the root cause of the problem? Yes. If an audio driver is explicitly specified by the user (via the AUDIODRIVER environment variable or the -t option), SoX will use this and there's no problem. Otherwise, SoX will try possible drivers in this (hard-wi

Bug#676167: WARN alsa: can't encode 0-bit Unknown or not applicable

2012-08-23 Thread Bob Proulx
I was very appreciative of the info in this bug when I hit this problem too. I am not getting a segfault but I am seeing the warning message. $ play -q anything.wav play WARN alsa: can't encode 0-bit Unknown or not applicable The suggested workaround of adding "-t alsa" works but shouldn't b