<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">ÑÑ€, 23 окт. 2024 г., 18:23 Phyllis Smith <<a href="mailto:phylsmith2017@gmail.com">phylsmith2017@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><span class="gmail_default" style="font-size:small"></span></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">may be we better to skip 7.1 completely?</blockquote></div><div class="gmail_default" style="font-size:small">This is disturbing. Usually if something is not working in one version, it is still carried to the next.<br></div></div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">I crossposted my frustration with current situation (when ffmpeg team one-sidely breaks not just us but everyone downstream) earlier this day.</div><div dir="auto"><br></div><div dir="auto">Of course team of professional developers will change their part (breaking things) much faster and effortlessly than I ever can hope to repair them.</div><div dir="auto"><br></div><div dir="auto">Because ffmpeg apparently set to 2-3 release per year, with unknown amount of breakage each time ...I am not really eager to fix something twice. yuv range fix still not agreed upon, as far as I can, may be it will end up as rework and not just fix. I amnot sure if 7.1 makes much sense for us in itself?</div><div dir="auto"><br></div><div dir="auto">Of course breakage that come in 7.2/8.0 might be so big that I'll prefer to fix 7.1 instead.</div><div dir="auto"><br></div><div dir="auto">My main worry that even outside ff-scale filter and profile vs vprofile change something broke with some vaapi/qsv profiles, and it might be harder to track down.</div><div dir="auto"><br></div><div dir="auto">Right now 7.1 *builds* fine if you add renamed patch10 at least, but on runtime ..... we have all those errors Terje reported.</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small"></div></div><br><div class="gmail_quote"><div style="font-size:small" class="gmail_default">...</div><div style="font-size:small" class="gmail_default">Snip, Snip, Snip!<br></div><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
Doesn't this correspond to what we previously also discussed for
ffmpeg 7.0.2?<br></div></blockquote><div><br></div><div>ffmpeg as cli does its own option processing, as far as I understand.</div><div><br></div><div>Using av_dict_* functions in c++ code was working with libav*/ffmpeg libs up to 7.0</div><div>but evidently not after..</div><div><br></div><div>I'll look into what ffmpeg cli does now, but if more changes in pipeline may be we better to skip 7.1 completely?</div><div><br></div></div></div></blockquote></div></div>
</blockquote></div></div></div>