[LAU] The future of audio plugins ?

jonetsu jonetsu at teksavvy.com
Wed Oct 19 16:35:51 UTC 2016


On Wed, 19 Oct 2016 17:25:34 +0200
Ralf Mardorf <ralf.mardorf at alice-dsl.net> wrote:

> But it does not explain what the network protocol is used for.

See the reply by Michael Noble then.
 
> IIUC you want an analysis tool, that does part of the work an audio
> engineer does. IIUC you think an audio engineer needs more time to do
> it, than a tool does. The analysis tool should load tools and talk to
> the tools, to provide good settings. Based on what? How should this
> work? If an engineer listens to sound and should describe another
> engineer what to do, who doesn't listen to the sound, it already
> is unlikely to get a good result. How should the analysing tool find
> the right words, to explain the tools what they need to do?

> What problem do you try to solve? IMO your vague idea would cause
> issues.

I'm afraid examples were given and there is no need to repeat ad vitam
since after all, the text is there and can be re-read.

You may call then 'settings' although IMHO it is a bit more than that
if only because when using the term 'settings' there is a heavy
connection being dragged along which consists of 100% static
definitions that exists before the task has started.  And this was also
mentioned previously.




More information about the Linux-audio-user mailing list