Re: [pulseaudio-discuss] flushing dynamically loaded modules

2012-09-20 Thread Richard Bown
A bit more info If I unload the jack sink and source modules before killing jackd, PA doesn't crash., there's a problem on the timing on my script that the modules look like the modules aren't unloaded before jackd shuts down,,, more sleep time. But still a problem if PA crashes due to the above,

Re: [pulseaudio-discuss] flushing dynamically loaded modules

2012-09-20 Thread Richard Bown
On Thu, 20 Sep 2012 21:43:23 +0300 Tanu Kaskinen wrote: > Please keep the mailing list in the recipients. > > On Thu, 2012-09-20 at 18:57 +0100, Richard Bown wrote: > > > How do you load the jack modules? There's certainly no tmp file storing > > > the jack module configuration, so if you have l

Re: [pulseaudio-discuss] flushing dynamically loaded modules

2012-09-20 Thread Tanu Kaskinen
Please keep the mailing list in the recipients. On Thu, 2012-09-20 at 18:57 +0100, Richard Bown wrote: > > How do you load the jack modules? There's certainly no tmp file storing > > the jack module configuration, so if you have loaded them just with > > pactl, restarting pulseaudio will clear the

Re: [pulseaudio-discuss] flushing dynamically loaded modules

2012-09-20 Thread Tanu Kaskinen
On Thu, 2012-09-20 at 18:10 +0100, Richard Bown wrote: > Hi , > sorry for the newbie type questions. > I've looked in the FAQs, and probably missed the answer. > If I load a module from CLI with pactl or with paprefs > is there a CLI command to flush the loaded modules. > > I haven't found th

[pulseaudio-discuss] flushing dynamically loaded modules

2012-09-20 Thread Richard Bown
Hi , sorry for the newbie type questions. I've looked in the FAQs, and probably missed the answer. If I load a module from CLI with pactl or with paprefs is there a CLI command to flush the loaded modules. I haven't found the config file which is created and added to by paprefs, or from pact

Re: [pulseaudio-discuss] [PATCH v2 0/3] Suspending loopback

2012-09-20 Thread Dalleau, Frederic
Hi Mikel, On Thu, Sep 20, 2012 at 2:28 PM, Mikel Astiz wrote: > From: Mikel Astiz > > v2 modifies previous patches as suggested by Tanu: > > - Sink-inputs and source-outputs are created corked, and immediately > afterwards uncorked if audio not suspended. > > - Patch v2 3/3 stops the rate adjus

[pulseaudio-discuss] [PATCH 3/3] sink, source: Really set the fixed latency in set_fixed_latency_within_thread(), always.

2012-09-20 Thread Tanu Kaskinen
The old assumption seemed to be that if a sink or source has the DYNAMIC_LATENCY flag set, it can never change, so the fixed latency will always be zero. This assumption doesn't hold with filter sinks and sources that are moved around. This fixes a crash with two module-virtual-sink instances on t

[pulseaudio-discuss] [PATCH 2/3] Propagate the PA_{SINK, SOURCE}_DYNAMIC_LATENCY flag changes through a chain of filter sinks/sources.

2012-09-20 Thread Tanu Kaskinen
An example: let's say that there's an alsa sink and two filter sinks on top of each other: alsa-sink -> filter1 -> filter2 With the old code, if filter1 gets moved to another sink, and the new sink doesn't have the DYNAMIC_LATENCY flag set (unlike alsa-sink), the DYNAMIC_LATENCY flag of filte

[pulseaudio-discuss] [PATCH 1/3] Propagate the PA_{SINK, SOURCE}_LATENCY flag changes through a chain of filter sinks/sources.

2012-09-20 Thread Tanu Kaskinen
An example: let's say that there's an alsa sink and two filter sinks on top of each other: alsa-sink -> filter1 -> filter2 With the old code, if filter1 gets moved to another sink, and the new sink doesn't have the LATENCY flag set (unlike alsa-sink), the LATENCY flag of filter1 is updated fi

[pulseaudio-discuss] [PATCH 0/3] Fix latency flag handling.

2012-09-20 Thread Tanu Kaskinen
Tanu Kaskinen (3): Propagate the PA_{SINK,SOURCE}_LATENCY flag changes through a chain of filter sinks/sources. Propagate the PA_{SINK,SOURCE}_DYNAMIC_LATENCY flag changes through a chain of filter sinks/sources. sink, source: Really set the fixed latency in set_fixed_latency_with

[pulseaudio-discuss] [PATCH v2 3/3] loopback: Disable adjust timer when suspended

2012-09-20 Thread Mikel Astiz
From: Mikel Astiz Stop the rate adjustment timer when no audio is flowing. --- src/modules/module-loopback.c | 40 +--- 1 files changed, 33 insertions(+), 7 deletions(-) diff --git a/src/modules/module-loopback.c b/src/modules/module-loopback.c index ad0381

[pulseaudio-discuss] [PATCH v2 2/3] loopback: Cork source-output if sink is suspended

2012-09-20 Thread Mikel Astiz
From: Frédéric Dalleau During initialization, the approach avoids having a needless short period of corked state in case the sink is suspended, by always creating the source-output corked and uncorking it immediately afterwards when the sink is not suspended. --- src/modules/module-loopback.c |

[pulseaudio-discuss] [PATCH v2 1/3] loopback: Cork sink-input if source is suspended

2012-09-20 Thread Mikel Astiz
From: Frédéric Dalleau During initialization, the approach avoids having a needless short period of corked state in case the source is suspended, by always creating the sink-input corked and uncorking it immediately afterwards when the source is not suspended. --- src/modules/module-loopback.c |

[pulseaudio-discuss] [PATCH v2 0/3] Suspending loopback

2012-09-20 Thread Mikel Astiz
From: Mikel Astiz v2 modifies previous patches as suggested by Tanu: - Sink-inputs and source-outputs are created corked, and immediately afterwards uncorked if audio not suspended. - Patch v2 3/3 stops the rate adjustment timer while the audio is suspended. From original cover-letter (from F

Re: [pulseaudio-discuss] device problem

2012-09-20 Thread Richard Bown
On Thu, 20 Sep 2012 11:45:10 +0300 Ștefan Săftescu wrote: > Hello, > > If I understand correctly, your four inputs and four outputs get > mapped to two stereo inputs and two stereo outputs. If that is the > case, you might want to look at module-remap-sink [1] four your > outputs. I'm not sure i

Re: [pulseaudio-discuss] device problem

2012-09-20 Thread Ștefan Săftescu
Hello, If I understand correctly, your four inputs and four outputs get mapped to two stereo inputs and two stereo outputs. If that is the case, you might want to look at module-remap-sink [1] four your outputs. I'm not sure if there is anything similar for sources/inputs, though, but you might be