Summary: | Please create module-ladspa-source | ||
---|---|---|---|
Product: | PulseAudio | Reporter: | Daniel Franke <dfoxfranke> |
Component: | modules | Assignee: | pulseaudio-bugs |
Status: | RESOLVED MOVED | QA Contact: | pulseaudio-bugs |
Severity: | enhancement | ||
Priority: | medium | CC: | lennart |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Daniel Franke
2017-05-15 01:15:06 UTC
Combinaiton of 'module-loopback' and 'module-ladspa-sink' seems be simple solution. Sequence: 1) load 'module-ladspa-sink' (e.g sink.ladspa -> sink) 2) load 'module-loopback' (e.g source -> sink.ladspa) Stream will be flow as below: source -> sink.ladspa -> sink ('source' would be your microphone.) What master do you suggest I provide to ladspa in this configuration? Using loopback would allow me to feed filtered microphone input directly back to an output device, but how would it ever reach an application? I think this is one of example scenario, 1) load module-null-sink. Then, 'null' sink will be created. 2) load module-ladspa-sink. Master sink argument points to 'null' sink. (e.g 'master=null') Then 'null.ladspa' sink will be created which will do process filter. 3) load 'module-loopback'. Sink argument points to 'null.ladspa' sink and source argument points to 'your mic' source. (e.g sink=null.ladspa source='your mic') The audio stream will be construct as below: 'your mic' source -> 'null.ladspa' sink -> 'null' sink My suggestion is that application will be able to get filtered mic stream from monitor source of ladspa. (e.g 'null.ladspa.monitor' source) -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/120. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.