From: Thomas White <taw@bitwiz.me.uk>
To: Guile User <guile-user@gnu.org>
Subject: Guile-OSC: Open Sound Control library for Guile
Date: Thu, 11 May 2023 20:58:06 +0200 [thread overview]
Message-ID: <20230511205806.7810b326cf0a0d1ebf9b40fb@bitwiz.me.uk> (raw)
Hi everyone,
I just wanted to mention a new project, Guile-OSC, which connects Guile
to Open Sound Control (http://opensoundcontrol.org/). It's a thin
wrapper around liblo (https://github.com/radarsat1/liblo), aiming for
just enough abstraction to enable idiomatic Scheme code.
Repository is here: https://github.com/taw10/guile-osc
With this, you can connect your Guile programs to physical control
devices with buttons, faders and knobs. There are hundreds of such
devices available, here are some randomly-selected examples:
https://www.allen-heath.com/ahproducts/xonek2
https://store.djtechtools.com/products/midi-fighter-twister
https://www.behringer.com/product.html?modelCode=P0B1X
A small interface program is usually needed to convert the native
protocol (usually MIDI over USB) to/from OSC, but there are many
options.
In my case, I'm using Guile-OSC it as part of my theatrical lighting
control DSL, Starlet (https://github.com/taw10/starlet).
Comments/pull requests/bug reports welcome!
Tom
--
Thomas White <taw@bitwiz.me.uk> <taw@physics.org>
https://www.bitwiz.me.uk https://github.com/taw10
next reply other threads:[~2023-05-11 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 18:58 Thomas White [this message]
2023-05-12 9:27 ` Guile-OSC: Open Sound Control library for Guile Mikael Djurfeldt
2023-05-15 20:32 ` Thomas White
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=20230511205806.7810b326cf0a0d1ebf9b40fb@bitwiz.me.uk \
--to=taw@bitwiz.me.uk \
--cc=guile-user@gnu.org \
/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).