9 Jan
2005
9 Jan
'05
2:14 p.m.
Hi All,
I was thinking about combining the functionality of the simple jack client
(from the example_clients), and apply_plugin (from the LADSPA SDK), but
before I do so, I was wondering if anyone knew of such a beast.
I'm looking for something as lightweight as possible, thats command line
driven with a minimal amount of user interface. I'm aware of ecasound,
but that was giving me trouble after bringing 3 or 4 ecasound sessions
up.
(In fairness, I think it was also somewhat realtime/kernel related, rather
than purely an ecasound issue)
Before I go ahead, and attempt to hack the two together (and try and fix
the memory leak issues documented in apply_plugin), has anyone already
done this, or know of such a beast ?
Iain
9 Jan
9 Jan
3:43 p.m.
On Sun, Jan 09, 2005 at 06:21:13 +0000, Iain Young wrote:
Hi All,
I was thinking about combining the functionality of the simple jack client
(from the example_clients), and apply_plugin (from the LADSPA SDK), but
before I do so, I was wondering if anyone knew of such a beast.
I'm looking for something as lightweight as possible, thats command line
driven with a minimal amount of user interface. I'm aware of ecasound,
but that was giving me trouble after bringing 3 or 4 ecasound sessions
up.
(In fairness, I think it was also somewhat realtime/kernel related, rather
than purely an ecasound issue)
Before I go ahead, and attempt to hack the two together (and try and fix
the memory leak issues documented in apply_plugin), has anyone already
done this, or know of such a beast ?
The example jack host in the DSSI distribution probably does most of this
allready, if not it would be easy to modify it so that it does. You would
need to add value setting on the command line, the the hard stuff (RT
safe-ness and so on) is done. The advantage is that it would work for
DSSI plugins too.
Taking the apply_plugin code and making it realtime safe wouldn't be
impossible, but it wouldn't be trivial either.
FWIW I would like such a tool too. I generally use jack-rack for this kind
of thing, but sometimes you want something thats command line only.
- Steve
10 Jan
10 Jan
5:57 a.m.
On Sunday 09 Jan 2005 19:43, Steve Harris wrote:
On Sun, Jan 09, 2005 at 06:21:13 +0000, Iain Young
wrote:
Yeah, definitely.
Making jack-dssi-host work for LADSPA plugins as well would involve
making it: (a) use the LADSPA path as well as the DSSI path; (b)
recognise that a .so is a LADSPA one and call the right lookup
function; and (c) create a dummy DSSI descriptor wrapper for a LADSPA
plugin. It's probably half an hour's work or so for someone who knows
the code, a couple of hours to get it right for someone who doesn't.
Note that jack-dssi-host will already do the right thing for DSSI
effects plugins, so no additional logic to make it handle effects as
well as synths will be necessary.
(Anyone thinking of working on this would be advised to start from the
CVS version of the host, which I think has some fixes specifically for
hosting effects that may not have been in the last release. We should
do another release soon I guess.)
I was thinking about combining the functionality
of the simple jack
client (from the example_clients), and apply_plugin (from the
LADSPA SDK), but before I do so, I was wondering if anyone knew of
such a beast.
[...]
The example jack host in the DSSI distribution probably does most of
this allready, if not it would be easy to modify it so that it does. You would need to add value setting on the command
line
That's true. Or, I had considered whether we should make the host
accept commands on stdin (structured like the OSC message calls).
Chris
6:28 a.m.
New subject: [DSSI] Re: [linux-audio-user] Lightweight Jack Client & LADSPA host
On Mon, Jan 10, 2005 at 09:56:42 +0000, Chris Cannam wrote:
For interactive stuff it may be interesting to do it as an OSC UI. It can
query the .so to find recommended ranges and so on, and provide a command
line interface.
- Steve
You would need
to add value setting on the command line
That's true. Or, I had considered whether we should make the host
accept commands on stdin (structured like the OSC message calls). 
9 Jan
9 Jan
3:54 p.m.
I was thinking about combining the functionality of
the
simple jack client (from the example_clients), and
apply_plugin (from the LADSPA SDK), but before I do so, I
was wondering if anyone knew of such a beast.
AFAIK, there isn't something comparable.
When I understood correctly, you are looking for a tool which
can load one single LADSPA and wrap it as a jack client so
one could use it - maybe - to apply delay to an acoustic
guitar.
I do not know such a tool, so I guess such a client would be
really great.
If you mean command line, would it at least have some ncurses
controls for the parameters to adjust, or would it be needed
to pass the parameters at start up?
Best regards
ce
4:05 p.m.
On Sun, Jan 09, 2005 at 08:54:44PM +0100, Christoph Eckert wrote:
It it were based on the DSSI server it would create an OSC control for the
ports, so you could control it that way.
- Steve
I was thinking about combining the functionality
of the
simple jack client (from the example_clients), and
apply_plugin (from the LADSPA SDK), but before I do so, I
was wondering if anyone knew of such a beast.
AFAIK, there isn't something comparable.
When I understood correctly, you are looking for a tool which
can load one single LADSPA and wrap it as a jack client so
one could use it - maybe - to apply delay to an acoustic
guitar.
I do not know such a tool, so I guess such a client would be
really great.
If you mean command line, would it at least have some ncurses
controls for the parameters to adjust, or would it be needed
to pass the parameters at start up?
4:26 p.m.
On Sun, Jan 09, 2005 at 08:54:44PM +0100, Christoph Eckert wrote:
If you mean command line, would it at least have some
ncurses
controls for the parameters to adjust, or would it be needed
to pass the parameters at start up?
Well either, both, or none :) I actually started this train of
thought when I wanted a (ncurses) volume/gain control for Jack.
Then I realised, hey why not just use the amp LADSPA plugin ?
All the code is in there, why re-invent the wheel ? Of course,
then I started thinking, why restrict it to the amp plugin ?
(And yes, I know ardour has a ksi interface, but that needs
direct access to the keyboard, and I had other trouble with it,
and boy did it confuse X|KDE after running it with the remote
keyboard...)
Certainly early versions would most likely just have the amp
plugin hard coded, with a quick ncurses interface to show a
slider, but no reason why it couldnt be made generic.
Iain.
4:48 p.m.
Certainly early versions would most likely just have
the
amp plugin hard coded, with a quick ncurses interface to
show a slider, but no reason why it couldnt be made
generic.
If you just need the amp plugin, but you're willing to make it
generic for any LADSPA or DSSI plugin, it would be great and
much appreciated - I guess not only be Steve and me :) .
Thanks & best regards
ce
7305
days inactive
7306
days old
linux-audio-user@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
Chris Cannam -
iain＠g7iii.net -
mchristoph.eckert＠t-online.de -
Steve Harris