michael@xxxxxxxxxxxxx (Michaël Cadilhac) writes:
> Hi there, world!
>
> I'm having trouble configuring a new PCM device. Here's the setup: I
> have a usb_stream device (card 1), configured as :
>
> pcm.!usb_stream {
> type usb_stream
> card 1
> }
>
> It works great with, say, jack, or when I fine tune the playing, i.e. :
>
> $ aplay /dev/urandom -D usb_stream -r 44100 \
> --period-size 128 --buffer-size 256
>
> but some software (e.g. Audacity) doesn't offer the ability to tweak the
> period and buffer sizes.
Let me get back to that. After reading parts of the pcm_usb_stream
code, I now understand that those values (period/buffer-size) are hard
coded, which is fine. So my question would be better worded as: why
Audacity fails completly at getting those information (or anything else,
for that matter, because it segfaults without any information).
It may be PortAudio's fault, so if I don't get any chance here, I'll go
see the guys there.
Thanks again!
--
Michaël `Micha' Cadilhac (LITQ, U. de Montréal) -- http://michael.cadilhac.name
|| Academia is made up of indiscrete matter
|| that is largely empty.
|| -- PhD Comics
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user
