All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fons Adriaensen <fons.adriaensen@skynet.be>
To: Karsten Wiese <annabellesgarden@yahoo.de>
Cc: alsa-devel@lists.sourceforge.net, jackit-devel@lists.sourceforge.net
Subject: Re: jack crackles using ice1712 or es1968 recently intoduced? was: usx2y jack driver
Date: Sun, 26 Sep 2004 23:47:13 +0200	[thread overview]
Message-ID: <20040926214713.GC3519@linux> (raw)
In-Reply-To: <200409261724.53800.annabellesgarden@yahoo.de>

On Sun, Sep 26, 2004 at 05:24:53PM +0200, Karsten Wiese wrote:
<alsa and jack readers may skip the first lines>

> I mean the data calculated at aeolus startup or on retune.

The actual wavetables. These depend on four things:

1. stop definitions
2. tuning
3. temperament
4. sample frequency

So there are a lot of possible combinations. Most users will
use the same one most of the time, so it would make sense to
cache the wavetables somehow. It's one of the things I may
implement some rainy day... 

> My setup looks alike, but aeolus still takes its minute to boot,
> which it shurely deserves ;-)

:-) A real organ takes some time to build up the air pressure :-)
(agreed, less than a minute)

> Are there some subtle changes in alsa/jack relating ice1712 and es1968 
> recently introduced?
> like in alsa pcm device syncing code, which jackd uses to simultaneously 
> start/stop capture and playback?

I strongly suspect there are, but it's difficult to point out what
exactly has changed. I recently upgraded to SL9.1. This didn't work
at all (for audio). After an on-line update of the kernel (now
2.6.5-7.104-default) and instaling a more recent JACK and qjackctl
things are usable again. I will upgrade the kernel again when the
dust settles down.

I think your suspicion of the syncing code is warranted. Also the
snd-usb-audio remapping from 48 frames to 2^n is suspect, but that's
of course one of the things usx2y is meant to solve (haven't tried
it yet).

Besides the Terratec (ice1712) I also have an Edirol UA-5, and this
actually worked better (with snd-usb-audio) before the upgrade than after.

Meanwhile I found out some more about the xruns reported in my previous
message. The ones I have when Aeolus is calculating its wavetables with
-p64 or -p128 are due to memory allocation in a non-RT thread (blocks of
about one Mbyte at a time). Probably an -mm kernel would fix that. 
The cracks that remain afterwards are triggered by qjackctl updating its
connection diplay every 10 seconds. No idea what's the mechanism here.

But all by all, the system I have now works quite well with -p256, and
that's about all I need ATM.

-- 
Fons







-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php

      reply	other threads:[~2004-09-26 21:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22 20:28 [PATCH] usx2y jack driver Karsten Wiese
2004-09-22 23:50 ` Rui Nuno Capela
2004-09-24 22:31   ` Rui Nuno Capela
2004-09-25  2:15     ` [Jackit-devel] " Lee Revell
2004-09-25 13:55       ` Karsten Wiese
2004-09-25 15:10         ` [Jackit-devel] " Rui Nuno Capela
2004-09-25 19:33           ` Lee Revell
2004-09-25 19:56             ` Rui Nuno Capela
2004-09-25 20:01               ` Lee Revell
2004-09-26  0:13           ` Re: [Jackit-devel] " Lee Revell
2004-09-26 13:48             ` Rui Nuno Capela
2004-09-24 15:28 ` usx2y jack driver: missing usx2yhwdeppcm.h Rui Nuno Capela
2004-09-24 16:23   ` Karsten Wiese
     [not found] ` <200409251911.44533.annabellesgarden@yahoo.de>
     [not found]   ` <20040926091255.GA3526@linux>
2004-09-26 15:24     ` jack crackles using ice1712 or es1968 recently intoduced? was: usx2y jack driver Karsten Wiese
2004-09-26 21:47       ` Fons Adriaensen [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=20040926214713.GC3519@linux \
    --to=fons.adriaensen@skynet.be \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=annabellesgarden@yahoo.de \
    --cc=jackit-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.