Re: [linux-audio-dev] ANNOUNCE: Rosegarden-4 v0.1.5 released

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: Re: [linux-audio-dev] ANNOUNCE: Rosegarden-4 v0.1.5 released
From: Tim Goetze (tim_AT_quitte.de)
Date: Wed May 08 2002 - 02:16:25 EEST


Stefan Westerfeld wrote:

>Well, you're of course right. LADSPA support for aRts has been on my TODO
>list since ages, and I am unhappy with the fact that although I have some
>prototype code for this, I still haven't committed it. This might, at least
>partially, give some reason why I haven't been so active on further extensions.

i think that whether you support it in your projects or not, your
input is crucial to any extension of ladspa. there have been some
good and bad ideas about that, and without your and richard's voice
(paul thankfully is a little quicker to make himself heard) it feels
like we are just talking plain b****hit here that doesn't need any
comment. that's not to say it isn't ;) but it's nice to know by
proof and not by assumption.

>On the other hand, I don't agree with you that the desktop lib discussion
>is insignificant, as whether or not linux audio software properly supports
>desktop environments can have a big strategical impact, which might well
>make linux audio software a lot better in the future. But as you don't want
>me to "express my meaning on something as inessential as the everlasting
>desktop lib flamewar", I'll rather go back to coding ... ;)

that's my man! :)

i'll rephrase that as 'inessential to linux audio' then; after all,
that's what this list is about. and i think that in this context, an
application's choice of toolkit/desktop env, or of no toolkit at all,
is mostly irrelevant, and rather a matter of taste.

you know it takes a whole lot of things to make good audio software:
solving the plethora of realtime and multithreading problems, having a
good plugin API, making the kernel scheduler consistent and quicker,
scripting interfaces, midi synchronization, clever handling of disk
accesses, good DSP code, lots of optimizations etc etc.

in contrast, a toolkit, or desktop env, can help make a good windowed
user interface. but it doesn't play in the same league. it doesn't
even play the same game, i think.

tim


New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Thu May 09 2002 - 14:00:53 EEST