Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Rosenauer <wolfgang@rosenauer.org>
To: tiwai@suse.de
Cc: alsa-devel@alsa-project.org
Subject: Re: Alsa 32-64 bit issue
Date: Wed, 02 Jul 2008 14:40:06 +0200	[thread overview]
Message-ID: <486B7726.1040608@rosenauer.org> (raw)
In-Reply-To: <s5h1w2ccwj4.wl%tiwai@suse.de>

Hi,

Takashi Iwai wrote:
> At Wed, 02 Jul 2008 13:48:18 +0200,
> Wolfgang Rosenauer wrote:
>> Hi,
>>
>> I'm new to to this list (and also Alsa) so please forgive me some newbie 
>> questions you probably find ;-)
>>
>> I have an application which does simple PCM output to Alsa. It works so 
>> far (if pulseaudio is not used but that's another issue).
>> But if I try to run the app (which is compiled for 32bit) on a 64bit 
>> Linux system it fails at snd_pcm_start() with the following error:
>>
>> "Datenübergabe unterbrochen (broken pipe)"
> 
> It means that no data is present on the buffer.

That could perfectly be the case. But that isn't really a 64bit system 
thing, is it? I admit there is most likely something wrong with the app 
as it is now :-(
The thing is that we can't guarantee that there are always audio frames 
in the buffer since we get it as a stream from somewhere else and need 
to do A/V sync.
Currently we just snd_pcm_start() and only afterwards write to the 
buffer as the data comes in what as I understood now is not the way it's 
gonna work?

I've tried to set a sensible start_threshold and just leave out the 
snd_pcm_start() but that created a very distorted sound output (but no 
broken pipe indeed).

Wolfgang

  reply	other threads:[~2008-07-02 12:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-02 11:48 Alsa 32-64 bit issue Wolfgang Rosenauer
2008-07-02 12:15 ` Takashi Iwai
2008-07-02 12:40   ` Wolfgang Rosenauer [this message]
2008-07-02 18:42     ` Wolfgang Rosenauer
2008-07-02 19:07       ` Gustavo da Silva Serra
2008-07-03 11:28         ` Wolfgang Rosenauer

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=486B7726.1040608@rosenauer.org \
    --to=wolfgang@rosenauer.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