[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sc-devel] scsynth -L option

If you are running at only a small percentage of the CPU then there will be virtually no difference between scheduling per sample block vs per hardware buffer. Most of your events will come when rendering is not happening and so will be scheduled for the first sample block anyway. Rendering is bursty not continuous.

--- james mccartney @ iphone

On Mar 4, 2008, at 7:34 AM, ronald kuivila <rkuivila@xxxxxxxxxxxx> wrote:

Hi all,

Maybe a little explanation is in order. There are several different
issues parameters involved in system latency:

   blockSize                -z option
   hardware buffer size        -Z option
Server object latency language side parameter that can be tuned

  Right now, if the hardware buffer size is bigger than blockSize,
untimestamped messages are processed  on the next hardware
buffer rather than the next sample block.  (This is the issue Alberto
mentioned on the list a while ago.)

  The Server object latency imposes a delay that should be larger
than the largest delay associated with hardware buffer size and UDP
This will guarantee accurate timing. It can be altered without
rebooting the server.


On Mar 4, 2008, at 5:01 AM, Stefan Kersten wrote:

On 29.02.2008, at 14:59, Christopher Frauenberger wrote:
now that version 3.2 is launched, I would commit the change proposed.
It essentially introduces a -L switch to scsynth when compiled with
port-audio to specify a preferred latency. This is important as the
suggested latency (especially on Windows) is sometimes really high
(0.2 sec) and could be reduced by the user for time-critical things
through the server options.

shouldn't the hardware buffer size -Z option be used for specifying
the latency? scsynth seems to be competing already with csound in
terms of command line options ;)


Sc-devel mailing list

Sc-devel mailing list