[Ardour-Users] a few thoughts
ampetrosillo at gmail.com
Tue Dec 4 11:21:53 PST 2012
> Aww heck - just "fix it in the mix!"
Who said I don't agree with you? I try to keep processing at a minimum.
Sometimes, though, you need FXs, for creative reasons, for simple
And sometimes, in some kinds of music, you usually heavily rely on FXs and
compression (ie. the ducking effect so common on dance tracks nowadays, or
the heavy reverb very common in trance music, or in general filtering or
deliberate heavy compression-smashing, as in some Beck's songs).
> Or they strive to create one single tool VERY good. And strangely those
> that do this tend to get a strong reputation for it, those that branch out
> to try to do everything tend to never be considered very good for it. It
> isn't limiting functionality to save identity, it is limiting
> because frankly you aren't as good in other areas and feel there are
> tools out there you shouldn't be competing with.
So you're saying Paul and his team would be utterly crap at making the
interface more customizable? After having coded an audio engine, written an
audio API (Jack), they really are unable to make some adjustments to the
GUI? If that were the case, I'd say that they either only know how to code
in very low-level C, or they are idiot savants who excel in doing one thing
and one thing only, that is coding a whole DAW but, at the same time, they
are completely inept at coding GUIs.
We know that's not the case, it's simply a question of priority, Paul and
his team wants to fix the engine before moving on to the leather seats, but
maybe I'm not the only one to say that leather seats (or rather, leather
seats as an added extra!) would be a very welcome addition, moving it up a
bit in the to-do list.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ardour-Users