user1950: In the docs for FFV1 there's a parameter -context, which can be set to 'small' or 'large'. That's all the documentation I can find. 

While I'm at it, what are the relative benefits of the different encoders: Golomb Rice vs Range Coder?

user3138: About your other question regarding the -coder option, I was also looking for more info on this.
The current (Dec. 2020) IETF/cellar WG draft "FFV1 Video Coding Format Version 0, 1, and 3" mentions in it's "4.2.3. coder_type" chapter :

Restrictions:
If coder_type is 0, then bits_per_raw_sample SHOULD NOT be > 8.
Background:
At the time of this writing, there is no known implementation of FFV1 bitstream supporting Golomb Rice algorithm with
bits_per_raw_sample greater than 8, and Range Coder is prefered.

So without understanding much about it, I just concluded : "always use -coder 1" ... :-)

user1871: The coder here refers to the process used for entropy coding the error residuals. The context size sets how many neighbouring residuals are considered in this process.
As to the relative benefits, have no particular experience here, but since this is a lossless process, the tradeoff will be between time, size and resource use. This latter question is better suited for https://dsp.stackexchange.com/

1950: <p>In the <a href="https://ffmpeg.org/~michael/ffv1.html" rel="noreferrer">docs</a> for FFV1 there's a parameter <code>-context</code>, which can be set to 'small' or 'large'. That's all the documentation I can find. </p>

<p><a href="https://i.stack.imgur.com/Y1gnj.png" rel="noreferrer"><img src="https://i.stack.imgur.com/Y1gnj.png" alt="enter image description here"></a></p>

<p>While I'm at it, what are the relative benefits of the different encoders: Golomb Rice vs Range Coder?</p>
 3138: <p>About your other question regarding the <code>-coder</code> option, I was also looking for more info on this.</p>
<p>The current (Dec. 2020) IETF/cellar WG draft &quot;<a href="https://datatracker.ietf.org/doc/draft-ietf-cellar-ffv1/" rel="nofollow noreferrer">FFV1 Video Coding Format Version 0, 1, and 3</a>&quot; mentions in it's &quot;<a href="https://www.ietf.org/archive/id/draft-ietf-cellar-ffv1-19.html#name-coder_type" rel="nofollow noreferrer">4.2.3. coder_type</a>&quot; chapter :</p>
<blockquote>
<p>Restrictions:</p>
<p>If coder_type is 0, then bits_per_raw_sample SHOULD NOT be &gt; 8.</p>
<p>Background:</p>
<p>At the time of this writing, there is no known implementation of FFV1 bitstream supporting Golomb Rice algorithm with
bits_per_raw_sample greater than 8, and Range Coder is prefered.</p>
</blockquote>
<p>So without understanding much about it, I just concluded : &quot;always use <code>-coder 1</code>&quot; ... :-)</p>
 1871: <p>The coder here refers to the process used for <a href="https://en.wikipedia.org/wiki/Entropy_encoding" rel="nofollow noreferrer">entropy coding</a> the error residuals. The context size sets how many neighbouring residuals are considered in this process.</p>

<p>As to the relative benefits, have no particular experience here, but since this is a lossless process, the tradeoff will be between time, size and resource use. This latter question is better suited for <a href="https://dsp.stackexchange.com/">https://dsp.stackexchange.com/</a></p>
