From: Philip Prindeville <philipp_subx@redfish-solutions.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Fixes for identifying VT1617 codec and MSI-7142 mobo
Date: Fri, 12 Aug 2005 11:08:17 -0600 [thread overview]
Message-ID: <42FCD781.3070306@redfish-solutions.com> (raw)
In-Reply-To: <s5hzmrn43d1.wl%tiwai@suse.de>
Well, this is what I get when I try the patch:
[root@media ~]# ./foo
Playing WAVE '/usr/share/system-config-soundcard/sound-sample.wav' :
Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
Warning: rate is not accurate (requested = 44100Hz, got = 48000Hz)
please, try the plug plugin (-Dplug:spdif)
Hooks PCM
Its setup is:
stream : PLAYBACK
access : RW_INTERLEAVED
format : S16_LE
subformat : STD
channels : 2
rate : 48000
exact rate : 48000 (48000/1)
msbits : 16
buffer_size : 16384
period_size : 4096
period_time : 85333
tick_time : 1000
tstamp_mode : NONE
period_step : 1
sleep_min : 0
avail_min : 4096
xfer_align : 4096
start_threshold : 16384
stop_threshold : 16384
silence_threshold: 0
silence_size : 0
boundary : 4611686018427387904
Slave: Hardware PCM card 0 'VIA 8237' device 0 subdevice 3
Its setup is:
stream : PLAYBACK
access : RW_INTERLEAVED
format : S16_LE
subformat : STD
channels : 2
rate : 48000
exact rate : 48000 (48000/1)
msbits : 16
buffer_size : 16384
period_size : 4096
period_time : 85333
tick_time : 1000
tstamp_mode : NONE
period_step : 1
sleep_min : 0
avail_min : 4096
xfer_align : 4096
start_threshold : 16384
stop_threshold : 16384
silence_threshold: 0
silence_size : 0
boundary : 4611686018427387904
access: RW_INTERLEAVED
format: S16_LE
subformat: STD
channels: 2
rate: 48000 (48000/1)
period_size: 4096
buffer_size: 16384
tick_time: 1000
[root@media ~]#
I also noticed that it sounds like the first 200ms or so of sound is
being dropped consistently...
-Philip
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-12 17:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 18:41 Fixes for identifying VT1617 codec and MSI-7142 mobo Philip Prindeville
2005-08-07 19:27 ` Sergey Vlasov
2005-08-08 16:16 ` Philip Prindeville
2005-08-08 16:42 ` Takashi Iwai
[not found] ` <42F8F69D.2050302@redfish-solutions.com>
2005-08-11 10:42 ` Takashi Iwai
2005-08-11 19:21 ` Philip Prindeville
2005-08-12 14:40 ` Takashi Iwai
2005-08-12 14:49 ` Takashi Iwai
2005-08-12 17:08 ` Philip Prindeville [this message]
2005-08-12 17:27 ` Takashi Iwai
2005-08-12 17:31 ` Philip Prindeville
2005-08-12 17:32 ` Takashi Iwai
2005-08-12 17:38 ` Philip Prindeville
2005-08-12 17:41 ` Takashi Iwai
2005-08-12 18:12 ` Philip Prindeville
2005-08-12 18:29 ` Takashi Iwai
2005-08-12 19:37 ` Philip Prindeville
2005-08-12 19:49 ` Philip Prindeville
2005-08-15 12:35 ` Takashi Iwai
2005-08-12 15:18 ` Philip Prindeville
2005-08-12 15:26 ` Lee Revell
2005-08-12 15:28 ` Philip Prindeville
2005-08-12 15:29 ` Philip Prindeville
2005-08-12 15:33 ` Takashi Iwai
[not found] ` <42FCD233.5010907@redfish-solutions.com>
2005-08-12 16:52 ` Takashi Iwai
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=42FCD781.3070306@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.