On Fri, Apr 19, 2019 at 08:09:28AM +, Andreas Håkon via ffmpeg-devel wrote:
>
> ‐‐‐ Original Message ‐‐‐
> On Thursday, 18 de April de 2019 22:13, Michael Niedermayer
> wrote:
>
> > On Thu, Apr 18, 2019 at 07:46:43AM +, Andreas Håkon via ffmpeg-devel
> > wrote:
> >
> > > Hi,
>
‐‐‐ Original Message ‐‐‐
On Thursday, 18 de April de 2019 22:13, Michael Niedermayer
wrote:
> On Thu, Apr 18, 2019 at 07:46:43AM +, Andreas Håkon via ffmpeg-devel
> wrote:
>
> > Hi,
> > This is the second part of my previous patch:
> > https://patchwork.ffmpeg.org/patch/12783/
> >
On Thu, Apr 18, 2019 at 07:46:43AM +, Andreas Håkon via ffmpeg-devel wrote:
> Hi,
>
> This is the second part of my previous patch:
> https://patchwork.ffmpeg.org/patch/12783/
>
> It improves the logs when the message "cur_dts is invalid" appears.
> If helps to identify which stream generates
Hi,
This is the second part of my previous patch:
https://patchwork.ffmpeg.org/patch/12783/
It improves the logs when the message "cur_dts is invalid" appears.
If helps to identify which stream generates the trouble,
and the status of the stream.
A lot of users suffers with the message, and the o
