In addition to pixel count we should also consider the varying computational demands of different codecs, i.e. H.264 and H.265, where H.265 decoding and encoding can be 2-5 times more computationally expensive than H.264. If we look at AWS as an example they charge 2x to transcode H.265 compared to H.264. Figuring out a method to charge for the compute demands of a job will also be useful for add-on features such as scene detection, watermarking, etc. Ivan Poleshchuk has proposed a formula to calculate the transcoding job cost in this post https://github.com/livepeer/go-livepeer/issues/2761#issuecomment-1440466702 AWS pricing https://aws.amazon.com/mediaconvert/pricing/
