in video editor, clips get blurred #57397

New Issue

ilia sibiryakov · 2018-10-26T22:57:24+02:00

ilia sibiryakov commented

2018-10-26 22:57:24 +02:00

Look at my last comment for more accurate report!!!

System Information
Ubuntu 18.10, running on intel haswell graphics.

Blender Version
Broken: 2.79 release from Ubuntu Apt. 2.8 build from 4th October had this problem as well.

Short description of error
When a video is passed through blender video editor, the detail is reduced(gets blurred), as if it is averaging 2x2 pixels for each one or something. The resolution in blender is identical to that of the video clip, so it should not do any scaling that could cause that. The resolution of my video is 2880x1080.

Exact steps for others to reproduce the error
Here is a frame after passing through blender:

Here's how it should look:

Open them in browser tabs and do Ctrl+tab between them to see the difference clearly - focus on the cars and road lines to see detail loss, also zoom in if screen resolution is lower than video.

Blend file and shortened video:
demo.blend
M17-0001_short.mov

**Look at my last comment for more accurate report!!!** **System Information** Ubuntu 18.10, running on intel haswell graphics. **Blender Version** Broken: 2.79 release from Ubuntu Apt. 2.8 build from 4th October had this problem as well. **Short description of error** When a video is passed through blender video editor, the detail is reduced(gets blurred), as if it is averaging 2x2 pixels for each one or something. The resolution in blender is identical to that of the video clip, so it should not do any scaling that could cause that. The resolution of my video is 2880x1080. **Exact steps for others to reproduce the error** Here is a frame after passing through blender: ![AfterBlender.png](https://archive.blender.org/developer/F5246546/AfterBlender.png) Here's how it should look: ![beforeBlender.png](https://archive.blender.org/developer/F5246598/beforeBlender.png) Open them in browser tabs and do Ctrl+tab between them to see the difference clearly - focus on the cars and road lines to see detail loss, also zoom in if screen resolution is lower than video. Blend file and shortened video: [demo.blend](https://archive.blender.org/developer/F5246717/demo.blend) [M17-0001_short.mov](https://archive.blender.org/developer/F5246723/M17-0001_short.mov)

ilia sibiryakov commented

2018-10-26 22:57:24 +02:00

Added subscriber: @stevefredpatrick

blender-admin commented

2018-10-26 22:57:24 +02:00

#61569 was marked as duplicate of this issue

Sebastian Parborg commented

2019-02-05 20:06:40 +01:00

Added subscribers: @iss, @ZedDB

Richard Antalik was assigned by Sebastian Parborg

2019-02-05 20:06:40 +01:00

Sebastian Parborg commented

2019-02-05 20:06:40 +01:00

@iss I'm guessing this is because we don't just take the raw input and output it? (There is some conversions going on in the pipeline first)

Richard Antalik commented

2019-02-05 21:39:56 +01:00

@ZedDB That shouldn't be the case.

@stevefredpatrick Can not reproduce (2.8 build) this when exporting image provided to PNG.
Can you send .blend with export settings that would reproduce issue? Maybe short movie with the same codec, if this is movie->PNG issue.
There is some color shift too, which shouldn't be there with settings of .blend file you provided...

Nice lens though...

@ZedDB That shouldn't be the case. @stevefredpatrick Can not reproduce (2.8 build) this when exporting image provided to PNG. Can you send .blend with export settings that would reproduce issue? Maybe short movie with the same codec, if this is movie->PNG issue. There is some color shift too, which shouldn't be there with settings of .blend file you provided... Nice lens though...

Sebastian Parborg commented

2019-02-05 21:45:45 +01:00

@iss I used the provided .blend file and saved the provided video clip in the same folder.
Then I compared the output to the "how it should look" image.
Did you also use the .mov file?

@iss I used the provided .blend file and saved the provided video clip in the same folder. Then I compared the output to the "how it should look" image. Did you also use the .mov file?

Richard Antalik commented

2019-02-05 21:48:45 +01:00

Sorry it tried to embed movie, but I can't display it... I see it now, will test again.

Richard Antalik commented

2019-02-06 03:06:16 +01:00

Added subscriber: @Sergey

Richard Antalik commented

2019-02-06 03:06:16 +01:00

Ok, so I can confirm this. There are 2 issues:

Pixel format conversion glitch:
In this image(top 3 pixels is reference image, bottom 3 "decoded" image), it is clear, that image is stretched by 1 pixel

Issue is in FFMPEG's swscale in anim_movie.c when converting to AV_PIX_FMT_RGBA, as changing flag SWS_FAST_BILINEAR to SWS_BILINEAR or SWS_BICUBIC seems to produce correct result.
swscale with any of those 3 flags was done in about 60ms.

Invalid colorspace:
May be same/similar to #60947 (FFMpeg color offset) but not sure...

I will look at this later this week and see if I will be able to fix this.

Ok, so I can confirm this. There are 2 issues: **Pixel format conversion glitch:** In this image(top 3 pixels is reference image, bottom 3 "decoded" image), it is clear, that image is stretched by 1 pixel ![diff2.png](https://archive.blender.org/developer/F6522271/diff2.png) Issue is in FFMPEG's swscale in `anim_movie.c` when converting to `AV_PIX_FMT_RGBA`, as changing flag `SWS_FAST_BILINEAR` to `SWS_BILINEAR` or `SWS_BICUBIC` seems to produce correct result. swscale with any of those 3 flags was done in about 60ms. **Invalid colorspace:** May be same/similar to #60947 (FFMpeg color offset) but not sure... I will look at this later this week and see if I will be able to fix this.

Sebastian Parborg commented

2019-02-16 11:20:09 +01:00

Added subscriber: @eguerras-2

Eduardo Guerras commented

2019-02-16 15:47:10 +01:00

Please read this, because it it of key importance here:

This blurring does NOT happen when choosing Codec: HuffYUV. The output in HuffYUV codec is lossless, pixel by pixel.
This blurring does NOT happen if the original video has chroma subsampling 4:2:0.
To see this blurring, you need both the following characteristics:
(a) Original footage that was either 4:2:2 or 4:4:4, and
(b) Rendering to lossless H.264 Codec (though I have not tried any codecs other than H.264 and HuffYUV).

Hence, the problem is as follows: when encoding in H.264, a 4:2:0 chroma subsampling is applied, no matter if the user chooses the 'lossless' option. If the HuffYUV codec (lossless) is chosen, the output is 4:4:4 and the full resolution is preserved.

Tested in Blender 2.79b. To reproduce, just import this image and make a few seconds video out of it:
http://www.ozone3d.net/public/jegx/201412/chroma-subsampling-test-4k-tv.png

Try the codec HuffYUV, and compare with H.264 lossless (Codec: H.264, Output quality: Lossless).

Many users do not notice this problem because most domestic cameras, and well as any footage ripped from DVD, Bluray and YouTube, is 4:2:0. You'll notice the subsampling only when you import pictures or get 4:2:2 footage from capturing video with special devices. I am getting around it by encoding to HuffYUV and then transcoding the final video externally.

Please read this, because it it of key importance here: 1. This blurring does NOT happen when choosing Codec: HuffYUV. The output in HuffYUV codec is lossless, pixel by pixel. 2. This blurring does NOT happen if the original video has chroma subsampling 4:2:0. 3. To see this blurring, you need both the following characteristics: (a) Original footage that was either 4:2:2 or 4:4:4, and (b) Rendering to lossless H.264 Codec (though I have not tried any codecs other than H.264 and HuffYUV). Hence, the problem is as follows: when encoding in H.264, a 4:2:0 chroma subsampling is applied, no matter if the user chooses the 'lossless' option. If the HuffYUV codec (lossless) is chosen, the output is 4:4:4 and the full resolution is preserved. Tested in Blender 2.79b. To reproduce, just import this image and make a few seconds video out of it: http://www.ozone3d.net/public/jegx/201412/chroma-subsampling-test-4k-tv.png Try the codec HuffYUV, and compare with H.264 lossless (Codec: H.264, Output quality: Lossless). Many users do not notice this problem because most domestic cameras, and well as any footage ripped from DVD, Bluray and YouTube, is 4:2:0. You'll notice the subsampling only when you import pictures or get 4:2:2 footage from capturing video with special devices. I am getting around it by encoding to HuffYUV and then transcoding the final video externally.

Eduardo Guerras commented

2019-04-07 19:01:06 +02:00

This is confirmed in 2.80, hash 0e78e3038d, Linux 64-bit. Please see the attached .blend files, both rendering a 1 min video of the attached picture chroma.png.
chroma.h264.blend

chroma.huffyuv.blend

I attach the corresponding screen captures where the results can be compared:

This is the result of creating a h.264 allegedly lossless video:

And this is the result of creating a huffyuv lossless video. See the text crisp and clear:

The importance of this bug has been deemed only 'medium', probably because there the workaround of using HuffYUV to later transcode outside Blender, but those HuffYUV files are enormous.

This is confirmed in 2.80, hash 0e78e3038d02, Linux 64-bit. Please see the attached .blend files, both rendering a 1 min video of the attached picture chroma.png. [chroma.h264.blend](https://archive.blender.org/developer/F6917202/chroma.h264.blend) [chroma.huffyuv.blend](https://archive.blender.org/developer/F6917201/chroma.huffyuv.blend) ![chroma.png](https://archive.blender.org/developer/F6917200/chroma.png) I attach the corresponding screen captures where the results can be compared: This is the result of creating a h.264 allegedly lossless video: ![screen.capture.of.h.264.video.png](https://archive.blender.org/developer/F6917205/screen.capture.of.h.264.video.png) And this is the result of creating a huffyuv lossless video. See the text crisp and clear: ![screen.capture.of.huffyuv.video.png](https://archive.blender.org/developer/F6917206/screen.capture.of.huffyuv.video.png) The importance of this bug has been deemed only 'medium', probably because there the workaround of using HuffYUV to later transcode outside Blender, but those HuffYUV files are enormous.

ilia sibiryakov commented

2019-08-21 18:55:22 +02:00

Ok I went back to this. The colour difference in the example is my mistake, I think I originally took a screenshot of GNOME video player (it changes the colours when no one asks it to).

Complete method to replicate the bug:

Set blender resolution to 2880x1080, 100%
Enter video editor mode
Import the video sample I provided in first post
Render a frame, save it as a PNG
Open that clip in VLC and take a snapshot, will save a PNG
Compare

Here is a clearer comparison I made using this method:

To me it looks like actual blurring, not just chroma 4:2:0 conversion. But I may be wrong. At least there is no colour difference, sorry for the original low quality report.

In #57397#614243, @iss wrote:
Ok, so I can confirm this. There are 2 issues:

Pixel format conversion glitch:
In this image(top 3 pixels is reference image, bottom 3 "decoded" image), it is clear, that image is stretched by 1 pixel

Issue is in FFMPEG's swscale in anim_movie.c when converting to AV_PIX_FMT_RGBA, as changing flag SWS_FAST_BILINEAR to SWS_BILINEAR or SWS_BICUBIC seems to produce correct result.
swscale with any of those 3 flags was done in about 60ms.

I think you are completely right about this!

It is a bit odd that resizing is done even when the image does not need to be resized.

Ok I went back to this. The colour difference in the example is my mistake, I think I originally took a screenshot of GNOME video player (it changes the colours when no one asks it to). Complete method to replicate the bug: 1. Set blender resolution to 2880x1080, 100% 2. Enter video editor mode 3. Import the video sample I provided in first post 4. Render a frame, save it as a PNG 5. Open that clip in VLC and take a snapshot, will save a PNG 6. Compare Here is a clearer comparison I made using this method: ![Video_VLC.png](https://archive.blender.org/developer/F7681999/Video_VLC.png) ![Video_Blender.png](https://archive.blender.org/developer/F7682005/Video_Blender.png) To me it looks like actual blurring, not just chroma 4:2:0 conversion. But I may be wrong. At least there is no colour difference, sorry for the original low quality report. > In #57397#614243, @iss wrote: > Ok, so I can confirm this. There are 2 issues: > > **Pixel format conversion glitch:** > In this image(top 3 pixels is reference image, bottom 3 "decoded" image), it is clear, that image is stretched by 1 pixel > ![diff2.png](https://archive.blender.org/developer/F6522271/diff2.png) > > Issue is in FFMPEG's swscale in `anim_movie.c` when converting to `AV_PIX_FMT_RGBA`, as changing flag `SWS_FAST_BILINEAR` to `SWS_BILINEAR` or `SWS_BICUBIC` seems to produce correct result. > swscale with any of those 3 flags was done in about 60ms. > I think you are completely right about this! It is a bit odd that resizing is done even when the image does not need to be resized.

Richard Antalik was unassigned by Dalai Felinto

2019-12-23 16:35:54 +01:00

blender-admin commented

2021-06-02 21:29:38 +02:00

This issue was referenced by 13ab6b7bb6

This issue was referenced by 13ab6b7bb60c3af82c6f99c2177f2fb2576ccd22

blender-admin commented

2021-06-02 21:29:38 +02:00

This issue was referenced by 1f55786791

This issue was referenced by 1f557867916bd6ab43ced4b4fd651a7d1d11f8ac

Richard Antalik commented

2021-06-02 21:44:18 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Richard Antalik closed this issue

2021-06-02 21:44:18 +02:00

Richard Antalik self-assigned this 2021-06-02 21:44:18 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

in video editor, clips get blurred #57397