Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000067]: Alsa sound repeats first half a second over and over
Date: Tue, 31 May 2005 18:02:11 +0200	[thread overview]
Message-ID: <a32754724d8dd0211733c2d735cbfdff@bugtrack.alsa-project.org> (raw)


The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=67> 
======================================================================
Reported By:                trejkaz
Assigned To:                perex
======================================================================
Project:                    ALSA - driver
Issue ID:                   67
Category:                   PCI - via82xx
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Distribution:               Gentoo
Kernel Version:             2.6.2
Resolution:                 suspended
Fixed in Version:           
======================================================================
Date Submitted:             02-17-2004 10:05 CET
Last Modified:              05-31-2005 18:02 CEST
======================================================================
Summary:                    Alsa sound repeats first half a second over and over
Description: 
When playing a sound with /usr/bin/aplay, it will play the first half a
second and repeat the same fragment of the file over and over.

Playing with /usr/bin/play, it repeats every second instead.
======================================================================

----------------------------------------------------------------------
 trejkaz - 02-26-04 13:47 
----------------------------------------------------------------------
Okay, I'll take this up with the kernel team.  Although I noticed Kernel
2.6.3 had a whole bunch of fixes which may or may not be relevant anyway,
I just need to get it to compile. ;-)

----------------------------------------------------------------------
 perex - 03-14-04 19:50 
----------------------------------------------------------------------
No further response from user.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
02-17-04 10:05 trejkaz        New Issue                                    
02-17-04 10:09 trejkaz        Issue Monitored: trejkaz                     
02-17-04 10:10 trejkaz        Note Added: 0000249                          
02-17-04 18:49 tiwai          Note Added: 0000258                          
02-17-04 22:04 trejkaz        Note Added: 0000261                          
02-26-04 12:06 perex          Note Added: 0000339                          
02-26-04 13:47 trejkaz        Note Added: 0000349                          
03-14-04 19:50 perex          Status                   new => resolved     
03-14-04 19:50 perex          Resolution               open => suspended   
03-14-04 19:50 perex          Assigned To               => perex           
03-14-04 19:50 perex          Note Added: 0000603                          
05-31-05 18:02 perex          Status                   resolved => closed  
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005

                 reply	other threads:[~2005-05-31 16:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=a32754724d8dd0211733c2d735cbfdff@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox