On 16.04.2016 05:08, Raymond Yau wrote:
>>
>>
>> >
>> >> do loopback module assume sink is not running when it start
source capture?
>> >>
>> > Sink and source are started independently. Source data is
discarded until the sink-input has
>> > called pop() the first time.
>>
>> But you cannot
>>
>>
>> >
>> >> do loopback module assume sink is not running when it start source
capture?
>> >>
>> > Sink and source are started independently. Source data is discarded
until the sink-input has
>> > called pop() the first time.
>>
>> But you cannot skip more than 9ms source data since you need 1
Hi,
On Fri, Apr 15, 2016 at 06:31:00PM +0530, Arun Raghavan wrote:
> Hi folks,
> Tanu rightly pointed out that we're almost upon the freeze date for
> 9.0, which is 22nd Apr.
>
> I know we've got a large patch backlog, so if your patches didn't make
> it, please be patient and we'll get to them.
Now that all layers in the stack support memfd blocks, add memfd
support for the daemon's global core mempool. Also introduce
"enable-memfd=" daemon argument and configuration option.
For now, memfd support is an opt-in feature to be activated only
when daemon's enable-memfd= is set to yes.
Signe
Now that all layers in the stack support memfd blocks, add memfd
pools support for client context and audio playback data.
Use such memfd pools by default only if the server signals memfd
support in its connection negotiations.
Also add ability for clients to force-disable memfd transport
through
Hi!
Now that most of the memfd series is merged except the last two
patches, this is a submission of the last two commits modified to
make memfds an opt-in feature instead of being enabled by default.
To test memfds support, just add enable-memfd=yes to the daemon's
configuration file ~/.config/p
I'd like to see this merged before 9.0.
Sincerely, Nazar Mokrynskyi
github.com/nazar-pc
Skype: nazar-pc
Diaspora: naza...@diaspora.mokrynskyi.com
Tox:
A9D95C9AA5F7A3ED75D83D0292E22ACE84BA40E912185939414475AF28FD2B2A5C8EF5261249
On 24.03.16 15:59, Nazar Mokrynskyi wrote:
`Mic` is now detected a
2016-04-15 21:36 GMT+05:00 Arun Raghavan :
>
> On 15-Apr-2016 10:04 PM, "Alexander E. Patrakov" wrote:
>>
>> 2016-04-15 18:01 GMT+05:00 Arun Raghavan :
>> > Hi folks,
>> > Tanu rightly pointed out that we're almost upon the freeze date for
>> > 9.0, which is 22nd Apr.
>> >
>> > I know we've got a
On 15-Apr-2016 10:04 PM, "Alexander E. Patrakov" wrote:
>
> 2016-04-15 18:01 GMT+05:00 Arun Raghavan :
> > Hi folks,
> > Tanu rightly pointed out that we're almost upon the freeze date for
> > 9.0, which is 22nd Apr.
> >
> > I know we've got a large patch backlog, so if your patches didn't make
>
2016-04-15 18:01 GMT+05:00 Arun Raghavan :
> Hi folks,
> Tanu rightly pointed out that we're almost upon the freeze date for
> 9.0, which is 22nd Apr.
>
> I know we've got a large patch backlog, so if your patches didn't make
> it, please be patient and we'll get to them.
>
> If you think something
Hi folks,
Tanu rightly pointed out that we're almost upon the freeze date for
9.0, which is 22nd Apr.
I know we've got a large patch backlog, so if your patches didn't make
it, please be patient and we'll get to them.
If you think something is crucial for this release (critical bug fix,
regressio
11 matches
Mail list logo
