Answers.Body: <p>Use the <strong>print_info</strong> flag to see what the scaler is doing, example from an actual conversion:</p>
  
  <pre><code>-filter:v "scale=w=1280:h=-2:flags=print_info+bicubic"
  </code></pre>
  
  <p>Part of the relevant output:</p>
  
  <pre><code>[Parsed_scale_0 @ 000001d8187fef00] w:1280 h:-2 flags:'print_info+bicubic' interl:0
  [swscaler @ 000001d819bc7fc0] bicubic scaler, from yuv420p to yuv420p using MMXEXT
  [swscaler @ 000001d819bc7fc0] 1920x804 -&gt; 1280x536
  Parsed_scale_0 @ 000001d8187fef00] w:1920 h:804 fmt:yuv420p sar:1/1 -&gt; w:1280 h:536 fmt:yuv420p sar:1/1 flags:0x1004
  </code></pre>
  
  <p>Edit:  I also always use "-loglevel verbose", don't know if that changes the level of detail the scaler filter outputs.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-03-09T21:48:15.900Z
Answers.LastActivityDate: 2019-03-09T21:48:15.900Z
Answers.UserDisplayName: Carlos Alloatti
Body: <p><a href="https://ffmpeg.org/ffmpeg-scaler.html" rel="nofollow noreferrer">https://ffmpeg.org/ffmpeg-scaler.html</a></p>
  
  <pre><code>ffmpeg -i in.png -vf scale=3840:2160 -sws_flags lanczos out.png
  
  -vf scale=3840x2160:flags=lanczos
  </code></pre>
  
  <p>I went down the list upscaling a 720p image to 4k using the various ones on the documentation, lanczos is input above. I tried the variation below as well. I noticed 0 difference after tossing them in gimp and zooming in and comparing....exact same. I also noticed it doesn't matter what I type, i could call them something wrong or spell them wrong and the command works the same. They don't seem to be applying at all. Is there any indication in command prompt as to what scaling algorithm is being used so I can confirm ? I didn't see any difference.</p>
  
  <p><a href="https://i.sstatic.net/oE3hJ.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/oE3hJ.jpg" alt="enter image description here"></a></p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-03-07T04:48:30.417Z
Comments.Text: Set `-v 40` to see selected algo.
Comments.UserDisplayName: Gyan
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-03-07T05:03:33.747Z
Comments.Text: w: 3840 h: 2160 flags: 'bicubic' interl:0......it keeps saying bicubic regardless of what I put in the commands. Hash program also telling me they are indeed the exact same images.
Comments.UserDisplayName: kite
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-03-07T07:43:27.647Z
Comments.Text: Bug with `-sws_flags` but `-vf scale=3840x2160:flags=lanczos` works here.
Comments.UserDisplayName: Gyan
Tags: <ffmpeg><scale>
Title: ffmpeg scaler options not working
UserDisplayName: kite
ThreadText: # ffmpeg scaler options not working
  
  (Asked by: username_0 on 2019-03-06)
  
  <https://ffmpeg.org/ffmpeg-scaler.html>
  
  ```
  ffmpeg -i in.png -vf scale=3840:2160 -sws_flags lanczos out.png
  
  -vf scale=3840x2160:flags=lanczos
  
  ```
  
  I went down the list upscaling a 720p image to 4k using the various ones on the documentation, lanczos is input above. I tried the variation below as well. I noticed 0 difference after tossing them in gimp and zooming in and comparing....exact same. I also noticed it doesn't matter what I type, i could call them something wrong or spell them wrong and the command works the same. They don't seem to be applying at all. Is there any indication in command prompt as to what scaling algorithm is being used so I can confirm ? I didn't see any difference.
  
  [![enter image description here](https://i.sstatic.net/oE3hJ.jpg)](https://i.sstatic.net/oE3hJ.jpg)
  
  **Tags:** ffmpeg, scale
  
  > **Comments:**
  > **username_1**: Set `-v 40` to see selected algo.  
  > **username_0**: w: 3840 h: 2160 flags: 'bicubic' interl:0......it keeps saying bicubic regardless of what I put in the commands. Hash program also telling me they are indeed the exact same images.  
  > **username_1**: Bug with `-sws_flags` but `-vf scale=3840x2160:flags=lanczos` works here.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2019-03-09. Score: 1
  
  Use the **print\_info** flag to see what the scaler is doing, example from an actual conversion:
  
  ```
  -filter:v "scale=w=1280:h=-2:flags=print_info+bicubic"
  
  ```
  
  Part of the relevant output:
  
  ```
  [Parsed_scale_0 @ 000001d8187fef00] w:1280 h:-2 flags:'print_info+bicubic' interl:0
  [swscaler @ 000001d819bc7fc0] bicubic scaler, from yuv420p to yuv420p using MMXEXT
  [swscaler @ 000001d819bc7fc0] 1920x804 -> 1280x536
  Parsed_scale_0 @ 000001d8187fef00] w:1920 h:804 fmt:yuv420p sar:1/1 -> w:1280 h:536 fmt:yuv420p sar:1/1 flags:0x1004
  
  ```
  
  Edit: I also always use "-loglevel verbose", don't know if that changes the level of detail the scaler filter outputs.
  
  
  ---
  
  