From: Tim Blechmann <tim@klingt.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: pointer callback question
Date: Thu, 12 Feb 2009 19:04:10 +0100 [thread overview]
Message-ID: <4994649A.8080005@klingt.org> (raw)
In-Reply-To: <s5hy6wbillh.wl%tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 974 bytes --]
Takashi Iwai wrote:
> At Thu, 12 Feb 2009 18:55:49 +0100,
> Tim Blechmann wrote:
>>>> the brief log is (4 periods of 64 frames):
>>>> stream_pointer at 64
>>>> stream_pointer at 128
>>>> stream_pointer at 192
>>>> stream_pointer at 256
>>> This is invalid. The pointer callback must return 0 in this case.
>>> The value the pointer callback returns is between 0 and buffer_size-1.
>> sry, typo, 5 periods of 64 frames
>
> Then it must be OK. If the stream is stopped, it's likely by the
> buffer underrun detection or so...
is there any way to compile alsa to get some debugging information about
that?
> BTW, you should be sure that the buffer size is aligned to the period
> size if such a design is assumed. Without the extra constraint, it
> could be unaligned as default.
hm, afaict alignment should be ok ...
thnx, tim
--
tim@klingt.org
http://tim.klingt.org
A good composer does not imitate; he steals.
Igor Stravinsky
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2009-02-12 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 17:50 pointer callback question Tim Blechmann
2009-02-12 17:54 ` Takashi Iwai
2009-02-12 17:55 ` Tim Blechmann
2009-02-12 17:58 ` Takashi Iwai
2009-02-12 18:04 ` Tim Blechmann [this message]
2009-02-13 6:26 ` Takashi Iwai
2009-02-26 14:44 ` Tim Blechmann
2009-02-28 12:48 ` Tim Blechmann
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=4994649A.8080005@klingt.org \
--to=tim@klingt.org \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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