From: Takashi Iwai <tiwai@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Karel Kulhavy <clock@twibright.com>,
Michal Schmidt <xschmi00@stud.feec.vutbr.cz>,
linux-kernel@vger.kernel.org
Subject: Re: software mixing in alsa
Date: Wed, 18 May 2005 15:44:55 +0200 [thread overview]
Message-ID: <s5hmzqssl60.wl@alsa2.suse.de> (raw)
In-Reply-To: <1116372742.2567.1.camel@mindpipe>
At Tue, 17 May 2005 19:32:22 -0400,
Lee Revell wrote:
>
> On Tue, 2005-05-17 at 17:36 -0400, Lee Revell wrote:
> > On Tue, 2005-05-17 at 23:04 +0200, Karel Kulhavy wrote:
> > > On Tue, May 17, 2005 at 09:28:03PM +0200, Michal Schmidt wrote:
> > > > Lee Revell wrote:
> > > > >mpg123 is an open source application so there's no excuse for it not to
> > > > >support ALSA in 2005.
> > > >
> > > > Its COPYING file says:
> > > > This software may be distributed freely, provided that it is
> > > > distributed in its entirety, without modifications, ...
> > > > This doesn't look like an open source license at all.
> > > > That's why Debian puts mpg123 in non-free.
> > > >
> > > > Karel, you may want to try mpg321 instead. It already has ALSA support.
> > >
> > > Tried with the same result: fast forward.
> > >
> >
> > Then the problem is probably with your ALSA configuration, or (less
> > likely) an ALSA bug. I suspect your MP3s are 44100 KHz and they are
> > being played at 48000 KHz.
>
> OK, I found this bug report that describes the same problem:
>
> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1098
This sounds similar, but I guess it's different.
> The short answer is that you need to have mpg321 use the "plug:dmix"
> device.
The recent libao opens "default" PCM. So, dmix should work without
any changes when you install ALSA 1.0.9(rc3).
Takashi
prev parent reply other threads:[~2005-05-18 13:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 9:56 software mixing in alsa Karel Kulhavy
2005-05-17 10:08 ` Jan Spitalnik
2005-05-17 14:13 ` Karel Kulhavy
2005-05-17 18:32 ` Lee Revell
2005-05-17 19:24 ` Karel Kulhavy
2005-05-17 19:32 ` Lee Revell
2005-05-17 20:27 ` Valdis.Kletnieks
2005-05-17 20:36 ` Lee Revell
2005-05-18 13:32 ` Karel Kulhavy
2005-05-18 13:53 ` Jaroslav Kysela
2005-05-18 17:47 ` Lee Revell
2005-05-18 6:30 ` ross
2005-05-18 8:42 ` Lee Revell
2005-05-18 13:21 ` Karel Kulhavy
2005-05-18 13:50 ` Nix
2005-05-18 13:48 ` Takashi Iwai
2005-05-18 14:38 ` Pierre Ossman
2005-05-18 18:25 ` Lee Revell
2005-05-19 15:10 ` Valdis.Kletnieks
2005-05-18 9:22 ` Pavel Machek
2005-05-17 19:28 ` Michal Schmidt
2005-05-17 21:04 ` Karel Kulhavy
2005-05-17 21:36 ` Lee Revell
2005-05-17 23:32 ` Lee Revell
2005-05-18 13:44 ` Takashi Iwai [this message]
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=s5hmzqssl60.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=clock@twibright.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=xschmi00@stud.feec.vutbr.cz \
/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