-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear Luis, dear Dave,
> From [EMAIL PROTECTED] Sat Sep 8 12:33:34 2001
> Date: Wed, 05 Sep 2001 14:19:07 -0300
> From: luis jure <[EMAIL PROTECTED]>
> To: Dave Phillips <[EMAIL PROTECTED]>
> Subject: Re: babo bug?
>
> Dave Phillips escribió:
>
> >
> > This is definitely not happening for me. However, I am running a
> > low-latency kernel, with Csound compiled with the setuid flag.
>
>
> hi dave,
>
> yet another mail about this babo business!
>
> i nailed down the problem: the -b flag.
>
> i don't have an extremely fast machine, and don't have the low-latency
> patched kernel either, so i have to set a bigger buffer size when using
> the babo opcode in real-time. that seems to cause problems in the
> unofficial linux csound.
>
> i haven't been too systematic, but i can state the following:
>
> 1) using for example -b4096 for buffer size produces temporal deviations
> in the real-time output of orchestras using babo opcode (the pulses of
> the fof opcode in the example, that should be regular, become irregular)
>
> 2) that doesn't happen with lower buffer sizes, or not using the -b flag
> at all (but for the problems i mentioned above, in my machine i get
> plops in the output, since the compilation isn't fast enough)
this is very funny indeed. Does this happen also when you direct the
output to a file?
Can you provide a orc/sco pair or a .csd file which produces the problem?
What unofficial version are you using?
[snip]
> 4) this doesn't happen in the "official" version, either the buffer is
> big enough for a clean output or not, but the tempo doesn't change
this is even funnier :) the babo sources are practically identical,
save some differences in comments or in inlining functions...
You got me really curious now :)
ciao
nicb
+--------------------------------------------------------------------+
|Nicola Bernardini |
|E-mail: [EMAIL PROTECTED] |
|GPG Fingerprint = 6AE6 AF21 E160 D9B3 396E EBAC 906C CFAE 4D65 D910|
+--------------------------------------------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Made with pgp4pine
iD8DBQE7mfVEkGzPrk1l2RARAtieAKCA28sZ8zd0o0JhrA1ge7xbDjgPugCgkuh3
Uk/hZ4D4mYfLxc4lPEZHgyU=
=YgRv
-----END PGP SIGNATURE-----