Add glossary, case scenarios, and GUI-based transcoding tools

[gnd8596]

Checklist

• I've referred to the Guidelines for contributing

This pull request adds a structured glossary of core FFmpeg and digital preservation terms, embeds glossary links throughout ffmprovisr, and introduces several real-world case scenarios illustrating common FFmpeg uses.

Changes include:

• A new glossary with definitions, context, and references
• Embedded glossary links across existing recipes
• Case scenarios broken into context, solution, and outcome
• Documentation for GUI-based tools (Shutter Encoder, XLD, and HandBrake) to support users with limited command-line experience

This work was informed by interviews with moving image preservation professionals and aims to lower barriers to entry for students and small institutions.

[kfrn]

Hello! This looks really good, but is there any chance that you could tidy it up into discrete commits for easier reviewing? e.g. one commit per new recipe/entry/change

Edit: recommend something like this:

# Make sure you have the latest gh-pages branch (prob the case already, just being thorough here)
git fetch --all

# Remove your commits but keep your changes in your working directory
git reset --mixed amiaopensource:gh-pages

# Use the patch commit to add each recipe/change in a separate commit
git add . --patch   # NB: this can be abbreviated to git add . -p
gcmsg "Add glossary of technical terms"
# and so on...

[kieranjol]

+1! This is great but it would make it easier to review and merge if it was broken up a bit.

…

On Mon 22 Dec 2025 at 02:31, Katherine Frances Nagels < ***@***.***> wrote: *kfrn* left a comment (amiaopensource/ffmprovisr#486) <#486 (comment)> Hello! This looks really good, but is there any chance that you could tidy it up into discrete commits for easier reviewing? e.g. one commit per new recipe/entry/change — Reply to this email directly, view it on GitHub <#486 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAITFPVHAPQNO6RQH5SZWDL4C5JWNAVCNFSM6AAAAACPOPVQJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMOBQGA4TSNRSHE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[jmf-nyu]

Thanks for your feedback @kieranjol and @kfrn.

I wanted to reach out as the professor of the two students submitting this pull request as part of a class assignment. I completely understand that thematic commits are regarded as best practice. However, I'm wondering if you can extend some grace even though the code will be a bit harder to review. The students were using Github for the first time and this is their first ever pull request.

I believe you can review the version of FFmprovisr with their changes here if that's helpful: https://gnd8596.github.io/GD_CH_ffmprovisr/

[kieranjol]

Hi Jonathan, I understand your point. It is a bit overwhelming to go through all the changes (I tried there but realised it would take a more focussed session) but I hope to find some time to go through them. Perhaps we could tackle it by breaking down some of the high level changes. For example, before going into a deeper review, I’m not sure if expanding the scope of this project to include GUI tools is the right thing to do? I’d be leaning towards removing those sections and perhaps diverting the great info to a project such as COPTR? Best, Kieran

…

On Mon 6 Apr 2026 at 00:03, Jonathan Farbowitz ***@***.***> wrote: *jmf-nyu* left a comment (amiaopensource/ffmprovisr#486) <#486 (comment)> Thanks for your feedback @kieranjol <https://github.com/kieranjol> and @kfrn <https://github.com/kfrn>. I wanted to reach out as the professor of the two students submitting this pull request as part of a class assignment. I completely understand that thematic commits are regarded as best practice. However, I'm wondering if you can extend some grace even though the code will be a bit harder to review. The students were using Github for the first time and this is their first ever pull request. I believe you can review the version of FFmprovisr with their changes here if that's helpful: https://gnd8596.github.io/GD_CH_ffmprovisr/ — Reply to this email directly, view it on GitHub <#486 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAITFPWWGDFEDQXNITIKQFD4ULQ23AVCNFSM6AAAAACPOPVQJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCOBZGY3TOMRXGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[retokromer]

For example, before going into a deeper review, I’m not sure if expanding the scope of this project to include GUI tools is the right thing to do?

In my personal opinion, it would be more interesting to discuss how to integrate ffmprovisr-derived recipes into HandBrake, Shutter Encoder and Audacity.

[retokromer]

Started reviewing, but need much more time.

[retokromer]

I would say also in the second sentence All ProRes 422 variants, because this information does not apply to the ProRes 4444 family nor the ProRes RAW family.

[retokromer]

This reference is interesting for historical reasons, but I really would include the official specification IETF RFC 9043.