You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a reference software that is different for different scenarios. For example S3 uses HM16.22 whereas S2 uses HM16.23. The streams.csv is clear about this. We should add this.
The text was updated successfully, but these errors were encountered:
The scripts are not checking with the encoder version directly. The current behavior, for all encoders, is :
Both HM16.22 and HM16.23 result in the 'HM' encoder id being used. The HM encoder executable path are configured through environment path.
When building the docker image, the HM version can be specified at build time with the docker build --build-arg. In that case, it is recommended to tag the docker image with the version used.
for instance:
We have a reference software that is different for different scenarios. For example S3 uses HM16.22 whereas S2 uses HM16.23. The streams.csv is clear about this. We should add this.
The text was updated successfully, but these errors were encountered: