14 Oct
2016
14 Oct
'16
1:46 p.m.
On Fri, 14 Oct 2016 13:07:38 +0200
Ralf Mardorf <ralf.mardorf(a)alice-dsl.net> wrote:
>A template will obviously not recognize the audio
it is being applied
>on since it has no intelligence, since it is static. This is a large
>difference with the approach sketched here, for the enjoyment of a
>discussion.
Analysing a vocal track without analysing other tracks
and knowing
what the audio engineer and/or artists wants to do, doesn't allow to
estimate any EQ settings that could be close to something useful, let
alone compressor settings.
It's a balance of the two, mostly. The end result has to be in
conjunction with the remaining of the tracks but then, it can very well
be that a single track by itself does need so adjustments no matter
what.
This said I am certainly not going into the details of how Track
Assistant works as the subject as I defined it, is not about that. I
think it steers away from the subject. So I will not address it.
Providing an exciter as a default tool to
mix vocals is completely wrong.
If this is what Track Assistant does, then that's their choice.
"intelligent" is an absolutely wrong term
for such a bad gimmick.
To continue on this 'gimmick' would have to be defined. Eg. is this
out of TA or is it an example you bring forward on your own ?
I also don't understand how adding a selection of
effects and default
settings is related to communication among the plugins and the host.
Because, as with, if you wish, Pianoteq sounds, the selection does not
exist before the action of creating it is being made. It is created on
the spot.
The selection does not exist.
It doesn't matter if an analysing plugin adds
templates of plugins
with selected templates of settings for those plugins, or if a user
simply adds such a template manually. For doing this, nothing is
required that isn't already provided. There's no need for plugin 1 to
share information with plugin 2.
Because the 'selected templates of settings' does not exist.