On 2021-05-20 19:38, Nicolas George wrote:
Michael Fabian 'Xaymar' Dirks (12021-05-20):
Unfortunately I was not able to get rid of the new cluster spam, so I
moved it down a few logging levels into "verbose".
So you silenced the warning, but did not fix the issue it was warning
about.
If you were a physician, you would just have prescribed morphine for a
broken leg: hide the pain, leave the fracture, likely to worsen.
Regards,
_______________________________________________
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".
The issue can't be fixed, as it is a problem with the Matroska specification
only allowing signed 16-bit integer offsets for the block timestamps. Your
analogy is not only wrong, but also misplaced here, if you want to voice your
distaste for the Matroska limitations, the IETF standardization process is the
go-to:
- https://github.com/ietf-wg-cellar/matroska-specification/issues/422
- https://github.com/ietf-wg-cellar/matroska-specification/pull/425
- https://github.com/ietf-wg-cellar/matroska-specification/pull/437
--
Sincerely | Mit freundlichen Grüßen
Michael Fabian 'Xaymar' Dirks
Software Designer & Engineer
_______________________________________________
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".
