public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: LWATCDR <lwatcdr@gmail.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Simple question.
Date: Tue, 03 Jan 2006 22:24:12 +0000	[thread overview]
Message-ID: <43BAF98C.6030408@superbug.co.uk> (raw)
In-Reply-To: <8c38cea40601031342s7b3158e2k99de34c50c4fb6ff@mail.gmail.com>

LWATCDR wrote:
> I am just starting to work with Alsa I compiled a test program from one of
> the tutorials and I am getting this error message.
> Unknown Error 126.
> Does anyone know what error 126 is?
> I am using "plughw:0,0" as the device name.
> and this is the segment of code that generates the error.
> 
> for (i = 0; i < 10; ++i) {
> if ((err = snd_pcm_writei (playback_handle, buf, 128)) != 128) {
>     fprintf (stderr, "write to audio interface failed (%s)\n", snd_strerror
> (err));
>     exit (1);
>     }
> }
> 
> 
> I am running Suse 9.3+kde 3.5
> 
> I hope this is the correct list to ask this.
> 

If the err > 0, it tells you how many frames were written to the sound 
card. As you can see here, 126 frames were written, probably due to 
sound card's hardware buffer being full.

James



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

      reply	other threads:[~2006-01-03 22:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03 21:42 Simple question LWATCDR
2006-01-03 22:24 ` James Courtier-Dutton [this message]

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=43BAF98C.6030408@superbug.co.uk \
    --to=james@superbug.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=lwatcdr@gmail.com \
    /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