13 May
2007
13 May
'07
7:24 p.m.
Folks,
Any opinions on lmms ?
I haven't installed it yet, am only thinking about it. As with most,
I come from a Windows background where monolithic apps rules. But
then, I've been working with Linux for several years now and one thing
that's omnipresent - so far - in the Linux Way is modularity. Be it in
chaining small apps to get results (eg. cat bigFile | grep error) to
having a clear concern separation between functionality and user
interface.
And this is what I like with the actual state of most of the Linux
audio apps. Soemone makes a new synth ? Fine, we just use it through
jack. No encompassing large apps that tries, with various degrees of
flexibility, to do it all. Well, there must be some out there. Maybe
jokosher. And maybe lmms.
What I'd like to know, is that, from a 'techie' point of view that
feels that it's allright to use many X screens to have many apps
running at the same time, what is lmms bringing ? Is it only but a
Windows-inspired application ?
Cheers,
Al
14 May
14 May
5:40 p.m.
On Sun, May 13, 2007 at 05:29:12PM -0400, lanas wrote:
Folks,
Any opinions on lmms ?
It is pretty good. A bit like Fruity Loops..
What I'd like to know, is that, from a 'techie' point of view that
feels that it's allright to use many X screens to have many apps
running at the same time, what is lmms bringing ? Is it only but a
Windows-inspired application ?
Until all linux apps are lash compatible, it can be a bit of a
pain to set up which synths to use, and which patches to load...
lmms has a big advantage from this point of view.
OTOH I personally prefer aldrin for a similar style of app...
best to give them a try and see what you like best.
James
15 May
15 May
5:46 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, May 14, 2007 at 08:40:11PM +0100, James Stone wrote:
On Sun, May 13, 2007 at 05:29:12PM -0400, lanas
wrote:
Naw, that's what BASH and Python scripts are for. :-P
- -ken
Folks,
Any opinions on lmms ?
It is pretty good. A bit like Fruity Loops..
What I'd like to know, is that, from a 'techie' point of view that
feels that it's allright to use many X screens to have many apps
running at the same time, what is lmms bringing ? Is it only but a
Windows-inspired application ?
Until all linux apps are lash compatible, it can be a bit of a
pain to set up which synths to use, and which patches to load...
lmms has a big advantage from this point of view. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFGSWVMe8HF+6xeOIcRAtTFAKD+loQL8kaZPWwncddACqJHncMh3QCg+Ger
Rb6VrMsOXcCusMWDoOAUMmI=
=sN0m
-----END PGP SIGNATURE-----
8:23 a.m.
Ken Restivo wrote:
Naw, that's what BASH and Python scripts are for.
:-P
Yes indeed. I have a variety of scripts I use to launch some number of
apps at once, including my music apps. Very convenient, very fast. It's
not lash, but it's a pretty darned useful method.
If state is a concern then lash is preferable (if it's available).
Best,
dp
8:27 a.m.
On 5/13/07, lanas <lanas(a)securenet.net> wrote:
What I'd like to know, is that, from a 'techie' point of view that
feels that it's allright to use many X screens to have many apps
running at the same time, what is lmms bringing ? Is it only but a
Windows-inspired application ?
Very interesting question... I'm presently involved in a port of a
venerable Windows audio app to Linux (Psycle, a 'modular music studio'
similar to Buzz/Aldrin, that performs synthesis, tracking and
sequencing all in one place), and I hadn't considered the question of
it being 'monolithic' before, and whether that makes sense on Linux.
I really like the Unix philosophy of do one thing and do it well, and
the idea of mixing and matching the tools to the job, and of avoiding
lock-in to a particular app.
In defense of the monolithic style, I would say it is more intuitive
to newcomers to have everything contained within one place. They
download one app, and with a hopefully not-too-long browse of the
manual can get it to do something. I think it takes a lot more skill
to grasp the idea of routing the output of one app into another, at
least for those not coming from an audio hardware background.
Maybe with this ever-anticipated "year that Linux gets big",
"Windows-style" applications can ease the transition for people coming
from one environment to another. I think having a choice of style is
a good thing.
It is important these apps don't take too much of a walled-garden
approach though, and provide some interaction at least, with
DSSI/LADSPA/LV2, Jack, etc, and if it were possible, hopefully some
kind of transferable open file format.
Neil
18 May
18 May
5:07 p.m.
Le Mardi, 15 May 2007 11:27:33 +0100,
"Neil Mather" <ngmather(a)gmail.com> a écrit :
In defense of the monolithic style, I would say it is
more intuitive
to newcomers to have everything contained within one place. They
download one app, and with a hopefully not-too-long browse of the
manual can get it to do something. I think it takes a lot more skill
to grasp the idea of routing the output of one app into another, at
least for those not coming from an audio hardware background.
It was, at least once, said that successful GUIs are ones that stands
for metaphors to real life objects. I'm not that much convince that
the sacro-saint newcomer is actually well-defined.
I mean, what would a 'newcomer' do just after buying a DVD 5.1 system
for his/her living room ? Would we immediately think that this person
will be lost connecting it to his/her TV, as well as connecting the
speakers and cable ?
I think that the 'newcomer' stereotype is defined on the low side. And
being defined that way, it does not push forward any notion that is not
more complicated than connecting home theatre components together.
After all, the newcomer is sitting in front of a computer. It is
absolutely not like sitting and staring at the taoster in the
morning ! ;-)
I think it wouldn't be faretched to introduce the notion, at the
'newcomer' level, of components that have to be conencted together.
It's just that it hasn't been done yet. And as far a Linux is
concerned, and me, the inter-communication is not yet mature enough.
Heck, I can't even get lash going on my FC6 x86_64 SMP machine, not to
mention which apps actually supports lash and to what extent.
It is important these apps don't take too much of
a walled-garden
approach though, and provide some interaction at least, with
DSSI/LADSPA/LV2, Jack, etc, and if it were possible, hopefully some
kind of transferable open file format.
A transferable file format would be quite something. Imagine doing a
rough fast sketch with Seq24 and having that seq file being read by a
more sophisticated sequencer later for detailed work.
Cheers,
Al
19 May
19 May
12:35 p.m.
I mean, what would a 'newcomer' do just after buying a DVD 5.1 system
for his/her living room ? Would we immediately think that this person
will be lost connecting it to his/her TV, as well as connecting the
speakers and cable ?
I think that the 'newcomer' stereotype is defined on the low side. And
being defined that way, it does not push forward any notion that is not
more complicated than connecting home theatre components together.
i agree. To me, coming more from the hardware-side connecting tapedecs,
turntables mixers and effect-racks, not ever having used any audio
software before starting with linux three years ago, the concept of
interconnecting small apps is much more intuitive than anything
monolithic like lmms or rosegarden.
I had a look at those and quickly returned to connecting seq24 with zyn,
nekobee, ardour and others.
just one opinion from one newcomer, there might be different kinds of them.
'newcomer' level, of components that have to
be conencted together.
It's just that it hasn't been done yet. And as far a Linux is
concerned, and me, the inter-communication is not yet mature enough.
Heck, I can't even get lash going on my FC6 x86_64 SMP machine, not to
mention which apps actually supports lash and to what extent.
lash is on its way, and i am looking forward to the NEAR future when
ingen, ardour, zyn, seq24, dssi, lv2 save their states with one click!
it'll be a pleasure, and at that point linux audio will be absolutely
newbie-ready, as well as musician-ready - IMHO far more than
apple/windows, as many musicians are used to that interconnecting
concept, and those migrating to linux from other platforms are by far
not the only newcomers out there!
(olpc -
Until then we'll have fun compiling code and writing nice little scripts
- still many musicians wont want to do this.
that necessity at least led me to quite a bit of computer knowledge --
me very grateful for that, now learning how to program to push things
forward.
machts jut,
david
5:27 p.m.
On Saturday 19 May 2007, David Adler wrote:
The problem with this approach is that all these processes and data-streams
need mucho cpu power. My PIII clunker cannot handle, say, playing something
into jack, routing through jamin. Running a similar plugin in the playing
will work.
Of course, we can all afford the new quad-core wonders so the issue is mute.
I mean, what
would a 'newcomer' do just after buying a DVD 5.1 system
for his/her living room ? Would we immediately think that this person
will be lost connecting it to his/her TV, as well as connecting the
speakers and cable ?
I think that the 'newcomer' stereotype is defined on the low side. And
being defined that way, it does not push forward any notion that is not
more complicated than connecting home theatre components together.
i agree. To me, coming more from the hardware-side connecting tapedecs,
turntables mixers and effect-racks, not ever having used any audio
software before starting with linux three years ago, the concept of
interconnecting small apps is much more intuitive than anything
monolithic like lmms or rosegarden.
I had a look at those and quickly returned to connecting seq24 with zyn,
nekobee, ardour and others.
just one opinion from one newcomer, there might be different kinds of them.
'newcomer' level, of components that have
to be conencted together.
It's just that it hasn't been done yet. And as far a Linux is
concerned, and me, the inter-communication is not yet mature enough.
Heck, I can't even get lash going on my FC6 x86_64 SMP machine, not to
mention which apps actually supports lash and to what extent.
lash is on its way, and i am looking forward to the NEAR future when
ingen, ardour, zyn, seq24, dssi, lv2 save their states with one click!
it'll be a pleasure, and at that point linux audio will be absolutely
newbie-ready, as well as musician-ready - IMHO far more than
apple/windows, as many musicians are used to that interconnecting
concept, and those migrating to linux from other platforms are by far
not the only newcomers out there!
(olpc -
Until then we'll have fun compiling code and writing nice little scripts
- still many musicians wont want to do this.
that necessity at least led me to quite a bit of computer knowledge --
me very grateful for that, now learning how to program to push things
forward. 
5:31 p.m.
On Sat, 2007-05-19 at 22:27 +0300, David Baron wrote:
On Saturday 19 May 2007, David Adler wrote:
The problem with this approach is that all these processes and data-streams
need mucho cpu power. My PIII clunker cannot handle, say, playing something
into jack, routing through jamin. Running a similar plugin in the playing
will work.
Really? I thought context switching was pretty cheap on Linux,
especially compared to things like Jamin.
--ll
I mean,
what would a 'newcomer' do just after buying a DVD 5.1 system
for his/her living room ? Would we immediately think that this person
will be lost connecting it to his/her TV, as well as connecting the
speakers and cable ?
I think that the 'newcomer' stereotype is defined on the low side. And
being defined that way, it does not push forward any notion that is not
more complicated than connecting home theatre components together.
i agree. To me, coming more from the hardware-side connecting tapedecs,
turntables mixers and effect-racks, not ever having used any audio
software before starting with linux three years ago, the concept of
interconnecting small apps is much more intuitive than anything
monolithic like lmms or rosegarden.
I had a look at those and quickly returned to connecting seq24 with zyn,
nekobee, ardour and others.
just one opinion from one newcomer, there might be different kinds of them.
'newcomer' level, of components that have
to be conencted together.
It's just that it hasn't been done yet. And as far a Linux is
concerned, and me, the inter-communication is not yet mature enough.
Heck, I can't even get lash going on my FC6 x86_64 SMP machine, not to
mention which apps actually supports lash and to what extent.
lash is on its way, and i am looking forward to the NEAR future when
ingen, ardour, zyn, seq24, dssi, lv2 save their states with one click!
it'll be a pleasure, and at that point linux audio will be absolutely
newbie-ready, as well as musician-ready - IMHO far more than
apple/windows, as many musicians are used to that interconnecting
concept, and those migrating to linux from other platforms are by far
not the only newcomers out there!
(olpc -
Until then we'll have fun compiling code and writing nice little scripts
- still many musicians wont want to do this.
that necessity at least led me to quite a bit of computer knowledge --
me very grateful for that, now learning how to program to push things
forward. 
26 May
26 May
7:44 a.m.
On Fri, 2007-05-18 at 15:05 -0400, lanas wrote:
A transferable file format would be quite something.
Imagine doing a
rough fast sketch with Seq24 and having that seq file being read by a
more sophisticated sequencer later for detailed work.
Seq24 just saves as a midi file.
Gordon
6444
days inactive
6457
days old
linux-audio-user@lists.linuxaudio.org
9 comments
9 participants
participants (9)
-
Dave Phillips -
David Adler -
David Baron -
Gordon JC Pearce -
James Stone -
Ken Restivo -
lanas -
Lars Luthman -
Neil Mather