[LAU] qjackctl and ubuntu 11.10 unity

Ralf Madorf ralf.mardorf at alice-dsl.net
Wed Dec 28 13:52:50 UTC 2011


On Wed, 2011-12-28 at 13:11 +0100, hermann wrote:
> Am Mittwoch, den 28.12.2011, 11:34 +0100 schrieb Ralf Madorf:
> > On Wed, 2011-12-28 at 10:51 +0100, hermann wrote:
> > > What I didn't like in your previous post is the totalitär attitude you
> > > use do describe what professional audio have to be. 
> > > Please, be aware that others could have other way's to get stuff done.
> > > What today seems to be the best way, didn't must be tomorrow true.
> > > The modular work-flow under linux is (and now because jack is MULTI OS
> > > COMPATIBLE, was) unique under the OS's, and have some big advance over
> > > the AIO flow witch is the way to do stuff like you said.
> > 
> > Full ACK, but my claim still is
> > "Everybody should be able to go from one studio to the next and know how
> > to handle the equipment. The approach off pro-audio is to keep things
> > easy for the engineer.
> > 
> [SATIRE ON]
> To turn around your statement, you said : session handlers are bad
> because audio engineers are to stupid to use them ?
> Or do you mean : we didn't have to have session handlers because the
> others didn't have them to ?

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
done.

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
> > approach. The policy of several apps + a session handler is a step in
> > the wrong direction."
> > 
> 
> Again turn it around, do you mean that all linux audio stand alone
> applications, except Ardour and Qtractor are non Professional and at
> least only a wast of time, and they have to be plugins for those 2
> Master Applications, it shouldn't be allowed to them to run outside of
> them, application connections with jack is a bad idea, do you mean
> that ? Do you believe that non of them are in use in any Professional
> Audio Studio ?

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!
> > 
> > > To see that, you need to free up your mind from oldish ways.
> > 
> > That's not the point. I do this for home recording.
> 
> No, the point is that innovations need to be done, and sometimes you
> need to walk on new way's to get them done. Otherwise, you can still sit
> down and do what you ever do, without the need of learn something new.
> But if you have made your feats wet, you see fast a bunch of possible
> new ways and will walk on.

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
computer.

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
recorded program.

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
> > what should be post fader for a mixing console. A mixing console that
> > has another way to do things could be very good, but it isn't regarding
> > to usability for pro-audio.
> > 
> > You know the sentence of the office mob? "If I'm not at work, nobody
> > would be able to do the work." They say this with proud, instead of
> > being ashamed.
> > 
> > For pro-audio you need to make it idiotproof.
> > Pro-audio means to do good recordings, for "normal" music.
> > 
> For me, Pro Audio means a bit more then that, so definitions could
> differ. 
> 
> > Working modular with electronics and computers is something I do myself.
> > This is part of some compositions. Hopefully it's on a high level ;),
> > but a high level anyway has less to do with professional work for daily
> > bread.
> > 
> So, professional work wouldn’t happen on high level ?

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
> > "klickibunti" de.wikipedia.org/wiki/Klickibunti already wit 98, and XP.
> > Correct, but what the hell is KDE4, GNOME3, Unity. The same people tody
> > tend to claim similar to "To see that, you need to free up your mind
> > from oldish ways."
> > 
> What, the same people do that ?? Crazy :-))
> [SATIRE OF]

;D

Cheers!

Ralf




More information about the Linux-audio-user mailing list