New release of the jury replays module.

[Jean-François Lamy]

There is now a release 1.8.0 of the jury replays module (see documentation for what this is about).  

SHORT VERSION: If you install that, you need to adjust your config file -- go see the new default.toml file to copy-paste what you need.

LONG VERSION:  For those of you who like the fireside stories from grandpa:

The main purpose of this release is to solve a mystery with HDMI cameras: I was able to capture smooth replays from HDMI cameras on Raspberry Pi500 simple computers, but some people experienced stuttering on much more capable gaming laptops or Macs, especially when using HDMI. 

The mystery turned out to be related to the capture cards.   By sheer instinct, I had bought what is known as an "active" capture card for my Pi -- these often have a "loop-out" port to connect an HDMI monitor in addition to the USB output.  These cards process the input a fair bit, and the computer has less to do.  Conversely, the more common and less expensive capture card are known as "passive" cards, and they just convert the signal, leaving the hard work to the computer.

The simple fix for this was to increase buffer sizes. But while I was at it, I thought that using the GPU that all recent laptops have would be a good move. 

But when I added the parameters, nothing changed.  After a bit of head scratching and AI assistance, I found out that the ffmpeg video processing program used requires parameters to be in a specific order, something that the program was not doing correctly.

Release 1.8.0 now segregates the parameters for reading the camera (that go first) from those about writing the output (that must come later). 

And for good measure, the GPU configuration parameters are completely different for NVIDIA, AMD and Intel QSV GPUs.So there is now a default.toml file with all these variations.  New users can just pick the one they need, existing users need to copy paste the relevant lines back to their config.