On 1/25/25 09:47, Kenneth wrote:
> I did some research (yet again!) about video encoding and codecs, because it is
> all so complicated to remember. Your video's stats are fairly standard stuff
> AFAIU-- except for the 4:4:4 chroma subsampling.  4:2:0 is the typical scheme
> for h.264; I use that myself. Take a look at Wikipedia's "h.264" page,
> particularly the subsection "Feature support in particular profiles". It appears
> that 4:4:4 is only supported in a particular high-end 'flavor' of h.264; perhaps
> that presents a problem for Firefox, and/or for Windows 10's built-in video
> codecs.
> 
> Or maybe you encoded the videos using 10-bit colors rather than the more
> standard 8-bit?

Hi Kenneth,

Excepting - maybe - the noise video where output grayscale and I 
remember trying the flag '-vf format=gray' to get a smaller mp4 file 
(made no difference), everything should be 8 bits because the png output 
is defaulting to 8 bits per channel.

Thank you for taking the time to investigate the problem you've seen 
with my ffmpeg encoded videos! I'm an amateur having encoded very few 
animations over the years - and I've posted fewer still.

I'd captured recommendations Dick Balaska made years ago for options 
(which included a '-pix_fmt yuv420p' setting), however, when I tried the 
command line late last year I kept getting errors I didn't understand.

Being lazy, I dropped back to a very simple command with a flag for 
frame rate, the input pattern for saved image frames and the output file 
name... Things seemed to work, so I went with ffmpeg's defaulting. :-) 
  
  
  
  
  
  


Next time I create an animation with ffmpeg, I'll try to get the 4:2:0 
chroma sub-sampling.

Bill P.

Post a reply to this message