ping
On 10/04/2017 09:50 AM, Oleksandr Andrushchenko wrote:
gentle reminder
On 09/26/2017 02:35 PM, Oleksandr Andrushchenko wrote:
Clemens, Sakamoto-san,
could you please review the below if you by chance have a minute?
Thank you,
Oleksandr
On 09/19/2017 11:57 AM, Oleksandr Andrushchenko wr
gentle reminder
On 09/26/2017 02:35 PM, Oleksandr Andrushchenko wrote:
Clemens, Sakamoto-san,
could you please review the below if you by chance have a minute?
Thank you,
Oleksandr
On 09/19/2017 11:57 AM, Oleksandr Andrushchenko wrote:
Hi, all!
We did some work on implementing the idea with
Clemens, Sakamoto-san,
could you please review the below if you by chance have a minute?
Thank you,
Oleksandr
On 09/19/2017 11:57 AM, Oleksandr Andrushchenko wrote:
Hi, all!
We did some work on implementing the idea with
feedback events from the backend to the frontend.
Please see attached
Hi, all!
We did some work on implementing the idea with
feedback events from the backend to the frontend.
Please see attached the changes to the existing sndif protocol [1]:
1. Introduced a new event channel from back to front
2. New event with number of bytes played/captured (XENSND_EVT_CUR_
On Tue, Sep 5, 2017 at 10:24 AM, Clemens Ladisch wrote:
> Oleksandr Andrushchenko wrote:
We understand that emulated interrupt on the frontend side is completely
not
acceptable
>
> Allow me to expand on that: Proper synchronization requires that the
> exact position is communicate
Oleksandr Andrushchenko wrote:
>>> We understand that emulated interrupt on the frontend side is completely not
>>> acceptable
Allow me to expand on that: Proper synchronization requires that the
exact position is communicated, not estimated. Just because the nominal
rate of the stream is known