Description
Description:
Both for offline and live processing, it would be beneficial to add a high-level API to adjust the processing behavior. For filtering, particularly the --df-beta should be exposed, but not in a way that would require the user to know its implementation details.
We should provide the user a simplistic "less-or-more?" setting, and handle its propagation from the frontend all the way to the MediaProcessor.
Use Case:
Primarily for live feeds, as it will provide an immediate improvement in processed media. It will also be useful for offline analysis, allowing users to tune the resulting media.
Proposed Solution:
Partially covered in the description. Most likely reuse the MediaHandler on the backend (pending an in-progress refactor), and introduce a dedicated class on the MediaProcessor side to provide an API for the backend.
Additional Context:
N/A