<p>Converting an existing clean 8k Quicktime Prores 444 file in FFmpeg yields banding.  It's a lenflare with a completely smooth gradient from center out to edge of frame (no alpha).  If I use AE2020 to convert it to Prores 444, the new file is clean without banding.  Am I doing something wrong?  Here is the command string:</p>
<p>ffmpeg.exe -i file_8k.mov -map_metadata -1 -c:v prores_ks -profile:v 4 -pix_fmt yuv444p10le -color_primaries 1 -color_trc 1 -colorspace 1 -color_range 2 -y file_6k.mov</p>
<p>In this case I'm converting it down to 6k, however other resolutions show the same problem, plus even converting to the same res.</p>

CC BY-SA 4.0
2021-01-29T06:53:33.853Z
Sorry didn't include my rescale code: -filter:v "scale=5760:-1" however I'm presuming this has nothing to do with the problem.
brian dm
CC BY-SA 4.0
2021-01-29T11:46:40.903Z
Share full log.
Gyan
CC BY-SA 4.0
2021-01-30T23:09:42.920Z
@Gyan let me know if this qualifies as a log:  https://finalight.com/maindir/webpages/ffmpeg_batch.txt
brian dm
CC BY-SA 4.0
2021-02-03T00:07:40.350Z
Have you tried `-c:v prores` rather than `prores_ks` I know there were some bugs with banding a while ago with prores_ks.
stib
CC BY-SA 4.0
2022-07-22T04:56:54.990Z
Will give that a try.  Sorry, long time reply.
brian dm
<ffmpeg><prores>
ffmpeg prores 4444 banding
brian dm
# ffmpeg prores 4444 banding

(Asked by: username_0 on 2021-01-29)

Converting an existing clean 8k Quicktime Prores 444 file in FFmpeg yields banding. It's a lenflare with a completely smooth gradient from center out to edge of frame (no alpha). If I use AE2020 to convert it to Prores 444, the new file is clean without banding. Am I doing something wrong? Here is the command string:

ffmpeg.exe -i file\_8k.mov -map\_metadata -1 -c:v prores\_ks -profile:v 4 -pix\_fmt yuv444p10le -color\_primaries 1 -color\_trc 1 -colorspace 1 -color\_range 2 -y file\_6k.mov

In this case I'm converting it down to 6k, however other resolutions show the same problem, plus even converting to the same res.

**Tags:** ffmpeg, prores

> **Comments:**
> **username_0**: Sorry didn't include my rescale code: -filter:v "scale=5760:-1" however I'm presuming this has nothing to do with the problem.  
> **username_1**: Share full log.  
> **username_0**: @username_1 let me know if this qualifies as a log:  https://finalight.com/maindir/webpages/ffmpeg_batch.txt  
> **username_2**: Have you tried `-c:v prores` rather than `prores_ks` I know there were some bugs with banding a while ago with prores_ks.  
> **username_0**: Will give that a try.  Sorry, long time reply.  

---

## 0 answers

