what is "auto_buffer" parameter in graph.configure()?

[caffeinism]

https://pyav.basswood-io.com/docs/stable/api/filter.html#av.filter.graph.Graph.configure

I'm curious about this, but I can't find any explanation, questions, or code related to it. Is there anyone who could explain this to me?

[abdullayevziyodulla]

In the current implementation, auto_buffer is accepted in the signature but is not used in the method body. Passing True or False therefore does not select different behavior there.

You can see this in Graph.configure: it checks whether the graph is already configured, calls FFmpeg's avfilter_graph_config, marks the graph configured, then registers filter contexts that FFmpeg inserted. It never branches on auto_buffer.

This is separate from force: force=True bypasses the "already configured" early return. It is also separate from FFmpeg automatically inserting conversion filters to satisfy the graph's format requirements.

So I would not interpret auto_buffer=True as automatically creating your input buffer/abuffer and output sink nodes, nor rely on False to disable automatic conversion. Explicitly construct and link the source, filters and sink that your graph needs. For an older installed release, inspect that release's source rather than assuming the unused current argument had identical historical behavior.