On Wed, 2011-12-28 at 13:11 +0100, hermann wrote:
Using a session handler should be possible, but to overlook a setup that
is based on modules is hard, if it's done by another person.
You could build already the mixer by modules, but a standardised mixer
already provides what's needed and everybody is able to overlook what's
When there are several ways to do something, than it's not an advantage
to have all the ways available, e.g. mute the microphone by the mixer's
mute option + by a switch provided by the microphone will make it less
good to overlook where the microphone is muted. Modular systems make it
much harder to overlook the situation than this example does describe,
anyway, it already describe a situation where jackd might fix an issue
caused by borked apps.
> > Applications like Ardour and Qtractor come closer and closer to this
1. There are other AIO apps too, e.g. Rosegarden.
2. No, modular usage of apps can be useful. This idea isn't a new
invention of Linux, it's older than computers are, but it never had
success to become a common denominator.
> > Tinkerer do amazing music. I'm tinker my self, AT HOME!
Again, it's not an innovation. It was already part of some proprietary
solutions for computers and it was a concept that is older than the
It's a good idea, but it's not a good concept, if several people work on
the same project, what usually is done for pro-audio.
For analog tapes you have a colour code for different speeds.
Additionally you have a a coloured tape that shows interruptions of the
You don't have such standards because audio engineers are idiots, you
have got standards because they aren't idiots.
If one engineer has got a cold, another can finish her/his work. It's
not like it is for the office mob, when one of them has got a cold and
can't come to the office, that nobody else is able to overlook the other
ones work flow.
> > For hardware we have unwritten standards, e.g. what should be pre and
That's not what I'm saying. I said that not every high level production
is professional regarding to the work flow.
A coder might be able to program very good software by her/his own work
flow, e.g. some spaghetti code could be on a high level, but if a group
of coders will work on the same code, this isn't a good approach.
Modular audio setups are similar to what is spaghetti code for software.
> > Regarding to DEs the Linux community claimed that Windows was
Linux-audio-user mailing list