From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000617]: Front / rear out of sync
Date: Tue, 7 Dec 2004 15:38:42 +0100 [thread overview]
Message-ID: <9455ce5d46f11b706889e6fa902500a4@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=617>
======================================================================
Reported By: henkie_
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 617
Category: PCI - cs46xx
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: SuSE 9.0
Kernel Version: 2.4.26
======================================================================
Date Submitted: 10-30-2004 18:20 CEST
Last Modified: 12-07-2004 15:38 CET
======================================================================
Summary: Front / rear out of sync
Description:
When using the config specified below the sound gets out of sync (front and
rear sound) in xmms. The higher cpu-usage is the faster the sound goes
out-of-sync. When using mplayer in combo with this config, cpu usage goes
up, and the image of the movie halts but sound keeps playing. Without this
config the cpu-usage is around 20%. Tested on P4 2.8GHz.
In alsa <1.0 the front and rear sound was duplicated, is it possible to
reimplement that behaviour again?
pcm.ch40dup {
type route
slave.pcm surround40
slave.channels 4
ttable.0.0 1
ttable.1.1 1
ttable.0.2 1
ttable.1.3 1
}
======================================================================
----------------------------------------------------------------------
tiwai - 12-06-04 20:53
----------------------------------------------------------------------
Could you try another one (config2.diff)?
The patches are already merged into ALSA CVS, BTW.
----------------------------------------------------------------------
darkbrain - 12-07-04 15:38
----------------------------------------------------------------------
ok perfect!
Issue History
Date Modified Username Field Change
======================================================================
10-30-04 18:20 henkie_ New Issue
10-30-04 18:20 henkie_ Distribution => SuSE 9.0
10-30-04 18:20 henkie_ Kernel Version => 2.4.26
11-10-04 12:43 tiwai Note Added: 0002368
11-10-04 22:37 henkie_ Note Added: 0002379
11-29-04 15:13 darkbrain Note Added: 0002636
12-02-04 00:53 darkbrain Note Added: 0002672
12-02-04 02:02 henkie_ Note Added: 0002673
12-02-04 12:17 tiwai Note Added: 0002678
12-02-04 14:32 lemoncurry Note Added: 0002680
12-02-04 14:55 tiwai Note Added: 0002681
12-02-04 14:55 tiwai File Added: cs46xx-front-dup.diff
12-02-04 14:56 tiwai File Added: cs46xx-front-dup-config.diff
12-02-04 15:53 lemoncurry Note Added: 0002685
12-02-04 19:18 tiwai Note Added: 0002688
12-04-04 15:08 darkbrain Note Added: 0002716
12-06-04 20:53 tiwai Note Added: 0002733
12-06-04 20:54 tiwai File Added: cs46xx-front-dup-config2.diff
12-07-04 15:38 darkbrain Note Added: 0002748
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next reply other threads:[~2004-12-07 14:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 14:38 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-07 16:47 [ALSA - driver 0000617]: Front / rear out of sync bugtrack
2004-12-07 14:42 bugtrack
2004-12-06 19:54 bugtrack
2004-12-04 14:08 bugtrack
2004-12-02 18:18 bugtrack
2004-12-02 14:53 bugtrack
2004-12-02 13:55 bugtrack
2004-12-02 13:32 bugtrack
2004-12-02 11:17 bugtrack
2004-12-02 1:02 bugtrack
2004-12-01 23:53 bugtrack
2004-11-29 14:13 bugtrack
2004-11-10 21:37 bugtrack
2004-11-10 11:43 bugtrack
2004-10-30 16:20 bugtrack
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=9455ce5d46f11b706889e6fa902500a4@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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 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.