autovmaf wants to change profile parameters through its interface. OSAAS api gets the profile from http. Make a decision and implement. #62
Description
OSAAS encore api profile parameter description
User can provide a url to a profiles file on instance creation. If no such url is provided a url to default profiles is used.
If this is the case, then the user is required to have the profile hosted on http? Right now the default profiles are on github. I assume similar hosting would be required if one was to use their own profile.yml. As autovmaf is designed today, the user expects to have the ability to affect the resolution and bitrate of the transcoding output through the autovmaf interface. How do we want to solve this?
Local profile.yml pushed somewhere where the OSAAS encore api can access it?
Deliverable
Should be able to start a job in exact same process flow as local and aws pipelines. This likely implies that we will need some way for the autovmaf job parameters to be pushed to the hosted encore profile. Current control flow is that a .yml profile is stored on github or other http host, thereby accessible by the encore OSAAS api?
https://svt.github.io/encore-doc/#profiles
As described by the SVT encore documentation
A Profile can be seen as a general abstraction of an FFmpeg configuration - example, bitrate to use, thumbnail generation, the codec to use.
A Profile specifies a big part of the configuration used by an Encore Job - metadata, FFmpeg configuration and specific codec configuration.
A Profile is specified in the yaml-format.