alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Raymond Yau <superquad.vortex2@gmail.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Which project to choose?
Date: Fri, 16 Jul 2010 08:39:29 +0800	[thread overview]
Message-ID: <AANLkTik16UoQM2zZMgs3An1dv8-i0gWpiTEg3qOLqFTC@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1007150007340.16744@eeebox2.perex-int.cz>

2010/7/15 Jaroslav Kysela <perex@perex.cz>

> On Wed, 14 Jul 2010, David Henningsson wrote:
>
> > 2010-07-14 17:25, Jaroslav Kysela skrev:
> >> On Wed, 14 Jul 2010, David Henningsson wrote:
> >>
> >>> 2010-07-14 13:13, Raymond Yau skrev:
> >>>
> >>>> localhost pulseaudio[24553]: alsa-util.c:   appl_ptr     : 735801008
> >>>> localhost pulseaudio[24553]: alsa-util.c:   hw_ptr       : 735846184
> >>>>
> >>>> This is underrun as you can see appl_ptr is behing hw_ptr
> >>>
> >>> Ehm, isn't that a ring buffer? I e, there is nothing wrong with
> appl_ptr
> >>> being less than hw_ptr.
> >>
> >> For playback, if appl_ptr is less than hw_ptr, it's underrun situation
> >> (application didn't feed samples in time to the driver's ring buffer).
> >>
> >> Note that pointers in ALSA are in range 0..boundary not
> >> 0..ring_buffer_size (boundary is near LONG_MAX value) - it's design to
> >> detect such situations (underrun, overrun).
> >
> > Okay, thanks for the clarification. But LONG_MAX (as in 2^31) would
> > still wrap around every thirteen hours (at 44100 Hz), so are we having
> > bugs, such as e g failure to detect underruns, at those occasions?
>
> >From values above, it looks like a standard underrun (samples didn't
> arrive in time to the ring buffer). Just check the real system time
> between I/O operations and you'll see if it's issue in the ALSA driver or
> a task scheduling problem.
>
>                                        Jaroslav
>

Looking  at the ens1371 specification , it seem to me that alsa-lib cannot
perform rewind too
I guess those 44101 rate is not really the best supported rate


4.2 Bus Master Cache Control (CCB)
This block control the transfer of data between the PCI memory and the
internal memory.
The Serial block signal when a cache fill/transfer is required in three
memory buffers

5.5 PCI Data transfer

Only brust read/write transfers are allowed. All data transfer are 8 Long
Word brust transfers

  reply	other threads:[~2010-07-16  0:39 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-13 23:02 Which project to choose? Chris
2010-07-13 23:26 ` Raymond Yau
2010-07-14  0:01   ` Chris
2010-07-14  1:20     ` Raymond Yau
2010-07-14  1:31       ` Chris
     [not found]         ` <AANLkTimNSRELBq7i1Ypi9K2tmFu9NKLvQAOOqPwuU13x@mail.gmail.com>
     [not found]           ` <1279074303.29042.3.camel@localhost.localdomain>
2010-07-14 12:23             ` Raymond Yau
2010-07-14 22:15               ` Chris
2010-07-15  0:08                 ` Raymond Yau
2010-07-15  1:38                   ` Chris
2010-07-15 12:58                     ` Colin Guthrie
2010-07-15 14:07                       ` Jaroslav Kysela
2010-07-15 22:54                         ` Chris
2010-07-15 23:15                           ` Raymond Yau
2010-07-16  0:24                             ` Chris
2010-07-16  5:32                               ` Jaroslav Kysela
2010-07-16  1:19                             ` Chris
2010-07-16  5:40                           ` Jaroslav Kysela
2010-07-17  0:22                             ` Raymond Yau
2010-07-15 22:02                       ` Raymond Yau
2010-07-19  1:44                       ` Raymond Yau
2010-07-19  2:56                         ` Chris
2010-07-19  6:35                           ` Raymond Yau
2010-07-19  7:53                             ` Colin Guthrie
2010-07-19 22:52                               ` Chris
2010-07-20  1:23                                 ` Raymond Yau
2010-07-20  2:13                                   ` Chris
2010-07-20 11:41                                     ` Raymond Yau
2010-07-20 22:19                                       ` Chris
2010-07-21  8:17                                         ` Raymond Yau
2010-07-21 22:57                                           ` Chris
2010-07-22  0:33                                             ` Raymond Yau
2010-07-22  1:07                                               ` Chris
     [not found]                                                 ` <AANLkTim7iY_w96CPkVIlyB7Z9NGWUIvX2wKwvgu4wdjn@mail.gmail.com>
     [not found]                                                   ` <1279766127.7841.11.camel@localhost.localdomain>
     [not found]                                                     ` <AANLkTim_FkOXlYihEQikJ8Vpo5zXreCdqQnDW3acsrAu@mail.gmail.com>
     [not found]                                                       ` <1279797682.7841.15.camel@localhost.localdomain>
2010-07-22 11:42                                                         ` Raymond Yau
2010-07-20 22:49                                       ` Chris
2010-07-24  3:51                       ` Raymond Yau
2010-07-25 14:14                         ` Colin Guthrie
2010-07-26  5:53                           ` Raymond Yau
2010-07-26  8:09                             ` Raymond Yau
2010-07-15 13:08                     ` Raymond Yau
2010-07-14 22:32     ` Raymond Yau
2010-07-14 22:58       ` Chris
2010-07-14 11:13 ` Raymond Yau
2010-07-14 15:06   ` David Henningsson
2010-07-14 15:25     ` Jaroslav Kysela
2010-07-14 19:45       ` David Henningsson
2010-07-14 22:13         ` Jaroslav Kysela
2010-07-16  0:39           ` Raymond Yau [this message]
2010-07-16  1:30           ` Raymond Yau
2010-07-15  0:52     ` Raymond Yau
2010-07-23 11:51     ` Raymond Yau

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=AANLkTik16UoQM2zZMgs3An1dv8-i0gWpiTEg3qOLqFTC@mail.gmail.com \
    --to=superquad.vortex2@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).