On 2022-07-14 04:01 pm, Paul B Mahol wrote:
On Thu, Jul 14, 2022 at 12:21 PM Gyan Doshi wrote:
Pushed as 882aac99d2a7d15492ce1da9859676b0c04295b8
and cherry-picked to 5.1
Why?
The cherry-pick? Because 5.1 hasn't been tagged yet as already explained
in my last msg in v3 thread.
Regard
On Thu, Jul 14, 2022 at 12:21 PM Gyan Doshi wrote:
> Pushed as 882aac99d2a7d15492ce1da9859676b0c04295b8
> and cherry-picked to 5.1
>
Why?
>
> On 2022-07-14 01:46 pm, Gyan Doshi wrote:
> > This is a per-file input option that adjusts an input's timestamps
> > with reference to another input, so
Pushed as 882aac99d2a7d15492ce1da9859676b0c04295b8
and cherry-picked to 5.1
On 2022-07-14 01:46 pm, Gyan Doshi wrote:
This is a per-file input option that adjusts an input's timestamps
with reference to another input, so that emitted packet timestamps
account for the difference between the start
This is a per-file input option that adjusts an input's timestamps
with reference to another input, so that emitted packet timestamps
account for the difference between the start times of the two inputs.
Typical use case is to sync two or more live inputs such as from capture
devices. Both the tar
