Re: [LAD] [LAU] So what do you think sucks about Linux audio ?

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <gerald.mwangi@...>
Cc: <linux-audio-user@...>, <linux-audio-dev@...>, Dan MacDonald <allcoms@...>
Date: Sunday, February 10, 2013 - 10:55 pm

--bcaec554e1067f22ee04d566ad75
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Feb 10, 2013 at 5:48 PM, wrote:

> Hi

(1) your HTTP-only email confuses even gmail, and is probably inappropriate
for a technically oriented mailing list like this one.

(2) i'm not really that interested in preserving the "diversity
experience". i think it is much more valuable for developers, who get to
work on their own custom, standalone apps rather than being forced into a
framework as happens with plugin developers. there are a LOT of "linux
audio apps" that would be much more useful as plugins than they are as
standalone JACK clients. but this is only helpful for users, and puts
limitations on developers. look around you to see the result ....

--bcaec554e1067f22ee04d566ad75
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sun, Feb 10, 2013 at 5:48 PM, <g=
erald.mwangi@gmx.de
> wrote:
Hi-- Sent from my HP TouchPad
On 10.02.2013 23:30, Paul Davis <paul@linuxaudiosystems.com<=
/a>> wrote:
On Sun, Feb 10, 2013 at 5:05 PM, <
gerald.mwangi@gmx.de> =
wrote:
Auto mode for JACK latency is a good idea.=A0I have another proposition=
: a dedicated graphical front-end for jack session. It could help users set=
up their workflow , by providing a list of all the jack aware programs inst=
alled, categorized by type (sampler, daw, synth). The program should aid in=
setting up a project , eg firing up ardour with several tracks, firing up =
synths (lv2 instruments/hosts incl) with presets selectable from the front-=
end with a preview sound. The front-end could trigger the synth in question=
with a midi note when selecting a preset. Lv2 plugins, that is pure audio =
effects, could also listed with the ability to directly send a signal from =
the audio interface through the selected plugin to quickly hear what it doe=
s. One could then associate the selected plugin with, say a track in ardour=
, and another plugin with a track in hydrogen or so.

what you are descr=
ibing is basically the "monolithic app" experience (from a user p=
erspective) but created using a set of independent applications and process=
es.
speaking personally, i think there are better things to do with our tim=
e.
=A0Well just for the initialization of the project. The=
diversity experience of the multiple programs , ecosystem shall still be p=
reserved
(1) your HTTP-only email confuses even gmail, a=
nd is probably inappropriate for a technically oriented mailing list like t=
his one.(2) i'm not really that interested in preserving the &q=
uot;diversity experience". i think it is much more valuable for develo=
pers, who get to work on their own custom, standalone apps rather than bein=
g forced into a framework as happens with plugin developers. there are a LO=
T of "linux audio apps" that would be much more useful as plugins=
than they are as standalone JACK clients. but this is only helpful for use=
rs, and puts limitations on developers. look around you to see the result .=
...

--bcaec554e1067f22ee04d566ad75--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

This is the only confirmed message in this thread.
Possibly related messages: