Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Sjostrand <gorm@cucumelo.org>
To: Peter Good <psgood@petesinternet.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH] cs46xx: variable period size support,	Santa Cruz rear output fixes
Date: Sat, 09 Nov 2002 12:43:05 +0100	[thread overview]
Message-ID: <3DCCF4C9.8040707@cucumelo.org> (raw)
In-Reply-To: 1036817449.30137.2.camel@pete

>
>
>So should the drive be able to set period size with this patch?
>
>Reason I ask is this.
>
>spongy@pete:~$ alsaplayer
>error on set_period_size (1024)
>  
>
Still maximum period size is 512, just as before.
Try start alsaplayer:
alsaplayer -f 2048
alsaplayer -f 1024
alsaplayer -f 512
alsaplayer -f 128
alsaplayer -f 64

And you can try start jackd:
/usr/local/bin/jackd -R -a -d alsa -p 512 -d pcm.cs46xx
/usr/local/bin/jackd -R -a -d alsa -p 128 -d pcm.cs46xx
/usr/local/bin/jackd -R -a -d alsa -p 64 -d pcm.cs46xx
/usr/local/bin/jackd -R -a -d alsa -p 32 -d pcm.cs46xx

Should work OK, however you probably wil have a lot of xruns
with low period sizes.
Should be interesting test this with low-latency patch, or
preemptive-scheduler.

/Benny




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-11-09 11:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-09  4:50 [PATCH] cs46xx: variable period size support, Santa Cruz rear output fixes Peter Good
2002-11-09 11:43 ` Benny Sjostrand [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-03 22:11 Benny Sjostrand
2002-11-04  1:13 ` Benny Sjostrand
2002-11-04 14:13   ` Takashi Iwai

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=3DCCF4C9.8040707@cucumelo.org \
    --to=gorm@cucumelo.org \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=psgood@petesinternet.net \
    /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