6 Dec
2011
6 Dec
'11
10:36 p.m.
Hello everyone!
For one of my users I wish to insert a few ladspa plugins for the
microphone, but if at all possible not for the output, since then everything
will get evilly distorted and fiendishly loud. I have the basic setup for the
plugins, but I can't think of a way to only insert the plugins for inputs. All
inputs of that card will do, since only the microphone will be in use.
Unfortunately I can't raise the mic volume from the hardware any more and
neither does the phone application have any additional volume control, that I
can see.
Does anyone have a good suggestion or two?
Warm regards
Julien
=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!
====== Find my music at ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)
6 Dec
6 Dec
10:44 p.m.
On Tue, Dec 06, 2011 at 10:37:04PM +0100, Julien Claassen wrote:
For one of my users I wish to insert a few ladspa
plugins for the
microphone, but if at all possible not for the output, since then
everything will get evilly distorted and fiendishly loud. I have the
basic setup for the plugins, but I can't think of a way to only insert
the plugins for inputs. All inputs of that card will do, since only the
microphone will be in use. Unfortunately I can't raise the mic volume
from the hardware any more and neither does the phone application have
any additional volume control, that I can see.
Insert into what ?
--
FA
Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
10:49 p.m.
Hello!
I'm sorry, I didn't make myself clear.
I'm using ALSA's ladspa-plugin modle and I'm inserting the necessary
entries
into .asoundrc for that user. JACK is not available. I've tried it and it will
hang. I think a few people commented on the alsa->JACK plugin not being the
best way of doing it, and most apps, that use it, don't even handle their ALSA
too well. :-( I'm not complaining, just explaining.
Warm regards
Julien
=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!
====== Find my music at ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)
11:22 p.m.
On Tue, Dec 06, 2011 at 10:49:45PM +0100, Julien Claassen wrote:
I'm using ALSA's ladspa-plugin modle and
I'm inserting the necessary
entries into .asoundrc for that user.
The only docs I could find about this is
<http://alsa.opensrc.org/Ladspa_%28plugin%29>
which provides an example:
pcm.ladspa {
type ladspa
slave.pcm "plughw:0,0";
path "/usr/lib/ladspa";
plugins [{
label delay_5s
input {
controls [ 0.8 0.3 ]
}
}]
}
It's not clear at all from the syntax where the plugin is
supposed to go: capture, playback or both (!). Given the
context of the example it will be in at least the playback
path, maybe in both.
<rant> This is one more example showing that the
asoundrc syntax despite its baroque qualities is
missing its target. </rant>
Ciao,
--
FA
Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
11:26 p.m.
Hello Fons!
I didn't fnd this one, but it looked very similar. It said, that the output
could go to a hardware or software mixer (dmix or plughw). It does work on the
capture part. I've tested it and there it does, what it's supposed to do, but
the playback for that user sounds just horrible. :-) Unfortunately my options
are very limited by being restricted to pure alsa here.
Thanks for the looking though!
Warmly yours
Julien
=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!
====== Find my music at ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)
11:33 p.m.
On Tue, Dec 06, 2011 at 11:27:09PM +0100, Julien Claassen wrote:
I didn't fnd this one, but it looked very
similar. It said, that the
output could go to a hardware or software mixer (dmix or plughw). It does
work on the capture part. I've tested it and there it does, what it's
supposed to do, but the playback for that user sounds just horrible. :-)
Unfortunately my options are very limited by being restricted to pure
alsa here.
If you have a working ALSA hw: device, and it's not too weird
regarding sample formats etc. then Jack should just work with it.
Also the ALSA to Jack bridge just works, at least here and on five
or so other systems I installed it on.
Ciao,
--
FA
Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
11:37 p.m.
Hello Fons!
The ALSA->JACK bridge normally works for me. But it hangs with skype, which
is rather picky overall and it did hang with asterisk. For asterisk I tried
looking a bit, but I'm totally inexperienced and the system is rather
overwehlmingly big, if well organised, as far as I could see. Still it was
frightening. Skype of course is closed-source. To tell you how strange it is:
It doesn't work properly, if I set all four cpu-cores running at full speed.
:-(
For things like yatm, ogg123 and mpg321 the alsa-jack-plugin always worked
well. No complaints there.
Warm regards
Julien
=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!
====== Find my music at ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)
7 Dec
7 Dec
5:52 a.m.
On 12/06/2011 05:37 PM, Julien Claassen wrote:
asterisk I tried looking a bit, but I'm totally
inexperienced and the
system is rather overwehlmingly big, if well organised, as far as I
could see. Still it was frightening. Skype of course is closed-source.
To tell you how strange it is: It doesn't work properly, if I set all
four cpu-cores running at full speed. :-(
How are you controlling CPU speeds? I haven't been able to find a way
to change CPU speeds on my Fedora 14 system. I've googled it, and tried
the suggestions there, but nothing works. I can MONITOR the CPU speed,
and see it changing with load changes, but I can't set it to full speed,
for example.
9:11 a.m.
Hello Al!
I have cpufreqd installed, but disabled. I think this was necessary for some
reason.
I wrote myself toscripts cpu_up.sh and cpu_down.sh and in these I accessed
the files found in the /sys hirarchy, especially in
/sys/devices/system/cpu/cpu0/cpufreq/
and:
/sys/devices/system/cpu/cpu0/online
Same goes for the other cores (cpu1, cpu2 and cpu3). That way turned out to
work quite well for me and my requirements. I can check the speed and number
of cores in /proc/cpuinfo, which does seem reliable in these circumstances.
Warm regards
Julien
=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!
====== Find my music at ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)
6 Dec
6 Dec
11:43 p.m.
On Tue, Dec 06, 2011 at 11:27:09PM +0100, Julien Claassen wrote:
I didn't fnd this one, but it looked very
similar. It said, that the
output could go to a hardware or software mixer (dmix or plughw). It does
work on the capture part. I've tested it and there it does, what it's
supposed to do, but the playback for that user sounds just horrible. :-)
So, are you telling us that ALSA inserts the plugin in both
the capture and playback paths ? That would be absolutely
braindead.
If the ALSA device doesn't provide enough level on the mic
input then there is something wrong with either the driver
or its configuration. If it's one that depends on 'quirks',
you'll have to find the right ones...
Ciao,
--
FA
Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
11:48 p.m.
Hello Fons!
I'm using an MAudio delta 1010LT card, meaning the ice1712 chip, which has
always been fine. I guess my microphone isn't the right tool for voip. For
audio recordings it has severd me nicely, but I could always amplify the
signal by a fair amount.
But yes, the plugin does seem to be applied to both capture and playback. I
listened to the recording using another account and I listened to wellknown
music on that user's account. So I am VERY certain about this.
Warmly yours
Julien
=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!
====== Find my music at ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)
7 Dec
7 Dec
12:27 a.m.
On Tue, Dec 6, 2011 at 5:43 PM, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
So, are you telling us that ALSA inserts the plugin in
both
the capture and playback paths ? That would be absolutely
braindead.
doesn't work that way at all.
the app opens "plughw:ladspa" (for example) for playback. presto: the
ladspa plugin is applied to the playback stream.
the app opens "hw:0" (for example) for capture. no plugin processing
on the capture stream.
the app opens "plughw:ladspa" (for example) for capture. presto: the
ladspa plugin is applied to the capture stream.
remember that there is no such thing as a duplex ALSA stream (similar
to several other audio device APIs).
If the ALSA device doesn't provide enough level on
the mic
input then there is something wrong with either the driver
or its configuration.
agreed.
12:46 a.m.
On Tue, Dec 06, 2011 at 06:27:23PM -0500, Paul Davis wrote:
On Tue, Dec 6, 2011 at 5:43 PM, Fons Adriaensen
<fons(a)linuxaudio.org> wrote:
And what if the app opens the device for capture and playback ?
Isn't the whole 'plug' system meant to be transparent to apps,
so an app can just use 'default' and get whatever the user
configured to be 'default' ?
So, are you telling us that ALSA inserts the
plugin in both
the capture and playback paths ? That would be absolutely
braindead.
doesn't work that way at all.
the app opens "plughw:ladspa" (for example) for playback. presto: the
ladspa plugin is applied to the playback stream.
the app opens "hw:0" (for example) for capture. no plugin processing
on the capture stream.
the app opens "plughw:ladspa" (for example) for capture. presto: the
ladspa plugin is applied to the capture stream. remember that there is no such thing as a duplex ALSA
stream (similar
to several other audio device APIs).
Very well, but the .asoundrc syntax seems to be in terms of
duplex devices. How would you configure a plugin in 'default's
capture stream only ?
Ciao,
--
FA
Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
12:57 a.m.
On Tue, Dec 6, 2011 at 6:46 PM, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
On Tue, Dec 06, 2011 at 06:27:23PM -0500, Paul Davis
wrote:
it will open two streams, and the processing on each one depends on
the device name it uses to open each stream.
On Tue, Dec 6, 2011 at 5:43 PM, Fons Adriaensen
<fons(a)linuxaudio.org> wrote:
And what if the app opens the device for capture and playback ? So, are you telling us that ALSA inserts the
plugin in both
the capture and playback paths ? That would be absolutely
braindead.
doesn't work that way at all.
the app opens "plughw:ladspa" (for example) for playback. presto: the
ladspa plugin is applied to the playback stream.
the app opens "hw:0" (for example) for capture. no plugin processing
on the capture stream.
the app opens "plughw:ladspa" (for example) for capture. presto: the
ladspa plugin is applied to the capture stream. Isn't the whole 'plug' system meant to be
transparent to apps,
so an app can just use 'default' and get whatever the user
configured to be 'default' ?
yes, that works too. but most users (and your example) don't define
"default".
Very well, but the .asoundrc syntax seems to be in
terms of
duplex devices. How would you configure a plugin in 'default's
capture stream only ?
the capture stream only exists when a process opens the device for
capture. it is not a separate property or entity. the properties of
the stream depend on the name of the device.
Vor uns liegt ein weites Tal, die Sonne scheint - ein
Glitzerstrahl.
so does this quote predate kraftwerk or are you finally embracing the
frozen four? :)
1:05 a.m.
On Tue, Dec 06, 2011 at 06:57:05PM -0500, Paul Davis wrote:
Is that a way of saying 'can't be done' ?
I've always loved 'Autobahn' - it's the perfect expression of the
strange mix of pleasure and tedium of driving on German highways.
Ciao,
--
FA
Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
Very well, but
the .asoundrc syntax seems to be in terms of
duplex devices. How would you configure a plugin in 'default's
capture stream only ?
the capture stream only exists when a process opens the device for
capture. it is not a separate property or entity. the properties of
the stream depend on the name of the device. Vor uns liegt
ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
so does this quote predate kraftwerk or are you finally embracing the
frozen four? :)
12:58 a.m.
You hit the point spot-on Fons. Still, I think this isn't really a fault of
the ALSA architecture. If an app does open a device both ways, then that's
their fault. Still it would be nice. I'll still keep on looking.Perhaps
something can be done with dsnoop and dmix or dshare or one of those.
Kindly yours
Julien
=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!
====== Find my music at ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)
12:59 a.m.
On Wed, Dec 7, 2011 at 4:59 AM, Julien Claassen <julien(a)mail.upb.de> wrote:
You hit the point spot-on Fons. Still, I think this
isn't really a fault of
the ALSA architecture. If an app does open a device both ways, then that's
their fault. Still it would be nice. I'll still keep on looking.Perhaps
something can be done with dsnoop and dmix or dshare or one of those.
nope.
if you want different processing on the playback and capture streams,
you'll need to use two different device names for each stream.
1:01 a.m.
Paul!
the problem is, I don't think the app offers to use different input and
output device names or stream names. There I'm stuck then.
Kind regards
Julien
=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!
====== Find my music at ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)
1:06 a.m.
On Wed, Dec 7, 2011 at 5:02 AM, Julien Claassen <julien(a)mail.upb.de> wrote:
Paul!
the problem is, I don't think the app offers to use different input and
output device names or stream names. There I'm stuck then.
actually, you're not.
a careful reading of the docs reveals:
type ladspa # LADSPA plugin PCM
slave STR # Slave name (see pcm_slave)
path STR # Path or paths (delimited with ':')
plugins | playback_plugins | capture_plugins {
[ ... ]
note the 3 choices for the line that might start "plugins" ...
1:12 a.m.
On Tue, Dec 06, 2011 at 07:06:22PM -0500, Paul Davis wrote:
a careful reading of the docs reveals:
type ladspa # LADSPA plugin PCM
slave STR # Slave name (see pcm_slave)
path STR # Path or paths (delimited with ':')
plugins | playback_plugins | capture_plugins {
[ ... ]
note the 3 choices for the line that might start "plugins" ...
You have a pointer to those docs ? I've been searching the
ALSA site for some time - no luck.
Ciao,
--
FA
Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.
1:17 a.m.
On Tue, Dec 6, 2011 at 7:12 PM, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
On Tue, Dec 06, 2011 at 07:06:22PM -0500, Paul Davis
wrote:
i typed:
asoundrc syntax
into google. that took me to:
http://alsa.opensrc.org/.asoundrc
which linked to:
http://alsa.opensrc.org/Asoundrc.txt
which is where the above quote is from.
a careful reading of the docs reveals:
type ladspa # LADSPA plugin PCM
slave STR # Slave name (see pcm_slave)
path STR # Path or paths (delimited with ':')
plugins | playback_plugins | capture_plugins {
[ ... ]
note the 3 choices for the line that might start "plugins" ...
You have a pointer to those docs ? I've been searching the
ALSA site for some time - no luck.
1:18 a.m.
Aha, revelation. I didn't think it was possible. Theother syntax is the only
one, that I've ever seen and thought on rediscovery, that this was it. that
should tell me a lesson.
Warm regards
Julien
=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!
====== Find my music at ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)
12:55 a.m.
Ah, there is the problem, which I stupidly ignored. I put this into the
pcm.!defalt device, because I don't know how to set specific alsa devices for
skype, if at all possible. In any case it's qt, which I can't use. I'm not
sure, if there is any distro, that has teh new QT with the access bridge. so
I'm working out an ALSA way to solving this problem, if possible. I'll
continue my quest then.
Kind regards
Julien
=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!
====== Find my music at ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)
6 Dec
6 Dec
10:46 p.m.
So the effect of the plugins should only be audible in the recording,
not the monitoring output?
If so, then simply route in -> out and in -> ladspa -> recordingapp.
If jack is for some reason not available then I guess it depends on the
host of the plugins. If alsa routing is required, I have no idea.
Regards,
Philipp
9:13 a.m.
Hello Clemens!
This is a neat solution. Thank you. I'll try that one as well.
Warm regards
Julien
=-=-=-=-=-=-=-=-=-=-=-=-
Such Is Life: Very Intensely Adorable;
Free And Jubilating Amazement Revels, Dancing On - FLOWERS!
====== Find my music at ======
http://juliencoder.de/nama/music.html
.....................................
"If you live to be 100, I hope I live to be 100 minus 1 day,
so I never have to live without you." (Winnie the Pooh)
4809
days inactive
4810
days old
linux-audio-user@lists.linuxaudio.org
25 comments
6 participants
participants (6)
-
Al Thompson -
Clemens Ladisch -
Fons Adriaensen -
Julien Claassen -
Paul Davis -
Philipp Überbacher