From: "Marcelo Borges Ribeiro" <marcelo@datacom-telematica.com.br>
To: <linux-kernel@vger.kernel.org>
Subject: Re: via82cxxx_audio problems
Date: Tue, 13 Nov 2001 10:08:29 -0200 [thread overview]
Message-ID: <004601c16c3c$8f865e70$1300a8c0@marcelo> (raw)
In-Reply-To: <20011112220630.A1200@bruder.net> <20011113121907.A9058@telia.com>
The problem with via82xx is that it is locked in 48000Hz (you can see this
in dmesg) and cannot play in any other rate. With mplayer you can see
messages such as requested 16000Hz got (480000) that explains why it sounds
like chip'n'dale ;-). P.s. I don´t know why it works with xmms but with
mpg123 it refuses to play at all becouse these sound rates.
----- Original Message -----
From: "André Dahlqvist" <andre.dahlqvist@telia.com>
To: <linux-kernel@vger.kernel.org>
Sent: Tuesday, November 13, 2001 9:19 AM
Subject: Re: via82cxxx_audio problems
> sergio@bruder.net <sergio@bruder.net> wrote:
>
> > With rapid fast-forward in mplayer, The sound just mutes itself and
> > mplayer just crawls down to 1-2 frames per second. Looking at
> > /var/log/messages Ive got:
>
> Try the latest 2.4.15-preX kernel since that has a much newer VIA audio
> driver which might fix this.
> --
>
> André Dahlqvist <andre.dahlqvist@telia.com>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2001-11-13 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 0:06 via82cxxx_audio problems sergio
2001-11-13 11:19 ` André Dahlqvist
2001-11-13 12:08 ` Marcelo Borges Ribeiro [this message]
2001-11-13 12:17 ` Jeff Garzik
2001-11-13 12:39 ` Alan Cox
2001-11-13 13:50 ` Tobias Ringstrom
2001-11-13 16:53 ` Alan Cox
2001-11-14 2:27 ` sergio
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='004601c16c3c$8f865e70$1300a8c0@marcelo' \
--to=marcelo@datacom-telematica.com.br \
--cc=linux-kernel@vger.kernel.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