Hi Tanu,
Here a new picture:
DIAGRAM FOR HARDWARE SINK 1 BEFORE STARTING THE MOVE (OR BEFORE STARTING A
REWIND)
+-+-
| client stream memblockq
|
On 16.06.19 12:28, Georg Chini wrote:
I sent the patch that introduces the history queue to the list.
Please take a look. I think it is rather simple.
Hi Tanu,
I tried your proposal to synchronize read and write index of the
history queue immediately after the push and then to add the
render
I sent the patch that introduces the history queue to the list.
Please take a look. I think it is rather simple.
___
pulseaudio-discuss mailing list
pulseaudio-discuss@lists.freedesktop.org
On 16.06.19 10:39, Tanu Kaskinen wrote:
On Sat, 2019-06-15 at 11:31 +0200, Georg Chini wrote:
On 15.06.19 10:01, Tanu Kaskinen wrote:
On Tue, 2019-06-11 at 22:08 +0200, Georg Chini wrote:
Hi Tanu,
the first diagram should look like this:
DIAGRAM FOR HARDWARE SINK 1 BEFORE STARTING THE MOVE
On Sat, 2019-06-15 at 11:31 +0200, Georg Chini wrote:
> On 15.06.19 10:01, Tanu Kaskinen wrote:
> > On Tue, 2019-06-11 at 22:08 +0200, Georg Chini wrote:
> > > Hi Tanu,
> > >
> > > the first diagram should look like this:
> > >
> > > DIAGRAM FOR HARDWARE SINK 1 BEFORE STARTING THE MOVE
> > >
>
On 15.06.19 10:01, Tanu Kaskinen wrote:
On Tue, 2019-06-11 at 22:08 +0200, Georg Chini wrote:
Hi Tanu,
the first diagram should look like this:
DIAGRAM FOR HARDWARE SINK 1 BEFORE STARTING THE MOVE
+-+-
On Tue, 2019-06-11 at 22:08 +0200, Georg Chini wrote:
> Hi Tanu,
>
> the first diagram should look like this:
>
> DIAGRAM FOR HARDWARE SINK 1 BEFORE STARTING THE MOVE
>
> +-+-
> > client stream
Hi Tanu,
the first diagram should look like this:
DIAGRAM FOR HARDWARE SINK 1 BEFORE STARTING THE MOVE
+-+-
| client stream memblockq
|
