i think I saw some mentioning of bitstream filtering as early as git history starts ... March 2016

But code was quite different back then ...

https://git.cinelerra-gg.org/git/?p=goodguy/history.git;a=commit;h=50a589b1decdd353a984d8a710e064ebaf8b4f7b

https://git.cinelerra-gg.org/git/?p=goodguy/history.git;a=blob;f=cinelerra-5.1/cinelerra/ffmpeg.C;h=68a131589b9306794143ddba06753bd77bc2e32b;hb=50a589b1decdd353a984d8a710e064ebaf8b4f7b

пн, 13 июн. 2022 г., 21:43 Cinelerra GG Bug Tracker <noreply@cinelerra-gg.org>:
On 2022-06-13 18:43, PhyllisSmith mentioned you on:

https://www.cinelerra-gg.org/bugtracker/view.php?id=614

@Andrew-R
Looks like this will require some serious analyzing.  In checking other render
formats, there are zero that have any parameters like:
       ... | h264_metadata=crop_left=20:crop_right=20
on the first line next to only the 2 parameters like:  mp4 libx264
And this is really interesting because to quote the manual (which I did not even
know was there and do not remember ever having discussed this):

"In typ.ext
encoder parameter files, the first line is defined as:

        muxer codec
(or) muxer codec | bitstream filter [ bitstream filter options ]

where the | represents piping the codec data through the bitstream filter."

If I can find the original email where this came from, perhaps it will become
clearer.