unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: joakim@verona.se
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Integrating Midi into Emacs
Date: Sat, 10 Jan 2015 09:28:59 +0100	[thread overview]
Message-ID: <m3iogfqbsk.fsf@exodia.verona.se> (raw)
In-Reply-To: <87h9vzmww4.fsf@fencepost.gnu.org> (David Kastrup's message of "Fri, 09 Jan 2015 23:06:51 +0100")

David Kastrup <dak@gnu.org> writes:

> joakim@verona.se writes:
>
>> - I'm sure you considered OSC, but heres a link anyway:
>>   http://delysid.org/emacs/osc.el>
>> My idea with OSC was to embedd gtk sliders in a buffer, and drive a
>> softsynth made with Overtone with these sliders using OSC.
>>
>> Anyway, good luck with your project!
>
> I actually don't have the foggiest what I am supposed to do with OSC and
> osc.el.  At any rate, opening a link into some generic sound control
> network server is not at the same level of complexity as operating some
> Midi device.  So I'm going to pursue my Midi entry project
> independently.  Whether or not one can use OSC as an alternative source
> of the respective events: no idea.

OSC is indeed on a level above plain Midi, so they are not mutually
exclusive. I mostly thought it was related, thats all.


-- 
Joakim Verona



      reply	other threads:[~2015-01-10  8:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-02 11:28 Integrating Midi into Emacs David Kastrup
2015-01-02 13:24 ` davi
2015-01-02 21:11 ` Christopher Allan Webber
2015-01-03  9:27   ` David Kastrup
2015-01-09 21:21 ` joakim
2015-01-09 21:59   ` David Kastrup
2015-01-10  8:32     ` joakim
2015-01-14  9:42       ` Niels Giesen
2015-01-14 10:49         ` David Kastrup
2015-01-14 11:20           ` David Kastrup
2015-01-09 22:06   ` David Kastrup
2015-01-10  8:28     ` joakim [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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3iogfqbsk.fsf@exodia.verona.se \
    --to=joakim@verona.se \
    --cc=dak@gnu.org \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).