25 Jan
2011
25 Jan
'11
10:54 p.m.
Hi,
I want to start using OSC to see what can be done with it.
What options are there for sending OSC messages?
For instance, what can I use to type OSC messages (or assign them to
keystrokes) and then send them?
Just something that is a good general purpose program and not
specialized to OSC messages for a particular application so that I can
start playing with it.
Cheers,
James
P.S. Prompted by a GUI freeze in Ardour and me wondering if it would
respond to OSC.
25 Jan
25 Jan
11:32 p.m.
Hey James,
I'd advise starting with Python, and a library called "liblo". It has a
dead-simple function
ardoursPortNumber = 3819 # usually anyway!
liblo.send( liblo.Address( ardoursPortNumber ), '/ardour/command/here',
parameter, parameter )
<shameless self promotion>
I wrote a blog post about it a while ago, still relevant although I belive
ardour has more OSC
functionality in the mean time. Here's the link:
http://harryhaaren.blogspot.com/2009/12/tut-6-ardour-control-using-osc-pyth…
</shameless self promotion>
Cheers, -Harry
On Tue, Jan 25, 2011 at 9:54 PM, James Morris <jwm.art.net(a)gmail.com> wrote:
Hi,
I want to start using OSC to see what can be done with it.
What options are there for sending OSC messages?
For instance, what can I use to type OSC messages (or assign them to
keystrokes) and then send them?
Just something that is a good general purpose program and not
specialized to OSC messages for a particular application so that I can
start playing with it.
Cheers,
James
P.S. Prompted by a GUI freeze in Ardour and me wondering if it would
respond to OSC.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
26 Jan
26 Jan
2:29 a.m.
On Wed, Jan 26, 2011 at 6:54 AM, James Morris <jwm.art.net(a)gmail.com> wrote:
Hi,
I want to start using OSC to see what can be done with it.
What options are there for sending OSC messages?
If visual patching is your style then take a look at puredata, in particular
the osc objects in the mrpeach external. See
http://www.youtube.com/watch?v=rxHIJx-O3iU to get a general idea. Note, that
there are a couple of patches in the wild to control ardour over osc through
pd, including http://gwen.coffy.name/Puredata/Apostool/ and
http://lists.puredata.info/pipermail/pd-list/2010-02/076045.html. Finally,
the PD floss manual has a small section on using OSC.
The flexibility of pd will allow you to bind osc messages to keystokes,
mouse movements or essentially any number of data inputs or outputs.
-michael
3:18 a.m.
James Morris wrote:
I want to start using OSC to see what can be done with
it.
Hi James,
An article on OSC that you might find useful:
http://www.linuxjournal.com/content/introduction-osc
Best,
dp
11:18 a.m.
On 01/25/2011 10:54 PM, James Morris wrote:
Hi,
I want to start using OSC to see what can be done with it.
What options are there for sending OSC messages?
Is there any osc-sequencer around? Something that records conventional
midi (like muse) but allows mapping of noteon/noteoff to OSC?
I guess it would be easy to make a mapping in chuck or something like
that, but a clever app could be better...
--
Atte
http://atte.dk http://modlys.dk
12:38 p.m.
On 01/26/2011 11:18 AM, Atte André Jensen wrote:
On 01/25/2011 10:54 PM, James Morris wrote:
I am beginning with implementing a mapping app pretty soon, but the
focus will be on doing calculations on sensor data. It is planned to
receive OSC, and send OSC (and Midi), but I guess receiving Midi would
also be a good idea - so we might do that eventually.
/ Hans
--
Hans Wilmers
NOTAM
Nedre gate 5
N-0551 Oslo Norway
tlf: +47 2235 8065
http://www.notam02.no
Hi,
I want to start using OSC to see what can be done with it.
What options are there for sending OSC messages?
Is there any osc-sequencer around? Something that records conventional
midi (like muse) but allows mapping of noteon/noteoff to OSC?
I guess it would be easy to make a mapping in chuck or something like
that, but a clever app could be better...
1:17 p.m.
Atte André Jensen wrote:
Is there any osc-sequencer around? Something that records conventional
midi (like muse) but allows mapping of noteon/noteoff to OSC?
I guess it would be easy to make a mapping in chuck or something like
that, but a clever app could be better...
http://code.google.com/p/midi2osc/
http://www.niallmoody.com/otherprograms.htm (Mouse2Osc)
http://kymatica.com/Software/AlgoScore (sequences OSC messages)
http://www.linuxjournal.com/content/linux-audio-update (further notes on
OSC and Linux audio softs)
Best,
dp
3:29 p.m.
Hi James!
if you want to give SuperCollider a try, i have this for SuperCollider
---osc---> Ardour control:
https://bitbucket.org/smoge/ardourcontrol
best!
5:51 p.m.
Quite a lot of different replies. But which would be the best place to
start for someone who doesn't know any of python, supercollider,
csound, chuck, algoscore, etc etc?
Why is OSC support not more widespread?
For instance, could/should there be an OSC tab in QjackCTL?
Should we not be able to create tracks in
muse/qtractor/seq24/rosegarden that output to OSC to provide all the
advantages OSC gives over MIDI?
Why isn't there an OSC-console style application, possibly curses
based, lightweight in size and dependencies, for simple sending of OSC
messages.
Installing supercollider pulled in emacs - according to the 'installed
size' that's 22mb + 93mb respectively - a little excessive for my use
case.
Harry, I probably should have tried your python suggestions first -
but not knowing any python has put me off - but at least python was
installed already on my system.
Thanks for replies.
James.
On 25 January 2011 21:54, James Morris <jwm.art.net(a)gmail.com> wrote:
Hi,
I want to start using OSC to see what can be done with it.
What options are there for sending OSC messages?
For instance, what can I use to type OSC messages (or assign them to
keystrokes) and then send them?
Just something that is a good general purpose program and not
specialized to OSC messages for a particular application so that I can
start playing with it.
Cheers,
James
P.S. Prompted by a GUI freeze in Ardour and me wondering if it would
respond to OSC.
--
_
: http://jwm-art.net/
-audio/image/text/code/
6:17 p.m.
On Wed, Jan 26, 2011 at 11:51 AM, James Morris <jwm.art.net(a)gmail.com> wrote:
Quite a lot of different replies. But which would be
the best place to
start for someone who doesn't know any of python, supercollider,
csound, chuck, algoscore, etc etc?
Why is OSC support not more widespread?
because there are almost no standards for OSC. this is not a protocol
like MIDI that defines semantics. there is no standard way, for
example, to tell an "OSC supporting app" to "start playing". an OSC
sender has to know a lot about the OSC receiver. this severely limits
OSC's usefulness (but does not make it zero by any means).
For instance, could/should there be an OSC tab in
QjackCTL?
could there be? if someone added OSC port support to JACK (which is
relatively easy to do), sure.
Should we not be able to create tracks in
muse/qtractor/seq24/rosegarden that output to OSC to provide all the
advantages OSC gives over MIDI?
ardour4 will support this. for whatever that's worth.
27 Jan
27 Jan
8:13 a.m.
Paul Davis wrote:
On Wed, Jan 26, 2011 at 11:51 AM, James
Morris<jwm.art.net(a)gmail.com> wrote:
I wonder if it could
make sense/be interesting for this community to
put forward some effort in this direction. That is, discussing and then
trying to agree on a standard (broad meaning intended) for
audio/music-aware applications, hardware etc. that use OSC... could be
'LADOSC' :)
I'm no OSC expert myself, and am grateful to the James for opening the
discussion which has already given me various interesting pointers and
insights.
I've always been looking at OSC as better alternative to MIDI, but
(partly due to usual laziness of course) have also looked at the
familiarity and 'cosiness' of the good ol' MIDI standard.
A first step might be to try 'porting' all standard MIDI stuff to some
agreed OSC scheme, exploiting the latter's functionality. For e.g. one
apparently trivial, but IMHO iportant aspect, is the fact that precision
isn't limited to 127 like in MIDI.
Another aspect is: apart from real-time use, how is osc 'recored'? Would
a simple timestamped list of OSC messages do? What about time
resolution? Is this (persistence) aspect relevant? Does it make sense to
think of OSC-files similar a la MIDIfiles?
Just some thoughts/ideas
Lorenzo.
[...]
Why is OSC support not more widespread?
because there are almost no standards for
OSC. this is not a protocol
like MIDI that defines semantics. there is no standard way, for
example, to tell an "OSC supporting app" to "start playing". an OSC
sender has to know a lot about the OSC receiver. this severely limits
OSC's usefulness (but does not make it zero by any means). For instance,
could/should there be an OSC tab in QjackCTL?
could there be? if someone added OSC
port support to JACK (which is
relatively easy to do), sure.
Should we not be able to create tracks in
muse/qtractor/seq24/rosegarden that output to OSC to provide all the
advantages OSC gives over MIDI?
ardour4 will support this. for whatever that's
worth.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
26 Jan
26 Jan
9:28 p.m.
On Wednesday 26 January 2011 17:51:41 James Morris wrote:
Quite a lot of different replies. But which would be
the best place to
start for someone who doesn't know any of python, supercollider,
csound, chuck, algoscore, etc etc?
Why is OSC support not more widespread?
It is relatively wide spread. However due to its nature, it neither defines a
standard way of detecting "remote" apps with osc interface, nor does it
provide a standard way to introspect. So for example a pair of apps that do
gui->backend split will work because both written by the same author(s) know
how to detect and talk to each other. For apps written by different authors, it
gets difficult. And its basically impossible to write any "generic osc sender
tool"...
For instance, could/should there be an OSC tab in
QjackCTL?
If osc was a protocol that has a centralized distribution like jack does for
audio and midi and alsa-midi does for midi. But most osc usage happens over
udp, that is network. That is fine to have gui and backend on different machines
but completely incompatible with qjackctl providing a "central patchbay" (not
that this concept would make any sense for osc).
In general it would be possible to send osc over jack-ports. Jack supports
generic port types and osc isn't actually fixed on using udp. But the problem
is: when app A sends osc across a jack-osc-connection, who guarantees that app
B can actually do something useful with it? osc just defines a way messages are
sent. It doesn't care about specific messages, it doesn't care about answers,
it doesn't care about the transport...
BTW: For entry into osc, python and its liblo-interface should give you a good
start.
Have fun,
Arnold
27 Jan
27 Jan
7:25 a.m.
On Wed, Jan 26, 2011 at 09:28:09PM +0100, Arnold Krille wrote:
On Wednesday 26 January 2011 17:51:41 James Morris
wrote:
Yes, this lack of introspection is a significant obstacle. It was a huge PITA to figure
out what parameters of various DSSI synths were available and how to control them. I ended
up having to use write/adapt an OSC sniffer (http://restivo.org/projects/oscsniff) in
order to figure out WTF was going on between the GUI and the synths.
Quite a lot of different replies. But which would
be the best place to
start for someone who doesn't know any of python, supercollider,
csound, chuck, algoscore, etc etc?
Why is OSC support not more widespread?
It is relatively wide spread. However due to its nature, it neither defines a
standard way of detecting "remote" apps with osc interface, nor does it
provide a standard way to introspect. So for example a pair of apps that do
gui->backend split will work because both written by the same author(s) know
how to detect and talk to each other. For apps written by different authors, it gets difficult. And its basically impossible to write
any "generic osc sender
tool"...
For instance, could/should there be an OSC tab in
QjackCTL?
If osc was a protocol that has a centralized distribution like jack does for
audio and midi and alsa-midi does for midi. But most osc usage happens over
udp, that is network. That is fine to have gui and backend on different machines
but completely incompatible with qjackctl providing a "central patchbay" (not
that this concept would make any sense for osc).
In general it would be possible to send osc over jack-ports. Jack supports
generic port types and osc isn't actually fixed on using udp. But the problem
is: when app A sends osc across a jack-osc-connection, who guarantees that app
B can actually do something useful with it? osc just defines a way messages are
sent. It doesn't care about specific messages, it doesn't care about answers,
it doesn't care about the transport...
BTW: For entry into osc, python and its liblo-interface should give you a good
start.
Have fun,
Arnold _______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
5 p.m.
On Thu, Jan 27, 2011 at 1:24 AM, Ken Restivo <ken(a)restivo.org> wrote:
Yes, this lack of introspection is a significant
obstacle. It was a huge PITA to figure out what parameters of various DSSI synths were
available and how to control them. I ended up having to use write/adapt an OSC sniffer
(http://restivo.org/projects/oscsniff) in order to figure out WTF was going on between the
GUI and the synths.
there *is* a "standard" for introspection, and its implemented by
liblo. i don't have time right now to come up with the URL for the
paper that defines it.
but this doesn't help with semantics.
12:54 a.m.
On Wed, Jan 26, 2011 at 11:51 AM, James Morris <jwm.art.net(a)gmail.com> wrote:
Quite a lot of different replies. But which would be
the best place to
start for someone who doesn't know any of python, supercollider,
csound, chuck, algoscore, etc etc?
[SNIP]
Why isn't there an OSC-console style application,
possibly curses
based, lightweight in size and dependencies, for simple sending of OSC
messages.
Install pyliblo (http://das.nasophon.de/pyliblo/) and try the send_osc
command line utility.
Combining the python cmd module
(http://wiki.python.org/moin/CmdModule) with pyliblo would probably
give you nice start towards an "OSC-console".
5052
days inactive
5054
days old
linux-audio-user@lists.linuxaudio.org
14 comments
12 participants
participants (12)
-
Arnold Krille -
Atte André Jensen -
Bernardo Barros -
Dave Phillips -
Hans Wilmers -
Harry Van Haaren -
James Morris -
Ken Restivo -
Lorenzo Sutton -
michael noble -
Paul Coccoli -
Paul Davis