> agreed. but its much more likely to be something about the cardbus
> support under linux than the hdsp driver, and neither side (the
> cardbus people or us hdsp people) knows the other side at all.
to figure that out, someone who knows what's going on in the hdsp driver
has to tell the pcmcia guy
Despite the indifference to this issue, I thought it only fair to say that
switching to mmap seems to have stopped the problem from occuring.
- Tom.
Tom Browne wrote:
> Hi all,
>
> I am having serious trouble with ALSA using the poll method as shown
> in the pcm.c test app...
>
> Under certain c
Tom Browne wrote:
> Under certain conditions (yet to be established properly - it doesn't
> happen every single time) with this ICE1712 card (DSP24),
> snd_pcm_writei doesn't just block... it never comes back.
What is the state of the PCM device when this happens?
(see /proc/asound/cardX/pcm0p/*)
Patrick Boettcher wrote:
> I'm using a usbsnoop program to do some basic sniffing. Logs are
> really big :/.
Try to play some 0.01-seconds wave file, and don't connect any other
USB devices.
> After plugging in, the device shows like this in /proc/bus/usb/devices:
>
> I: If#= 0 Alt= 0 #EPs= 0 Cl
John H. wrote:
> see, this is what is weird, it worked last week, now it doesn't
> work with exaudio or alsa! same errors!
Then it's not a problem of the sound driver.
> cannot submit datapipe for urb 0, err = -38
-38 means "not implemented". Probably some bug in the USB core in
your kernel.
H
Clemens Ladisch wrote:
> Tom Browne wrote:
>> Under certain conditions (yet to be established properly - it doesn't
>> happen every single time) with this ICE1712 card (DSP24),
>> snd_pcm_writei doesn't just block... it never comes back.
>
> What is the state of the PCM device when this happens?
>
On Mon, Apr 05, 2004 at 06:00:01PM +0200, Clemens Ladisch wrote:
> Patrick Boettcher wrote:
> > I'm using a usbsnoop program to do some basic sniffing. Logs are
> > really big :/.
>
> Try to play some 0.01-seconds wave file, and don't connect any other
> USB devices.
Check the log of the init pha
Am Samstag 03 April 2004 03:24 schrieb Rui Nuno Capela:
> I have news, and they're good this time.
>
> After some juggling and persistance around compiling and patching the
> snd-usb-usx2y module, I've finally got that dreaded INPUT MONITOR LED come
> to light and, as Karsten rightly predicted, pla
Hi Clemens,
On Mon, 5 Apr 2004, Clemens Ladisch wrote:
> Class 0xff means vendor-specific. This is not a "USB Audio Device" as
> defined in the USB specifications.
Yes, I noticed it already, but I hoped that the vendor-specific part is
not so much vendor-specific, because they use a "normal" soun
Hi martin,
On Mon, 5 Apr 2004, Martin Langer wrote:
> Check the log of the init phase. Perhaps the MBox needs a firmware download
> at first.
I don't think so, as I wrote in the last answer to Clemens, the owner
told, me that he has to do a static firmware update (like a bios update).
And the us
Hi,
small supplement:
http://vaasa.wi-bw.tfh-wildau.de/~pboettch/digi_mbox/
there is the 0.04-wave file played with winamp on WinXP, and the
appropriate log file produced by usbsnoop.
Patrick
---
This SF.Net email is sponsored by: IBM Linux
TAS1020:
http://focus.ti.com/docs/prod/folders/print/tas1020b.html
"The TAS1020B integrated circuit (IC) is a universal serial bus (USB) peripheral
interface device designed specifically for applications that require isochronous
data streaming. Applications include digital speakers, which require
I don't use aplay to play the wav file but i use:
dd of=thefile.wav of=/dev/audio0
Do you think i should use aplay instead?
Is this the problem?
I'm trying to cross-compile the alsa-util library but, i have some trouble
at the compilation (configure: error: No linkable libasound was found).
libas
Karsten Wiese wrote:
> Am Samstag 03 April 2004 03:24 schrieb Rui Nuno Capela:
>> I have news, and they're good this time.
>> After some juggling and persistance around compiling and patching
>> the snd-usb-usx2y module, I've finally got that dreaded INPUT
>> MONITOR LED come to light and, as Kars
Pedro Lopez-Cabanillas wrote:
> This patch adds three new options to arecordmidi.
Committed, with some changes.
Thanks,
Clemens
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, Pres
On Mon, 5 Apr 2004, Mathieu Rondonneau wrote:
> I don't use aplay to play the wav file but i use:
> dd of=thefile.wav of=/dev/audio0
This is definitely wrong. The /dev/audio devices expect mu-Law
format at 8000Hz.
Jaroslav
-
Jaroslav Kysela <[
16 matches
Mail list logo
