Re: [ecasound] My presentation + error in the OSC documentation

From: ORL <fakeorl@email-addr-hidden>
Date: Tue Feb 07 2012 - 20:44:46 EET

Le 07/02/2012 11:34, ORL a écrit :
> Hi there,
> I'm new to this list, quite new to eacsound (though I already used it to
> record live shows, and used ecasignalview to monitor some things several
> years ago), but not quite new to Linux Audio things.
> I'm working in an Freak and Free Arts Coo[r]p called AMMD
> (, which are artists caring about artists (production,
> management, booking, ads...), with a very high ethical sense of all this
> these words, and the whole thing being sustained by the use of Free Art
> License only, and Free Softwares also (thought some artists coming by us
> use several proprietary things when they arrive).
> My job in here consists in:
> - first, being a musician/actor, especially in the band Sebkha-Chott
> (, and also in several other projects,
> - second, manage the whole AMMD, and lead and book most of the projects,
> being only the administrative starter on this,
> - third, I'm sound technician in the AMMD, which owns a studio (see
> for details, or check,
> - fourth, teach the use of free softwares for live shows and audio/video
> production ; on this part I teach future sound guys, as well as already
> sound guys, as well as musician, music teacher, or even teenage
> beginning music. Our aim is to make it possible for each and everyone,
> and by working for already skilled people (who have funds raising for
> their continuous learning), we might teach for teenage people (who have
> nothing),
> - fifth, I do help theater companies, bands, and so on, to adapt their
> setup with free softwares, sometimes developping part of a software for
> them. Though, I'm not a skilled applicative progammer at all, and
> generally, my patches, though working in the very special case I've
> written them for, are refused by the apps developpers!!! ;)
> Well, that's it.
> So, I'm going to use ecasound in a quite big project, including synths,
> rhythmbox, audio routing and mixing, monitors management, and so on.
> I want to control it with OSC (as all other softwares I use are using
> it), and I found an error in the OSC documentation ; it's written that
> the standard path for an op is:
> /ecasound/chain/NAME/op/OPID/param/ID
> but this doesn't work, I finally found it is:
> /ecasound/chain/CHAINID/op/OPID/param/ID
> Actually, as I've thought this part is being developped right now, I
> would suggest the following:
> /ecasound/chain/CHAINNAME/op/OPNAME/param/PARAMNAME
> because it's much easier for "non-informatic" people, and much more
> readable when you monitor your OSC messages by the way.
> See you.
> Aurélien

Ahem, auto-reply, just to announce I didn't had understood that -a:
could be followed by a string, and that this string was called
"chainname". So it's working perfectly, and there's no error in the doc.

I've checked the code a bit, but didn't find any easy way to get op
giving their name to the OSC path, directly. It's annoying, as if you,
for example, choose to use another op before the others, all your OSC
controls upon that chain will be false.... In my particular case, it
obliged me to make 2 chains for each "strip", the second beginning with
-eadb, so that I'm sure I will act on the attenuation by sending an osc
message at the 1st op.

Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
Ecasound-list mailing list
Received on Tue Feb 7 20:15:02 2012

This archive was generated by hypermail 2.1.8 : Tue Feb 07 2012 - 20:15:02 EET