5 Nov
2002
5 Nov
'02
2:45 p.m.
We at the LinuxSampler project,
http://linuxsampler.sourceforge.net will go the GUIless route too
and as Juan L. suggested it is probably wise to use a TCP socket because it
allows remote controllability which can sometimes be very helpful.
Imagine these racks found in webfarms starting making music :-)
Anyway as our project advances, I hope that some good soul will implement
a CLI interface for the sampler too so that it becomes more accessibile for
people with disabilities.
I agree with your stance about merging GUI and engine code: it is a mess and
often introduces many maintenance and performance problems.
Most audio programmer so not seem to realize that using mutexes called from
GUI threads that share data with the audio thread speaks SUICIDE because you
will never be able to ensure that your sub-5 msec audio engine does not drop
out under heavy load. Yes ... (blocking) mutexes simplify a bit the
programmer's task , but I'm sorry to say it your product will never be usable
in the pro audio field.
Hoping for a peaceful, client-server centric audio application world.
:-)
Benno
--
http://linuxsampler.sourceforge.net
Building a professional grade software sampler for Linux.
Please help us designing and developing it.
5 Nov
5 Nov
7:27 p.m.
New subject: [linux-audio-dev] GUIless friendly applications
Benno Senoner <sbenno(a)gardena.net> writes:
We at the LinuxSampler project,
http://linuxsampler.sourceforge.net will go the GUIless route too
and as Juan L. suggested it is probably wise to use a TCP socket because it
allows remote controllability which can sometimes be very helpful.
This is more or
less the way Kai choose for Ecasound, and I suddenly
was able to create my own "gui" for alot of useful aspects of ecasound.
I think simple command-line based pipes/tcp sockets with a nicely parseable
syntax are just the way to go.
Anyway as our project advances, I hope that some good
soul will implement
a CLI interface for the sampler too so that it becomes more accessibile for
people with disabilities.
Please dont start this too late. It is vitally important to implement
a cli interface at the very beginning, and actually use it for some things like
scripted test cases or whatever. This ensures that you dont forget
anything very important which you embedd in the GUI and which turns out
to be not controllable from the outside later on.
I agree with your stance about merging GUI and engine
code: it is a mess and
often introduces many maintenance and performance problems.
And make the
application less flexible.
--
CYa,
Mariok
9:36 p.m.
New subject: [linux-audio-dev] GUIless friendly applications
I agree with your stance about merging GUI and engine
code: it is a
mess and often introduces many maintenance and performance problems.
As someone who has just spent the best part of three months rewriting
code - ohh I learnt the hard way ;)
dave
7990
days inactive
7990
days old
linux-audio-dev@lists.linuxaudio.org
2 comments
3 participants
participants (3)
-
Benno Senoner -
Dave Griffiths -
Mario Lang