From: Thomas White <taw@bitwiz.me.uk>
To: guile-user@gnu.org
Cc: mikael@djurfeldt.com
Subject: Re: Guile-OSC: Open Sound Control library for Guile
Date: Mon, 15 May 2023 22:32:05 +0200 [thread overview]
Message-ID: <20230515223205.dc90e735b0413b14885b2c13@bitwiz.me.uk> (raw)
In-Reply-To: <CAA2XvwJ__aj6ypcBkAzwcyFLxyXm1WHSK+ZntFaHBuQJCmr5ew@mail.gmail.com>
On Fri, 12 May 2023 11:27:22 +0200
Mikael Djurfeldt <mikael@djurfeldt.com> wrote:
> Sorry, but I couldn't help it: What happens if there's a garbage
> collection in the middle of an arpeggio? :))
Haha, even though one isn't "supposed" to use a garbage collected
language for anything "real-time", in practice it's been completely
fine. First, the time resolution of the underlying control protocol
(DMX) is only about 20 ms anyway. Second, the changes in output are
usually smooth curves over several seconds, so millisecond-level jitter
isn't perceptible - if it even affects the output values at all.
Tom
--
Thomas White <taw@bitwiz.me.uk> <taw@physics.org>
https://www.bitwiz.me.uk https://github.com/taw10
prev parent reply other threads:[~2023-05-15 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 18:58 Guile-OSC: Open Sound Control library for Guile Thomas White
2023-05-12 9:27 ` Mikael Djurfeldt
2023-05-15 20:32 ` Thomas White [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230515223205.dc90e735b0413b14885b2c13@bitwiz.me.uk \
--to=taw@bitwiz.me.uk \
--cc=guile-user@gnu.org \
--cc=mikael@djurfeldt.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).