Hi Clemens,

On 20/09/16 15:26, Clemens Ladisch wrote:
> Felipe Ferreri Tonello wrote:
>> On 19/09/16 13:27, Clemens Ladisch wrote:
>>> And applications that care about the time of received events
>>> tell the sequencer to overwrite the timestamp with the actual delivery
>>> time anyway.
>>
>> Applications only need to care about the timestamp field for that event,
>> it doesn't matter who set it (the ALSA Seq scheduler or other client, in
>> this case the BLE driver).
> 
> When the receiving port has timestamping mode enabled, the sequencer
> will overwrite any timestamp that the event had.
> 
> When the receiving port does not have timestamping mode enabled, the
> application will not read the timestamp, because there is no guarantee
> that it is set.
> 
> In other words: any application that does care about timestamps will
> never see your timestamps.

Yes. And that's why my first question.

How can we implement this timestamp feature in ALSA with the current
implementation? If it is not possible, how feasible is for us to add
this feature? Any suggestions?

-- 
Felipe

Attachment: 0x92698E6A.asc
Description: application/pgp-keys

_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev

Reply via email to