13 Jul
2013
13 Jul
'13
7:50 p.m.
Hello, dear folks.
I'm still (constantly) tweaking my raspberry here and there when I
can. I have some configurations/sessions that run ok, Looper
(jack+sooperlooper), Looper+Fx
(jack+sooperlooper+rakarrack/guitarrix). But I'm still having some
annoying problems that wanted to share with you:
1) Simple session script, Looper, runs quite well when launched (via
ssh -X or from console) logged as PI user. When I run it as a
boot/init script (simple launcher script placed in /etc/init.d and
then installed with "update-rc.d launcherscript defaults 99"), almost
in every first start there's crackles and noise and my loops sound
distorted, even with clean guitar; if I restart then it goes well (2nd
or 3d time).
2) Next step forward I added Rakarrack in charge of guitar FX routed
to the Looper. First, it happens almost same thing as mentioned about
noise. Well, I guess It should have something to do with the signal
path and things connected to the same power supplier, so I'll have to
reserve some time to debug and switch off things until I get a cleaner
signal and get rid of the hum and crackles.
But the main issue is that there's problems with Rakarrack not been
able to start because several problems with not enough Jack ports and
Jack and RT. I didn't have any of these problems before.
I got to solve the problem with ports changing -p16 to -p32 when
launching jack+sooperlooper (-p24 is enough for just Rakarrack).
Then I made a launcher script LSB compliant (service script placed in
/etc/init.d and then installed with "update-rc.d servicescript
defaults", with LSB flags and functions for "start" and "stop",
as a
proper newer Debian service, and configured to launch last in boot
phase) which then call the Jack-config+Rakarrack+Sooperlooper session
launcher script. I can see on screen in the init messages this error:
"JACK is running in realtime mode, but you are not allowed to use
realtime schedule..."
But I know RT is already configured, so I guessed it was something to
do with the boot/init stage configuration and environment.
I tried using "su" with several different parameters to run the
launcher script as "pi" user, as It runs quite well when logged as
this user (calling just the script and even with "sudo
/etc/init.d/script start").
So, maybe you can't get RT in init phase on RaspberryPI and you can
only when you get to the login prompt and everything is loaded and
ready. But I think there's a "Puredata on Raspberry PI" project that
runs some scripts in the init stage; and it seems that in order to get
a headless FX+looper station, running some configuration+apps-launcher
at boot time is an obvious choice.
I'm sure something escapes me after so much try-error-code cicles.
Maybe you have some ideas.
Thanks as always.
--
Carlos sanchiavedraz
* Musix GNU+Linux
http://www.musix.es
13 Jul
13 Jul
7:59 p.m.
New subject: Raspberry: problems with shell script launcher when booting
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/13/2013 09:50 PM, Carlos sanchiavedraz wrote:
Hello, dear folks.
I'm still (constantly) tweaking my raspberry here and there when I
can. I have some configurations/sessions that run ok, Looper
(jack+sooperlooper), Looper+Fx
(jack+sooperlooper+rakarrack/guitarrix). But I'm still having some
annoying problems that wanted to share with you:
1) Simple session script, Looper, runs quite well when launched
(via ssh -X or from console) logged as PI user. When I run it as a
boot/init script (simple launcher script placed in /etc/init.d and
then installed with "update-rc.d launcherscript defaults 99"),
almost in every first start there's crackles and noise and my loops
sound distorted, even with clean guitar; if I restart then it goes
well (2nd or 3d time).
Hi Carlos,
Try resetting the JACK buffersize with jack_bufsize after starting
your program. This does the trick for me on the RPi.
2) Next step forward I added Rakarrack in charge of
guitar FX
routed to the Looper. First, it happens almost same thing as
mentioned about noise. Well, I guess It should have something to do
with the signal path and things connected to the same power
supplier, so I'll have to reserve some time to debug and switch off
things until I get a cleaner signal and get rid of the hum and
crackles. But the main issue is that there's problems with
Rakarrack not been able to start because several problems with not
enough Jack ports and Jack and RT. I didn't have any of these
problems before.
I got to solve the problem with ports changing -p16 to -p32 when
launching jack+sooperlooper (-p24 is enough for just Rakarrack).
Then I made a launcher script LSB compliant (service script placed
in /etc/init.d and then installed with "update-rc.d servicescript
defaults", with LSB flags and functions for "start" and "stop",
as
a proper newer Debian service, and configured to launch last in
boot phase) which then call the Jack-config+Rakarrack+Sooperlooper
session launcher script. I can see on screen in the init messages
this error:
"JACK is running in realtime mode, but you are not allowed to use
realtime schedule..."
But I know RT is already configured, so I guessed it was something
to do with the boot/init stage configuration and environment. I
tried using "su" with several different parameters to run the
launcher script as "pi" user, as It runs quite well when logged as
this user (calling just the script and even with "sudo
/etc/init.d/script start"). So, maybe you can't get RT in init
phase on RaspberryPI and you can only when you get to the login
prompt and everything is loaded and ready. But I think there's a
"Puredata on Raspberry PI" project that runs some scripts in the
init stage; and it seems that in order to get a headless FX+looper
station, running some configuration+apps-launcher at boot time is
an obvious choice.
I'm sure something escapes me after so much try-error-code cicles.
Maybe you have some ideas.
http://lists.linuxaudio.org/pipermail/linux-audio-user/2013-March/091750.ht…
Regards,
Jeremy
Thanks as always.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQIcBAEBAgAGBQJR4bG2AAoJEF63J34m6LiUDq4P+QHsb/bODOeBtL0dQUvmNrD2
jXeYyU57kAF5Al5Nf7e8vtAKuGSsLuVhF30CYGtcM1VUHYT0PFVfaOkZxlQsLJ6W
nM2w36ADyIEgboadWmS9DqoEP+L80XR6EpK9Bz1ZuMYgLsKg5eOP6m94v4rArsjQ
KDZTEIB5S4d1F4ZvDHbAnH2vY2wlhaH7Ii0R8IKuNCZwJP3L96abayNB9AjA6Fzu
SiKmjrnibujvonXOi3ew/86mES7AbOCJ9Bc4FnP+ZDlLMhvV3LGQQ5/lG5mLXW78
nqwQM958pZJrn7ZHgsU73mhi6i1iBP7hjGTtbdOd6NeUyNcWPeVnhJbHJAM9HCBE
xs0NkNVoQJnmRrBnT8yYcrZY3Vk6+8dzC/XbRlo97yvfNixKHEfTaAY2aMptQuCu
+zPURKNij22FHU1+r7IzZQR6zvoHIxN2zqs7k8677CQEzYFJ8OOcu3YiixmIhPll
q9ZVTiy13fONzgdenhwY9Ow+26vtQF+HVcLt3d5WegaEjjkykxvX/6CLX0nLrlqz
3DwyQ0DD0Wk20DwejIsfVo0zDhmw9XKZY2UPX6zCm9p/JIuD/IxYq5mzvZXiGToS
5KTBrT2NAn3t03591M1HiekA8YEj8p4BHVOM8yVTxI3T5RSiT09kYSuKg2RpAfNJ
tp6jusbkXuF0aEZav7K2
=hhBs
-----END PGP SIGNATURE-----
15 Jul
15 Jul
12:23 p.m.
New subject: Raspberry: problems with shell script launcher when booting
Hi Jeremy,
2013/7/13 Jeremy Jongepier <jeremy(a)autostatic.com>om>:
I implemented just the first part that solution: uncomment the line
"session required pam_limits.so"
in "/etc/pam.d/su".
Now my script and applicacionts run with "pi" user. Great again, Jeremy!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/13/2013 09:50 PM, Carlos sanchiavedraz wrote:
It seems it did my trick as well, great!
For the moment sound seems to be as clean as it can until the moment I
debug other inner noises (it sounds like that of physical hard drives
turning, but there's none in RPi (?)) when nothing is plugged in the
audio interface.
Hello, dear folks.
I'm still (constantly) tweaking my raspberry here and there when I
can. I have some configurations/sessions that run ok, Looper
(jack+sooperlooper), Looper+Fx
(jack+sooperlooper+rakarrack/guitarrix). But I'm still having some
annoying problems that wanted to share with you:
1) Simple session script, Looper, runs quite well when launched
(via ssh -X or from console) logged as PI user. When I run it as a
boot/init script (simple launcher script placed in /etc/init.d and
then installed with "update-rc.d launcherscript defaults 99"),
almost in every first start there's crackles and noise and my loops
sound distorted, even with clean guitar; if I restart then it goes
well (2nd or 3d time).
Hi Carlos,
Try resetting the JACK buffersize with jack_bufsize after starting
your program. This does the trick for me on the RPi. 2) Next step forward I added Rakarrack in charge
of guitar FX
routed to the Looper. First, it happens almost same thing as
mentioned about noise. Well, I guess It should have something to do
with the signal path and things connected to the same power
supplier, so I'll have to reserve some time to debug and switch off
things until I get a cleaner signal and get rid of the hum and
crackles. But the main issue is that there's problems with
Rakarrack not been able to start because several problems with not
enough Jack ports and Jack and RT. I didn't have any of these
problems before.
I got to solve the problem with ports changing -p16 to -p32 when
launching jack+sooperlooper (-p24 is enough for just Rakarrack).
Then I made a launcher script LSB compliant (service script placed
in /etc/init.d and then installed with "update-rc.d servicescript
defaults", with LSB flags and functions for "start" and "stop",
as
a proper newer Debian service, and configured to launch last in
boot phase) which then call the Jack-config+Rakarrack+Sooperlooper
session launcher script. I can see on screen in the init messages
this error:
"JACK is running in realtime mode, but you are not allowed to use
realtime schedule..."
But I know RT is already configured, so I guessed it was something
to do with the boot/init stage configuration and environment. I
tried using "su" with several different parameters to run the
launcher script as "pi" user, as It runs quite well when logged as
this user (calling just the script and even with "sudo
/etc/init.d/script start"). So, maybe you can't get RT in init
phase on RaspberryPI and you can only when you get to the login
prompt and everything is loaded and ready. But I think there's a
"Puredata on Raspberry PI" project that runs some scripts in the
init stage; and it seems that in order to get a headless FX+looper
station, running some configuration+apps-launcher at boot time is
an obvious choice.
I'm sure something escapes me after so much try-error-code cicles.
Maybe you have some ideas.
http://lists.linuxaudio.org/pipermail/linux-audio-user/2013-March/091750.ht…
Regards,
Jeremy
> Thanks as always.
>
>
Now, there's just a minimum issue, but I can live with it. Rackarrack
runs now as "pi" user and it should take its configuration from user's
$HOME, that is what it should be "/home/pi", but it seems that it
doesn't.
The difference between running the launcher script when logged in as
pi is that it takes the MIDI mapping configured in preferences, but
when launched automatically on init phase it takes the default MIDI
mapping.
I run the launcher script from the service script with:
su -l -c $STARTPATH/launcherscript.sh pi
...and "-l" should load the pi environment (I checked it when
debugging). Maybe is something specific with Rakarrack.
Thanks so much, Jeremy.
--
Carlos sanchiavedraz
* Musix GNU+Linux
http://www.musix.es
1:47 p.m.
New subject: Raspberry: problems with shell script launcher when booting
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/15/2013 02:23 PM, Carlos sanchiavedraz wrote:
What kind of audio interface are you using? You might have to ground
it properly (assunimg you're using an USB interface):
http://sourceforge.net/apps/mediawiki/guitarix/index.php?title=Guitarix_Emb…
[...]
Hi Jeremy,
[...]
Hi Carlos,
Try resetting the JACK buffersize with jack_bufsize after
starting your program. This does the trick for me on the RPi.
It seems it did my trick as well, great! For the moment sound seems
to be as clean as it can until the moment I debug other inner
noises (it sounds like that of physical hard drives turning, but
there's none in RPi (?)) when nothing is plugged in the audio
interface.
Now, there's just a minimum issue, but I can live with it.
Rackarrack runs now as "pi" user and it should take its
configuration from user's $HOME, that is what it should be
"/home/pi", but it seems that it doesn't. The difference between
running the launcher script when logged in as pi is that it takes
the MIDI mapping configured in preferences, but when launched
automatically on init phase it takes the default MIDI mapping.
I run the launcher script from the service script with: su -l -c
$STARTPATH/launcherscript.sh pi
...and "-l" should load the pi environment (I checked it when
debugging). Maybe is something specific with Rakarrack.
Thanks so much, Jeremy.
I'm using 'su -l pi -c /some/command' myself but the order shouldn't
matter I guess. Otherwise you could take a look at start-stop-daemon.
Examples can be found in /etc/init.d/skeleton
Jeremy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBAgAGBQJR4/17AAoJEF63J34m6LiUMf0P/1w0LSRQLVKlSc9Kvacl7f3N
ZowKUqcZcPgubZB85XB8ii5u5LUJKTVM7na/gL36l2sjEWafPZR5K/kT1wijYI6m
bsTBZzPnEroSQld8Jwcyd3t7Gnp2Xo2amnszUjgadc4Cmu0PTlRzqKOd+Vmwjfnf
PGpXbxix+0EyBK4TNiW+XtxwKOBiYisbK/gScMEoXHhcK31cdpC03OVYI89U8Yw9
rrgAC/E5RZtVmHptN2wyXDn0cL6cBCq+GuZtU474jvDfGX9gLeKa0jRErngifMZY
S0ZLkrOymujTuB5rYw7qPCzYOGrOg9ItINIKTroGTJ2kC+TUNG8B1VFUdb0yPfF7
JFQlTTrqW9ciA1alAFRFJ9ZXFEoxwgEcIGjCmMNbpDtHFuX8ZRp1v76m3bNNgZn/
LaigRkXUjDilYKf62vQAsmZTRBx9SLZWJLJ360dGdkc/CSO3uAnTeMQMB3yqfSja
pyb9e6K1dachCWHyF9jHIvADuXUC7fgSdfRhYllrFT5qMKu03NYXrT0lJjVQh+yD
hmiIDF2RmHEbrsFfvsvyEFeiVeoDbJGPdOFzPSrn/8ruHQr83NZWjkUGv/8yjzf7
fES+4FIUuAREagZG1bX08e85l5q4mU0mlV74uBfhLY9D2p4XLU+ikyq3nAWPHlrJ
jrn2YzjmbLa1EkaiGxVB
=TOji
-----END PGP SIGNATURE-----
16 Jul
16 Jul
1:47 p.m.
New subject: Raspberry: problems with shell script launcher when booting
Hi Jeremy,
2013/7/15 Jeremy Jongepier <jeremy(a)autostatic.com>om>:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/15/2013 02:23 PM, Carlos sanchiavedraz wrote:
What kind of audio interface are you using? You might have to ground
it properly (assunimg you're using an USB interface):
http://sourceforge.net/apps/mediawiki/guitarix/index.php?title=Guitarix_Emb…
What I supposed is exactly what it points in that article:
"noise on the USB power line will feed into the preamplifier of the
audio interface",
or maybe not, but it is probably. But cutting cables and soldering I'm
afraid it's not an option for now; don't want to change my audio
interface into some Frankenterface and break it.
I'll see if I can clean a little bit more without going extremes.
Hi Jeremy,
[...]
Hi
Carlos,
Try resetting the JACK buffersize with jack_bufsize after
starting your program. This does the trick for me on the RPi.
It seems it did my trick as well, great! For the moment sound seems
to be as clean as it can until the moment I debug other inner
noises (it sounds like that of physical hard drives turning, but
there's none in RPi (?)) when nothing is plugged in the audio
interface.
[...]
My service script is based on Debian norms:
http://wiki.debian.org/LSBInitScripts
Basically:
* First the config for Run-time dependencies in the format indicated
* Shell methods for start, stop...
On my method start is that command I mentioned:
su -l -c
Now, there's just a minimum issue, but I can live with it.
Rackarrack runs now as "pi" user and it should take its
configuration from user's $HOME, that is what it should be
"/home/pi", but it seems that it doesn't. The difference between
running the launcher script when logged in as pi is that it takes
the MIDI mapping configured in preferences, but when launched
automatically on init phase it takes the default MIDI mapping.
I run the launcher script from the service script with: su -l -c
$STARTPATH/launcherscript.sh pi
...and "-l" should load the pi environment (I checked it when
debugging). Maybe is something specific with Rakarrack.
Thanks so much, Jeremy.
I'm using 'su -l pi -c /some/command' myself but the order shouldn't
matter I guess. Otherwise you could take a look at start-stop-daemon.
Examples can be found in /etc/init.d/skeleton
Jeremy > $STARTPATH/launcherscript.sh pi
I've seen that other service run whichever command but preceded by
start-stop-daemon -v, but I'm not sure it makes a difference for this
issue. And since this is not a proper "service" but a launcher at the
very beginning, I didn't use start-stop-daemon.
Thanks again.
--
Carlos sanchiavedraz
* Musix GNU+Linux
http://www.musix.es
15 Jul
15 Jul
1:04 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 13 Jul 2013 21:50:28 +0200
Carlos sanchiavedraz <csanchezgs(a)gmail.com> wrote:
Hello, dear folks.
I'm still (constantly) tweaking my raspberry here and there when I
can. I have some configurations/sessions that run ok, Looper
(jack+sooperlooper), Looper+Fx
(jack+sooperlooper+rakarrack/guitarrix).
Hi Carlos, just curious - how does the pi manage these loads? I
remember some rakarrack effects being quite CPU intensive... Do you use
it alongside guitarrix or only one at a time?
I'm considering abandoning my home server project for the pi and
getting back to one of my "ultimate guitar processor with linux"
quests...
cheers
renato
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
iQEcBAEBAgAGBQJR4/NxAAoJEBz6xFdttjrfUDsH/3bHO9aYrgRhkGYh91RKz2av
IXTxPlO0aqIhxIZN/gtzyCUsymG5RaBTzO8fHgiS5PROd164tcL7wtFDAwD7QxT5
3Je5PeLgiJ+zM9HlvoG7yXNCoYfgn/Vge6qI6P+rLJy5F5z6tF38ZMh8s5ALIcVb
64nmcWWxnCB1ndsBWV0yfXNvWHOpNQA8oTQIvKWaMD6wxr19ZwSNYAXJcosCjqSd
vw948qc1v41BJkV44qitVM7J+frplHX5sVNzfv21lyCNEfnPD/p/os88rgHxh98A
DfFJdFUF0dakEQDkhaGFt3wR16r0gOmy8roI2oVzVAmSlu9A59nDla8+dABq+Yc=
=HMFS
-----END PGP SIGNATURE-----
16 Jul
16 Jul
1:37 p.m.
New subject: Raspberry: problems with shell script launcher when booting
Hi, Renato,
2013/7/15 Renato <rennabh(a)gmail.com>om>:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 13 Jul 2013 21:50:28 +0200
Carlos sanchiavedraz <csanchezgs(a)gmail.com> wrote:
By now I use Rakarrack standalone (FX), and also
connected to
Sooperlooper (FX+looper).
I made some time ago, for a different not-powerful device, preset
which have in its signal path just FX that are let's say "simple":
Compressor, Echo, Chorus, Flanger... No Convolver or the other stereo
versions of those fx. It would be great to have some kind of colored
(red-yellow-green) list of FX by CPU consumption, but for now I just
guess which plugins could RPI handle.
On this preset I chose also Harmonizer, but it turns out that for RPi
and jack with buffer up to 256 the voice generated has noises, so is a
little unusable, and for higher buffer values you start to notice the
delay. I have to try some more to see if I can tweak something (right
now it is selected the minimum quality (4) for Harmonizer in Rakarrack
preferences).
--
Carlos sanchiavedraz
* Musix GNU+Linux
http://www.musix.es
Hello, dear folks.
I'm still (constantly) tweaking my raspberry here and there when I
can. I have some configurations/sessions that run ok, Looper
(jack+sooperlooper), Looper+Fx
(jack+sooperlooper+rakarrack/guitarrix).
Hi Carlos, just curious - how does the pi manage these loads? I
remember some rakarrack effects being quite CPU intensive... Do you use
it alongside guitarrix or only one at a time?
I'm considering abandoning my home server project for the pi and
getting back to one of my "ultimate guitar processor with linux"
quests...
cheers
renato
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
iQEcBAEBAgAGBQJR4/NxAAoJEBz6xFdttjrfUDsH/3bHO9aYrgRhkGYh91RKz2av
IXTxPlO0aqIhxIZN/gtzyCUsymG5RaBTzO8fHgiS5PROd164tcL7wtFDAwD7QxT5
3Je5PeLgiJ+zM9HlvoG7yXNCoYfgn/Vge6qI6P+rLJy5F5z6tF38ZMh8s5ALIcVb
64nmcWWxnCB1ndsBWV0yfXNvWHOpNQA8oTQIvKWaMD6wxr19ZwSNYAXJcosCjqSd
vw948qc1v41BJkV44qitVM7J+frplHX5sVNzfv21lyCNEfnPD/p/os88rgHxh98A
DfFJdFUF0dakEQDkhaGFt3wR16r0gOmy8roI2oVzVAmSlu9A59nDla8+dABq+Yc=
=HMFS
-----END PGP SIGNATURE-----
1:50 p.m.
New subject: Raspberry: problems with shell script launcher when booting
2013/7/16 Carlos sanchiavedraz <csanchezgs(a)gmail.com>om>:
Hi, Renato,
2013/7/15 Renato <rennabh(a)gmail.com>om>:
Arpie works well also. I would be trying FX to see which of them RPi
can/cannot handle. Would love to know you're (Renato and all)
experiences about.
--
Carlos sanchiavedraz
* Musix GNU+Linux
http://www.musix.es
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 13 Jul 2013 21:50:28 +0200
Carlos sanchiavedraz <csanchezgs(a)gmail.com> wrote:
By now I use Rakarrack standalone (FX), and
also connected to
Sooperlooper (FX+looper).
I made some time ago, for a different not-powerful device, preset
which have in its signal path just FX that are let's say "simple":
Compressor, Echo, Chorus, Flanger... No Convolver or the other stereo
versions of those fx. It would be great to have some kind of colored
(red-yellow-green) list of FX by CPU consumption, but for now I just
guess which plugins could RPI handle.
On this preset I chose also Harmonizer, but it turns out that for RPi
and jack with buffer up to 256 the voice generated has noises, so is a
little unusable, and for higher buffer values you start to notice the
delay. I have to try some more to see if I can tweak something (right
now it is selected the minimum quality (4) for Harmonizer in Rakarrack
preferences).
--
Carlos sanchiavedraz
* Musix GNU+Linux
http://www.musix.es Hello, dear folks.
I'm still (constantly) tweaking my raspberry here and there when I
can. I have some configurations/sessions that run ok, Looper
(jack+sooperlooper), Looper+Fx
(jack+sooperlooper+rakarrack/guitarrix).
Hi Carlos, just curious - how does the pi manage these loads? I
remember some rakarrack effects being quite CPU intensive... Do you use
it alongside guitarrix or only one at a time?
I'm considering abandoning my home server project for the pi and
getting back to one of my "ultimate guitar processor with linux"
quests...
cheers
renato
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
iQEcBAEBAgAGBQJR4/NxAAoJEBz6xFdttjrfUDsH/3bHO9aYrgRhkGYh91RKz2av
IXTxPlO0aqIhxIZN/gtzyCUsymG5RaBTzO8fHgiS5PROd164tcL7wtFDAwD7QxT5
3Je5PeLgiJ+zM9HlvoG7yXNCoYfgn/Vge6qI6P+rLJy5F5z6tF38ZMh8s5ALIcVb
64nmcWWxnCB1ndsBWV0yfXNvWHOpNQA8oTQIvKWaMD6wxr19ZwSNYAXJcosCjqSd
vw948qc1v41BJkV44qitVM7J+frplHX5sVNzfv21lyCNEfnPD/p/os88rgHxh98A
DfFJdFUF0dakEQDkhaGFt3wR16r0gOmy8roI2oVzVAmSlu9A59nDla8+dABq+Yc=
=HMFS
-----END PGP SIGNATURE-----
3943
days inactive
3946
days old
linux-audio-user@lists.linuxaudio.org
7 comments
3 participants
participants (3)
-
Carlos sanchiavedraz -
Jeremy Jongepier -
Renato