14 Jun
2007
14 Jun
'07
5:23 a.m.
And yes, I must admit I have a small agenda too,
against Ardour. I don't
think ardour's user interface is very efficient [1]. Ardour is great, but it
why hasnt ardour been fixed. is it because the GUI is written in C++ with GnomeCanvas or
something and only 2 people now how its written and theyre both too busy to do anything
about the TODO list? ive never needed a digital tapedeck (when i do, arecord is fine) so i
havent used ardour but if a usable daw really has millions of these little corner cases in
the UI design and workflow features (which i believe it does, as using samplitude or
abletonlive after struggling with ardour or protools will attest), then do we really need
all the effort spread out between traverso, qtractor, ardour, and jokosher?
is ardour significantly better than the others for things like realtime recording
track-counts? thats mostly a disk thing unless your coding is _really_ bad, right? which
puts us back into UI space (which is why i'll be porting thomas grill's xsample~
to lv2 and writing guis in JS/Lua rather than attempting to add to ardour)