Newer versions of the library added a new binary output format, and prefer
using it by default.
Those binary files seem to cause issues for a lot of users, where ffmpeg fails
to (sometimes?) read
back the trf file it has just written itself.
My guess is that this might be because of the fopen-mode of "w" below, where
"wb" would be needed.
But since we can't really know what format the library is about to write, it's
better to force
it into ASCII mode when possible.
---
libavfilter/vf_vidstabdetect.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/libavfilter/vf_vidstabdetect.c b/libavfilter/vf_vidstabdetect.c
index b27b1e40a6..7170f56f81 100644
--- a/libavfilter/vf_vidstabdetect.c
+++ b/libavfilter/vf_vidstabdetect.c
@@ -110,6 +110,10 @@ static int config_input(AVFilterLink *inlink)
return AVERROR(EINVAL);
}
+#ifdef ASCII_SERIALIZATION_MODE
+ md->serializationMode = ASCII_SERIALIZATION_MODE;
+#endif
+
// set values that are not initialized by the options
s->conf.algo = 1;
s->conf.modName = "vidstabdetect";
--
2.34.1
_______________________________________________
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".
