The ActiveEncode API currently uses hashes for input, output, and technical metadata which makes it hard to reason about what information an adapter should try to supply and what information a client can expect to consume. This will help on the FFmpeg adapter.
The ActiveEncode API currently uses hashes for input, output, and technical metadata which makes it hard to reason about what information an adapter should try to supply and what information a client can expect to consume. This will help on the FFmpeg adapter.