@torrent-tv/proxy 2.31.0 → 2.33.0

package/CHANGELOG.md

@@ -1,3 +1,13 @@
+## 2.33.0
+
+- **New**: A quality step is judged on the machine it will actually run on. The encoder benchmark measures a QUIET host — one ffmpeg and nothing else — while the addon host was measured 99 % busy, and a step predicted at 1.83x ran at 1.01-1.12x (2026-08-17). The offer now multiplies each prediction by the share of the machine that is free, taken from the same `host-load` reading that is already printed every five seconds. What is subtracted is ONLY the work nobody has been charged for — the kernel, the container, whatever else the owner runs — because our own encoders are already priced by the concurrency arithmetic and the proxy's own work per megabyte moved. Charging those here as well is what shipped in 2.21.0 and emptied the quality menu down to a single copied height. On the field reading the correction is about 0.77, and the "not offering" line now says what the machine had to spare when it decided.
+- **New**: Each step reports what its prediction was worth. When a step runs with the machine to itself, the log states the speed it was predicted at, the speed it measured, and the ratio — so the error that REMAINS after the availability correction is a number in the field rather than an argument. It is written when it moves by more than a tenth, so a steady step says it once. On the field case that correction takes 1.83x to 1.41x against 1.01-1.12x measured: part of the gap, not all of it, and this line is how the rest gets found.
+
+## 2.32.0
+
+- **New**: The decode cost is fitted from a clip set that can be checked, and a term the measurements do not determine is refused instead of published as a zero. The set that shipped until now was three clips for three unknowns — an EXACT system, with two of the clips at the same pixel rate — and such a system cannot fail visibly: it returns whatever satisfies its equations. On 2026-08-17 it returned `0.007542 × Mpx/s + 0.000000 × Mbit/s + 0.0000 s/s`, so a film's own bitrate never entered its price, and the prediction built on it was 1.8-2.2x optimistic against the same file measured while playing. The new set is six clips — three sizes × two bitrates, the axes varied INDEPENDENTLY — cut from the same Netflix Open Content "Meridian" footage (CC BY 4.0, `assets/calibration/NOTICE.md`), 7.7 MB against 8.8 MB before. Three spare measurements give the fit a residual, and with it two questions it could not ask before: whether a term's whole effect across the measured range exceeds the scatter, and whether the coefficient exceeds its own standard error. A term that fails either is dropped, the rest are fitted again, and the log names it — a zero now means "not measured" only when it says so. A NEGATIVE coefficient is dropped too rather than clamped to zero: more pixels cannot cost less work, so a negative fit is noise beating an effect, not a discovery about the host. Measured on the developer's machine, the new set determines all three terms (`0.000520 × Mpx/s + 0.002086 × Mbit/s + 0.0033 s/s`, typical disagreement 0.0012 s/s), and the bitrate term it recovers matches the difference between the two 1080p clips to 15 %. The arithmetic is a pure module with the degenerate case as a test (`services/decode-cost-fit.js`).
+- **Chore**: What the calibration costs at startup, measured rather than assumed: six clips take 14.8 s on the developer's Windows box, of which the decoding is about 50 ms per clip — an empty ffmpeg spawn there costs 774 ms, and opening each file most of the rest. Shortening the clips would therefore save nothing; the cost is spawning ffmpeg once per clip, and it is paid before any viewer exists.
+
 ## 2.31.0
 
 - **Chore**: The encoder run's two status strings are gone; both are now outputs of the state table shipped in 2.23.0. `session.progress.state` was maintained by hand at seven sites and `session.state` at nine, and neither could answer on its own — the warm-up test had to read both under an `||`, because one said "starting" from the first spawn until something overwrote it while the other said it again on its own schedule. What the browser is told is computed where it is sent (`wireState(runState)`), and `session.state` is reduced to the session's own lifetime: it exists, or it has been disposed. That deletes the line in the spawn path that read `state === "disposed" ? "disposed" : "starting"` — two lifetimes in one variable, which is what it was there to paper over. Verified before the change that nothing in the browser reads the wire string, so the value set is unchanged and unobserved either way; the four values it can take are the same four as before.

package/assets/calibration/NOTICE.md

@@ -1,30 +1,63 @@
 # Calibration clips — attribution
 
