[FFmpeg-user] Yes or No? About the processing pipeline.

[Mark Filipak]

On 19/06/2025 18.31, Carl Zwanzig wrote:
> On 6/19/2025 11:44 AM, Mark Filipak wrote:
>> On 19/06/2025 12.16, Carl Zwanzig wrote:
>>> On 6/19/2025 3:37 AM, Mark Filipak wrote:
>>>> Take a pill, Z.
>>>
>>> what is that supposed to mean?
> 
> Please answer that.

Did you see the movie "THE MATRIX"? The pill was the blue pill that evoked conformity.

>> Why would I search for 'ffmpeg "sost"', Z? 
> 
> To find out what it could mean,

Z, if I searched for every invented term and unexplained acronym that FFmpeg uses, I'd spend the 
rest of my life searching. It is literary best practice to define acronyms when first used in an 
article. Example: United States Chamber of Commerce (USCC). FFmpeg's documentation doesn't do that. 
So, what does "sost" mean? I did a search. It turned up strings that contained the letters "sost". 
Of course, there was no explanation what that means. Z, your demand is unreasonable.

> of course. Heck, you could search on the entire message! Might turn 
> up something useful.
> 
> 
>> I was faced with an statement that doesn't even say it is an error, embedded in a sea of jargon, 
>> [...]
> 
> Which you do not seem interested in understanding or researching on your own...

Now you're being insulting.

>... Just like you've 
> claimed to write in multiple assemblers and managed software projects but without any apparent 
> effort to learn or understand other languages...

You're being insulting, again.

>... If you can't be bothered to learn some new things, 
> like enough 'c' to read some of the code,...

You're kidding.

>... or can't be bothered to use the various search engines (or 
> even to read the doc),...

I have read FFmpeg documentation, such as it is, for years. Most filter directives (arguments, 
options, whatever you want to call them -- they are not formatted as function calls) don't document 
units, many don't document upper or lower bounds or datatypes. The directives don't identify which 
library they come from. The libraries are not documented at all!

I don't want to complain, but I'm attacked for not knowing things I can't know.

>... why should any else be bothered to answer your ill-formed "questions"?

What is ill-formed about my question?

> On 6/19/2025 12:33 PM, Mark Filipak wrote:
>> If the input is 8-bit ybr420-smpte170m, then the head end of the processing pipeline is also 8-bit 
>> ybr420-smpte170m. Yes or No?
> What do you think? Why does it matter? If the demuxer outputs that, then that's probably how the 
> pipeline will start. Note that libav may invisibly insert scalers as needed to connect filters 
> (that's in the doc).
> 
> ffmpeg may be "quirky", but that's not going to change. Live with it or don't use it.

That's not an acceptable answer and it's not an acceptable attitude.