linuxaudio.org

On Wed, Aug 04, 2010 at 09:56:31AM -0500, Jack O'Quin wrote:
> On Wed, Aug 4, 2010 at 8:01 AM,   wrote:

quoted text
>

> > I'm still in doubt what to do with the configuration files. Since adding

> > OSC is easy, they could just be the textual form of OSC they are now.

> > The other option is to skip this and turn the config files into active

> > Python code, directly using the API.

> >

> > Integrating a Python interpreter with real-time code and event-driven

> > GUI code requires some trickery which I'll explore and hopefully get

> > working while in holiday (end of this month).

>

> That seems like a good approach. There's a lot to be said for using a

> complete programming language for configuration. Python provides

> functions, variables, control flow and classes, everything you'd be

> likely to need.

In particular when you consider that an Ambdec configuration consists

mostly of numbers that have to be calculated and that just can't be

modified 'manually' in any way that makes sense. If you want to

experiment and modify the matrices you need programming. Using Python

means you can do the calculations as part of the configuration, and

e.g. link them to parameters set in the GUI.
More generally I always tend to view a configuration as something

imperative rather than just a description. Which is one of the reasons

why I dislike XML and friends in this role.
Ciao,
--

FA
There are three of them, and Alleline.
_______________________________________________

Linux-audio-dev mailing list

Linux-audio-dev@lists.linuxaudio.org

http://lists.linuxaudio.org/listinfo/linux-audio-dev