Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pete <peterpion@yahoo.com>
To: John Rigg <aldev@sound-man.co.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: Xrun stack trace for 1010LT
Date: Mon, 15 Dec 2008 07:23:36 -0800 (PST)	[thread overview]
Message-ID: <395938.70869.qm@web65412.mail.ac4.yahoo.com> (raw)
In-Reply-To: <20081205160215.GA3295@localhost>

I have fixed my problem and thought it was best to make a record of what worked in case anyone is ever searching for it. This will I guess be obvious to most people seeing this but if I had been able to find a snippet like this a month ago, I would have saved many dozens of hours searching and trying things! So for those like me who dont intuitivley know this...

Turned out very simple, I just used /dev/sda3 (a 'raw' partition on the disk) as the output file. Now having tested for many hours, it works perfectly, and there has not been a single overrun, on a non RT kernel, with no special permissions, priority, prempt flags or anything. This is probably not suitable for many people as the output 'file' is not as conveniently accessable as a simple file, but if you need to make it work, thats how to do it.

I found that I couldent use arecord to write directly to the partition, im not exactly sure why but I guess its because arecord dosent quite know how to write to a partition. However making arecord output the digital data to stdout and piping it to dd which then writes it to the partition works fine. For the record thats 16 channels at 88200 kHz, 24 bit.

The partition can then be turned into a file using DD again to read it from the partition and write it to a file.

BTW if any developers are reading this, maybe you can improve the performance of some of the tools youre writing by using a scratch disk accessed directly? I would be interested to try if anyone does write it.

Thanks for the help.


John Rigg <aldev@sound-man.co.uk> wrote: On Fri, Dec 05, 2008 at 07:23:00AM -0800, Pete wrote:
> Is there likely to be any disadvantage to running arecord rather
> than say Jack to capture? Does (say) Jack read the card in a 'better' 
> way?

jackd runs with realtime priority if -R option is specified
when starting it. Running it without -R produces xruns fairly 
often, but with -R they almost never happen on a properly configured
system. I don't know if arecord can run with realtime priority.

John
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      parent reply	other threads:[~2008-12-15 15:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 14:18 Xrun stack trace for 1010LT Pete cat
2008-12-05 14:26 ` Takashi Iwai
2008-12-05 14:48   ` Pete cat
2008-12-05 15:17     ` John Rigg
2008-12-05 15:20       ` Pete
2008-12-05 15:23         ` Pete
2008-12-05 16:02           ` John Rigg
2008-12-05 16:11             ` Pete
2008-12-05 19:41               ` John Rigg
2008-12-05 21:39                 ` Pete
2008-12-06 14:46                   ` John Rigg
2008-12-15 15:23             ` Pete [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=395938.70869.qm@web65412.mail.ac4.yahoo.com \
    --to=peterpion@yahoo.com \
    --cc=aldev@sound-man.co.uk \
    --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