scale filters in_range and out_range have no effect

[Videogamer555]

Summary of the bug:
When I noticed that the output of the padding filter (-vf pad=x=37:y=20:width=254:height=263:color=black) was generating black who's padding "black" values were anything but black (they had a pixel value of 16, not 0), I realized that it was thinking I wanted an output range of 16 to 235, but that wasn't what I wanted. So I decided to override it with a scaling filter. The new filter command I was now using was (-vf scale=in_range=limited:out_range=full,pad=x=37:y=20:width=254:height=263:color=black). Unfortunately the padding STILL had the range of 16 to 235.

How to reproduce:

ffmpeg -i video.mp4 -vf scale=217:243:in_range=limited:out_range=full,setsar=1,pad=x=37:y=20:width=254:height=263:color=black -r 30 -f rawvideo -dn -an -sn -pix_fmt gray8 -y video.data

ffmpeg version N-93298-g0ce759defd

built with gcc 8.2.1 (GCC) 20190212

I've attached the input and output files to this ticket. The input file is video.mp4 and the output is video.data

Note that this is on the Windows version of FFMPEG, not sure if the same bug exists on the Linux version, as a 3rd party is the only one compiling for Windows (that 3rd party is ffmpeg.zeranoe.com). The official build is always for Linux, but I don't have a Linux computer, so that is not an option for me.

[Videogamer555]

Unfortunately I made an error in my above post, regarding the existence of attachments. I didn't realize a file size limit exited, so my statement "I've attached the input and output files to this ticket. The input file is video.mp4 and the output is video.data" is no longer an accurate statement as to the condition of this post. This post DOES NOT have any attachments, so you can IGNORE that statement which claims it DOES have attachments, or (if you are an admin and have post editing-capabilities, please DELETE that statement from my post).Unfortunately I am not able to edit my own post, so I can't remove that statement myself, only add a comment to warn others that that statement is not accurate.

Keep in mind that this doesn't mean the bug doesn't exist. It certainly does. So admins, please DO NOT close this ticket. It's just that the attachments I claimed were posted here, are in fact not posted here.