8 Dec
2004
8 Dec
'04
7:59 a.m.
Hi all,
Just a quick note that we are currently considering starting a new version of
spiralsynthmodular from scratch (well almost) that will at first take the form
of a osc server/jack client that will load and connect ladspa plugins together.
Just wondering if anyone has an idea of an osc protocol for building modular
synths in this manner (thinking supercollider) and if we should use something
approaching a standard syntax of osc messages... this would mean that work
such as graphical user interfaces could be shared, etc...
Or has some or all this stuff already been done? Most of the work will be in
converting ssm's 50+ existing plugins to ladspa - and writing a gui that sends
osc messages.
My main motivation at this point is to just have a lightweight scriptable
non-gui jack ladspa modular effects rack for live performance use, should I
just use ecasound?
cheers,
dave
8 Dec
8 Dec
8:18 a.m.
I'm pretty sure someone else is working on something like this, OSC driven
UI, modules as LADSPA plugins, cant remeber the name though.
DSSI might be better for some SSM modules, it allows bulk data transfer
from UI->plugin and a couple of other things you might need.
- Steve
On Wed, Dec 08, 2004 at 12:48:52PM +0100, Dave Griffiths wrote:
Hi all,
Just a quick note that we are currently considering starting a new version of
spiralsynthmodular from scratch (well almost) that will at first take the form
of a osc server/jack client that will load and connect ladspa plugins together.
Just wondering if anyone has an idea of an osc protocol for building modular
synths in this manner (thinking supercollider) and if we should use something
approaching a standard syntax of osc messages... this would mean that work
such as graphical user interfaces could be shared, etc...
Or has some or all this stuff already been done? Most of the work will be in
converting ssm's 50+ existing plugins to ladspa - and writing a gui that sends
osc messages.
My main motivation at this point is to just have a lightweight scriptable
non-gui jack ladspa modular effects rack for live performance use, should I
just use ecasound?
cheers,
dave
11:41 a.m.
Steve Harris <S.W.Harris(a)ecs.soton.ac.uk> writes:
I'm pretty sure someone else is working on
something like this, OSC driven
UI, modules as LADSPA plugins, cant remeber the name though.
Its called Om, and AFAIK maintained by drobilla on #lad.
It has a very cool design, UI agnostic and all. Go Om, go!
--
CYa,
Mario
11:54 a.m.
On Wed, 08 Dec 2004 16:41:24 +0100, Mario Lang wrote
Steve Harris <S.W.Harris(a)ecs.soton.ac.uk>
writes:
yep, checking it out now - is the osc communication documented anywhere?
cheers,
dave
I'm pretty sure someone else is working on
something like this, OSC driven
UI, modules as LADSPA plugins, cant remeber the name though.
Its called Om, and AFAIK maintained by drobilla on #lad.
It has a very cool design, UI agnostic and all. Go Om, go! 
9 Dec
9 Dec
2:02 a.m.
On Wed, 2004-08-12 at 16:43 +0100, Dave Griffiths wrote:
On Wed, 08 Dec 2004 16:41:24 +0100, Mario Lang wrote
No, not yet. It's final exam time here, so I won't be able to do any
work on Om for 3 weeks or so. Hoping for a release in January. I've
intentionally not mentioned it on LAD yet to avoid the vapourware effect
- Om is not ready for casual users yet. Please don't mention it on LAU.
Please. :)
The version in CVS right now isn't polyphonic and there's no subpatching
yet, for the record - but both will be trivial to get working (polyphony
has already worked in the past, just not right now). It is, however,
exactly what you described - an OSC controlled LADSPA modular synth,
with a focus on live performance (and being a proper realtime jack
client), and it works right now. Sometimes. ;)
Obligatory outdated screenshot that says nothing about the program
whatsoever can be found here:
http://www.scs.carleton.ca/~drobilla/om.png
(Any #lad-ers around, feel free to front questions about Om if this
thread lives on - I'm way too busy to keep on top of LAD right now.)
If you really wish to see the OSC communication, the top of
src/engine/OSCReceiver.cpp has all the OSC callback registrations in one
nice little chunk of easily readable code. Many of the commands are
just random placeholders with no thought put into them whatsoever
though. :) I would like to clean up the protocol before release though,
so any input there is much appreciated.
I'll get around to creating a mailing list Real Soon Now(TM), promise.
--
-DR-
P.S. If anyone checks out the code, yes, the console client is broken
ATM.
Steve Harris <S.W.Harris(a)ecs.soton.ac.uk>
writes:
yep, checking it out now - is the osc communication documented anywhere?
cheers,
dave I'm pretty sure someone else is working on
something like this, OSC driven
UI, modules as LADSPA plugins, cant remeber the name though.
Its called Om, and AFAIK maintained by drobilla on #lad.
It has a very cool design, UI agnostic and all. Go Om, go!
2:04 a.m.
On Wed, 2004-08-12 at 12:18 +0000, Steve Harris wrote:
I'm pretty sure someone else is working on
something like this, OSC driven
UI, modules as LADSPA plugins, cant remeber the name though.
DSSI might be better for some SSM modules, it allows bulk data transfer
from UI->plugin and a couple of other things you might need.
- Steve
Oh yeah, forgot to mention: DSSI is on the TODO list as well.
Om is directly the reason I brought up that DSSI-midi-output thing on
the DSSI list a while back. :)
-DR-
7343
days inactive
7344
days old
linux-audio-dev@lists.linuxaudio.org
6 comments
5 participants
participants (5)
-
Dave Griffiths -
Dave Robillard -
Marek Peteraj -
Mario Lang -
Steve Harris