From: Jan Kiszka <jan.kiszka@web.de>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] alsaaudio: increase default buffer sizes
Date: Fri, 02 May 2008 23:00:32 +0200 [thread overview]
Message-ID: <481B80F0.8050705@web.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0805022335240.2121@linmac.oyster.ru>
[-- Attachment #1: Type: text/plain, Size: 2701 bytes --]
malc wrote:
> On Fri, 2 May 2008, Jan Kiszka wrote:
>
>> Sound though the ALSA driver is skipping here unless I increase the
>> buffer size. OSS seems to use 16K as well, and 1K was obviously to small
>> for recording anyway.
>>
>> [ PS: Can someone explain to me why I also have to override the
>> DAC/ADC_FIXED_FREQ to 48000 to make ALSA work? Suboptimal... ]
>
> How exactly it doesn't work if you don't override it? Do you get any
> messages prefixed with "alsa:"? As for the defaults they were set to
> 1024/256 because that's what was needed to make it sound on par with OSS
> on the two machines i had at the time.
alsa: Could not initialize ADC
alsa: Failed to set period size 256
alsa: Reason: Invalid argument
alsa: Could not initialize ADC
alsa: Failed to set period size 256
alsa: Reason: Invalid argument
audio: Failed to create voice `wm8750.input1'
alsa: Could not initialize ADC
alsa: Failed to set period size 256
alsa: Reason: Invalid argument
alsa: Could not initialize ADC
alsa: Failed to set period size 256
alsa: Reason: Invalid argument
audio: Failed to create voice `wm8750.input2'
alsa: Could not initialize ADC
alsa: Failed to set period size 256
alsa: Reason: Invalid argument
alsa: Could not initialize ADC
alsa: Failed to set period size 256
alsa: Reason: Invalid argument
audio: Failed to create voice `wm8750.input3'
alsa: Could not initialize DAC
alsa: Failed to set period size 256
alsa: Reason: Invalid argument
alsa: Could not initialize DAC
alsa: Failed to set period size 256
alsa: Reason: Invalid argument
audio: Failed to create voice `wm8750.speaker'
alsa: Could not initialize DAC
alsa: Failed to set period size 256
alsa: Reason: Invalid argument
alsa: Could not initialize DAC
alsa: Failed to set period size 256
alsa: Reason: Invalid argument
audio: Failed to create voice `wm8750.headphone'
alsa: Could not initialize DAC
alsa: Failed to set period size 256
alsa: Reason: Invalid argument
alsa: Could not initialize DAC
alsa: Failed to set period size 256
alsa: Reason: Invalid argument
audio: Failed to create voice `wm8750.monomix'
BTW, I picked up those ALSA settings from user reports on kvm-devel,
dating back to mid of last year. So I'm not alone, and it shouldn't be a
wm8750-specific thing.
>
> By the by: OSSs fragment size is specified in bytes, ALSAs on the other
> hand in frames. So 16*1024 in the patch bellow means(considering
> S16/stereo) 65536 bytes large buffer and 1024 bytes large period. For
> OSS it's 16K bytes buffer and 4096 bytes period.
>
Ah, OK. However, 4*1024 is not enough for the DAC here, and there were
similar reports by kvm users.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2008-05-02 21:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 19:06 [Qemu-devel] [PATCH] alsaaudio: increase default buffer sizes Jan Kiszka
2008-05-02 19:48 ` [Qemu-devel] " malc
2008-05-02 21:00 ` Jan Kiszka [this message]
2008-05-03 19:43 ` malc
2008-05-04 7:34 ` Jan Kiszka
2008-05-04 17:09 ` malc
2008-05-04 17:41 ` Jan Kiszka
2008-05-04 19:35 ` Jan Kiszka
2008-05-05 18:03 ` malc
2008-05-05 18:43 ` Jan Kiszka
2008-05-06 17:37 ` malc
2008-05-06 17:59 ` Jan Kiszka
2008-05-07 18:36 ` malc
2008-05-07 22:24 ` Jan Kiszka
2008-05-08 17:44 ` malc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=481B80F0.8050705@web.de \
--to=jan.kiszka@web.de \
--cc=av1474@comtv.ru \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).