-The three clips in this folder are excerpts from **"Meridian"**, part of
+The clips in this folder are excerpts from **"Meridian"**, part of
 [Netflix Open Content](https://opencontent.netflix.com/), licensed under the
 **Creative Commons Attribution 4.0 International (CC BY 4.0)** licence:
 <https://creativecommons.org/licenses/by/4.0/>.
 
 They were cut from `Meridian/Meridian_UHD4k5994_HDR_P3PQ.mp4` and re-encoded to
-H.264 High, 24 fps, 5.04 s (121 frames), no audio:
+H.264 High, 24 fps, 2 s each, no audio:
 
 | file | resolution | bitrate |
 |---|---|---|
-| `cal-1080-hi.mp4` | 1920×1080 | 11.38 Mbit/s |
-| `cal-1080-lo.mp4` | 1920×1080 | 0.97 Mbit/s |
-| `cal-720.mp4` | 1280×720 | 2.25 Mbit/s |
+| `cal-h264-1080-hi.mp4` | 1920×1080 | 9.36 Mbit/s |
+| `cal-h264-1080-lo.mp4` | 1920×1080 | 1.00 Mbit/s |
+| `cal-h264-720-hi.mp4` | 1280×720 | 9.95 Mbit/s |
+| `cal-h264-720-lo.mp4` | 1280×720 | 1.04 Mbit/s |
+| `cal-h264-480-hi.mp4` | 854×480 | 9.48 Mbit/s |
+| `cal-h264-480-lo.mp4` | 854×480 | 1.25 Mbit/s |
 
-## Why these three, and why real footage
+## Why six, and why this grid
 
-`services/hwaccel.js` decodes them at startup and solves the host's decode cost,
-`a × Mpixel/s + b × Mbit/s + c`, from the three measurements. The first two
-clips share a pixel count and differ 11.7× in bitrate; the third changes the
-pixel count. Three points, three unknowns.
+`services/hwaccel.js` decodes them at startup and fits the host's decode cost,
+`a × Mpixel/s + b × Mbit/s + c`, from the measurements
+(`services/decode-cost-fit.js`).
 
-Real, grainy live action rather than a generated pattern: measured 2026-08-14 on
-the addon host, this material decodes 11 % away from the film being served,
-where a generated `testsrc2` clip is 158 % away.
+The set before this one was three clips for three unknowns — an EXACT system,
+with two of the clips sharing a pixel count. Such a system cannot fail visibly:
+it returns whatever satisfies its three equations, and on 2026-08-17 it returned
+`0.007542 × Mpx/s + 0.000000 × Mbit/s + 0.0000 s/s` — the bitrate term and the
+constant exactly zero, so a film's own bitrate never entered its price, and the
+prediction built on it was 1.8-2.2x optimistic against the same file measured
+while playing.
 
-Replacing a clip is allowed — the benchmark reads each clip's dimensions, frame
-rate and bitrate from ffmpeg's own output rather than from this table — but the
-three must keep spanning the two axes, or the fit has nothing to separate.
+Six clips are three sizes × two bitrates, with the two axes varied
+**independently**. That gives three spare measurements, so the fit has a
+residual — something to notice a degeneracy WITH — and lets a term be refused
+when the data does not determine it, instead of being published as a zero that
+looks measured.
+
+A 480p clip at 9.5 Mbit/s is not content anyone ships; that is the point. The
+bitrate has to vary at every size, or it cannot be told apart from the size.
+
+## Why real footage
+
+Grainy live action rather than a generated pattern: measured 2026-08-14 on the
+addon host, this material decodes 11 % away from the film being served, where a
+generated `testsrc2` clip is 158 % away. It also matches most of what the
+product actually plays — a survey of 133 releases (2026-07-10) found ~67 %
+H.264 live action, the rest HEVC, XviD and animation.
+
+## Replacing or extending the set
+
+Allowed: the benchmark reads each clip's dimensions, frame rate and bitrate from
+ffmpeg's own output rather than from this table. Two rules hold, though:
+
+- **more measurements than terms**, or there is no residual and no way to see a
+  degenerate fit;
+- **the axes stay independent** — every size at both bitrates. Dropping one cell
+  reintroduces the collinearity that produced the zeros above.
+
+Codecs other than H.264 (HEVC, AV1, 10-bit) decode dearer per pixel, and the
+model fitted here does not describe them. Covering them means a set per codec
+family and constants chosen by the source's own codec — roadmap item 3(b).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@torrent-tv/proxy",
-  "version": "2.31.0",
+  "version": "2.33.0",
   "description": "Torrent proxy client that exposes webseed-like HTTP stream endpoint.",
   "license": "GPL-3.0-or-later",
   "publishConfig": {

package/services/available-share.js

@@ -0,0 +1,89 @@
+/**
+ * @file How much of the machine a new encoder can actually have.
+ *
+ * The encoder benchmark measures a QUIET host: one ffmpeg, nothing else. A real
+ * encode runs on a machine that is also downloading, hashing and serving, and
+ * on the addon host that machine was measured 99 % busy — `ffmpeg=52-60%
+ * proxy=17-24% system=99%` — while a step predicted at 1.83x ran at 1.01-1.12x
+ * (2026-08-17).
+ *
+ * What this corrects is ONLY the part nobody has been charged for. That
+ * distinction is the whole of the file, because the alternative has already
+ * shipped once and broke the product: in 2.21.0 the budget ADDED what else was
+ * running while the per-file costs were being LEARNED from runs that already
+ * contained that other work, so every cost was counted twice, every re-encoded
+ * step was refused, and the quality menu emptied itself down to the one copied
+ * height (fixed in 2.21.1).
+ *
+ * So: our own encoders are priced by the concurrency arithmetic, and the
+ * proxy's own work — the torrent, the hashing, the delivery — is priced per
+ * megabyte moved. Both are already in the budget. What is NOT in it is
+ * everything else the machine does: the kernel, the container runtime, whatever
+ * else the owner runs on their box. That is what is subtracted here, and
+ * nothing more.
+ */
+
+/**
+ * The share of the machine available to a new encoder.
+ *
+ * @param {object} reading - Fractions of the WHOLE machine (all cores), as
+ *   `shareOfMachine` reports them.
+ * @param {number | null} reading.systemBusy - Everything the machine is doing.
+ * @param {number | null} reading.encoderShare - Our own ffmpeg processes.
+ * @param {number | null} reading.proxyShare - The proxy process itself.
+ * @returns {{ share: number, unattributed: number, known: boolean }}
+ *   `known` is false when the host does not report its own load — then the
+ *   share is 1 and the caller must say it is uncorrected rather than pretend.
+ */
+export function availableShareFrom(reading = {}) {
+  const systemBusy = finite(reading.systemBusy);
+  if (systemBusy === null) {
+    // No reading at all: not every host has /proc. An uncorrected prediction is
+    // the honest answer, and the caller says so.
+    return { share: 1, unattributed: 0, known: false };
+  }
+  const ours = (finite(reading.encoderShare) ?? 0) + (finite(reading.proxyShare) ?? 0);
+  // Rounding, and the two readings being taken microseconds apart, can put our
+  // own share fractionally above the system total. Below zero is not a
+  // measurement of anything.
+  const unattributed = clamp(systemBusy - ours, 0, 1);
+  return { share: clamp(1 - unattributed, 0, 1), unattributed, known: true };
+}
+
+/**
+ * Apply the correction to a predicted speed.
+ *
+ * A speed is work per unit time, so a machine that can give a new encoder only
+ * `share` of itself produces `share ×` the speed the benchmark measured alone.
+ *
+ * @param {number} predictedSpeed - From the quiet-host benchmark.
+ * @param {{ share: number, known: boolean }} availability
+ * @returns {number}
+ */
+export function correctForAvailability(predictedSpeed, availability) {
+  if (!Number.isFinite(predictedSpeed) || predictedSpeed <= 0) {
+    return predictedSpeed;
+  }
+  if (!availability?.known) {
+    return predictedSpeed;
+  }
+  return predictedSpeed * availability.share;
+}
+
+/**
+ * @param {unknown} value
+ * @returns {number | null}
+ */
+function finite(value) {
+  return Number.isFinite(value) ? Number(value) : null;
+}
+
+/**
+ * @param {number} value
+ * @param {number} low
+ * @param {number} high
+ * @returns {number}
+ */
+function clamp(value, low, high) {
+  return Math.min(high, Math.max(low, value));
+}

package/services/decode-cost-fit.js

@@ -0,0 +1,331 @@
+/**
+ * @file Fit the cost of decoding from measured clips — and say which terms the
+ * measurements actually determine.
+ *
+ * The model is `cost = pixelTerm × Mpixel/s + bitrateTerm × Mbit/s +
+ * constantTerm`, in seconds of work per second of content.
+ *
+ * What went wrong with the fit this replaces, measured 2026-08-17: three clips
+ * for three unknowns is an EXACT system, and two of those clips shared a pixel
+ * rate and differed only in bitrate. A system that near-singular does not fail
+ * loudly — it returns whatever satisfies the three equations, and on that boot
+ * it returned `0.007542 × Mpx/s + 0.000000 × Mbit/s + 0.0000 s/s`. The bitrate
+ * term and the constant were zero, so a film's own bitrate never entered its
+ * price, and the whole prediction was 1.8-2.2x optimistic against what the same
+ * file measured while playing.
+ *
+ * Two things are different here, and both are about honesty rather than
+ * accuracy:
+ *
+ *   - the system is OVER-determined (six clips, three unknowns) and solved by
+ *     least squares, so no single noisy reading decides a term;
+ *   - a term is published only if the measurements determine it. The test is
+ *     the coefficient against its OWN standard error: a term smaller than the
+ *     uncertainty in it has not been measured, and stating it as a number —
+ *     zero or otherwise — claims knowledge that is not there. It is dropped,
+ *     the remaining terms are fitted again, and the caller is told which shape
+ *     survived.
+ *
+ * There is no threshold to tune in that rule and no coefficient anywhere in
+ * this file. "Smaller than its own uncertainty" is a statement about the data,
+ * not a setting.
+ */
+
+/**
+ * One measured clip.
+ *
+ * @typedef {object} DecodeSample
+ * @property {number} megapixelsPerSecond - Width × height × frame rate ÷ 1e6.
+ * @property {number} megabitsPerSecond - The clip's own measured bitrate.
+ * @property {number} costSecondsPerSecond - Seconds of work per second of
+ *   content, from ffmpeg's own progress.
+ */
+
+/**
+ * The fitted model, with the shape the data supported.
+ *
+ * @typedef {object} DecodeCostModel
+ * @property {number} pixelTerm
+ * @property {number} bitrateTerm
+ * @property {number} constantTerm
+ * @property {string} shape - Which terms were determined.
+ * @property {string[]} dropped - Terms the measurements could not determine.
+ * @property {number} samples
+ * @property {number} residualRms - Typical disagreement between the fit and a
+ *   measurement, in the same units as the cost.
+ */
+
+/** Every term the model can carry, in column order. */
+const TERMS = ["pixels", "bitrate", "constant"];
+
+/**
+ * Fit the model, dropping any term the measurements do not determine.
+ *
+ * @param {DecodeSample[]} samples
+ * @returns {DecodeCostModel | null} Null when nothing at all can be said: fewer
+ *   measurements than terms, or no measurable dependence on the source.
+ */
+export function fitDecodeCost(samples) {
+  const usable = (Array.isArray(samples) ? samples : []).filter(
+    (sample) =>
+      Number.isFinite(sample?.megapixelsPerSecond) &&
+      sample.megapixelsPerSecond > 0 &&
+      Number.isFinite(sample?.megabitsPerSecond) &&
+      sample.megabitsPerSecond >= 0 &&
+      Number.isFinite(sample?.costSecondsPerSecond) &&
+      sample.costSecondsPerSecond > 0
+  );
+  // Fitting three terms to three points is what produced the degenerate answer
+  // this file exists to prevent: it has no residual and therefore no way to
+  // notice that two of the points said the same thing.
+  if (usable.length < TERMS.length + 1) {
+    return null;
+  }
+
+  let columns = [...TERMS];
+  let dropped = [];
+  for (let attempt = 0; attempt < TERMS.length; attempt += 1) {
+    const fit = leastSquares(usable, columns);
+    if (!fit) {
+      return null;
+    }
+    // Which terms the data did not determine: a coefficient no larger than the
+    // uncertainty in it. Only one is dropped per pass — removing a column
+    // changes the uncertainty in the others, so the question has to be asked
+    // again of the smaller model.
+    const undetermined = columns
+      .map((name, index) => ({
+        name,
+        coefficient: fit.coefficients[index],
+        ratio: determination(usable, columns, name, fit.coefficients[index], fit.standardErrors[index], fit.residualRms)
+      }))
+      // The pixel term is the one relationship every measurement agrees on, and
+      // a model without it says nothing at all. If IT is undetermined the
+      // answer is no model, which the caller handles by pricing the encoder
+      // alone and refusing nothing.
+      // A NEGATIVE coefficient is undetermined whatever its ratio says. Every
+      // term here is physically non-negative — more pixels cannot cost less
+      // work, and neither can more bits — so a negative fit is noise winning
+      // over an effect, not a discovery about the host. Clamping it to zero
+      // instead, which the first version of this file did, publishes a zero
+      // that looks measured: exactly the dishonesty the module exists to
+      // remove.
+      .filter((term) => term.ratio < 1 || term.coefficient < 0)
+      .sort((left, right) => {
+        const negative = (term) => (term.coefficient < 0 ? 0 : 1);
+        return negative(left) - negative(right) || left.ratio - right.ratio;
+      });
+
+    if (undetermined.length === 0) {
+      return published(columns, fit, dropped, usable.length);
+    }
+    const weakest = undetermined[0].name;
+    if (weakest === "pixels") {
+      return null;
+    }
+    columns = columns.filter((name) => name !== weakest);
+    dropped = [...dropped, weakest];
+    if (columns.length === 0) {
+      return null;
+    }
+  }
+  return null;
+}
+
+
+/**
+ * How well one term is determined, as a ratio against 1.
+ *
+ * Two ways a term can fail to be measured, and both have to be asked, because
+ * each is blind where the other sees:
+ *
+ *   - **against the noise.** The term's effect across the range the clips
+ *     actually cover — its coefficient times the spread of its own column — has
+ *     to be larger than the typical disagreement between the fit and the
+ *     measurements. A term whose whole contribution is smaller than the scatter
+ *     was not measured; it was fitted to the scatter.
+ *   - **against the arithmetic.** When a fit happens to be exact the scatter is
+ *     zero, every standard error vanishes, and a coefficient of 7e-18 — which
+ *     is how double-precision writes "nothing" — passes any test framed as a
+ *     ratio. So the effect must also be larger than what the arithmetic itself
+ *     can represent at this scale. That floor is a property of the numbers, not
+ *     a setting: it moves with the size of the measurements.
+ *
+ * @param {DecodeSample[]} samples
+ * @param {string[]} columns
+ * @param {string} name
+ * @param {number} coefficient
+ * @param {number} standardError
+ * @param {number} residualRms
+ * @returns {number} Below 1 means the measurements do not determine this term.
+ */
+function determination(samples, columns, name, coefficient, standardError, residualRms) {
+  const values = samples.map((sample) => {
+    if (name === "pixels") {
+      return sample.megapixelsPerSecond;
+    }
+    if (name === "bitrate") {
+      return sample.megabitsPerSecond;
+    }
+    return 1;
+  });
+  const spread = name === "constant" ? 1 : Math.max(...values) - Math.min(...values);
+  const effect = Math.abs(coefficient) * spread;
+  const meanCost = samples.reduce((sum, sample) => sum + sample.costSecondsPerSecond, 0) / samples.length;
+  const arithmeticFloor = Math.abs(meanCost) * Number.EPSILON * samples.length * columns.length;
+  const noiseFloor = Math.max(residualRms, arithmeticFloor);
+  const againstNoise = noiseFloor > 0 ? effect / noiseFloor : Number.POSITIVE_INFINITY;
+  const againstError = standardError > 0 ? Math.abs(coefficient) / standardError : Number.POSITIVE_INFINITY;
+  return Math.min(againstNoise, againstError);
+}
+
+/**
+ * Assemble the answer, with absent terms as zero — and `dropped` saying that
+ * the zero means "not measured" rather than "measured to be nothing".
+ *
+ * @param {string[]} columns
+ * @param {{ coefficients: number[], residualRms: number }} fit
+ * @param {string[]} dropped
+ * @param {number} samples
+ * @returns {DecodeCostModel | null}
+ */
+function published(columns, fit, dropped, samples) {
+  const value = (name) => {
+    const index = columns.indexOf(name);
+    return index < 0 ? 0 : fit.coefficients[index];
+  };
+  const pixelTerm = value("pixels");
+  // A negative price for pixels is not a host being unusual — it is noise
+  // larger than the effect, and carrying it would price a bigger picture as
+  // cheaper than a smaller one.
+  if (!(pixelTerm > 0)) {
+    return null;
+  }
+  const constantTerm = value("constant");
+  return {
+    pixelTerm,
+    bitrateTerm: Math.max(0, value("bitrate")),
+    // A negative constant would make a small enough source free, which no
+    // measurement here supports: it is the fitted line crossing below zero
+    // outside the range that was measured.
+    constantTerm: Math.max(0, constantTerm),
+    shape: columns.join("+"),
+    dropped,
+    samples,
+    residualRms: fit.residualRms
+  };
+}
+
+/**
+ * Least squares over the named columns, with the standard error of each
+ * coefficient.
+ *
+ * Solved through the normal equations. The matrix is at most 3×3 and the
+ * columns are of similar magnitude once a clip set varies them deliberately,
+ * which is exactly what the set is designed for.
+ *
+ * @param {DecodeSample[]} samples
+ * @param {string[]} columns
+ * @returns {{ coefficients: number[], standardErrors: number[], residualRms: number } | null}
+ */
+function leastSquares(samples, columns) {
+  const rowOf = (sample) =>
+    columns.map((name) => {
+      if (name === "pixels") {
+        return sample.megapixelsPerSecond;
+      }
+      if (name === "bitrate") {
+        return sample.megabitsPerSecond;
+      }
+      return 1;
+    });
+  const width = columns.length;
+  const normal = Array.from({ length: width }, () => new Array(width).fill(0));
+  const right = new Array(width).fill(0);
+  for (const sample of samples) {
+    const row = rowOf(sample);
+    for (let i = 0; i < width; i += 1) {
+      right[i] += row[i] * sample.costSecondsPerSecond;
+      for (let j = 0; j < width; j += 1) {
+        normal[i][j] += row[i] * row[j];
+      }
+    }
+  }
+  const inverse = invert(normal);
+  if (!inverse) {
+    return null;
+  }
+  const coefficients = inverse.map((row) => row.reduce((sum, value, index) => sum + value * right[index], 0));
+
+  let residualSquares = 0;
+  for (const sample of samples) {
+    const row = rowOf(sample);
+    const predicted = row.reduce((sum, value, index) => sum + value * coefficients[index], 0);
+    residualSquares += (sample.costSecondsPerSecond - predicted) ** 2;
+  }
+  const degreesOfFreedom = samples.length - width;
+  const variance = degreesOfFreedom > 0 ? residualSquares / degreesOfFreedom : 0;
+  const standardErrors = inverse.map((row, index) => Math.sqrt(Math.max(0, variance * row[index])));
+  return {
+    coefficients,
+    standardErrors,
+    residualRms: Math.sqrt(residualSquares / samples.length)
+  };
+}
+
+/**
+ * Invert a small symmetric matrix by Gauss-Jordan, or null when it is singular.
+ *
+ * @param {number[][]} matrix
+ * @returns {number[][] | null}
+ */
+function invert(matrix) {
+  const size = matrix.length;
+  const work = matrix.map((row, index) => [
+    ...row,
+    ...Array.from({ length: size }, (_unused, column) => (column === index ? 1 : 0))
+  ]);
+  for (let column = 0; column < size; column += 1) {
+    let pivot = column;
+    for (let row = column + 1; row < size; row += 1) {
+      if (Math.abs(work[row][column]) > Math.abs(work[pivot][column])) {
+        pivot = row;
+      }
+    }
+    // Singular to the precision of the arithmetic: the columns are not
+    // independent, which is a statement about the clip set, not about the host.
+    if (Math.abs(work[pivot][column]) < 1e-12) {
+      return null;
+    }
+    [work[column], work[pivot]] = [work[pivot], work[column]];
+    const scale = work[column][column];
+    for (let k = 0; k < 2 * size; k += 1) {
+      work[column][k] /= scale;
+    }
+    for (let row = 0; row < size; row += 1) {
+      if (row === column) {
+        continue;
+      }
+      const factor = work[row][column];
+      for (let k = 0; k < 2 * size; k += 1) {
+        work[row][k] -= factor * work[column][k];
+      }
+    }
+  }
+  return work.map((row) => row.slice(size));
+}
+
+/**
+ * What a model prices one source at.
+ *
+ * @param {DecodeCostModel} model
+ * @param {{ megapixelsPerSecond: number, megabitsPerSecond: number }} source
+ * @returns {number} Seconds of work per second of content.
+ */
+export function decodeCostOf(model, source) {
+  return (
+    model.pixelTerm * source.megapixelsPerSecond +
+    model.bitrateTerm * source.megabitsPerSecond +
+    model.constantTerm
+  );
+}