On 2019-10-22 17:14, Andrey Semashev wrote:
On 2019-10-22 17:09, James Almer wrote:
On 10/22/2019 11:01 AM, Andrey Semashev wrote:
On 2019-10-18 02:18, James Almer wrote:
Actually reorder the values.
Should effectively fix ticket #8300.
Signed-off-by: James Almer <jamr...@gmail.com>
---
Now unconditionally propagating the field, since checking its value is
not correct usage of the field.
James, do you still plan working on this patch?
Yes, but i have no way to test it. Can you confirm the current
implementation in the tree misbehaves, and that this approach corrects
it?
No, I don't have a test video file that would cause frame reordering. At
least I don't think any of my files cause it.
I tried my v3 patch with the files I have, it worked as intended.
Actually, no, one of the files causes a delay for one frame, so I can
test it. Your v2 and my v3 patches work (i.e. the decoded
reordered_opaque lags behind input pts for one frame).
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
