>> The problem is the latency on receiving BLE packets. The timestamp the
> device sends and the "receiver's clock" (ALSA Seq) will very quickly
> get out-of-sync, causing this timestamp to be invalid.
As the protocol requires sender and receiver to both maintain "clocks" which
are synced (no do
Hi Clemens and others,
Any thoughts on this? I would like to start working on it.
On 30/09/16 21:32, Felipe Ferreri Tonello wrote:
> Hi Clemens,
>
> On 30/09/16 19:46, Clemens Ladisch wrote:
>> Felipe Ferreri Tonello wrote:
>>> This event we are discussing is time based.
>>> The only difference
Hi Clemens,
On 30/09/16 19:46, Clemens Ladisch wrote:
> Felipe Ferreri Tonello wrote:
>> This event we are discussing is time based.
>> The only difference is that the event time is not its delivered time,
>> but some time in the past.
>>
>> I just want to make ALSA Sequencer support this idea, wh
Felipe Ferreri Tonello wrote:
> This event we are discussing is time based.
> The only difference is that the event time is not its delivered time,
> but some time in the past.
>
> I just want to make ALSA Sequencer support this idea, which is new and a
> requirement for MIDI over BLE to work prope
Hi Paul,
On 30/09/16 14:48, Paul Davis wrote:
>
>
> On Fri, Sep 30, 2016 at 4:35 AM, Felipe Ferreri Tonello
> mailto:e...@felipetonello.com>> wrote:
>
>
> >
> > The time of an event is the time at which it is actually delivered.
> > If you want to be compatible with most other appl
On Fri, Sep 30, 2016 at 4:35 AM, Felipe Ferreri Tonello <
e...@felipetonello.com> wrote:
>
> >
> > The time of an event is the time at which it is actually delivered.
> > If you want to be compatible with most other applications, you have
> > to deliver the events at the desired time.
>
> Ok. This
Hi Clemens,
On 20/09/16 18:11, Clemens Ladisch wrote:
> Felipe Ferreri Tonello wrote:
>> On 20/09/16 15:26, Clemens Ladisch wrote:
>>> 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 i
Felipe Ferreri Tonello wrote:
> On 20/09/16 15:26, Clemens Ladisch wrote:
>> 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
> imple
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.
>>
>> Appl
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 e
Hi Clemens,
On 19/09/16 13:27, Clemens Ladisch wrote:
> Felipe Ferreri Tonello wrote:
>> * We want to deliver these events *ASAP* to the application -
>> scheduling adds latency, a lot;
>> * Timestamps are in the past relative to the central.
>>
>> But I still need the timestamp information. Why
Felipe Ferreri Tonello wrote:
> * We want to deliver these events *ASAP* to the application -
> scheduling adds latency, a lot;
> * Timestamps are in the past relative to the central.
>
> But I still need the timestamp information. Why? The spec doesn't
> explain, but it makes sense to believe it
Hi Clemens,
On 17/09/16 08:42, Clemens Ladisch wrote:
> Felipe Ferreri Tonello wrote:
>> On 16/09/16 18:41, Clemens Ladisch wrote:
>>> Felipe Ferreri Tonello wrote:
I have a question. I would like to send sequencer events without
scheduling but with a timestamp information associated wit
Felipe Ferreri Tonello wrote:
> On 16/09/16 18:41, Clemens Ladisch wrote:
>> Felipe Ferreri Tonello wrote:
>>> I have a question. I would like to send sequencer events without
>>> scheduling but with a timestamp information associated with. Is that
>>> possible?
>>
>> You could set the timestamp fi
Hi Clemens,
On 16/09/16 18:41, Clemens Ladisch wrote:
> Felipe Ferreri Tonello wrote:
>> I have a question. I would like to send sequencer events without
>> scheduling but with a timestamp information associated with. Is that
>> possible?
>
> You could set the timestamp field of the event, but wh
Felipe Ferreri Tonello wrote:
> I have a question. I would like to send sequencer events without
> scheduling but with a timestamp information associated with. Is that
> possible?
You could set the timestamp field of the event, but why bother when
nobody is ever going to read it?
Regards,
Clemen
Hello all,
I have a question. I would like to send sequencer events without
scheduling but with a timestamp information associated with. Is that
possible?
Thanks,
Felipe
0x92698E6A.asc
Description: application/pgp-keys
___
Linux-audio-dev mailing list
17 matches
Mail list logo
