Settings which are likely to vary from machine to machine ought to be increasingly available to the user to tune based on the impact the setting will have on the session and user interest. Low interest, static settings which may remain forever untouched belong in code. Medium interest settings which remain static throughout an established session might live in a text config file. Higher interest items get dynamic controls which update during a session and GUI widgets or CLI control messages. The settings of highest interest which are determined to work in certain cases may have additional layers of control in software to assist in the automation of optimization.
Settings which are likely to vary from machine to machine ought to be increasingly available to the user to tune based on the impact the setting will have on the session and user interest. Low interest, static settings which may remain forever untouched belong in code. Medium interest settings which remain static throughout an established session might live in a text config file. Higher interest items get dynamic controls which update during a session and GUI widgets or CLI control messages. The settings of highest interest which are determined to work in certain cases may have additional layers of control in software to assist in the automation of optimization.
This is a medium to high interest setting: https://github.com/jhgorse/onevideo/blob/master/onevideo/ov-local-peer-setup.c#L120 "These values give the lowest audio latency with the least chance of audio artefacting."