15 Feb
2013
15 Feb
'13
9 p.m.
I'm trying to figure out what is the best way to use the Guitarix-Amp
and Guitarix-FX LADSPA plugins on a headless system (read Raspberry Pi).
I've tried it with Ecasound but it already consumes more CPU than the
guitarix application itself! So I'm obviously doing something wrong.
Maybe this is because the Guitarix-Amp plugin has one input and two
outputs, read something about Ecasound starting up multiple instances of
the plugin in such a case which is not what I want. So any hints or tips
on getting this to run smoothly? I can use either JACK or ALSA directly.
I prefer using JACK, somehow using bare ALSA produces large amounts of
xruns.
Thanks in advance,
Jeremy
15 Feb
15 Feb
9:16 p.m.
Hello Jeremy!
Oh bugger, I would have suggested Ecasound/Nama as your first options. :-)
but there is csound, although I have a feeling, that it's LADSPA support can
be a little confusing not to say buggy. No idea, what the current state is, I
tried it last over a year ago.
Perhaps CLM has LADSPA/DSSI support as well.
But I'm really wondering, why Ecasound should use so much CPU power. Yes it
does like to start two instances of plugns. I'm not sure how it behaves
exactly, when there's a discrepancy between inputs and outputs. but running it
in Ecasound would have a few advantages: MIDI controllability from the
outside, a stable and well-behaved host.
I had been looking, but didn't find it. But I'm sure, that either in
relation to the sndfile-suite or in the neighbourhood of jack-dssi-host there
had been another small utility to run LADSPA plugins. Sorry I can't be more
specific.
At least sox can handle ADSPA. But sox to my knowledge has no JACK support.
I hope some of this may be of help to you.
Good luck
Julien
----------------------------------------
http://juliencoder.de/nama/music.html
9:24 p.m.
Hi Jeremy
Guitarix amp plugin have 1 in 1 out.
Fx plug have 2 in 2 out.
Seems you run 2amp instances.
Will try to answer more presice when I'm back from my travel.
Hermann
--
Diese Nachricht wurde von meinem Android Mobiltelefon mit WEB.DE Mail gesendet.
Jeremy Jongepier <jeremy(a)autostatic.com> schrieb:
I'm trying to figure out what is the best way to use the Guitarix-Amp
and Guitarix-FX LADSPA plugins on a headless system (read Raspberry Pi).
I've tried it with Ecasound but it already consumes more CPU than the
guitarix application itself! So I'm obviously doing something wrong.
Maybe this is because the Guitarix-Amp plugin has one input and two
outputs, read something about Ecasound starting up multiple instances of
the plugin in such a case which is not what I want. So any hints or tips
on getting this to run smoothly? I can use either JACK or ALSA directly.
I prefer using JACK, somehow using bare ALSA produces large amounts of
xruns.
Thanks in advance,
Jeremy
_____________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
9:27 p.m.
Hi!
Jeremy, if the plugin has 1in and 1out, then you can do:
ecasound -f:16,1,44100 -i intput -o output
-eli:guitarix_1amp_unique_id,param1,param2,...
this should only get you one plugin and if you're interested I can tell you
how to control some plugin parameters via midi as well.
Best regards
Julien
----------------------------------------
http://juliencoder.de/nama/music.html
9:48 p.m.
Hi Jeremy,
On Fri Feb 15 2013, Jeremy Jongepier wrote:
I'm trying to figure out what is the best way to
use the Guitarix-Amp
and Guitarix-FX LADSPA plugins on a headless system (read Raspberry
Pi). I've tried it with Ecasound but it already consumes more CPU
than the guitarix application itself! So I'm obviously doing
something wrong. Maybe this is because the Guitarix-Amp plugin has
one input and two outputs, read something about Ecasound starting up
multiple instances of the plugin in such a case which is not what I
want. So any hints or tips on getting this to run smoothly? I can use
either JACK or ALSA directly. I prefer using JACK, somehow using bare
ALSA produces large amounts of xruns.
How about jack-dssi-host?
$ DSSI_PATH=/usr/lib/ladspa jack-dssi-host guitarix_amp.so
jack-dssi-host will then print out (among other things) its OSC path. Use this path with
dssi_osc_send to set the plugin parameters (append '/control' to the path):
$ dssi_osc_send
osc.udp://youraddresshere.com:13160/dssi/guitarix_amp/guitarix_amp/chan00/control 5 -20
which sets control port 5 to -20. You can query the current state of the plugin:
$ dssi_osc_update
osc.udp://youraddresshere.com:13160/dssi/guitarix_amp/guitarix_amp/chan00
and don't forget analyseplugin to get the port numbers. HTH,
-Sean
9:53 p.m.
On Fri, Feb 15, 2013 at 1:00 PM, Jeremy Jongepier <jeremy(a)autostatic.com>wrote;wrote:
I'm trying to figure out what is the best way to
use the Guitarix-Amp and
Guitarix-FX LADSPA plugins on a headless system (read Raspberry Pi). I've
tried it with Ecasound but it already consumes more CPU than the guitarix
application itself! So I'm obviously doing something wrong. Maybe this is
because the Guitarix-Amp plugin has one input and two outputs, read
something about Ecasound starting up multiple instances of the plugin in
such a case which is not what I want. So any hints or tips on getting this
to run smoothly? I can use either JACK or ALSA directly. I prefer using
JACK, somehow using bare ALSA produces large amounts of xruns.
Thanks in advance,
Jeremy
Non-Mixer has a noui mode... You can run a previously defined mix
(including any number of ladspa plugins) and control them via OSC.
9:57 p.m.
On 02/15/2013 10:16 PM, Julien Claassen wrote:
Hello Jeremy!
Oh bugger, I would have suggested Ecasound/Nama as your first
options. :-)
Ha ha, well, it was the first tool that popped up in my mind. And I got
it to work quite quickly, it's well documented.
but there is csound, although I have a feeling,
that it's LADSPA
support can be a little confusing not to say buggy. No idea, what the
current state is, I tried it last over a year ago.
Perhaps CLM has LADSPA/DSSI support as well.
But I'm really wondering, why Ecasound should use so much CPU power.
Yes it does like to start two instances of plugns. I'm not sure how it
behaves exactly, when there's a discrepancy between inputs and outputs.
but running it in Ecasound would have a few advantages: MIDI
controllability from the outside, a stable and well-behaved host.
I get that idea too that it starts two instances of the first plugin in
the signal path (Guitarix-Amp). I'll try your suggestion you gave in
your other mail (using -f with a channel count of 1).
I had been looking, but didn't find it. But
I'm sure, that either in
relation to the sndfile-suite or in the neighbourhood of jack-dssi-host
there had been another small utility to run LADSPA plugins. Sorry I
can't be more specific.
At least sox can handle ADSPA. But sox to my knowledge has no JACK
support.
I hope some of this may be of help to you.
It sure is, thanks! Going to check out my other options.
Jeremy
Good luck
Julien
----------------------------------------
http://juliencoder.de/nama/music.html
9:59 p.m.
On 02/15/2013 10:48 PM, Sean Bolton wrote:
Hi Jeremy,
On Fri Feb 15 2013, Jeremy Jongepier wrote:
Hi Sean,
Thanks! Didn't think about that while I've used jack-dssi-host on
several other occasions. I'll give it a whirl!
Jeremy
I'm trying to figure out what is the best way
to use the Guitarix-Amp
and Guitarix-FX LADSPA plugins on a headless system (read Raspberry
Pi). I've tried it with Ecasound but it already consumes more CPU
than the guitarix application itself! So I'm obviously doing
something wrong. Maybe this is because the Guitarix-Amp plugin has
one input and two outputs, read something about Ecasound starting up
multiple instances of the plugin in such a case which is not what I
want. So any hints or tips on getting this to run smoothly? I can use
either JACK or ALSA directly. I prefer using JACK, somehow using bare
ALSA produces large amounts of xruns.
How about jack-dssi-host?
$ DSSI_PATH=/usr/lib/ladspa jack-dssi-host guitarix_amp.so
jack-dssi-host will then print out (among other things) its OSC path. Use this path with
dssi_osc_send to set the plugin parameters (append '/control' to the path):
$ dssi_osc_send
osc.udp://youraddresshere.com:13160/dssi/guitarix_amp/guitarix_amp/chan00/control 5 -20
which sets control port 5 to -20. You can query the current state of the plugin:
$ dssi_osc_update
osc.udp://youraddresshere.com:13160/dssi/guitarix_amp/guitarix_amp/chan00
and don't forget analyseplugin to get the port numbers. HTH,
-Sean
10:01 p.m.
On 02/15/2013 10:23 PM, brummer- wrote:
Hi Jeremy
Guitarix amp plugin have 1 in 1 out.
Fx plug have 2 in 2 out.
Seems you run 2amp instances.
Will try to answer more presice when I'm back from my travel.
Hermann
Hi Hermann,
I get that idea too. But there are several other options I could try so
I think I'll get it going before LAC2013 (I'd love to demo guitarix on
the RPi if my workshop proposal gets accepted).
Jeremy
10:06 p.m.
On 02/15/2013 10:53 PM, J. Liles wrote:
Non-Mixer has a noui mode... You can run a previously
defined mix
(including any number of ladspa plugins) and control them via OSC.
Hi Jonathan,
Even more options, great! I've used Non-Mixer before so I think it's
quite easy to set up a defined mix and load it onto the RPi.
Unfortunately no packages for the RPi :( Hopefully it cross-compiles
without any serious issues (it probably will). I'll give it a go too.
Jeremy
10:14 p.m.
On Fri, Feb 15, 2013 at 2:06 PM, Jeremy Jongepier <jeremy(a)autostatic.com>wrote;wrote:
On 02/15/2013 10:53 PM, J. Liles wrote:
No packages indeed. I'd be interested to know how if/how it works on ARM.
Non-Mixer has a noui mode... You can run a
previously defined mix
(including any number of ladspa plugins) and control them via OSC.
Hi Jonathan,
Even more options, great! I've used Non-Mixer before so I think it's quite
easy to set up a defined mix and load it onto the RPi. Unfortunately no
packages for the RPi :( Hopefully it cross-compiles without any serious
issues (it probably will). I'll give it a go too. 
16 Feb
16 Feb
1:23 a.m.
On Sat, Feb 16, 2013 at 7:06 AM, Jeremy Jongepier <jeremy(a)autostatic.com>wrote;wrote:
Even more options, great!
Yet another option may be the [plugin~] object in puredata, which hosts
ladspa and dssi plugins. I know PD has a Pi build, but not sure about
plugin~.
8:28 p.m.
On 02/15/2013 10:48 PM, Sean Bolton wrote:
Hi Jeremy,
How about jack-dssi-host?
$ DSSI_PATH=/usr/lib/ladspa jack-dssi-host guitarix_amp.so
jack-dssi-host will then print out (among other things) its OSC path. Use this path with
dssi_osc_send to set the plugin parameters (append '/control' to the path):
$ dssi_osc_send
osc.udp://youraddresshere.com:13160/dssi/guitarix_amp/guitarix_amp/chan00/control 5 -20
which sets control port 5 to -20. You can query the current state of the plugin:
$ dssi_osc_update
osc.udp://youraddresshere.com:13160/dssi/guitarix_amp/guitarix_amp/chan00
and don't forget analyseplugin to get the port numbers. HTH,
-Sean
Tried running:
DSSI_PATH=/usr/lib/ladspa jack-dssi-host ladspa_guitarix.so:guitarix-amp
ladspa_guitarix.so:guitarix-fx -v -n -a
CPU maxes out and RPi becomes unusable. So I fear I have to rule this
option out :(
Jeremy
8:35 p.m.
On 02/15/2013 10:27 PM, Julien Claassen wrote:
Hi!
Jeremy, if the plugin has 1in and 1out, then you can do:
ecasound -f:16,1,44100 -i intput -o output
-eli:guitarix_1amp_unique_id,param1,param2,...
this should only get you one plugin and if you're interested I can
tell you how to control some plugin parameters via midi as well.
Best regards
Julien
Hi Julien,
Like brummer said, the guitarix-amp plugin has 1 in and 1 out and the
guitarix-fx plugin has 2 in and 2 out. How do I tell Ecasound to only
use one instance of each plugin and properly lay down the signal path?
Can I use multiple -f options for instance? Or do I need to use -chcopy?
Jeremy
9:07 p.m.
On 02/15/2013 11:14 PM, J. Liles wrote:
No packages indeed. I'd be interested to know how
if/how it works on ARM.
I've repackaged the KXStudio source package using distcc and it compiled
almost flawlessly. Only jackpatch.c gave an error but I think I don't
need that yet as it's part of NSM. It seems to run well too. Time to
create a defined mix.
Jeremy
9:49 p.m.
On 02/16/2013 10:07 PM, Jeremy Jongepier wrote:
On 02/15/2013 11:14 PM, J. Liles wrote:
Ok done and CPU usage is acceptable. Now how do I run non-mixer in noui
mode? non-mixer -h doesn't show a noui option and the manual only
mentions one cli option (--osc-port).
Jeremy
No packages indeed. I'd be interested to know
how if/how it works on ARM.
I've repackaged the KXStudio source package using distcc and it compiled
almost flawlessly. Only jackpatch.c gave an error but I think I don't
need that yet as it's part of NSM. It seems to run well too. Time to
create a defined mix.
Jeremy
17 Feb
17 Feb
12:47 a.m.
Hi Jeremy and Herman,
On Sat Feb 16 2013, Jeremy Jongepier wrote:
Tried running:
DSSI_PATH=/usr/lib/ladspa jack-dssi-host
ladspa_guitarix.so:guitarix-amp ladspa_guitarix.so:guitarix-fx -v -n
-a
CPU maxes out and RPi becomes unusable. So I fear I have to rule this
option out :(
CPU maxes out on my system also *when there is no input*. As soon as I
feed it some sound, CPU drops to reasonable levels. Looks like there
may be a denormal problem in ladspa_guitarix.so:guitarix-amp. This was
using guitarix 0.21.0. (I also tried today's guitarix git, and couldn't
reproduce the problem, but I also couldn't get anything but a
clean/bypass sound from the amp plugin, so I don't think I actually
tested it.)
-Sean
10:50 a.m.
I'm trying to figure out what is the best way to use the Guitarix-Amp and
Guitarix-FX LADSPA plugins on a headless system (read Raspberry Pi). I've
tried it with Ecasound but it already consumes more CPU than the guitarix
application itself! So I'm obviously doing something wrong. Maybe this is
because the Guitarix-Amp plugin has one input and two outputs, read
something about Ecasound starting up multiple instances of the plugin in
such a case which is not what I want. So any hints or tips on getting this
to run smoothly? I can use either JACK or ALSA directly. I prefer using
JACK, somehow using bare ALSA produces large amounts of xruns.
Thanks in advance,
Jeremy
Hi Jeremy,
maybe compiling alsaequal and a little tweaking on asoundrc is needed.
Try this if fits your needs
http://www.thedigitalmachine.net/alsaequal.html
http://code.google.com/p/tokland/wiki/RealTimeLADSPAPlugins
Cheers
--
Giorgio Baù
*Sound engineer*
T.Rex Studio
www.trexstudio.com
7:31 p.m.
Normaly we use sse2 to set DAZ.
There is a compile option for arm processors in gcc as well, but i havn't add it to
the optimazion flag for now.
That should need some research.
--
Diese Nachricht wurde von meinem Android Mobiltelefon mit WEB.DE Mail gesendet.
Sean Bolton <sean(a)smbolton.com> schrieb:
Hi Jeremy and Herman,
On Sat Feb 16 2013, Jeremy Jongepier wrote:
Tried running:
DSSI_PATH=/usr/lib/ladspa jack-dssi-host
ladspa_guitarix.so:guitarix-amp ladspa_guitarix.so:guitarix-fx -v -n
-a
CPU maxes out and RPi becomes unusable. So I fear I have to rule this
option out :(
CPU maxes out on my system also *when there is no input*. As soon as I
feed it some sound, CPU drops to reasonable levels. Looks like there
may be a denormal problem in ladspa_guitarix.so:guitarix-amp. This was
using guitarix 0.21.0. (I also tried today's guitarix git, and couldn't
reproduce the problem, but I also couldn't get anything but a
clean/bypass sound from the amp plugin, so I don't think I actually
tested it.)
-Sean
18 Feb
18 Feb
5:37 p.m.
On Sat, Feb 16, 2013 at 1:49 PM, Jeremy Jongepier <jeremy(a)autostatic.com>wrote;wrote:
On 02/16/2013 10:07 PM, Jeremy Jongepier wrote:
When it's installed, it installs a symlink called non-mixer-noui (to
non-mixer) Just run it by that name. If the symlink doesn't exist for some
reason, just create one yourself.
On 02/15/2013 11:14 PM, J. Liles wrote:
Ok done and CPU usage is acceptable. Now how do I run non-mixer in noui
mode? non-mixer -h doesn't show a noui option and the manual only mentions
one cli option (--osc-port).
No packages indeed. I'd be interested to know
how if/how it works on ARM.
I've repackaged the KXStudio source package using distcc and it compiled
almost flawlessly. Only jackpatch.c gave an error but I think I don't
need that yet as it's part of NSM. It seems to run well too. Time to
create a defined mix.
Jeremy
5:42 p.m.
On Sat, Feb 16, 2013 at 1:07 PM, Jeremy Jongepier <jeremy(a)autostatic.com>wrote;wrote:
On 02/15/2013 11:14 PM, J. Liles wrote:
Also, this is great to hear... Does non-sequencer work too? What is the
error in jackpatch? I'd love to post whatever info you have on getting
non-* running on the R Pi on the Non Wiki.
No packages indeed. I'd be interested to know
how if/how it works on ARM.
I've repackaged the KXStudio source package using distcc and it compiled
almost flawlessly. Only jackpatch.c gave an error but I think I don't need
that yet as it's part of NSM. It seems to run well too. Time to create a
defined mix.
Jeremy
9:03 p.m.
On 02/17/2013 01:48 AM, Sean Bolton wrote:
CPU maxes out on my system also*when there is no
input*. As soon as I
feed it some sound, CPU drops to reasonable levels. Looks like there
may be a denormal problem in ladspa_guitarix.so:guitarix-amp. This was
using guitarix 0.21.0. (I also tried today's guitarix git, and couldn't
reproduce the problem, but I also couldn't get anything but a
clean/bypass sound from the amp plugin, so I don't think I actually
tested it.)
-Sean
Hello Sean,
Thanks! I'll give it a go again.
Jeremy
21 Mar
21 Mar
1:03 p.m.
On 02/18/2013 06:42 PM, J. Liles wrote:
Also, this is great to hear... Does non-sequencer work
too? What is the
error in jackpatch? I'd love to post whatever info you have on getting
non-* running on the R Pi on the Non Wiki.
non-sequencer works too. What is the minimal -p (ports) setting I can
use by the way? I was using -p16 and pulled out quite some hairs because
non-sequencer was segfaulting all the time and I couldn't find what was
causing it. In the end I removed the -p16 option and it fired up right away.
And the error in jackpatch is probably related to using distcc with a
cross-compiler. I've now set up a pbuilder environment for Raspbian that
uses qemu-arm-static and so far that works quite good.
Regards,
Jeremy
3857
days inactive
3891
days old
linux-audio-user@lists.linuxaudio.org
23 comments
7 participants
participants (7)
-
brummer- -
Giorgio - Audiophilo -
J. Liles -
Jeremy Jongepier -
Julien Claassen -
michael noble -
Sean Bolton