All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Schmidt <mista.tapas@gmx.net>
To: alsa-devel@alsa-project.org
Subject: Re: [ALSA - driver 0000371]: dmix does not work with snd-cs46xx driver
Date: Thu, 15 Jul 2004 15:01:43 +0200	[thread overview]
Message-ID: <20040715150143.37ad191c@mango.fruits.de> (raw)
In-Reply-To: <20040715121018.7AFE315009@server.perex-int.cz>

On Thu, 15 Jul 2004 14:10:18 +0200 (CEST)
noreply@alsa-project.org wrote:

> 
> The following bug has been ASSIGNED.
> ======================================================================
> Summary:                    dmix does not work with snd-cs46xx driver
> Description: 
> When trying to use dmix with the snd-cs46xx driver, no output is produced.
> ======================================================================

Hi,

i also wanted to chime in here with another remark [i seem to be unable to create a mantis account [see end of this message]:

Well, not only does dmix not work with cs46xx, but also dsnoop doesn't work correctly when cs46xx is slave. Like someboy else mentioned on  this list already, the appl_pointers from the corresponding slave devices don't advance [while the hw pointers do]. Symptom for dsnoop: the first recorded buffer after opening the dsnoop pcm is repeated over and over [this is not surprising if none of the pointers advance]. Symptom for dmix: the first buffer is played back over and over which results in silence when the first period of the playback contains silence..

the alsa pcm ladspa plugin doesn't have this problem btw..


Regards,
  Florian Schmidt


----- This is what i get from mantis:

ALSA bugtracking system

Warning: Cannot modify header information - headers already sent by (output started at /srv/www/mantisbt-0.18.3/core/html_api.php:139) in /srv/www/mantisbt-0.18.3/core/gpc_api.php on line 220

Warning: Cannot modify header information - headers already sent by (output started at /srv/www/mantisbt-0.18.3/core/html_api.php:139) in /srv/www/mantisbt-0.18.3/core/print_api.php on line 37

Warning: Cannot modify header information - headers already sent by (output started at /srv/www/mantisbt-0.18.3/core/html_api.php:139) in /srv/www/mantisbt-0.18.3/core/print_api.php on line 39

Warning: Cannot modify header information - headers already sent by (output started at /srv/www/mantisbt-0.18.3/core/html_api.php:139) in /srv/www/mantisbt-0.18.3/core/print_api.php on line 44

-- 
Palimm Palimm!
Sounds/Ware:
http://affenbande.org/~tapas/



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

  reply	other threads:[~2004-07-15 12:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-15 12:10 [ALSA - driver 0000371]: dmix does not work with snd-cs46xx driver noreply
2004-07-15 13:01 ` Florian Schmidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-29 17:10 bugtrack
2006-03-26  1:06 bugtrack
2006-03-25  1:17 bugtrack
2006-03-24  1:54 bugtrack
2006-03-24  1:16 bugtrack
2006-03-22 17:50 bugtrack
2006-03-22  2:42 bugtrack
2005-03-11 21:15 bugtrack
2005-03-10 14:03 bugtrack
2005-03-09 17:37 bugtrack
2005-03-09  2:09 bugtrack
2004-07-09 13:59 noreply

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=20040715150143.37ad191c@mango.fruits.de \
    --to=mista.tapas@gmx.net \
    --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.